Out of Band management port
This port can be configured to allow out of band management sessions with the 5300-E series. It is typically connected to a private management network.

Console port

This port is used to establish a local console session with the 5300-E using a VT100 terminal or emulation program. The baud rate is 9600. It is used for debug or local diagnostic purposes only. Primary configuration of the 5300-E is performed from a web browser as covered in Chapter 3: Configuring the 5300-E.

Getting Started

Physical Installation
The 5300-E is designed for 19 rack mount installation. Please observe the following guidelines when installing the system: Never assume that the AC cord is disconnected from a power source. Always check first. Never place objects greater than 5 lbs on top of the 5300-E as damage to the chassis may result. Always connect the AC power cord to a properly grounded AC outlet to avoid damage to the system or injury. Ensure that the physical location of the installation has adequate air circulation and meets the minimum operating conditions as provided in the environmental specifications for the system.

Connecting to the 5300-E

The 5300-E is configured using a web browser such as Internet Explorer or Netscape Navigator. The 5300-E is shipped with a pre-configured IP address for its LAN port of 192.168.1.1. To connect to the 5300-E, do the following: 1. Connect a PC using an IP address of 192.168.1.2 and subnet mask of 255.255.255.0 to the 5300-E LAN port or the LAN switch associated with the 5300-E LAN port.
2. Launch a web browser on the PC and enter the URL string: 192.168.1.1. Press Return. The initial 5300-E main configuration menu appears.
3. Select the Network link - enter the username root and the password default to log into the system. 4. Continue to configure the system using the information provided in Chapter 3: Configuring the 5300-E.

Configuring the 5300-E

The 5300-E is a flexible, easy to use converged network appliance that provides many critical networking functions for IP based voice and data. It can be installed in several different topologies: At the customer premise for IP Centrex applications At the station side of enterprise IP PBXs At the trunk side of enterprise IP PBXs
Most users will follow the steps provided in the System Configuration section of this manual to initially connect the 5300-E into their IP network. The remainder of the configuration can be different based on the application, VoIP topology and presence of other networking equipment such as firewalls or DHCP servers. In general, however, the steps used to configure the 5300-E are:

Call quality monitoring and test tools.
VoIP Operations Center Softswitch Application Server NMS

Gateway

Enterprise T1/FT1 5300-E WAN Router T1/FT1
Enterprise 5300-E WAN Router

EM012A

Configuration Outline
Task System Configuration Subtask configure LAN/WAN interface set Ethernet link rate enable the DHCP server configure SNMP VoIP Configuration enable the VoIP ALG configure a VoIP subnet route Data Networking Configuration dynamic NAT static NAT static IP routing Configure For IP Centrex Application? Yes Optional Optional but recommended Optional Yes Optional Optional but recommended Optional Optional

Firewall Configuration

enable the data firewall configure basic settings configure advanced settings
Yes Optional Optional Yes Yes
Traffic Management Configuration
enable traffic shaping enable Call Admission Control
Configuration Guide For Station Side IP PBX Applications
Most private enterprise VoIP networks use an IP PBX at the corporate headquarters location to provide voice switching between headquarters, branch offices and the PSTN. The 5300-E is used in these environments to securely connect branch office employees to the IP PBX installed in the corporate headquarters location.

Headquarters IP PBX

5300-E

WAN Router T1 PSTN

Branch Office T1/FT1 5300-E WAN Router WAN Router T1/FT1

Branch Office 5300-E

EM013A
The installation of an 5300-E on the station side of an enterprise IP PBX is very similar to the IP Centrex application above. The branch office is connected to the corporate network using VPNs or private T1 links terminated by a WAN router. The 5300-E is then connected directly to the WAN router and the LAN port of the 5300-E is connected to the enterprise ethernet local area network (typically a layer 2 switch). The IP PBX in the corporate headquarters location performs VoIP signaling and the 5300-E acts as a proxy for the voice devices installed at the branch office. The 5300-E can perform the following functions in this application: WAN/LAN IP routing. Traffic shaping and priority queuing to guarantee high quality voice traffic. These mechanisms protect voice and data traffic from contending for the same network resources to guarantee low latency and the highest call quality possible for VoIP traffic. At the same time they ensure the best utilization of WAN bandwidth by enabling data traffic to burst up to full line rate in the absence of voice calls. Precedence is given to traffic for the range of addresses reserved for the IP phones. NAT/PAT translation for IP phones and PCs. This allows a single IP address to be used on the WAN link to represent all of the private IP addresses assigned to the LAN IP phones and PCs. A VoIP aware firewall. A full layer 7 gateway for voice traffic and a stateful packet inspection firewall for data traffic. Call Admission Control (CAC). CAC uses a deterministic algorithm to decide when there are insufficient network resources available to adequately support new calls and then return the equivalent of a fast busy to new call requests. DHCP server and TFTP relay. These features are used to simplify and expedite the IP configuration of phones and PCs. This also includes VoIP signaling gateway information (MGCP, SIP, and H.323). Call quality monitoring and test tools.

Configure For Station Side IP PBX Application? Yes Optional Optional but recommended Optional
Task System Configuration
Subtask configure LAN/WAN interface set Ethernet link rate enable the DHCP server configure SNMP

VoIP Configuration

enable the VoIP ALG configure a VoIP subnet route
Yes Optional Optional but recommended Optional Optional Yes Optional Optional Yes Optional
Data Networking Configuration
dynamic NAT static NAT static IP routing
Configuration Guide For Trunk Side IP PBX Applications
Companies using shared WAN links for inter-office IP voice communications can use the 5300-E as a traffic shaper to meet the stringent jitter, latency and packet loss requirements for toll quality voice. The 5300-E is deployed in the network between WAN and LAN connections in headquarters and branch office locations. One appliance is required for each end of a WAN link and they are installed logically between IP PBX trunk interfaces.

Branch Office

Headquarters IP PBX 5300-E T1/E1 Frame Relay Or IP Network T1/E1 WAN Router

5300-E IP PBX WAN Router

WAN Router

IP PBX

EM014A
The 5300-E performs WAN/LAN IP routing and traffic management functions in this application.
Task System Configuration Subtask configure LAN/WAN interface set Ethernet link rate enable the DHCP server configure SNMP VoIP Configuration enable the VoIP ALG configure a VoIP subnet route Data Networking Configuration dynamic NAT static NAT static IP routing Firewall Configuration enable the data firewall configure basic settings configure advanced settings Traffic Management Configuration enable traffic shaping enable Call Admission Control Configure For Trunk Side IP PBX Application? Yes Optional Not required Optional Not required Not required Not required Not required Not required Not required Not required Not required Yes Not required
Configuration Guide For Hosted Video Applications
A typical 5300-E installation for hosted video applications is depicted in the diagram below. In this scenario, the 5300-Es are used to connect all of the video endpoints to the Gatekeeper. The video endpoints should be configured to point to the LAN address of the 5300-E as the Gatekeeper and the 5300-E will proxy RAS and call setup messages to the Gatekeeper

3 - 12

