• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
ESNATECH UC Network Optimization
 

ESNATECH UC Network Optimization

on

  • 1,086 views

Esnatech's UC Network Optimization guideline for proper UC deployment and best practises

Esnatech's UC Network Optimization guideline for proper UC deployment and best practises

Statistics

Views

Total Views
1,086
Views on SlideShare
1,084
Embed Views
2

Actions

Likes
0
Downloads
12
Comments
0

1 Embed 2

http://esnatechuc.blogspot.com 2

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    ESNATECH UC Network Optimization ESNATECH UC Network Optimization Document Transcript

    • Optimizing Network Traffic with Multiple Network Adaptors and Telephony Office-LinX doc v. 7.0.2.0 June 2009
    • Optimizing Network Traffic with Multiple Network Adaptors and Telephony Office-LinX 2 1 Optimizing Network Traffic with Multiple Network Adaptors and Telephony Office-LinX In a typical environment, there are 2 types of traffic that are generally present in a Telephony Office Linx server: 1. Voice traffic. Voice traffic refers to all information exchanged from the communication network that is connected to TOLEE. 2. Data traffic. TOLEE exchanges information with other data servers to perform its tasks as a Unifed Communications server. This data includes: e-mail synchronization; database synchronization in High Availability systems; client access via web, desktop clients and mobile clients; SMTP, IMAP, LDAP and other types of data traffic Servers with multiple network adaptors can optimize their network traffic by creating a division between the voice and data traffic. Voice (and fax) represent real time data exchange and their nature as real time information requires their traffic to be prioritized. This document discusses the methods available to IT departments to optimize the traffic between the two types of data. Environments with multiple sub network addresses In many environments, their voice traffic is on a separate sub network. For example, data traffic resides on 192.168.0.x and voice traffic resides on 192.168.1.x sub network. In this case, the simplest way to direct network traffic is to assign one network adaptor to 192.168.0.x sub network and one network adaptor to 192.168.1.x sub network. In this example, the VoIP PBX or Gateway should be on the same sub network as the voice adaptor on 192.168.1.x. Since TOLEE applications will try to connect via TCP to their destination via the Windows TCP stack, Telephony Office-LinX preference will be automatically given to the network adaptor within the sub network that the application is trying to reach. This will isolate TOLEE applications’ attempts to connect to the VoIP end point to the network adaptor within the same sub network. Visual examples of both single server and high availability implementations of multiple network adaptor configurations are shown below. Telephony Office-LinX Copyright © 2009 Esna Technologies Inc.
    • Optimizing Network Traffic with Multiple Network Adaptors and Telephony Office-LinX 3 1 Telephony Office-LinX Binding SIP voice traffic to a particular network adaptor TOLEE allows you to bind a specific adaptor to the SIP application layer. This can be done by: 1. Open the ETSIPSERVICE.INI file. 2. Find the line that states Internal IP =. 3. The default value is DETECT. Change this to the physical address of the network adaptor to be bound, e.g. 192.168.1.100. 4. Save the file. 5. Open Service Control Manager. 6. Locate and STOP the UC SIP Service. Note: Any active calls will be disconnected when you stop the services. 7. The service will automatically restart. The SIP endpoints (PBX, Media Gateway, etc.) should be configured on the voice subnetwork IP range only to avoid any cross routing between networks and thus defeating the purpose of separate adaptors. Telephony Office-LinX Copyright © 2009 Esna Technologies Inc.
    • Optimizing Network Traffic with Multiple Network Adaptors and Telephony Office-LinX 4 1 Ensuring application data separation To ensure the use of a separate adapter, the application servers and clients must be configured to use the corresponding sub network intended for data use. Relevant configuration parameters are listed below: E-mail (IMAP) Synchronization Ensure that the IMAP server intended for configuration resides on the same data network as the intended data NIC (our example uses the 192.168.0.x sub network). Figure 1 below illustrates an example configuration of a data network configured IMAP server. If your IMAP server resides on another network or the internet, ensure the default gateway for the UC server resides on the data network and is configured for the data NIC only (voice NIC default gateway configuration should be left blank). Telephony Office-LinX Figure 1 - Example IMAP configuration Database Synchronization (High Availability systems only) Ensure that the Consolidated database server in the high availability configuration resides on the same data network as the intended data NIC (our example uses the 192.168.0.x sub network). Figure 2 below illustrates an example configuration of a data network configured Consolidated database server. Since the Consolidated server does not handle voice traffic, it only requires one NIC connected to the data network. Figure 2 - Consolidated server IP setting Telephony Office-LinX Copyright © 2009 Esna Technologies Inc.
    • Optimizing Network Traffic with Multiple Network Adaptors and Telephony Office-LinX 5 1 Web Client Access Verify that the IIS Website IP Address setting is configured to the data sub network as depicted in Figure 3 on the web site properties dialog, and that all DNS entries and client access attempts are directed to this IP. Figure 3 - IIS site properties dialog Desktop Clients (UC Client Manager) Telephony Office-LinX Ensure that all clients are configured to connect to the UC server via the data network address (our example uses the 192.168.0.x sub network). If connecting externally, ensure all relevant NAT, DNS or Routing entries direct requests to the data network IP. Figure 4 - UC Client manager login screens (2.0 left, 2.5 right) Mobile Clients Similar to the desktop clients, all UC Mobile clients should be directed to the data network IP. If connecting externally, ensure all relevant NAT, DNS or Routing entries direct requests to the data network IP. Telephony Office-LinX Copyright © 2009 Esna Technologies Inc.
    • Optimizing Network Traffic with Multiple Network Adaptors and Telephony Office-LinX 6 1 SMTP, IMAP, LDAP and others The following fields should be entered to only use the data sub network as well: VPIM/SMTP: IMAP Server: Telephony Office-LinX LDAP Synchronization Host Name: Telephony Office-LinX Copyright © 2009 Esna Technologies Inc.
    • Optimizing Network Traffic with Multiple Network Adaptors and Telephony Office-LinX 7 1 Company Domain Name/IP Address: This ensures that all relevant UC Communication and non-voice protocols are transmitted via the data network rather than voice. Telephony Office-LinX Reference Documents Note: Microsoft does not recommend assigning multiple network adaptors to the same physical network and subnet. Please refer to the link below. http://support.microsoft.com/?id=175767 Note: To read about Network adaptor teaming and server clustering refer to the link below. http://support.microsoft.com/?id=254101 Note: To read about configuring your server for network load balancing, please refer to the link below. http://support.microsoft.com/kb/323431/en-us Telephony Office-LinX Copyright © 2009 Esna Technologies Inc.