to be manually configured. Please contact your service provider for the PPPoE username and password as this will be required for link authentication
The 5300-E uses PAP authentication and you should inform your provider that this is required to ensure compatibility.
Press Submit. Enter the User Name and Password. Press Submit. The service provider will automatically assign your WAN IP address.
4. Select DHCP if you want to receive your WAN IP address from a DHCP server located in the WAN. 5. Press Submit.
Configure the LAN Interface
1. Select the Network link. 2. Enter the IP Address. 3. Enter the Subnet Mask (e.g. 255.255.255.0). 4. Press Submit. Warning
After pressing submit the 5300-E will become unreachable until you use a PC with an address on the same subnet as entered in steps B and C above.
Set Ethernet Link Rate Warning
The vast majority of Ethernet networking devices including the 5300-E use autonegotiate as a default setting. Chances are that you will not have to set the ethernet link rate as described below. Please use caution if manually configuring the link rate as a speed or duplex mismatch will result in a loss of connectivity
If needed configure the rate of the physical ethernet port on the 5300-E. The default setting for the Ethernet port is to autonegotiate both the link speed and duplex with locally attached devices. 1. Select System. 2. Select System Overview. 3. Select Set Link Rate. 4. Select LAN and/or WAN.

3 - 13

5. Select the appropriate link rate for your Ethernet network:
10baseT-HD = 10Mbits per second using half duplex transmission 10baseT-FD = 10Mbits per second using full duplex transmission 100baseT-HD = 100Mbits per second using half duplex transmission 100baseT FD = 100Mbits per second using full duplex transmission Autonegotiate = The 5300-E will autonegotiate link rate and duplex with the directly attached device. 6. Press Submit. Set WAN MTU size The WAN MTU size may be set to reduce the latency that is introduced when large data packets are sent over a slow link. The default setting is 1500 bytes for static IP addresses. PPPoE links negotiate the value automatically although the value can be overridden using this field. If the WAN Upstream Bandwidth is less than 256 Kbit/s, the MTU size is automatically reduced to 800 bytes. Warning
When manually configuring the MTU size we recommend that you use a setting of 800 bytes or greater. You may experience problems with certain types of VoIP traffic if the MTU size is set below 800 bytes.
1. Select System. 2. Select System Overview. 3. Enter the WAN MTU size 4. Press Submit.

Delete a DHCP IP Address

1. Select DHCP Server. 2. To delete an IP address or a range of IP addresses highlight the entry in the DHCP IP Addresses list and press the Delete key on your keyboard.

3 - 16

3. Press Submit.

Disable the DHCP Server

1. Select DHCP Server. 2. Uncheck the Enable DHCP Server checkbox. 3. Press Submit.

Configure SNMP

The 5300-E can be managed remotely by an SNMP network management system such as HP Openview. The 5300-E supports SNMPv1 and MIB-II (RFC1213). All MIB-II variables are read only. The MIB variables sysContact and sysLocation are set by the web GUI.
1. Select System. 2. Select System Overview. 3. Select Services Configuration. 4. Select the Enable SNMP checkbox. 5. Enter the Read-Only Community. This is the community string that the management station uses when accessing read-only objects from the 5300-E. The default is 'public'. 6. Enter the System Location. This is a comment string that can be used to indicate the location of the 5300-E. By default, no value is set.

3 - 17

7. Enter the System Contact. This is the administrative contact information for the 5300-E. By default, no value is set. 8. Enter the SNMP Port. This is the port that the 5300-E uses for SNMP communications with the network management system. The default is 161. 9. Press Submit.

Disable SNMP

1. Select System. 2. Select System Overview. 3. Select Services Configuration. 4. Uncheck the Enable SNMP checkbox. 5. Press Submit.
Enable Remote System Logging The 5300-E can be configured to log system messages to an external syslog server. 1. Select System. 2. Select System Overview. 3. Select Services Configuration. 4. Select the Enable Remote System Logging checkbox. 5. Enter the IP address of the Remote Syslog Host. 6. Press Submit.
Disable Remote System Logging
1. Select System. 2. Select System Overview. 3. Select Services Configuration. 4. Uncheck the Enable Remote System Logging checkbox. 5. Press Submit.

3 - 18

Change the Administration Password
We strongly recommend that you change the default password for the root administrative account using the following steps:
1. Select System. 2. Select changed in the Change Password section of the GUI. 3. Enter the New Password. Note
The new password must be between 6 and 20 characters in length. Any combination of alpha and numeric characters is accepted.
4. Enter the password you chose in step C again in the Confirm Password to ensure that there were no mistakes in the initial entry. 5. Press Submit.

Read-only User

Viewing or Changing the ToS Byte Setting
To view or change the ToS byte setting, use the following steps:

3 - 22

1. Using the configuration graphical user interface, from the Configuration Menu on the left-hand side, click Traffic Shaper. 2. Scroll down the area of the screen shown below.
3. For most situations, you should leave this setting as it is. Only change it if your provider indicates that you should do so. If your provider indicates that you need to change the ToS byte setting, that provider should also provide the other parameters required on this screen. 4. If you have changed the values, click Submit to activate the new settings.

3 - 23

H.323 Configuration
To access the H.323 Settings page, select VoIP ALG > H.323 in the Configuration Menu.

3 - 24

The H.323 Settings page has the following areas: Gatekeeper Mode WAN/Provider-side gatekeeper mode settings LAN/Subscriber-side gatekeeper mode settings Embedded gatekeeper mode settings LRQ Size Default Alias Stale Time Multicast Messages

3 - 25

H.460.18 Support Alias Restrictions
In the Gatekeeper mode area, select one of the following modes:
Item None WAN/Provider-side gatekeeper mode Description H.323 is disabled. Specifies that the system will forward all client RAS messages to the gatekeeper. If this is selected, you must configure the settings in the WAN/Provider-side gatekeeper mode settings area. Specifies that the system will act as a gatekeeper. If this option is selected, you must configure the settings in the LAN/Subscriber-side gatekeeper mode settings area. Allows calls to be forwarded to other endpoints based on the information sent from the endpoints. All the information about routing the call must be sent as part of the request or prefixes must be configured. Provides gatekeeper functions and accepts endpoint registrations. If this option is selected, you must configure the settings in the Embedded gatekeeper mode settings area. This mode supports a maximum of 50 registered endpoints for the E10 V2IU and 100 registered endpoints for the E25 V2IU.
LAN/Subscriber-side gatekeeper mode Peering-Proxy mode

Item Listen to multicast messages Description Select this checkbox to enable listening to multicast messages.
In the H.460.18 Support area, you can configure H.460.18 support. This allows the system to do NAT/Firewall traversal for clients behind NAT or firewall devices. This area includes the following configurable parameters:
Item Disabled Enabled Keep-alive time(s) Description Disables H.460.18 support. Enables H.460.18 support. Specifies the keep-alive time if H.460.18 support is enabled.
In the Alias Restrictions area, you can set a limit on the number of aliases that are allowed to register with the system. If this number is exceeded when a client tries to register, the registration is rejected. This area includes the following parameter:
Item Max Aliases Description Enter the maximum number of allowed aliases. If the value is set to 0, the maximum is not enforced.
The H.323 Settings page includes the following two buttons:
Item Submit Reset Description Applies the settings configured on this page. Clears all fields and selections and allows you to enter new information.

3 - 28

H.323 Activity
To access the H.323 Activity page, select VoIP ALG > H.323 Activity in the Configuration Menu.
The H.323 Activity page is a read-only page that shows the following information: Current time WAN Gatekeeper status Current payload bandwidth Estimated total bandwidth Activity log of recent H.323 events

H.323 Alias Manipulation

Alias manipulation is performed immediately when a message (such as an ARQ, LRQ or a Setup) is received. Any matching pattern is replaced with the specified string, allowing you to replace characters or strings that are hard or impossible to dial on certain endpoints. Normal call look-up is performed following alias manipulation.

3 - 29

To access the H.323 Alias Manipulation page, select VoIP ALG > H.323 >Alias Manipulation in the Configuration Menu.
This page includes the following areas:

Outbound from Site C to Site A
Site C dials an endpoint located at Site A: 94155551000@66.20.20.4. The PathNavigator receives the call and generates a Q.931setup to the V2IU for that subnet. The V2IU processes the Q.931 setup from the calling endpoint. The V2IU looks for a prefix match. In this case, the 9 creates a match. The Strip Matching Prefix rule is applied, the 9 is stripped, and the call is routed to

3 - 39

the Peering Proxy IP 10.10.10.1. The Peering Proxy applies the same rule set, in this case, NO matching prefix is found and ANNEX O dialing is applied. The call is now routed to Site A's V2IU. The call is forwarded to the LAN Side PathNavigator where the registered client with the E.164 of 4155551000 is located and the call is gatekeeper routed to the called endpoint.
Inbound from Site A to Site C
Site A dials: 8315551000@67.40.40.4. (The destination IP is the Peering Proxy WAN IP address.) The Peering Proxy is configured with prefix 8315and is mapped to the WAN IP of the V2IU 10.10.11.1. As explained earlier, the prefix could be 831* or 83. and so on, depending upon dial plan requirements. The PathNavigator receives the Q.931setup from the endpoint and forwards the call to the V2IU for that subnet. The V2IU receives the Q.931 setup from the calling endpoint. The V2IU looks for a prefix match, finds NO matching prefix, and ANNEX O dialing is applied. The call is now routed to the Peering Proxy IP 67.40.40.4. The Peering Proxy receives the Q.931 setup and looks for a prefix match, in this case 8315 creates a match. The Peering Proxy now changes the destination IP to 10.10.11.1 and routes the call to Site C's V2IU. The Q.931 setup is forwarded to the LAN Side PathNavigator where the registered client with the E.164 of 8315551000 is located, and the call is gatekeeper routed to the called endpoint.
Outbound from Site C to Site D
Site C dials an endpoint located at Site D: 95125551000@68.30.30.4. The PathNavigator receives the call and generates a Q.931 setup to the V2IU for that subnet. The V2IU processes the Q.931 setup from the calling endpoint. The V2IU looks for a prefix match, in this case the 9 creates a match. The Strip Matching Prefix rule is applied, the 9 is striped, and the call is routed to the Peering Proxy IP 10.10.10.1. The Peering Proxy applies the same rule set, in this case NO matching prefix is found, and ANNEX O dialing is applied. The call is now routed to the Peering Proxy for Private Video Network B IP 68.30.30.4. The Peering Proxy receives the Q.931 and looks for a prefix match. In this case, 5125 creates a match. The Peering Proxy now changes the destination IP to 172.16.2.1 and routes the call to Site D's V2IU. The V2IU is configured for Embedded Gatekeeper Mode. In this mode, the endpoint is directly registered and an E.164 registered client match is made. The call is then routed to the called endpoint.

Call Status

The call status shows the last state of the call at the time of the event. Each call progresses through a number of states when being established. If a call fails, the call-status in the call termination event can help trouble-shoot the cause of the call failure. For example, if the call fails at the Caller/Callee admission request received state, there may be a problem communicating with the gatekeeper, whereas if the call fails at the Attempting to establish outgoing Q.931 TCP connection state, the remote endpoint may not be reachable. The following are call status messages: Caller admission request received Received an admission request from the source endpoint and forwarded it to the gatekeeper. Caller admission response received Received an admission response (either confirm or reject) from the gatekeeper and forwarded it to the source endpoint. Incoming Q.931 TCP connection established Received an incoming Q.931 TCP connection from the source.

3 - 46

Attempting to establish outgoing Q.931 TCP connection Successfully resolved the destination of the call and attempting to establish an outgoing Q.931 TCP connection to the destination. Q.931 signaling received and forwarded Both Q.931 TCP connections have been successfully established and Q.931 signaling has been received and forwarded. Callee admission request received Received an admission request from the destination endpoint and forwarded it to the gatekeeper. Callee admission response received Received an admission response (either confirm or reject) from the gatekeeper and forwarded it to the destination endpoint. Incoming H.245 TCP connection established Received an incoming H.245 TCP connection from the source. Attempting to establish outgoing H.245 TCP connection Attempting to establish an outgoing H.245 TCP connection to the destination. H.245 signaling received and forwarded Both H.245 TCP connections have been successfully established and H.245 signaling has been received and forwarded. At this point, the call is considered established, even though no media channels have been opened up yet. Outgoing media channel established An outgoing media channel (from the LAN/subscriber side to the WAN/provider side) has been opened. Incoming media channel established An incoming media channel (from the WAN/provider side to the LAN/subscriber side) has been opened. Bidirectional media channels established Media channels have been opened in both directions. This is a normal call where media is being sent in both directions.

The 5300-E provides static IP routing and two types of Network Address Translation (NAT) functions for data traffic. This chapter explains the use and configuration of these features.

NAT for Data Traffic

NAT allows hosts on a private internal network (the LAN side of the 5300-E) to anonymously communicate with devices on an external network (the WAN side of the 5300-E). The 5300-E with NAT enabled will re-write outbound packet headers using public IP addresses in place of private IP addresses so that the private IP addresses are not exposed to the external network. Additionally, the ports used by the IP addresses are also changed as they traverse the 5300-E. This is known as Port Address Translation(PAT) and provides an additional security measure. The 5300-E maintains a table of these mappings so that return packets can be forwarded to the correct host on the private network.
The 5300-E provides two types of NAT functions: dynamic NAT and static NAT. Dynamic NAT allows many private IP addresses to be mapped to a single public IP address (using different port numbers of the public IP address). Static NAT maps private IP addresses and port numbers to public IP addresses and port numbers on a one-to-one basis. Note
The 5300-E ALG automatically handles NAT for voice devices as described in Chapter 3 VoIP Configuration.

3 - 56

Configure Dynamic NAT Use Dynamic NAT when you have multiple PCs installed on the LAN side of the 5300-E that require Internet or WAN access. Once Dynamic NAT is enabled the 5300-E will automatically perform an address translation for all packets to/from the LAN side PCs. 1. Select NAT. The default value for dynamic NAT is enabled. 2. Use the Enable Lan NAT checkbox to enable or disable dynamic NAT. 3. Press Submit. Configure Static NAT Use Static NAT when a server or PC located in the private network needs to be accessible from the external network. Some examples include a corporate web server, a mail server or an FTP server. In these instances, the 5300-E statically maps the public IP address of each server to the actual private IP address of the server. In order for Static NAT to function dynamic NAT must be enabled. 1. Select NAT. 2. Enter the public and private IP addresses and ports to be mapped in Static NAT Client Entries using the following format: Protocol;PublicIPAddress/netmask-port>PrivateIPAddress-port For example the entry tcp;198.66.203.19-80>192.168.1.3-8080 will map all web traffic destined to public IP address 198.66.203.19 to the private webserver 192.168.1.3 port 8080. The public IP address of 198.66.203.19 is automatically created as a subinterface or secondary address on the WAN interface of the 5300-E so that external hosts can reach the web server. Each entry should be placed on a new line. 3. Press Submit. Delete a Static NAT entry

1. Select NAT.

3 - 57
2. To delete an IP address or a range of IP addresses highlight the entry in the Static NAT Client Entries list and press the Delete key on your keyboard. 3. Press Submit.

Interface Information

The specific status and configuration information for the system interfaces is displayed in the Interface Information section. HDLC0 shows the interface statistics for the T1/E1 WAN link. ETH0 shows the interface statistics for the internal LAN interface between the 5300-E processor and the built-in LAN switch. Interface statistics for the external LAN ports are not displayed. The interface statistics can point to areas of congestion in the network. If the errors statistic is a few percent or more of the total packets sent it may be an indication of excessive congestion on the network interface. If the congestion is not corrected the quality of voice calls will be affected. The topology of the network attached to the network interface with the errors should be examined and modified to better segment and isolate network traffic.
Viewing Advanced System Information
To view advanced system information for the 5300-E proceed to the System Information page as follows: 1. Select System. 2. Select System Overview. 3. Select System Information. The following system information is displayed:

System Uptime

System Uptime displays the current time, the amount of time elapsed since the last system reboot, and the system load averages for the past 1, 5, and 15 minutes. Uptime can help trace when a power outage may have interrupted service. Load averages that remain greater than 2 indicate excessive system loading. Partitioning voice traffic using a second system may be required.

Process Information

Displays the active processes in the 5300-E.

Memory Usage

Displays detailed memory allocation information that may be of use to technical support.

System Logging Messages

Displays information logged during system boot and normal operation. Logging messages may indicate unauthorized attempts to access the 5300-E, process restart messages, and excessive resource utilization messages.
Passive Voice Call Monitoring
The 5300-E monitors live voice calls and performs objective speech quality assessment. This information enables the network operator to assess voice quality for the purposes of SLA tracking or problem isolation. Mean Opinion Score (MOS) results for RTP streams in both directions of a VoIP call are calculated at call completion. This information along with the IP addresses of the VoIP endpoints supporting the call are logged locally and optionally sent to an external syslog server (see Enable Remote System Logging for instructions on enabling logging to a remote syslog server). Additionally the 5300-E will generate a real-time message for any MOS values calculated less than 2.5 (considered poor quality) during an active call. Voice call quality information is found locally in the System Logging Messages section of the System Information page and a sample output is provided below.

Rebooting the system will interrupt services for a few minutes. All voice and data sessions currently in progress will be interrupted.

4 - 10

Saving and Restoring the 5300-E Configuration
The 5300-E stores all configuration information for the system in a series of individual files that reside in local flash memory. These files are read at boot time to determine the configuration identity of the 5300-E and then stored in RAM as running state. As you configure the 5300-E the submit command writes the configuration changes to both RAM and flash so that the files stored in flash are always up to date with the running state of the system. The 5300-E provides a utility that enables you to copy the individual configuration files stored in flash to a single, consolidated backup file. This single file can then be used as a backup for the entire system and restored at a later date if necessary. Multiple backup files with different system configurations can also be created and stored locally in the 5300-E or on remote TFTP servers. Note
No more than 2 backup files can be stored in the 5300-E flash due to size constraints. Also, it is recommended that you create a backup file after any configuration changes are made to the 5300-E. This is to prevent the loss of any configuration changes made since your last backup in the event that you must restore the system configuration.
Backup file operations are performed in the 5300-E CLI using the ewn command.

The ewn Command

The syntax for the ewn command is as follows: USAGE:
ewn help|list ewn save|load|delete [file name] ewn upload|download [file name] [ip address]
where file name must use extension.conf1 or.conf2
The ewn command can be used with a local terminal connection or remotely using SSH. 1. Use a NULL modem cable to connect to serial port 1 of the 5300-E 2. Use a terminal emulator such as Hyperterminal set to a baud rate of 115200, 8, 1 and none (databits, stop bits and parity) Alternatively you can connect to the 5300-E remotely using SSH: 1. Logon as root 2. Enter the password Once you are at the command prompt (bash#) you can create the backup file, store it to local flash, copy it to a remote TFTP server, copy it from a remote TFTP server, delete it, load it or list all available backup files.
Create a Backup File and Save in Local Flash
bash# ewn save <filename> Saves the current running configuration. Filename format (must use extension.conf1 or.conf2): <filename1>.conf1 <filename2>.conf2 <filenameX> can be a combination of both letters and characters. For example, EWN300_041503.conf1 or location1_E300.conf2. Trying to use any other filename format will result in the error message: EWN_ERROR_BAD_FILE_NAME. Warning

Regulatory Notices - 2

2.5 Software Transfer. You may permanently transfer all of your rights under this Agreement in connection with transfer of the PRODUCT, provided you retain no copies, you transfer all of the SOFTWARE PRODUCT (including all component parts, the media and printed materials, any upgrades, this Agreement, and, if applicable, the Certificate of Authenticity), and the recipient agrees to the terms of this Agreement. If the SOFTWARE PRODUCT is an upgrade, any transfer must include all prior versions of the SOFTWARE PRODUCT. However, if the SOFTWARE PRODUCT is marked "Not for Resale" or "NFR", you may not resell it or otherwise transfer it for value. 2.6 Copyright. All title and copyrights in and to the SOFTWARE PRODUCT (including but not limited to any images, photographs, animations, video, audio, music, text, and "applets" incorporated into the SOFTWARE PRODUCT), the accompanying printed materials, and any copies of the SOFTWARE PRODUCT are owned by POLYCOM or its suppliers. Title, ownership rights, and intellectual property rights in the SOFTWARE PRODUCT shall remain in POLYCOM or its suppliers. Title and related rights in the content accessed through the SOFTWARE PRODUCT is the property of such content owner and may be protected by applicable law. This Agreement gives you no rights in such content. 2.7 Confidentiality. The SOFTWARE PRODUCT contains valuable proprietary information and trade secrets of POLYCOM and its suppliers that remains the property of POLYCOM. You shall protect the confidentiality of, and avoid disclosure and unauthorized use of, the SOFTWARE PRODUCT. 2.8 Dual-Media Software. You may receive the SOFTWARE PRODUCT in more than one medium. Regardless of the type or size of medium you receive, you may use only one medium that is appropriate for your single PRODUCT. You may not use or install the other medium on another PRODUCT. 2.9 Reservation of Rights. POLYCOM reserves all rights in the SOFTWARE PRODUCT not expressly granted to you in this Agreement. 2.10 Additional Obligations. You are responsible for all equipment and any third party fees (such as carrier charges, internet fees, or provider or airtime charges) necessary to access the SOFTWARE PRODUCT. 3. SUPPORT SERVICES. POLYCOM may provide you with support services related to the SOFTWARE PRODUCT ("SUPPORT SERVICES "). Use of SUPPORT SERVICES is governed by the POLYCOM policies and programs described in the POLYCOM-provided materials. Any supplemental software code provided to you as part of the SUPPORT SERVICES is considered part of the SOFTWARE PRODUCT and is subject to the terms and conditions of this Agreement. With respect to technical information you provide to POLYCOM as part of the SUPPORT SERVICES, POLYCOM may use such information for its business purposes, including for product support and development. POLYCOM will not utilize such technical information in a form that personally identifies you.

User Guide V2IU 4300T Converged Network Appliance

V7.2.2 May 2007

Trademark Information
Polycom, the Polycom logo design, [and others that appear in your document] are registered trademarks of Polycom, Inc. [List other trademarks] are trademarks of Polycom, Inc. in the United States and various other countries. All other trademarks are the property of their respective owners.
2007 Polycom, Inc. All rights reserved. Polycom Inc. 4750 Willow Road Pleasanton, CA 94588-2708 USA No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Polycom, Inc. Under the law, reproducing includes translating into another language or format. As between the parties, Polycom, Inc. retains title to, and ownership of, all proprietary rights with respect to the software contained within its products. The software is protected by United States copyright laws and international treaty provision. Therefore, you must treat the software like any other copyrighted material (e.g. a book or sound recording). Every effort has been made to ensure that the information in this manual is accurate. Polycom, Inc. is not responsible for printing or clerical errors. Information in this document is subject to change without notice.

Contents

1 Introduction. 11
The Polycom V2IU 4300T Converged Network Appliance. 11 T1 Wide Area Network (WAN) Access Router. 11 Security. 11 VoIP. 11 Quality of Service. 11 Call Quality Monitoring. 12 Future-proof Scalability. 12 Feature Summary. 12 Front Panel LEDs. 13 Back Panel. 13 Power Connector. 14 Erase Button. 14 Management console port. 14 T1/E1 WAN port. 14 Ethernet WAN port. 15

2 Getting Started. 21

Physical Installation. 21 Desktop Installation. 21 Wall-Mount Installation. 22 Administration of the Polycom V2IU 4300T. 22
3 Configuring the Polycom V2IU 4300T. 31
Configuration Guide For IP Centrex Applications. 32 Configuration Outline. 33 Configuration Guide For Station Side IP PBX Applications. 34 Configuration Outline. 35 Configuration Guide For Trunk Side IP PBX Applications. 36 Configuration Outline. 37 Configuration Guide For Hosted Video Applications. 37 Configuration Guide For Enterprise Video Applications. 310 System Configuration. 312
Configure the LAN Interface. 312 Configuring VLANs in the Polycom V2IU 4300T. 313 Modify an Existing VLAN Configuration. 315 Delete an Existing VLAN Configuration. 315 Assign the Polycom V2IU 4300Ts ALG to your Priority VLAN. 316 Configure the WAN Interface. Protocol. Frame Relay Mode and DLCI. Timing. Payload Loopback. 319
Configure the DHCP Server. 319 Delete a DHCP IP Address. 321 Disable The DHCP Server. 322 Configure Hostname, SNMP and Remote Logging. Configure SNMP. Disable SNMP. Configure Remote System Logging. Disable Remote System Logging. Configure a local Hostname. Enable Mean Opinion Scoring (MOS). Set MOS Threshold. 324 324
Change the Administration Password. 325 Read-only User. 325 Enabling a Read-only User. 325 Subinterfaces. 326 How Subinterfaces Works. 326 Configuring Subinterfaces. 327 ToS Byte Setting. 328 How the ToS Byte Setting Works. 328 Viewing or Changing the ToS Byte Setting. 328 H.323 Configuration. 330 H.323 Activity. 335 H.323 Alias Manipulation. 335 H.323 Neighboring. 337 Regular Expressions. 339 Forwarding Rules. 340 How Forwarding Rules Works. 340 Example. 340 Configuring Forwarding Rules. 341 Peering Proxy. 343 How Peering Proxy Works. 343 Configuring Peering Proxy. 347

The Ethernet 10/100 Mbps port on the Polycom V2IU 4300T can be used as a WAN interface as an alternative to the T1 interface. This port is typically used when connecting the Polycom V2IU 4300T to an existing T1/E1 WAN router, cable or xDSL modem.

Getting Started

Physical Installation
The Polycom V2IU 4300T is designed for desktop, rack or wall-mount installation. Please observe the following guidelines when installing the system: Never assume that the AC cord is disconnected from a power source. Always check first. Always connect the AC power cord to a properly grounded AC outlet to avoid damage to the system or injury.
Ensure that the physical location of the installation has adequate air circulation and meets the minimum operating conditions as provided in the environmental specifications for the system. Warning
Secure the power supply using a fastener or nearby shelf so that it does not hang from the power connector.

Desktop Installation

1. Remove the Polycom V2IU 4300T and accessories from the shipping container. 2. Place the Polycom V2IU 4300T on a flat, dry surface such as a desktop, shelf or tray. 3. Connect the power and network cables to the appropriate ports on the back of the system. Caution
To reduce the risk of fire, use only 26 AWG or larger wire (e.g. 24, 22, 20, etc.) to connect the T1 port on your unit to an RJ-45 jack.

Wall-Mount Installation

The Polycom V2IU 4300T can be wall-mounted using the two mounting brackets on the bottom of the appliance. We recommend using two round or pan head screws. Install two screws 4 14/16 horizontally apart on a wall or other vertical surface. The screws should protrude from the wall so that you can fit the appliance between the head of the screw and the wall. 1. If you install the screws in drywall use hollow wall anchors to ensure that the unit does not pull from the wall due to prolonged strain from the cable and power connectors. 2. Remove the Polycom V2IU 4300T and accessories from the shipping container. 3. Hang the Polycom V2IU 4300T on the wall. 4. Connect the power and network cables to the appropriate ports on the back of the system. Warning

Caution

Administration of the Polycom V2IU 4300T
The Polycom V2IU 4300T is configured using a web browser such as Internet Explorer or Netscape Navigator. The Polycom V2IU 4300T is shipped with a pre-configured IP address for its LAN port of 192.168.1.1. To connect to the Polycom V2IU 4300T, do the following: 1. Connect a PC using an IP address of 192.168.1.2 and subnet mask of 255.255.255.0 to LAN port 4 of the Polycom V2IU 4300T. 2. Launch a web browser on the PC and enter the URL string: 192.168.1.1. Press Return. The initial Polycom V2IU 4300T main configuration menu appears.

Most installations will use a single DLCI for both voice and data traffic. However, in instances where the network will provide a different quality of service based on DLCI number it is desirable to place all voice traffic on one DLCI and then configure a second DLCI for data. In this case, the Secondary DLCI is configured as follows: 1. Select Network.

3 - 18

2. Select the T1 link next to the radio button to proceed to the T1 configuration page. 3. Select Enable in the Frame Relay Secondary Settings section of the page. 4. Enter the Secondary DLCI, IP Address, Network Mask and Gateway for the data traffic using the Secondary DLCI. Timing Display and set the clock timing source for the T1/E1 interface. The timing can be either derived from the network (External) or provided to the T1 interface by the V2IU (Internal). With a carrier-provided T1, the timing is usually derived from the network (External, the default setting). Warning
Mismatched timing modes can result in WAN connectivity but with intermittent data loss.
Payload Loopback Display and set the loopback setting. During T1 line testing the local interface can be set to Loopback to allow the network provider to verify connectivity and line quality. For normal operation the setting should always be No Loopback (the default setting).
Configure the DHCP Server

3 - 19

The Polycom V2IU 4300T can act as a DHCP server granting IP addresses to PCs, workstations, servers or voice devices (IP phones, IADs or softphones) connected to its LAN interfaces. DHCP is a protocol that enables IP devices to obtain temporary or permanent IP addresses (out of a pool) from centrally administered servers. The user can configure blocks of IP addresses, a default gateway, DNS servers, NTP server address, Time offset from NTP value, WINS address and TFTP/FTP server name that can be served to the requesting IP devices. In addition the Polycom V2IU 4300T will provide its LAN IP address in DHCP user options 150 and 151 for use by IP phones. Some IP phones use these values for configuration of their TFTP server and MGCP control server addresses. Note
The DHCP server in the Polycom V2IU 4300T should not be used if a DHCP server already exists in the same subnet as the Polycom V2IU 4300T. Also, it is recommended that you assign static IP addresses for common-access devices such as network printers or fax machines.
You can also enable or disable the Polycom V2IU 4300T DHCP server on a per VLAN basis. 1. Select DHCP Server. 2. If you are using VLANs select the desired VLAN ID from the drop down menu. 3. The default value for the DHCP server is disabled. Click the top checkbox to enable or disable the internal DHCP server (default is disabled). If you are using VLANs select the desired VLAN ID. 4. Enter the Lease Duration. The lease duration is the amount of time in days that an IP device may use an assigned IP address before requesting that it be renewed. The default value is 7 days and the valid range of input is 1 to 30 days. 5. Enter the Subnet Mask. This is the subnet mask that will be sent via DHCP to the requesting IP devices. 6. Enter the DHCP IP Addresses. This is the pool of IP addresses that will be provided to the requesting IP devices. You can enter both individual IP addresses or a range of addresses using the following format: 192.168.1.2 (single address) 192.168.1.4-10 (address range 192.168.1.4 through 192.168.1.10) Note

Allow UDP Port

Allows traffic with the specified UDP port to terminate on the 4300T.

Deny Hosts (IP)

Denies all traffic with the source IP address matching the specified hosts Denies all traffic matching the specified TCP port numbers and the specified source IP addresses
Deny Hostwise TCP (IP-Port)

3 - 67

Allow Hostwise UDP (IP-Port)
Allows all traffic matching the specified UDP port numbers and the specified source IP addresses
*Multiple entries are separated by a space *Port are specified using a - character. For example: 192.168.3.1-23 for Telnet. *Port ranges are specified using a : character. For example: 192.168.3.1-23:50 means port 23 through 50 *Classful IP addresses are assumed by default. For example: 192.168.3.1 uses a class c mask. Subnets can be specified using the / notation. E.g. 192.168.3.1/24
If a given packet does not match any of the configured rules, it is dropped. 1. Select Firewall. 2. Enter the desired Advanced Settings using the table above as a guide. 3. Select Submit. Remove Advanced Setting Entries To remove an advanced firewall setting simply highlight the value in the entry box and delete it using the keyboard.
1. Select Firewall. 2. Highlight the entry to be deleted in the Advanced Settings list and press the Delete key on your keyboard. 3. Press Submit.
Traffic management is required to ensure high quality voice and video calls when voice, video, and data traffic share the same WAN link. Voice and video traffic must be prioritized for transmission over data traffic to meet the stringent jitter, latency and packet loss requirements for high quality voice and video. The Polycom V2IU 4300T: Automatically prioritizes voice and video traffic over data traffic to ensure high quality voice and video calls. Maximizes WAN link utilization by allowing data traffic to burst up to full line rate in the absence of voice and video calls.

3 - 68

Controls the data transfer rate of far-end WAN TCP devices to limit WAN link congestion. Supports network-based QoS applications by setting the TOS bits for all VoIP packets sent to the WAN and the LAN. TOS bits are used so that VoIP packets can be prioritized in the network by DiffServ enabled routers. The TOS bit value used by the Polycom V2IU 4300T is to minimize delay and maximize throughput, or 0xb8 hexadecimal. This value is set for all VoIP packets processed by the Polycom V2IU 4300T and overwrites any specific TOS bit configuration set by VoIP endpoints. Ensures that bandwidth allocated to new voice and video calls does not adversely affect the quality of existing active calls (Call Admission Control or CAC).
The Polycom V2IU 4300T combines sophisticated traffic management mechanisms including classification, prioritization, queuing, rate limiting and CAC to ensure high quality voice and video calls. Fortunately the system manages this complexity for you and configuring traffic management is very straightforward: 1. Enable traffic shaping. 2. Specify the upstream and downstream bandwidth of your WAN link. 3. Enable CAC. Please follow the steps below to configure and enable traffic management.

Enable Traffic Shaping

1. From the Configuration Menu, select Traffic Shaper.

3 - 69

2. Select the Enable traffic shaper checkbox. 3. Specify the upstream and downstream bandwidth of your WAN link 4. Enter the WAN Downstream Bandwidth in Kbps. 5. Enter the WAN Upstream Bandwidth in Kbps. Note
For FT1/T1/E1 links the upstream and downstream bandwidths will always be the same value (the link is full-duplex).
Optionally enable priority IP addresses
VoIP traffic from devices that use the VoIP ALG function (phones, video stations, softphones on Pcs, etc.) are already marked as high priority and do not need to be manually configured in this list. This list is used to prioritize voice traffic from trunk interfaces of IP PBXs or other high priority devices that do not use the VoIP ALG function of the Polycom V2IU 4300T.
>> Enter the IP address of other high priority devices in the priority IP
Addresses box. You can enter individual IP addresses or a range using by appending a -character to the last octet. For example, 10.10.10.2-5 would specify 10.10.10.2, 10.10.10.3, 10.10.10.4 and 10.10.10.5 as voice devices. Warning
Care must be taken to ensure that the IP addresses entered do not include data devices such as PCs or workstations. Traffic from these devices will be placed in the priority voice queue internal to the Polycom V2IU 4300T and burst up to full line rate. This will starve actual voice devices by consuming priority bandwidth and result in dropped calls, busy signals & poor voice quality.

Enable CAC

The Polycom V2IU 4300T uses CAC to limit the number of active voice calls over the WAN link. This is necessary because a typical installation uses a ratio of 1:2 or 1:4 active voice calls to voice devices on the assumption that 50% or 25% of all users are on the phone at the same time. These ratios are guidelines only and at times the number of concurrent calls may exceed the amount of WAN bandwidth available to process the calls. In this instance existing phone calls will experience poor quality or be dropped all together. To prevent this from occurring a typical voice installation will set a threshold for the maximum number of concurrent voice calls supported by the WAN access link. New call requests in excess of this threshold will receive the equivalent of a fast busy and the WAN link will not become oversubscribed. For IP Centrex installations the maximum number of concurrent voice calls is usually configured in the Polycom V2IU 4300T by enabling CAC. When the Polycom V2IU 4300T is deployed in IP PBX applications the maximum number

3 - 70

of concurrent calls could be configured in the IP PBX. If the PBX is responsible for this setting you do not need to configure CAC in the Polycom V2IU 4300T. Please check with your IT administrator to determine if this is the case. Determining the maximum number of concurrent calls The maximum number of concurrent calls that can be supported by the WAN access link is calculated using the following formula: Max calls = (Maximum WAN upstream bandwidth *.85)/VoIP codec rate where, Maximum WAN upstream bandwidth = value entered in step D above (in Kbps) VoIP codec rate = 85.6Kbps for G.711 voice devices or 29.6Kbps for G.729 voice devices. The maximum WAN upstream bandwidth is multiplied by.85 in the formula above to reduce the total bandwidth available for voice calls by 15%. This reduction is necessary because the Polycom V2IU 4300T automatically reserves 15% of the total WAN bandwidth for low priority data traffic so that it is not starved completely. Starving data traffic completely would increase the number of retry attempts and exacerbate congestion on the link during periods of peak usage. Examples The maximum number of G.711 voice calls supported by a T1 (1.536 Kbps) WAN is calculated as follows: (1.536*.85)/85.6 = 15.3 or 15 total voice calls. The maximum number of G.711 voice calls supported by a 768Kbps fractional T1 WAN is calculated as follows: (768*.85)/85.6 = 7.6 or 7 total voice calls The maximum number of G.729 voice calls supported by a 256Kbps fractional T1 WAN is calculated as follows: (256*.85)/29.6 = 7.4 or 7 total voice calls After determining the maximum number of voice calls CAC is enabled as follows: 1. Select the Enable Call Admission Control checkbox. 2. Enter Maximum number of calls allowed as calculated above. 3. Press Submit.

The interface statistics can point to areas of congestion in the network. If the errors statistic is a few percent or more of the total packets sent it may be an indication of excessive congestion on the network interface. If the congestion is not corrected the quality of voice calls will be affected. The topology of the network attached to the network interface with the errors should be examined and modified to better segment and isolate network traffic.
Viewing Advanced System Information
To view advanced system information for the 4300T proceed to the System Information page as follows: 1. Select System. 2. Select System Overview. 3. Select System Information. The following system information is displayed:
System Uptime System Uptime displays the current time, the amount of time elapsed since the last system reboot, and the system load averages for the past 1, 5, and 15 minutes. Uptime can help trace when a power outage may have interrupted service. Load averages that remain greater than 2 indicate excessive system loading. Partitioning voice traffic using a second system may be required. Process Information Displays the active processes in the 4300T. Memory Usage Displays detailed memory allocation information that may be of use to technical support.
System Logging Messages Displays information logged during system boot and normal operation. Logging messages may indicate unauthorized attempts to access the 4300T, process restart messages, and excessive resource utilization messages.
Passive Voice Call Monitoring
The 4300T monitors live voice calls and performs objective speech quality assessment. This information enables the network operator to assess voice quality for the purposes of SLA tracking or problem isolation. Mean Opinion Score (MOS) results for RTP streams in both directions of a VoIP call are calculated at call completion. This information along with the IP addresses of the VoIP endpoints supporting the call are logged locally and optionally sent to an external syslog server. Additionally the 4300T will generate a real-time message for any MOS values calculated less than 2.5 (considered poor quality) during an active call. Voice call quality information is found locally in the System Logging Messages section of the System Information page and a sample output is provided below.

Backup file operations are performed in the 4300T CLI using the ewn command.

The ewn Command

The syntax for the ewn command is as follows: USAGE:
ewn help|list ewn save|load|delete [file name] ewn upload|download [file name] [ip address]
where file name must use extension.conf1 or.conf2
The ewn command can be used with a local terminal connection or remotely using SSH. 1. Use a NULL modem cable to connect to serial port 1 of the 4300T 2. Use a terminal emulator such as Hyperterminal set to a baud rate of 9600, 8, 1 and none (databits, stop bits and parity) Alternatively you can connect to the 4300T remotely using SSH: 1. Logon as root 2. Enter the password Once you are at the command prompt (#) you can create the backup file, store it to local flash, copy it to a remote TFTP server, copy it from a remote TFTP server, delete it, load it or list all available backup files.
Create a Backup File and Save in Local Flash
# ewn save <filename> Saves the current running configuration. Filename format (must use extension.conf1 or.conf2): <filename1>.conf1 <filename2>.conf2 <filenameX> can be a combination of both letters and characters. For example, EWN30_041503.conf1 or location1_E30.conf2. Trying to use any other filename format will result in the error message: EWN_ERROR_BAD_FILE_NAME. Warning
The.conf extensions have special significance. If you save a configuration with <filename-new>.conf1, then any existing <filename-old>.conf1 will be overwritten with the new one.
Copy a Backup File to a Remote TFTP Server
# ewn upload <filename> <tftp server IP Address>
Copy a backup file from the 4300T to a TFTP server.
Download a Backup File from a Remote TFTP Server
# ewn download <filename> <tftp server IP Address>
Download a backup file from a TFTP server to the V2IU.
List the Available Backup Files

# ewn list

List all backup files stored in FLASH. If no file has been saved, the command will only return the # prompt.

Delete a Backup File

# ewn delete <filename>
Delete the backup file specified in the filename.
Load a Backup File so that it Becomes the Running Configuration
# ewn load <filename>
Loads the specified backup file into RAM and makes it the active running configuration. Warning
Issuing this command will automatically restart the 4300T and therefore interrupt any active voice calls and data sessions.

Upgrading the 4300T

This chapter describes how to upgrade your 4300T to the latest software release available from Polycom.
It is recommended that you reboot the 4300T prior to performing the upgrade. This is to make sure there is enough dynamic memory available to handle the upgrade process. Warning
When you update your software telephone services will be unavailable for several minutes. It is therefore advised that upgrades be performed during a maintenance window when telephone traffic can be interrupted.

Specifications

WAN Ports LAN Ports Serial Ports Dimensions Weight Power Warranty 1xT1 CSU/DSU or 10/100 Ethernet 4x10/100 Ethernet (switched) 1xRS-232 Height (1.7), Width (10), Depth (7) 2 lb 12V 3A 1 Year

Appendix - 2

Regulatory Notices
Important Safeguards Read and understand the following instructions before using the system: Close supervision is necessary when the system is used by or near children. Do not leave unattended while in use. Only use electrical extension cords with a current rating at least equal to that of the system. Always disconnect the system from power before cleaning and servicing and when not in use. Do not spray liquids directly onto the system when cleaning. Always apply the liquid first to a static free cloth. Do not immerse the system in any liquid or place any liquids on it. Do not disassemble this system. To reduce the risk of shock and to maintain the warranty on the system, a qualified technician must perform service or repair work. Connect this appliance to a grounded outlet. Only connect the system to surge protected power outlets. Keep ventilation openings free of any obstructions.

SAVE THESE INSTRUCTIONS.

END-USER LICENSE AGREEMENT FOR POLYCOM SOFTWARE
IMPORTANT-READ CAREFULLY BEFORE USING THE SOFTWARE PRODUCT: This End-User License Agreement (Agreement) is a legal agreement between you (and/or any company you represent) and either Polycom (Netherlands) B.V. (in Europe, Middle East, and Africa), Polycom Hong Kong, Ltd. (in Asia Pacific) or Polycom, Inc. (in the rest of the world) (each referred to individually and collectively herein as POLYCOM), for the SOFTWARE PRODUCT licensed by POLYCOM. The SOFTWARE PRODUCT includes computer software and may include associated media, printed materials, and "online" or electronic documentation ("SOFTWARE PRODUCT"). By clicking "I AGREE" or by installing, copying, or otherwise using the SOFTWARE

Regulatory Notices - 1

PRODUCT, you agree to be and will be bound by the terms of this Agreement. If you do not agree to the terms of this Agreement, your use is prohibited and you may not install or use the SOFTWARE PRODUCT. The SOFTWARE PRODUCT is protected by copyright laws and international copyright treaties, as well as other intellectual property laws and treaties. The SOFTWARE PRODUCT is licensed (not sold) to you, and its use is subject to the terms of this Agreement. This is NOT a sale contract. 1. GRANT OF LICENSE. Subject to the terms of this Agreement, POLYCOM grants to you a non-exclusive, non-transferable, revocable license to install and use the SOFTWARE PRODUCT solely on the POLYCOM product with which this SOFTWARE PRODUCT is supplied (the "PRODUCT"). You may use the SOFTWARE PRODUCT only in connection with the use of the PRODUCT subject to the following terms and the proprietary notices, labels or marks on the SOFTWARE PRODUCT or media upon which the SOFTWARE PRODUCT is provided. You are not permitted to lease, rent, distribute or sublicense the SOFTWARE PRODUCT, in whole or in part, or to use the SOFTWARE PRODUCT in a time-sharing arrangement or in any other unauthorized manner. Further, no license is granted to you in the human readable code of the SOFTWARE PRODUCT (source code). Except as expressly provided below, this License Agreement does not grant you any rights to patents, copyrights, trade secrets, trademarks, or any other rights in respect to the SOFTWARE PRODUCT. 2. OTHER RIGHTS AND LIMITATIONS. 2.1 Limitations on Reverse Engineering, Decompilation, and Disassembly. You may not reverse engineer, decompile, modify or disassemble the SOFTWARE PRODUCT or otherwise reduce the SOFTWARE PRODUCT to human-perceivable form in whole or in part, except and only to the extent that such activity is expressly permitted by applicable law notwithstanding this limitation. The SOFTWARE PRODUCT is licensed as a single product. Its component parts may not be separated for use on more than one PRODUCT. You may not use the SOFTWARE PRODUCT for any illegal purpose or conduct. 2.2 Back-up. Except as expressly provided for under this Agreement you may not copy the SOFTWARE PRODUCT; except, however, you may keep one copy of the SOFTWARE PRODUCT and, if applicable, one copy of any previous version, for back-up purposes, only to be used in the event of failure of the original. All copies of the SOFTWARE PRODUCT must be marked with the proprietary notices provided on the original SOFTWARE PRODUCT. You may not reproduce the supporting documentation accompanying the SOFTWARE PRODUCT. 2.3 No Modifications. You may not modify, translate or create derivative works of the SOFTWARE PRODUCT. 2.4 Proprietary Notices. You may not remove or obscure any proprietary notices, identification, label or trademarks on or in the SOFTWARE PRODUCT or the supporting documentation.

Regulatory Notices - 3

4. TERMINATION. Without prejudice to any other rights, POLYCOM may terminate this Agreement if you fail to comply with any of the terms and conditions of this Agreement. In such event, you must destroy all copies of the SOFTWARE PRODUCT and all of its component parts. You may terminate this Agreement at any time by destroying the SOFTWARE PRODUCT and all of its component parts. Termination of this Agreement shall not prevent POLYCOM from claiming any further damages. If you do not comply with any of the above restrictions, this license will terminate and you will be liable to POLYCOM for damages or losses caused by your non-compliance. The waiver by POLYCOM of a specific breach or default shall not constitute the waiver of any subsequent breach or default. 5. UPGRADES. If the SOFTWARE PRODUCT is labeled as an upgrade, you must be properly licensed to use the software identified by POLYCOM as being eligible for the upgrade in order to use the SOFTWARE PRODUCT. A SOFTWARE PRODUCT labeled as an upgrade replaces and/or supplements the software that formed the basis for your eligibility for the upgrade. You may use the resulting upgraded SOFTWARE PRODUCT only in accordance with the terms of this Agreement. If the SOFTWARE PRODUCT is an upgrade of a component of a package of software programs that you licensed as a single product, the SOFTWARE PRODUCT may be used and transferred only as part of that single SOFTWARE PRODUCT package and may not be separated for use on more than one PRODUCT. 6. WARRANTY AND WARRANTY EXCLUSIONS. 6.1 Limited Warranty. POLYCOM warrants that (a) the SOFTWARE PRODUCT will perform substantially in accordance with the accompanying documentation for a period of ninety (90) days from the date of receipt by you, and (b) any SUPPORT SERVICES provided by POLYCOM shall be substantially as described in applicable written materials provided to you by POLYCOM. POLYCOM does not warrant that your use of the SOFTWARE PRODUCT will be uninterrupted or error free, or that all defects in the SOFTWARE PRODUCT will be corrected. You assume full responsibility for the selection of the SOFTWARE PRODUCT to achieve your intended results and for the installation, use and results obtained from the SOFTWARE PRODUCT. POLYCOM's sole obligation under this express warranty shall be, at POLYCOM's option and expense, to refund the purchase price paid by you for any defective software product which is returned to POLYCOM with a copy of your receipt, or to replace any defective media with software which substantially conforms to applicable POLYCOM published specifications. Any replacement SOFTWARE PRODUCT will be warranted for the remainder of the original warranty period or thirty (30) days, whichever is longer. 6.2 Warranties Exclusive. IF THE SOFTWARE PRODUCT DOES NOT OPERATE AS WARRANTED ABOVE, YOUR SOLE REMEDY FOR BREACH OF THAT WARRANTY SHALL BE REPAIR, REPLACEMENT, OR REFUND OF THE PURCHASE PRICE PAID, AT POLYCOM'S SOLE OPTION. TO THE FULL EXTENT ALLOWED BY LAW, THE FOREGOING WARRANTIES AND REMEDIES ARE EXCLUSIVE AND ARE IN LIEU OF ALL OTHER WARRANTIES, TERMS, OR CONDITIONS, EXPRESS OR

2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions: a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change. b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License. c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it. Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program. In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License. 3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following: a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or, b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of

Regulatory Notices - 9

conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program. If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances. It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice. This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License. 8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License. 9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation. 10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make

INDUSTRY CANADA (IC) NOTICE
NOTICE: This equipment meets the applicable Industry Canada Terminal Equipment Technical Specifications. This is confirmed by the registration number. The abbreviation, IC, before the registration number signifies that registration was performed based on a Declaration of Conformity indicating that Industry Canada technical specifications were met. It does not imply that Industry Canada approved the equipment. Before installing this equipment, users should ensure that it is permissible to be connected to the facilities of the local telecommunications company. The equipment must also be installed using an acceptable method of connection. The customer should be aware that compliance with the above conditions may not prevent degradation of service in some situations. Repairs to certified equipment should be coordinated by a representative designated by the supplier. Any repairs or alterations made by a user to this equipment, or equipment malfunctions, may give the telephone communications company cause to request the user to disconnect the equipment.

Regulatory Notices - 12

Users should ensure for their own protection, that the electrical ground connections of the power utility, telephone lines and internal metallic water pipe system, if present, are connected together. This precaution may be particularly important in rural areas. Caution: Users should not attempt to make such connections themselves, but should contact the appropriate electric inspection authority, or electrician, as appropriate. WARRANTY AND REPAIR SERVICE CENTER: The RAM Group Kent McDonald kent.macdonald@theramgroup.com (403) 266-5840 x 100 This Class (B) digital apparatus complies with Canadian ICES-003.

Regulatory Notices - 13

Regulatory Notices - 14