Table Of Contents
Configuring the Cisco Unified Videoconferencing 3500 Gateway
About Gateway Interface Users
Adding Gateway Interface Users
Editing Gateway Interface Users
Deleting Gateway Interface Users
Viewing LED Information
Viewing General Information About the Gateway
Updating Your License
Viewing Software Version Details
Setting the Time and Date on the Gateway
Setting the Gateway Location
Resetting Default Device Basic Settings
Viewing Address Settings
Changing Address Settings
Changing the Administrator Interface Web Server Port
Configuring Security
About the Gateway Administrator Interface
Viewing the Status Tab
Viewing B Channel Status
Refreshing Gateway Status
Configuring Gateway Settings
Configuring Basic Gateway Settings
Configuring IP Connectivity Settings
Configuring the Gateway to Register With a Gatekeeper
Configuring the Gateway for Peer-to-Peer IP Connectivity
About Peer-to-Peer H.323 Call Disconnect Reasons
Configuring IVR Settings
Configuring Outgoing Call Delimiters
About Encoding/Decoding Protocols
About Audio Transcoding
About T.120 Data Collaboration Support
Configuring Encoding/Decoding Protocols
Configuring ISDN Channel Bonding Settings for Downspeeding
Configuring Quality of Service Settings
Configuring Alert Indications
Gateway Event Types
Trap Severity Enumeration
Configuring Gateway Resources for Calls
Configuring Gateway Encryption
Configuring Advanced Settings
About DTMF Settings
About DTMF
About DTMF Detection on IP-to-ISDN Calls
About DTMF Detection on ISDN-to-IP Calls
Configuring DTMF Settings
Configuring Advanced Commands
About Gateway Services
Viewing Existing Services
Adding or Editing Services
Bonding Synchronization
Deleting Gateway Services
Configuring Port Settings
Configuring Basic Port Settings
Configuring Port Physical Interface Settings
PRI Ports
Configuring Fractional Channels
Configuring Line Coding, Framing and Signaling Type
BRI Ports
Configuring Service Profile Identification (SPID) Values
About Advanced ISDN Settings for PRI Gateways
About NSF Settings
Adding or Editing ISDN Information Elements
Configuring Network Specific Facility Settings
Deleting ISDN Information Elements
Configuring Port Call Policies
Configuring Port Supported Services
Viewing Call Information
Refreshing Call Information
Viewing Call Details
Disconnecting Calls
Viewing Gateway Alarm Events
Viewing Gateway Statistics
Configuring Gateway Maintenance Tasks
Saving Configuration Settings
Importing Configuration Files
Configuring the Cisco Unified Videoconferencing 3500 Gateway
This section describes the following topics:
•
About Gateway Interface Users
•Viewing LED Information
•Viewing General Information About the Gateway
•Viewing Address Settings
•Changing the Administrator Interface Web Server Port
•Configuring Security
•About the Gateway Administrator Interface
•Viewing the Status Tab
•Configuring Gateway Settings
•About Gateway Services
•Configuring Port Settings
•Viewing Call Information
•Viewing Gateway Alarm Events
•Viewing Gateway Statistics
•Configuring Gateway Maintenance Tasks
•Saving Configuration Settings
•Importing Configuration Files
About Gateway Interface Users
Users must have the appropriate access level to log in to the gateway interface. With Administrator-level access, a user can configure the gateway and monitor gateway activity. You can view and manage the list of gateway users in the Users tab of the Device section of the gateway interface. The Users tab displays all currently configured users and their access levels.
There are three types of gateway interface users:
•Administrator—Full access to the gateway interface to configure gateway settings.
•Operator—User can monitor or disconnect calls but otherwise only has read-only access to the gateway interface.
•Read-only—User has read-only access to the gateway interface.
Adding Gateway Interface Users
In the Users tab of the Device section of the gateway interface, you can add gateway interface users.
Procedure
Step 1 In the gateway interface, on the sidebar, click Device.
Step 2 Click the Users tab.
Step 3 Click Add to add a new user.
The Add User dialog box appears.
Step 4 In the User name field, enter the user login name.
Step 5 In the Access Level field, choose one of the following access levels: Administrator, Operator or Read only.
Step 6 In the Password field, enter the password that the user uses to login to the gateway interface.
Step 7 In the Confirm Password field, re-enter the password.
Step 8 Click Upload.
Editing Gateway Interface Users
In the Users tab of the Device section of the gateway interface, you can edit gateway interface users.
Procedure
Step 1 In the gateway interface, on the sidebar, click Device.
Step 2 Click the Users tab.
Step 3 Select an existing user and click Edit.
The Edit User dialog box appears.
Step 4 In the User name field, edit the user login name.
Step 5 In the Access Level field, choose one of the following access levels: Administrator, Operator or Read only.
Step 6 In the Password field, edit the password that the user uses to login to the gateway interface.
Step 7 In the Confirm Password field, re-enter the password.
Step 8 Click Upload.
Deleting Gateway Interface Users
In the Users tab of the Device section of the gateway interface, you can delete gateway interface users.
Procedure
Step 1 In the gateway interface, on the sidebar, click Device.
Step 2 Click the Users tab.
Step 3 Select a user and click Delete.
Viewing LED Information
In the LED Monitoring tab in the Device interface, you can monitor the status of all the gateway front and rear panel LED indicators. The LEDs are displayed in diagrams reproducing the layout of the gateway front and rear panels.
Procedure
Step 1 In the gateway interface, on the sidebar, click Device.
Step 2 Click the LED Monitoring tab.
Step 3 Place the mouse cursor over the required LED in the LED Monitoring tab to view a description of that LED.
Viewing General Information About the Gateway
In the Basics tab in the Device interface, you can view and configure general information about the hardware and software the gateway uses.
Procedure
Step 1 In the gateway interface, on the sidebar, click Device.
Step 2 Click the Basics tab.
Table 3-1 describes the elements that appear in the Basics tab.
Table 3-1 Device Basic Tab Elements
Field
|
Description
|
Device name
|
Identifies the model number of the device.
|
Location
|
User-configured description about the device. Click this field to type a new description, and then click Upload on the toolbar.
|
Serial number
|
The serial number that the factory assigned to the device.
|
License key
|
Your Cisco license key for accessing Cisco Unified Videoconferencing 3500 Gateway devices. Click the Update button to modify your Cisco license key.
|
Hardware version
|
The version number of the current hardware configuration.
|
Software version
|
The first two digits of the version number of the software installed on the device. Click the Details button to view details of the versions of software components installed on the device.
|
Date/Time
|
The date and time that the Cisco Unified Videoconferencing 3500 Gateway clock reports.
|
Related Topics
•Updating Your License
•Viewing Software Version Details
•Setting the Time and Date on the Gateway
•Setting the Gateway Location
•Resetting Default Device Basic Settings
Updating Your License
You use the Basics tab to update your gateway license.
Procedure
Step 1 On the sidebar, click Device.
Step 2 Click the Basics tab.
The Licensing and Registration dialog box appears.
Step 3 Access the Cisco web site to register before requesting a new license key by clicking the Click here to register at the web site link, or by copying the URL that appears in the lower half of the screen into your browser.
Step 4 Type your new license key in the New license key field and click Upload to activate the new license key.
Viewing Software Version Details
You use the Basics tab to view expanded software version information.
Procedure
Step 1 On the sidebar, click Device.
Step 2 Click the Basics tab.
Step 3 Locate the Software version field and click Details.
The Version Details dialog box appears.
Setting the Time and Date on the Gateway
You use the Basics tab to choose how your gateway tracks the date and time.
Procedure
Step 1 On the sidebar, click Device.
Step 2 Click the Basics tab.
Step 3 Locate the Date/Time field and click Change.
The Change Time dialog box appears. The date and time the gateway reports appear in the Set time to field.
Step 4 In the Change field, select the unit of time that you want to change.
Note There is no unit to change AM and PM. This designation rolls automatically when the hour rolls past 12 backward or forward. Similarly, seconds roll minutes, minutes roll hours, hours roll days, and days roll months.
Step 5 In the Set time to field, choose the up or down arrow to change that unit.
The unit you choose changes in the direction you choose: higher (up) or lower (down).
Step 6 Repeat steps 4 and 5 for as many units as you want to change.
Step 7 On the toolbar, click Upload.
Setting the Gateway Location
You can install the gateway anywhere on your network including at a remote site. In the Basics tab, you can describe the current location of the gateway.
Procedure
Step 1 On the sidebar, click Device.
Step 2 Click the Basics tab.
Step 3 In the Location field, enter the location information about the gateway that you want to display.
The field displays up to 23 characters.
Step 4 On the toolbar, click Upload to save to configuration memory.
Resetting Default Device Basic Settings
In the Basics tab, you can restore board basic settings to factory defaults.
Procedure
Step 1 On the sidebar, click Device.
Step 2 Click the Basics tab.
Step 3 Select the Reset to default settings check box.
Viewing Address Settings
In the Addressing tab, you can view address information for the gateway such as IP address informations, Domain Name Server (DNS) information and Ethernet port speed and duplex. Table 3-2 describes the elements that appear on the Addressing tab.
Table 3-2 Addressing Tab Elements
Field
|
Description
|
IP Address
|
IP Address
|
The IP address assigned to the gateway.
|
Router IP
|
The address of the router that the gateway uses.
|
Subnet Mask
|
The subnet address that the gateway uses.
|
DNS
|
DNS Server IP
|
The IP address of the Domain Name Server (DNS) that the gateway accesses.
|
Device DNS name
|
The device name of the Domain Name Server (DNS) that the gateway accesses (read-only).
|
Ethernet
|
Port type
|
Displays information about the Ethernet connection (read-only).
|
Port settings
|
The Ethernet speed and duplex that the gateway uses.
|
MAC address
|
Displays the Mandatory Access Control (MAC) code assigned to the gateway (read-only).
|
Port status
|
Displays the actual Ethernet speed and duplex the gateway uses on the network (read-only).
|
Related Topics
•Changing Address Settings
Changing Address Settings
In the Addressing tab, you can change the following address information for the gateway—IP address information, DNS information and the Ethernet port speed and duplex.
Procedure
Step 1 In the Administrator interface, on the sidebar, click Device.
Step 2 Click the Addressing tab.
Step 3 To change an IP address setting, do any of the following steps:
–In the IP Address field, type the IP address you want to assign to the gateway.
–In the Router IP field, type the IP address of the router you want the gateway to use.
–In the Subnet Mask field, type the subnet mask you want the gateway to use.
Step 4 In the DNS Server IP field, type the IP address of the DNS server that you want the gateway to use.
Step 5 In the Port settings field, choose the Ethernet port and duplex speed value you want to set.
Step 6 On the toolbar, click Upload.
Related Topics
•Viewing Address Settings
Changing the Administrator Interface Web Server Port
Port 80 is the default Administrator interface web server port. For additional security, you can modify the web server port in the Web tab.
Procedure
Step 1 In the gateway interface, on the sidebar, click Device.
Step 2 Click the Web tab.
Step 3 In the Web server port field, enter the port number.
Step 4 On the toolbar, click Upload.
Configuring Security
You can configure the access that external programs have to the gateway. These external programs include Telnet, Simple Network Management Protocol (SNMP), File Transfer Protocol (FTP), and ICMP (Internet Control Message Protocol, or ping).
Procedure
Step 1 In the gateway interface, on the sidebar, click Device.
Step 2 Click the Security tab.
Step 3 From the Security mode field, choose the access level you want the gateway to support:
–Standard—Enables SNMP, Telnet, FTP, and ICMP to access the gateway.
–High (no Telnet or Ftp)—Enables access to the gateway only through SNMP and ICMP.
–Maximum (no Telnet, ftp, SNMP, or ICMP)—Disallows external programs to access the gateway.
Step 4 In the SNMP Read community and Write community fields, enter default strings used to enable SNMP communication between the gateway and a external application.
Step 5 On the toolbar, click Upload.
About the Gateway Administrator Interface
In the gateway Administrator interface, you can view gateway resource information, define the gateway mode of operation, configure and edit gateway services, configure physical line settings, monitor and disconnect calls, view reported alert events, and view debugging details. Table 3-3 explains the tabs that appear in the gateway Administrator interface.
Note There may be slight variations between the configuration options described in this section and the options appearing in the gateway you are working with.
Table 3-3 Gateway Administrator Interface Tabs
Tab Name
|
Description
|
Status
|
Displays gateway resource usage information, number of calls currently in progress, and servicing gatekeeper details.
|
Settings
|
Defines the mode of gateway operation.
|
Services
|
Defines services that the gateway provides.
|
Port
|
Defines physical line settings for that particular PRI or BRI port.
|
Calls
|
Displays details on current calls and disconnect calls.
|
Event Log
|
Displays reported alert events.
|
Statistics
|
Displays specific system information such as call traces and debugging details.
|
Maintenance
|
Provides access to maintenance mode, in which you can prevent the gateway from accepting new calls, and perform software upgrades and other maintenance work.
|
Figure 3-1 and Table 3-4 display and list the elements in the gateway Administrator interface.
Figure 3-1 Gateway Administrator Interface
Table 3-4 Gateway Administrator Interface Elements
Number
|
Description
|
1
|
Device button
|
2
|
Gateway button
|
3
|
Upload button
|
4
|
Import button
|
5
|
Export button
|
6
|
Reset button
|
7
|
Refresh button
|
8
|
Logout button
|
9
|
Help button
|
Viewing the Status Tab
The Status tab displays the current rate of use of gateway resources, the total number of current calls, and servicing details. Table 3-5 lists the information in the Status tab.
Table 3-5 Status Tab Sections
Section Name
|
Description
|
General
|
•Status—Indicates the operational status of the gateway: OK or Failure. In cases of failure, a text description of the problem appears. For example, "PRI connection, remote side: loss of frame alignment."
|
Gateway Resource Meter
|
•Overall Gateway usage (%)—Displays the rate of gateway resources currently in use.
•CPU usage (%)—Displays the rate of CPU resources currently in use.
•Audio transcoder usage (%)—Displays the rate of audio transcoding resources currently used for video calls.
•ISDN B channels in use—Displays the total number of Integrated Services Digital Network (ISDN) B channels currently in use.
|
Calls
|
•Number of calls—Displays the total number of calls currently in progress in the gateway.
|
Servicing Gatekeeper
|
•IP address—Displays the IP address of the gatekeeper to which the gateway is currently registered.
•Host name—Displays the name of the servicing gatekeeper.
|
Related Topics
•Viewing B Channel Status
•Refreshing Gateway Status
Viewing B Channel Status
Note This section applies only to Cisco Unified Videoconferencing 3527 PRI Gateway.
From the Status tab in the gateway interface, you can view detailed status information for each B channel.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the Status tab (if not already selected).
Step 3 Click Details.
The Details dialog box appears, displaying the following information:
–Port 1 and Port 2—Displays the status of each of the B channels and of the D channel for each of the PRI ports. In gateways that support only one PRI port, only the Port 1 section appears.
–Disabled—Displays the number of disabled B channels for each port.
–Used—Displays the number of B channels currently in use for each port.
–Free—Displays the number of B channels currently available for each port.
–D channel—Displays the number of D channels for each port.
Refreshing Gateway Status
You can refresh the information that appears in the Status tab.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the Status tab (if not already selected).
Step 3 On the toolbar, click Refresh.
The information that appears in the Status tab is now refreshed.
Configuring Gateway Settings
In the Settings tab of the gateway interface, you can configure gatekeeper and Interactive Voice Response (IVR) addressing, the type of connection to the IP network, dialing delimiters, media encoding/decoding protocols, Quality of Service levels, which events cause the gateway to send SNMP traps, gateway resource levels for T.120 enabled and audio transcoded video calls, security settings, and advanced settings such as load balancing support.
The following topics discuss the settings you can configure in the Settings tab:
•Configuring Basic Gateway Settings
•Configuring IP Connectivity Settings
•Configuring IVR Settings
•Configuring Outgoing Call Delimiters
•About Encoding/Decoding Protocols
•Configuring Encoding/Decoding Protocols
•Configuring ISDN Channel Bonding Settings for Downspeeding
•Configuring Quality of Service Settings
•Configuring Alert Indications
•Configuring Gateway Resources for Calls
•Configuring Gateway Encryption
•Configuring Advanced Settings
•About DTMF Settings
•Configuring Advanced Commands
Configuring Basic Gateway Settings
In the Basics section of the Settings tab, you can set the gateway identifier, which is the name that the gateway uses when registering to a gatekeeper and when dialing to endpoints.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click the Basics button (if not already selected).
Step 4 In the Gateway Identifier field, type the gateway identifier.
Configuring IP Connectivity Settings
In the IP Connectivity section of the Settings tab, you can select the IP connectivity mode in which the gateway operates, set the address of the gatekeeper with which the gateway registers, and define the way in which the gateway interacts with the gatekeeper.
You can configure the IP connectivity mode in the following two ways:
•Using a gatekeeper—The gateway registers with a gatekeeper and uses the gatekeeper for every call (see the "Configuring the Gateway to Register With a Gatekeeper" section).
•Peer-to-Peer—The gateway connects directly to a peer device without the need for a gatekeeper (see the "Configuring the Gateway for Peer-to-Peer IP Connectivity" section). Peer devices include Cisco Unified CallManager.
Caution Changing the IP connectivity mode setting causes the gateway to reset.
Configuring the Gateway to Register With a Gatekeeper
In the IP Connectivity section of the Settings tab, you can configure the gateway to register with a gatekeeper.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click the IP Connectivity button.
Step 4 In the IP connectivity mode field, choose Using gatekeeper.
Step 5 Make one of the following selections:
–Select the Gatekeeper auto discover and register option button for the gateway to automatically search for and attempt to register to a gatekeeper.
–Select the Specify Gatekeeper address option button to specify the gatekeeper to which the gateway registers.
Step 6 In the Gatekeeper address field, do one of the following:
–Type the IP address of the gatekeeper to which the gateway registers.
—or—
–Click Browse.
The Discovered Gatekeepers dialog box appears, displaying all gatekeepers located on the same network segment as the gateway.
–Select a discovered gatekeeper.
–Click OK.
Step 7 In the Gatekeeper port field, type the port number of the gatekeeper. The default setting is 1719.
Step 8 Select the Registration refresh every n seconds check box to set the Time To Live interval (in seconds) that determines how often the gateway sends a "keep alive" message to the gatekeeper to ensure that the gateway registration is listed with the gatekeeper and does not expire. Enter a value in seconds in the field.
Step 9 In the Gateway registration mode field, choose the method of registration of services with the gatekeeper:
–Version 1—For gatekeepers that support H.323 version 1.
–Version 2—For gatekeepers that support H.323 version 2 or later.
Step 10 (PRI gateways only) Select the Unregister from Gatekeeper on ISDN connection failure check box to force the gateway to unregister from its gatekeeper when both ISDN D-channel connections are no longer active. The gatekeeper is forced to send new IP-to-ISDN calls through a different gateway, thus ensuring high call completion rates. The gateway re-registers to the gatekeeper when the ISDN connected is restored.
Step 11 the Select the Send load balancing messages (RAI) check box to enable the sending of RAI messages to the gatekeeper for the purpose of load balancing on the network. If you select this option, perform step 12 and step 13.
Gatekeepers can perform load balancing on the network using feedback from the gateway in the form of Resource Available Indication (RAI) messages that inform the gatekeeper of gateway resource availability. If the gateway is unavailable, the gatekeeper performs line hunting operations to route the call to an alternative gateway.
When you set the gateway for RAI/RAC, it sends periodic RAI messages that inform the gatekeeper of the current resource availability in the gateway. The gatekeeper responds with Resource Available Confirmation (RAC) messages to acknowledge receipt of the RAI messages. In step 12 and step 13, you can configure the upper and lower threshold for triggering RAI messages according to resource availability in the gateway.
Step 12 In the Send `busy' when load is more than field, enter the upper threshold for gateway resource utilization as a percentage of total resources. When resource use is greater than the threshold, the gateway sends the gatekeeper a `busy' RAI message, indicating to the gatekeeper that it should stop routing calls to this gateway.
Step 13 In the Send `free' when load is more than field, enter the lower threshold for gateway resource utilization as a percentage of total resources. When resource use is less than the threshold, the gateway sends the gatekeeper a `free' RAI message, indicating to the gatekeeper that it can resume routing calls to this gateway.
Configuring the Gateway for Peer-to-Peer IP Connectivity
In the IP Connectivity section of the Settings tab, you can configure the gateway for peer-to-peer IP connectivity.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click the IP Connectivity button.
Step 4 In the IP connectivity mode field, choose Peer-to-Peer.
Note Changing this setting causes the gateway to reset.
Step 5 In the Peer hunting mode field, choose one of the following options:
–Always start from first peer—The gateway attempts to connect a call to the first peer device on the Peer list section. If the call fails due to one of the H.323 call disconnect reasons (see the "About Peer-to-Peer H.323 Call Disconnect Reasons" section), the gateway tries each peer device in the Peer list section in order until the call is successfully connected. If the gateway fails to connect the call after trying all the peer devices on the list, it rejects the call.
–Always start from last successful peer—The gateway attempts to connect a call to the last peer device in the Peer list section with which a call was successfully established. An arrow in the Peer list section indicates with which of the peer devices a call was last connected successfully. If the call fails due to one of the H.323 call disconnect reasons (see the "About Peer-to-Peer H.323 Call Disconnect Reasons" section), the gateway tries each peer device in the Peer list section in order until the call is successfully connected. The arrow moves to the peer device with which the call connection is successful. If the gateway fails to connect the call after trying all the peer devices on the list, it rejects the call and the arrow indicates with which peer device a call was last connected successfully. This is the default setting.
–Round Robin—As for the Always start from last successful peer setting, except that the arrow advances to the next peer device in the Peer list section even if the call connection succeeds.
Note The peer hunting process starts when any of the following events occur: the gateway fails to establish a Transmission Control Protocol (TCP) connection to the specified peer device after a timeout; the gateway receives a "Release Complete" message from a peer device with a "No Resources" call rejection reason, or one of the other reasons that the Peer-to-Peer disconnect reason add advanced command specifies; or the gateway establishes a TCP connection to the specified peer device, but does not receive a valid H.323 message from the peer device after a timeout.
Step 6 In the Peer list section, you can configure peer devices currently configured to work with the gateway. The Peer list section displays all configured peer devices in a table with the following columns:
–Peer #—The sequential number of the peer in the list.
–Description—The description of the peer device.
–IP Address—The peer IP address.
–IP Port—The peer IP port number.
–Calls—Displays "Yes" or "No" to indicate whether or not there are currently any active calls between the peer and gateway.
To change the order of peer devices used in peer hunting, select a peer device and click the up or down arrow button to change its order.
To add or edit a peer device, click Add or select the peer device and click Edit. Perform the following steps in the Add peer or Edit peer dialog box:
–In the IP Address field, type or edit the peer IP address.
Note Two peers cannot have the same IP address or host name/Uniform Resource Locator (URL).
–In the IP Port field, enter or edit the peer IP port number.
–In the Description field, enter or edit the description of the peer.
–Click Upload.
Note You cannot add a single peer to the Peer list section more than once.
To delete a peer device, select the peer device and click Delete. Deleting a peer does not cause its active calls to disconnect, but no new calls are routed to the deleted peer.
Note The peer hunting process stops when one of the peer devices accepts the call or when the call is rejected with a disconnect reason. When a gateway has scanned the Peer list section and still cannot connect a call, the following rules apply: if at least one of the peers rejected the call due to capacity overload, the call rejection reason (towards the call originator) is "No Resources"; in all other cases, the call rejection reason is "Unreachable Destination."
Step 7 In the Peer hunting timeout (sec) field, enter the length of time (between 1 and 10 seconds) for which the gateway waits for a Transmission Control Protocol (TCP) response from each peer device contacted. The default value is 5 seconds.
Step 8 Select the Accept calls from defined peers only check box if you want the gateway to reject incoming calls from IP-side entities not defined in the peer list. If deselected, the gateway allows incoming calls from IP-side entities not defined in the Peer list section.
Step 9 In the Reject calls from peer devices when less than n B channels are free field, type the lower capacity threshold for rejecting calls from H.323 peer devices. The default setting is 6.
About Peer-to-Peer H.323 Call Disconnect Reasons
Table 3-6 lists the reasons for which the gateway peer-to-peer hunting module might disconnect a call.
Table 3-6 Peer-to-Peer H.323 Call Disconnect Reasons
Number
|
H.323 Call Disconnect Reason
|
1
|
There is no available bandwidth.
|
2
|
Gatekeeper resources have been exhausted.
|
3
|
The destination cannot be reached.
|
4
|
The destination rejected the transaction request.
|
5
|
Version is not compatible.
|
6
|
No permission to perform requested transaction.
|
7
|
The destination gatekeeper cannot be reached.
|
8
|
Gateway resources have been exhausted.
|
9
|
Destination address is not formatted correctly.
|
10
|
LAN crowding has caused the call to be dropped.
|
11
|
The destination is busy and cannot respond to the call transaction.
|
12
|
Undefined reason for transaction failure.
|
13
|
Call should be routed to a gatekeeper.
|
14
|
Call should be forwarded.
|
15
|
Call should be routed to an MC.
|
16
|
Call deflection has occurred.
|
17
|
Access denied.
|
18
|
The called party is not registered at the destination.
|
19
|
The calling party is not registered.
|
20
|
The connection failed and a new one should be made.
|
21
|
The called party has no H.245 capabilities.
|
22
|
Facility message sends conference list choice.
|
23
|
Request to establish H.245 connection.
|
24
|
An indication from an endpoint or a gatekeeper to send a new set of tokens in the tokens and/or cryptoTokens field of the Facility message.
|
25
|
Indicates that the purpose of the message is to update feature set information that was previously sent in the Facility message.
|
26
|
Indicates that the purpose of the message is to forward elements of another message, if that message cannot be sent.
|
27
|
Indicates that the purpose of the message is to transport higher-layer information.
|
Configuring IVR Settings
In the IVR section of the Settings tab, you can configure the gateway to route calls using an Interactive Voice Response (IVR) system.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click the IVR button.
Step 4 Select the type of IVR functionality:
–Use internal IVR—Enables the gateway IVR functionality so that incoming calls can route to an endpoint on the IP network. Follow step 5 to step 8.
Note The IVR must be enabled for the port that supports IVR.
–Use external IVR—Select to set the IP address and port number for an IVR system in another device. Follow step 9 and step 10.
Step 5 In the IVR registration name field, type the IVR registration alias used with the gatekeeper.
Step 6 Deselect the Transfer to Operator when `*' pressed during IVR check box to ignore the IVR operator digit (which is currently "*") and make it part of the dial string.
Step 7 In the IVR Operator Extension field, set the E.164 number of an endpoint that is registered with the gatekeeper to function as an IVR operator for incoming calls. To do this, type the same number for the IVR operator extension for each of the IP terminals that you want to include in the single number access. You can also use an ISDN endpoint as the IVR operator extension. To do this, define the IVR operator extension using the format <gateway service><ISDN number>.
Step 8 Select the IVR registers with gatekeeper check box to enable the internal IVR to register with the gatekeeper.
Step 9 In the IVR address field, type the IP address for the IVR system on the external device.
Step 10 In the Port field, type the port number for the IVR system on the external device. The default port setting is 1620.
Configuring Outgoing Call Delimiters
In the Delimiters section of the Settings tab, you can configure outgoing call delimiter characters.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click the Delimiters button.
Step 4 In the Second number delimiter field, type the character used as a second number delimiter for dialing more than one ISDN number in setting up a 2B call. You can use the pound sign (#), asterisk (*) or comma (,) as a delimiter in outgoing calls only.
Step 5 In the TCS4 extension delimiter field, type the character used as an extension number for TCS4 outgoing IP-to-ISDN call routing. You can use the pound sign (#), asterisk (*) or comma (,) as a delimiter in outgoing calls only. This setting does not apply for voice calls.
Note Since the comma cannot be used in the Party number field of the MCU Conference Control interface, we recommend that you do not use the comma as a second number delimiter or as a TCS4 extension delimiter.
About Encoding/Decoding Protocols
A number of video conferencing terminal applications require the G.722 and G.722.1 audio compression codecs to provide high quality voice communications. The G.722 and G.722.1 formats, using a digital sampling rate of 7 KHz, provide higher quality voice sampling with a greater dynamic range. The gateway does not transcode G.722 or G.722.1, but supports them transparently. Since the G.722 codec is of a much higher audio quality than other codecs and requires higher bandwidths, the gateway supports G.722 and G.722.1 at the following call bit rates:
•G.722 is supported in calls at 224, 256, 336, 384, 448, 512 Kbps (all gateways) and 768, 1472 and 1920 Kbps (PRI gateways only).
•G.722.1 is supported in calls at 64, 2B, and 128 Kbps.
Both endpoints in a call must support G.722 and G.722.1 audio codecs.
About Audio Transcoding
The Cisco Unified Videoconferencing 3527 PRI Gateway supports audio transcoding through on-board Digital Signal Processing (DSP).
The TCM is a PCI mezzanine card (PMC) that implements Digital Signal Processing (DSP). The TCM has a processing capacity of up to 20 channels for audio transcoding in video calls.
The gateway TCM can perform audio transcoding between the following types of audio protocols:
•G.711 (ISDN) to G.723.1 (IP)
•G.723.1 (IP) to G.711 (ISDN)
•G.728 (ISDN) to G.711 (IP)
•G.711 (IP) to G.728 (ISDN)
Note When your unit includes both a gateway and MCU, G.728 transcoding is supported on the MCU only.
Each audio codec differs in the audio quality, compression, and bit rates that it provides. The G.711 codec provides toll quality audio at 64 Kbps, the G.728 codec provides near toll quality audio at 16 Kbps, and the G.723.1 codec provides voice quality audio at 5.3 or 6.4 Kbps.
Endpoints on the ISDN network usually support the G.711 and G.728 codecs. Endpoints on IP networks support G.711 and G.723.1 codecs. By performing transcoding between these audio protocols, the gateway can support communication between endpoints with codecs that are incompatible with each other.
Audio transcoding can also optimize the audio bandwidth usage either on the IP network (G.723.1 < > G.711) or on the ISDN network (G.728 < > G.711). Transcoding is particularly useful for ISDN codecs, where bandwidth can be limited to 128 Kbps for a video call. For example, when transcoding between G.728 and G.711 takes place, the audio bandwidth usage is compressed to 16 Kbps. This provides an additional 40 Kbps of bandwidth to the existing video bit rate on the ISDN network, contributing to improved video quality.
Note The gateway automatically performs A-Law G.711-to-µ-Law G.711 translation between the IP and ISDN sides if needed.
You can configure the gateway to prioritize the transcoding, giving preference to a particular codec that is applied to calls, thus optimizing the resource allocation utilized by each call.
About T.120 Data Collaboration Support
The gateway provides full end-to-end support for T.120 data collaboration sessions, provided all terminals support the T.120 standard in their conferencing applications. In video calls with data transfer, the gateway accepts whatever bandwidth the ISDN connection defines for the data and dynamically adjusts the outgoing bandwidth used for data by using the MLP, HMLP and VarMLP formats.
If transcoding or T.120 capabilities are required, the gateway has to reserve resources for these. The gateway can differentiate between those calls that support T.120 and those that do not. When receiving calls, the gateway can check whether you are reserving resources for transcoding or for T.120 capabilities.
The gateway enables the user to determine the trade-off between the number of non-T.120 calls that the gateway can support and the number of calls sent with T.120 capabilities. The total number of calls that the gateway can support is accordingly reduced by this reallocation of resources.
The H.320 standard defines space allocation within a call. The H.320 standard defines the logic for bit rate allocation among audio, video and data channels in the context of the overall bit rate of a call. If you work with T.120, reallocation of bandwidth is always at the expense of available video resources. The requirements of the H.320 standard govern this reallocation—it is not configured in the gateway. The gateway simply decides whether or not to send T.120 capabilities. You configure T.120 capabilities in the Advanced section of the gateway interface Settings tab.
Configuring Encoding/Decoding Protocols
In the Media Modes section of the Settings tab, you can configure and prioritize encoding and decoding protocols.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click the Media Modes button.
Step 4 In the Transcoding priority field, choose the priority that determines the order of requested audio transcoding or choose Disable to disable audio transcoding priority.
Note When your unit includes both a gateway and an MCU, G.728 transcoding is supported on the MCU only.
Step 5 You can configure the following audio codec settings:
–Select the Enable G.722 check box to enable transparent support for the G.722 audio codec.
–Select the Enable G.722.1 check box to enable transparent support for the G.722.1 audio codec.
–Select the Enable G.728 check box to enable transparent support for the G.728 audio codec.
Step 6 You can configure the following video codec settings:
–Select the Enable H.263 check box to enable transparent support for the H.263 video codec.
–Select the Enable H.263+ check box to enable transparent support for the H.263+ video codec.
–Select the Enable H.264 check box to enable transparent support for the H.264 video codec.
Step 7 You can configure the following data settings:
–Select the Enable T.120 check box to enable transparent support for T.120 capabilities.
–Select the Enable FECC check box to enable transparent support for Far End Camera Control (FECC) capabilities.
Configuring ISDN Channel Bonding Settings for Downspeeding
In the Bonding section of the Settings tab, you can configure ISDN channel bonding parameters that affect downspeeding functionality.
Downspeeding is the ability to complete and maintain a call when ISDN conditions are bad. In downspeeding, call capabilities are automatically renegotiated when a call fails. Downspeeding contributes to a higher percentage of call completion on the network. The gateway supports downspeeding at call setup and in mid-call.
With downspeeding, when connection problems occur at call setup, the gateway attempts to connect a call at a lower bit rate than that requested. Administrators can configure the gateway to attempt to connect a video call at a specified minimum bit rate, or to attempt to connect the call as a voice call.
In downspeeding, when connection problems occur in mid-call, the gateway attempts to connect a video call at the specified lower bit rate. When downspeeding is complete and the call is connected at the specified lower bit rate, the gateway notifies the Internet Protocol (IP) endpoint of the new call rate.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click the Bonding button.
Step 4 Select the Enable bonding check box to enable ISDN bonding support.
Step 5 In the Maximum B channels for bonded call field, choose the maximum number of B channels—3, 4, 5, 6, 8, 12, 23 or 30—that you want to allow for a single bonded call. The default setting for PRI gateways is 30. The default setting for BRI gateways is 8.
When the number of B channels required to process a bonded call exceeds the number specified in this field, the gateway performs downspeeding as shown in Table 3-7.
Step 6 In the For bonded calls, allow downspeeding down to n B channels field, choose the minimum number of B channels that must be available before the gateway attempts to reconnect a video call.
Table 3-7 Downspeeding Policy Operation
Call Direction
|
Downspeed Advanced Command Parameter
|
If Call B Channels Exceed the Maximum:
|
IP (LAN) to WAN (ISDN)
|
enable (default)
|
Gateway tries to call at the maximum number of B channels
|
IP (LAN) to WAN (ISDN)
|
disable
|
Call disconnects
|
WAN (ISDN) to LAN (IP)
|
enable (default)
|
Call disconnects
|
WAN (ISDN) to LAN (IP)
|
disabled
|
Call disconnects.
|
Configuring Quality of Service Settings
You can configure the gateway to add a Quality of Service (QoS) IP precedence code in the IP header of outbound packets on the IP network. Routers on the network that support this method can give precedence to such coded packets and facilitate the transmission of the packets more efficiently. You can set priority levels on the gateway for voice calls, video calls, or both.
The Type of Service (TOS) field in the IP header contains eight bits and indicates the three abstract quality of service parameters:
Delay (D)
•Throughput (T)
•Reliability (R)
You can use the abstract parameters to choose the actual service parameters when transmitting a datagram through a particular network. The abstract parameters represent the three-way trade off between low delay, high throughput, and high reliability. Increasing the performance of one of the parameters can result in reduced performance of the other two. The TOS field in the IP header is shown in Figure 3-2.
Figure 3-2 TOS Field in the IP Header
Note The same fields can also be used to set DiffServ codepoint values
The function of each bit of the ToS field is as follows
•Bits 0-2: Precedence (an independent measure of the importance of the datagram)
•Bit 3: 0 = normal delay, 1 = low delay
•Bit 4: 0 = normal throughput, 1 = high throughput
•Bit 5: 0 = normal reliability, 1 = high reliability
•Bits 6-7: reserved for future use
The possible Precedence settings are as follows:
•111 = Network Control
•110 = Internetwork Control
•101 = CRITIC/ECP
•100 = Flash Override
•011 = Flash
•010 = Immediate
•001 = Priority
•000 = Routine
In the Quality of Service section of the Settings tab, you can assign a priority level to video and voice calls.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click the Quality of Service button.
Step 4 In the Quality of service support field, select one of the following option buttons:
–None—Select to disable quality of service support.
–Default (recommended)—Select to assign the default IP Type of Service (ToS) value for each media type.
–Custom—Select to assign your own IP ToS value for each media type. You can configure the following additional settings:
•In the Control Priority (0-63) field, enter a whole number from 0 to 63 to set the priority level of signaling packets that the gateway sends out. The default value is 26.
•In the Video Calls section Voice Priority (0-63) field, enter a whole number from 0 to 63 to set the priority level of voice packets that the gateway sends out. The default value is 34.
•In the Video Priority (0-63) field, enter a whole number from 0 to 63 to set the priority level of video packets that the gateway sends out. The default value is 34.
•In the Data Priority (0-63) field, enter a whole number from 0 to 63 to set the priority level of data packets that the gateway sends out. The default value is 26.
•In the Voice Calls section Voice Priority (0-63) field, enter a whole number from 0 to 63 to set the priority level of voice packets that the gateway sends out. The default value is 46.
Note You can click Restore Defaults to restore all default settings.
Configuring Alert Indications
In the Alert Indications section of the Settings tab, you can select which events trigger Simple Network Management Protocol (SNMP) traps. You can also define multiple SNMP servers to which the gateway sends the SNMP traps.
Note The gateway supports traps in the SNMPv1 format.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click the Alert Indications button.
Step 4 In the Events section, select events in the Disabled events field and click Add to select an event to monitor. Or, select an event in the Enabled events field and click Remove to remove that event from monitoring.
Step 5 Select the Send SNMP Traps check box to configure the IP address of the SNMP server to which the gateway sends SNMP trap notifications of the events selected in the Enabled events field. You can configure up to three different SNMP trap servers.
Step 6 In the Trap server IP and Port fields, enter the IP address and port number for each SNMP server to which you want the gateway to send SNMP trap notifications. To remove an SNMP server, set the SNMP server IP address to 0.0.0.0 and press the Upload button.
Related Topics
•Gateway Event Types
•Trap Severity Enumeration
Gateway Event Types
Table 3-8 lists proprietary Cisco SNMP trap event types for the Cisco Unified Videoconferencing 3527 PRI Gateway, as detailed in the RvTrapEventType textual convention.
Table 3-9 lists SNMP trap event types for the Cisco Unified Videoconferencing 3522 BRI Gateway, as detailed in the RvTrapEventType textual convention.
Note In certain cases, after a problem that caused a trap to be sent has been solved, an identical clearing trap is sent to indicate that the problem has been solved. The severity of the clearing trap is always 0. The trap OID and the RvTrapEventType value of the clearing trap are identical to those of the original trap sent when the problem occurred. The sending of a clearing trap is indicated by a severity level of "Clear".
Table 3-8 Cisco Unified Videoconferencing 3527 PRI Gateway SNMP Trap Event Types
Event Type
|
Trap is sent when ...
|
State
|
Severity
|
RAI status
|
A change in RAI status occurs.
|
TRUE
|
Warning
|
FALSE
|
Clear
|
Bad video
|
Corrupt or empty video packets are present in the gateway. Includes the ID number of the call during which the event occurs.
|
TRUE
|
Minor
|
FALSE
|
Clear
|
Power-up
|
The gateway has started to operate.
|
|
Information
|
Power-down
|
The gateway is shutting down.
|
|
Information
|
Gatekeeper registration state change
|
A change occurs in the registration status of the gateway.
|
TRUE
|
Clear
|
FALSE
|
Minor
|
Loss of ISDN
|
A state change occurs for each enabled ISDN line.
|
TRUE
|
Critical
|
FALSE
|
Clear
|
Loss of Ethernet
|
The network returns after going down. Indicates the time at which the network was restored.
|
TRUE
|
Critical
|
FALSE
|
Clear
|
Max resource meter
|
A call could not be established because of a lack of one of the following resources—CPU, audio transcoder, DTMF detector or T.120 resources.
|
|
Warning
|
Network problem
|
A problem occurs on the network.
|
TRUE
|
Major
|
FALSE
|
Clear
|
Card extract/Hot Swap
|
A card has been removed from the Cisco chassis under power or inserted into the chassis under power, or the when the gateway enters maintenance mode.
|
TRUE
|
Critical
|
FALSE
|
Clear
|
Abnormal disconnect
|
A call has disconnected for a reason other than normal, busy or no answer.
|
|
Warning
|
ISDN downspeed
|
ISDN downspeeding to a lower rate is taking place.
|
|
Warning
|
Corrupt IVR messages on host
|
Corrupt IVR files are present in the gateway.
|
|
Warning
|
Corrupt WEB data
|
Corrupt web files are present in the gateway.
|
|
Major
|
ISDN rollover activated
|
The gateway notifies the PSTN switch that the gateway cannot accept any further calls.
ISDN rollover requires support by the PSTN switch application and presumes the availability of a pool of stacked gateways across the managed network.
You can enable ISDN Rollover only after you set the gateway to work with the T1 interface.
|
|
Major
|
Call to peer rejected - trying alternate
|
A call to a peer has been rejected and the gateway is searching for an alternate peer.
|
|
Warning
|
Call from peer rejected due to capacity
|
A call from a peer has been rejected because the gateway does not have enough resources available.
|
|
Warning
|
Call to peer rejected by all listed peers
|
A call to a peer has been rejected by all listed peers.
|
|
Major
|
Call to peer failed - peer list empty
|
A call to a peer has failed because the peer list is empty.
|
|
Major
|
Incompatible sw version install
|
An attempt to burn a version of the gateway software onto incompatible hardware occurs.
|
|
Warning
|
Call from non-peer H.323 entity rejected
|
The gateway has rejected an incoming IP call because the source does not appear in the peer list.
|
|
Warning
|
Table 3-9 Cisco Unified Videoconferencing 3522 BRI Gateway SNMP Trap Event Types
Event Type
|
Trap is sent when ...
|
State
|
Severity
|
RAI status
|
A change in RAI status occurs.
|
TRUE
|
Warning
|
FALSE
|
Clear
|
Bad video
|
Corrupt or empty video packets are present in the gateway. Includes the ID number of the call during which the event occurs.
|
TRUE
|
Minor
|
FALSE
|
Clear
|
Power-up
|
The gateway has started to operate.
|
|
Information
|
Power-down
|
The gateway is shutting down.
|
|
Information
|
Gatekeeper registration state change
|
A change occurs in the registration status of the gateway.
|
TRUE
|
Clear
|
FALSE
|
Minor
|
Loss of ISDN
|
A state change occurs for each enabled ISDN line.
|
TRUE
|
Critical
|
FALSE
|
Clear
|
Loss of Ethernet
|
The network returns after going down. Indicates the time at which the network was restored.
|
TRUE
|
Critical
|
FALSE
|
Clear
|
Max resource meter
|
A call could not be established because of a lack of one of the following resources—CPU, audio transcoder, DTMF detector or T.120 resources.
|
|
Warning
|
Network problem
|
A problem occurs on the network.
|
TRUE
|
Major
|
FALSE
|
Clear
|
Card extract/Hot Swap
|
A card has been removed from the Cisco chassis under power or inserted into the chassis under power, or the when the gateway enters maintenance mode.
|
TRUE
|
Critical
|
FALSE
|
Clear
|
Abnormal disconnect
|
A call has disconnected for a reason other than normal, busy or no answer.
|
|
Warning
|
ISDN downspeed
|
ISDN downspeeding to a lower rate is taking place.
|
|
Warning
|
Corrupt IVR messages on host
|
Corrupt IVR files are present in the gateway.
|
|
Warning
|
Corrupt WEB data
|
Corrupt web files are present in the gateway.
|
|
Major
|
ISDN rollover activated
|
The gateway notifies the PSTN switch that the gateway cannot accept any further calls.
ISDN rollover requires support by the PSTN switch application and presumes the availability of a pool of stacked gateways across the managed network.
You can enable ISDN Rollover only after you set the gateway to work with the T1 interface.
|
|
Major
|
Call to peer rejected - trying alternate
|
A call to a peer has been rejected and the gateway is searching for an alternate peer.
|
|
Warning
|
Call from peer rejected due to capacity
|
A call from a peer has been rejected because the gateway does not have enough resources available.
|
|
Warning
|
Call to peer rejected by all listed peers
|
A call to a peer has been rejected by all listed peers.
|
|
Major
|
Call to peer failed - peer list empty
|
A call to a peer has failed because the peer list is empty.
|
|
Major
|
Incompatible sw version install
|
An attempt to burn a version of the gateway software onto incompatible hardware occurs.
|
|
Warning
|
Call from non-peer H.323 entity rejected
|
The gateway has rejected an incoming IP call because the source does not appear in the peer list.
|
|
Warning
|
Trap Severity Enumeration
Table 3-10 describes the proprietary Cisco gateway SNMP trap severity enumerations.
Table 3-10 Proprietary Cisco Gateway SNMP Trap Severity Enumerations
Trap Severity
|
Enumeration
|
Description
|
Cleared
|
0
|
One or more previously reported alarms have been cleared.
|
Information
|
1
|
Notification of a non-erroneous event.
|
Critical
|
2
|
A service-affecting event has occurred and immediate corrective action is required.
|
Major
|
3
|
A service-affecting event has occurred and urgent corrective action is required.
|
Minor
|
4
|
A non-service-affecting event has occurred and corrective action is required to prevent the condition becoming more serious.
|
Warning
|
5
|
A potential or impending service-affecting event has been detected, but no significant affects have been felt yet. Action should be taken to further diagnose and correct the problem to prevent the condition becoming more serious.
|
Configuring Gateway Resources for Calls
Note The Resources section is available in Cisco Unified Videoconferencing 3527 PRI Gateway only.
In the Resources section of the Settings tab, you can reserve gateway resources for T.120 enabled calls and for audio transcoded video calls. This section also displays the total number of calls that the gateway supports at specified bandwidths.
The gateway provides full end-to-end T.120 data collaboration sessions, provided that all terminals support the T.120 standard in their conferencing applications. In video calls with data transfer, the gateway accepts whatever bandwidth the ISDN connection defines for the data and dynamically adjusts the outgoing bandwidth used for data by using the MLP, HMLP and VarMLP formats.
You can also configure the gateway to prioritize the transcoding, giving preference to a particular codec that is applied to calls, thus optimizing the resource allocation utilized by each call.
The gateway supports up to 30 video calls on two B channels. If transcoding or T.120 capabilities are required, the gateway has to reserve resources for these. The gateway can differentiate between those calls that support T.120 and those that do not. When receiving calls, the gateway can check whether you are reserving resources for transcoding or for T.120 capabilities.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click the Resources button.
Step 4 In the Maximum number of T.120 calls field, enter the number of T.120 enabled calls that you want to reserve gateway resources for. The maximum number is 18.
Step 5 In the Maximum number of video calls with audio transcoding field, enter the number of audio transcoded video calls you want to reserve gateway resources for. The maximum number is 20.
Note The term audio transcoded video calls refers to the process whereby an audio stream in a multimedia call is transcoded from one codec type to another.
Step 6 In the Total call capacity: n calls of n Kbps field, choose a bandwidth.
Step 7 Click Update total call capacity.
The number of calls that the gateway can support at that bandwidth automatically appears.
Configuring Gateway Encryption
The gateway supports encrypted calls over IP networks. The encryption conforms to the H.325 standard and supports the following encryption algorithms:
•DES—With an encryption key of 56 bits
•AES—With an encryption key of 128 bits
Gateway encryption operates in one of the following modes or can be disabled entirely:
•Best effort—Implements a "best effort" encryption algorithm. If an endpoint supports encryption, it connects in an encrypted way. If not, it connects without encryption.
•Encryption required—Only connects encrypted calls. Encryption can either be AES 128 or DES 56. The gateway does not allow non-encrypted calls to connect.
•Strong encryption required—Only allows AES 128 encrypted calls. The gateway does not allow endpoints that do not support AES 128 to connect.
Table 3-11 summarizes the encryption-related capabilities that the gateway offers.
Table 3-11 Gateway Supported Encryption Capabilities
Mode
|
Capabilities
|
Encryption off
|
Priority 1: No encryption
|
Best effort
|
Priority 1: AES 128
Priority 2: DES 56
Priority 3: No encryption
|
Encryption required
|
Priority 1: AES 128
Priority 2: DES 56
|
Strong encryption required
|
Priority 1: AES 128
|
The following channels support encryption:
•Audio channel
•Video Channel
•Far End Camera Control (FECC)
Note All channels (audio, video and FECC, incoming, outgoing) on the same call must have the same encryption levels. If the same encryption on all channels is not achieved, the call disconnects.
In the Security section of the Settings tab, you can configure gateway encryption settings.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click the Security button.
Step 4 Select the Support encryption check box to enable gateway support for H.235 encryption for H.323 calls.
Step 5 In the Encryption mode field, choose one of the following settings:
–Best effort
–Encryption required
–Strong encryption required
Configuring Advanced Settings
In the Advanced section of the Settings tab, you can configure, enable, and disable various advanced gateway settings.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click the Advanced button.
Table 3-12 explains the IP-to-ISDN call settings you can configure in this section.
Table 3-13 explains the ISDN-to-IP call settings you can configure in this section.
Table 3-14 explains the IP call settings you can configure in this section.
Table 3-15 explains the ISDN call settings you can configure in this section (available in Cisco Unified Videoconferencing 3527 PRI Gateway only).
Table 3-16 explains the general call settings you can configure in this section.
Table 3-12 Advanced Settings—IP to ISDN Calls
Field or Check Box
|
Description
|
Conceal caller ID
|
Select to have the gateway hide the identifier of the calling endpoint on the IP network, regardless of whether the Support Presentation Restriction advanced setting is selected. The callerID field of the Q.931 message is sent over the ISDN network empty.
|
Ignore caller bearer rate and force service rate
|
Select to configure the gateway to ignore the incoming call bearer rate and to use instead the bandwidth specified for the service in the Services tab to process the call. If the service bit rate is set to Auto, the gateway process the call at the bearer rate.
Deselect to allow an administrator to limit a specific service to a maximum bit rate. When deselected and the bearer rate is greater than the service rate, the gateway processes the call at the service rate. When deselected and the bearer rate is lower than or equal to the service rate, the gateway processes the call at the bearer rate. If the bearer bit rate is set to Auto, the gateway process the call at the bearer rate.
|
Auto dial voice call in case of video call fail
|
Select to instruct the gateway to attempt to reconnect video calls as voice calls after a video call has failed at call setup. The gateway uses the auto-redial mechanism for outgoing video calls when any of the ISDN disconnect reasons listed below occur.
When selected, the gateway first tries to redial the call as a restricted video call at 56 Kbps. If the call fails for any of the reasons listed below, the gateway tries to redial the call as a voice call.
When deselected, the call disconnects.
The gateway log indicates both the disconnect reason and the gateway attempt at redialing.
Note The auto-redial mechanism operates independently of the downspeeding functionality.
The ISDN disconnect reasons are:
•0x12—No user responding.
•0x39—Bearer capacity not authorized.
•0x3a—Bearer capacity not presently available.
•0x3f—Reports a "service or option not available" event only when no other cause in the "service or option not available" class applies.
•0x4f—Reports a "service or option not implemented" event only when no other cause in the "service or option not implemented" class applies.
•0x41—Bearer capability not implemented.
•0x45—Requested facility not implemented.
•0x58—Incompatible destination.
|
Use default service bit rate of n kbps for services defined to use `auto' bit rate
|
Choose the default bit rate. When using a service with the bit rate set to Auto, the gateway uses the default bit rate if the received bearer rate is not one of the supported bit rates.
|
Table 3-13 Advanced Settings—ISDN to IP Calls
Field or Check Box
|
Description
|
Conceal caller ID
|
Select to have the gateway hide the identifier of the calling endpoint on the ISDN network, regardless of whether or not the Support Presentation Restriction advanced setting is selected. The callerID field of the Q.931 message is sent over the IP network containing the string "0000."
|
Enable T.120 capabilities in incoming IVR and TCS4 calls
|
Select to enable the gateway to send T.120 capabilities messages to the ISDN endpoint upon receiving a call at the IVR-internal or TCS4 stage. The gateway sends the T.120 messages before connecting to the IP network endpoint.
|
Support sub-address at Call Setup
|
Sub-addressing is a one-stage Direct Inward Dialing (DID) dialing mechanism in which a phone sends two numbers. One number is for routing on the circuit switched network. The other number is forwarded to the gateway inside a Q.931 sub-addressing information element for IP address resolution by the gatekeeper.
Sub-addressing can also be used for implementing ISDN fallback when not enough bandwidth is available for routing an IP-oriented call over IP.
Select for the gateway to take the E.164 number from the Q.931information element sub-address field and forward it to the gatekeeper for address resolution. Sub-addressing requires gatekeeper support.
|
Table 3-14 Advanced Settings—IP Options
Field or Check Box
|
Description
|
Support H.323 Fast Start in voice-only call setup
|
The H.323 fast start functionality enables endpoints that support the feature to join a voice conference in the gateway more quickly.
Standard call setup requires four round trips of messages between endpoints before the first media stream is exchanged between peers. The set of messages includes Setup/Connect (Q.931 procedure), Master/Slave Determination (H.245 procedure), Capability Exchange (H.245) and Open Logical Channel (H.245).
H.323 fast start shortens the time it takes to start a call by skipping the H.245 phase and combining the call setup procedure into a single H.225 transaction.
Select to encapsulate H.245 capabilities exchange and negotiation messages within Q.931 setup messages.
|
Enable packet handling (may increase call delay)
|
Select to configure the maximum rate of jitter tolerance in the Network jitter tolerance field. Jitter occurs when IP packets sent at a steady rate reach their destination at different speeds. Streams can also split on their way to the gateway between different routers. This can cause a "later" packet B to arrive before an "earlier" packet A, even though A was sent before B.
|
Network jitter tolerance
|
If you selected the Enable packet handling (may increase call delay) check box, then enter the maximum rate of jitter tolerate in milliseconds. Packet loss occurs when jitter exceeds the configured rate.
|
Table 3-15 Advanced Settings—ISDN Options
Field or Check Box
|
Description
|
Request ISDN rollover when less than n B channels are available (available in Cisco Unified Videoconferencing 3527 PRI Gateway only)
|
Select to define when the gateway uses the ISDN rollover feature (which is defined in advanced commands—see the "Configuring Advanced Commands" section for more information). When the total number of available B channels in both PRI ports falls below the number specified in this field, the gateway sends a "busy out" message to the PSTN switch for each of the remaining B channels. The switch application "busies out" the remaining B channels and diverts new calls to other gateways on the network with greater available resources. This setting is only active after you configure the gateway to use a 4ESS PRI line.
For example, you specify 10 in the Request ISDN rollover when less than n B channels are available field and the number of available B channels falls to 9. The gateway sends a "busy out" request message to the PSTN switch. The PSTN switch application routes new calls through other gateways on the network. When the total number of available B channels returns to at least 10, the gateway sends a "busy out" cancellation message to the PSTN switch indicating the restored ability to receive calls. The PSTN switch makes the "busied out" lines available and attempts attempt to route new calls through the gateway.
|
Table 3-16 Advanced Settings—General
Field or Check Box
|
Description
|
Restrict Gateway use to MCU conferences only
|
Select for the gateway to send and receive calls to and from a Cisco Unified Videoconferencing 35xx MCU only. This setting, together with a scheduling server, reserves resources for scheduled conferences only.
|
Support Presentation Restriction
|
Select to enable support for the presentation restriction feature. This feature responds to an instruction from the calling endpoint to forward or to conceal the endpoint identifier.
|
Support H.239
|
Select to enable support for dual video channels using the H.239 protocol. This setting is selected by default.
When selected, the gateway supports H.239 in ISDN-to-IP calls and in IP-to-ISDN calls. The gateway identifies the protocol version that an IP endpoint uses and sends H.239 capabilities only to those endpoints working with protocol version 4.0 or later. H.239 support has no impact on gateway capacity.
We recommend that you do not enable this feature if you establish communication with endpoints that do not support H.245 generic capabilities (endpoints based on H.323 version 2 or earlier) as this might cause the endpoints to fail upon receiving these capability exchanges.
|
About DTMF Settings
The Cisco Unified Videoconferencing 3500 Gatewayperforms Dual Tone Multi-Frequency (DTMF) detection on IP-to-ISDN calls and on ISDN-to-IP calls. The gateway can send DTMF tone information to the IP endpoint in-band only, or both in-band and out-of-band. The gateway sends DTMF tone information to the ISDN endpoint in-band only.
About DTMF
The signal generated by a DTMF encoder is a direct algebraic summation, in real time, of the amplitudes of time sine (or cosine) waves of different frequencies.
An example of the use of DTMF is in touch tone telephone dialing. DTMF tones are sent out as you dial. For example, pressing "1" sends a tone created by combining frequencies of 1209 Hz and 697 Hz.
The touch tone system uses pairs of tones to represent the various keys on the telephone. A "low tone" and a "high tone" are associated with each button (0-9, *, and #). The low tones vary according to the horizontal row in which the tone button is located in Table 3-17. The high tones correspond to the vertical column in which the tone is located. The local telephone company receives each pair of tones, decodes the number dialed and makes the connection.
Table 3-17 DTMF Tone Assignments
| |
1209 Hz
|
1336 Hz
|
1477 Hz
|
1633 Hz
|
697 Hz
|
1
|
ABC
2
|
DEF
3
|
A
|
770 Hz
|
GHI
4
|
JKL
5
|
MNO
6
|
B
|
852 Hz
|
PRS
7
|
TUV
8
|
WXY
9
|
C
|
941 Hz
|
*
|
oper
0
|
#
|
D
|
About DTMF Detection on IP-to-ISDN Calls
The gateway passes incoming in-band DTMF signals to the ISDN-side endpoint unchanged. In addition, you can configure the gateway to convert H.245 out-of-band DTMF signals from the IP side to in-band signals on the ISDN side. Figure 3-3 illustrates IP-to-ISDN DTMF processing.
Figure 3-3 IP-to-ISDN DTMF Processing
About DTMF Detection on ISDN-to-IP Calls
The gateway passes incoming in-band DTMF signals to the IP-side endpoint unchanged. In addition, you can configure the gateway to convert in-band DTMF signals from the ISDN side to H.245 out-of-band signals on the IP side. Figure 3-4 illustrates ISDN-to-IP DTMF processing.
Figure 3-4 ISDN-to-IP DTMF Processing
Configuring DTMF Settings
You can enable DTMF detection and settings in the Advanced section of the Settings tab.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click the Advanced button.
Step 4 In the IP to ISDN Calls section of the PRI gateway and the BRI gateway, you can select the Translate DTMF from IP out-of-band (H.245) to ISDN in-band (G.711 only) check box.
When selected, the gateway performs the following:
–Converts H.245 out-of-band DTMF signals coming from the H.323 IP-side endpoint to in-band signals on the ISDN side.
–Passes incoming in-band DTMF signals to the ISDN-side endpoint unchanged.
This setting is selected by default. If deselected, the gateway passes in-band DTMF signals to the ISDN-side endpoint unchanged.
Step 5 In the ISDN to IP Calls section of the PRI gateway and the BRI gateway, you can select the Duplicate DTMF signal from ISDN side as out-of-band on IP side check box.
When selected, the gateway performs the following:
–Converts in-band DTMF signals from the ISDN-side endpoint to out-of-band H.245 signals if the IP-side endpoint is located on an H.323 network.
–Passes incoming in-band DTMF signals to the IP-side endpoint unchanged.
This setting is selected by default. If deselected, the gateway passes in-band DTMF signals to the IP-side endpoint unchanged. If you do select this setting, perform step 6.
Step 6 In the Apply to field of the PRI gateway and the BRI gateway, choose the type of calls to which ISDN-to-IP DTMF processing applies: Voice calls or Voice and video calls. Voice calls is the default setting.
Tip Enabling DTMF detection for PRI gateway video calls reduces the number of supported calls at 128 Kbps from 30 to 22.
Configuring Advanced Commands
You can send text-based commands to the gateway for enhanced control. You can use these advanced commands to change certain settings in real time and monitor information such as debug information. Advanced commands are not case sensitive.
Table 3-18 describes common advanced commands.
Table 3-18 Advanced Command Settings
Command
|
Description
|
AddService2SrcNum
|
Notifies the IP endpoint of the gateway service number to which the ISDN-side endpoint has called.
Parameters: disable/enable.
|
CallSignalPort
|
Notifies the gatekeeper to which the gateway is registered on which port to communicate.
Parameters: 1000 to 3000.
Remarks: The number must be unique and not used for any other purpose.
|
DownSpeed
|
Instructs the gateway to support downspeeding.
Parameters: disable/enable.
|
EnhancedBillingForVoiceCalls
|
Instructs the gateway to support the CDR Real Connect Time field. Real Connect Time indicates the actual time at which an IP-to-ISDN voice call connects to the ISDN terminal.
When disabled, the Connect Time field is used for CDR billing purposes. Connect Time indicates the time at which the Connect message is sent to the source endpoint.
Parameters: disable/enable.
Remarks: Default value is disable. Relevant to voice calls only.
|
ForceG711ForMcu
|
Instructs the gateway to open only a G.711 channel in gateway-to-MCU calls.
Parameters: disable/enable.
|
NotifyLevel
|
Changes the type and number of debug messages that are generated.
Parameters:
0—Disables gateway logs.
3 (default)—Fatal error (gateway can no longer provide service), a problem affecting user functionality (for example, call connect failure or no resources available), or status prints for Customer Support use.
6—Debugging.
8—Extended debugging.
Remarks: We recommend that you do not exceed a NotifyLevel of 6 as this might overload the system with a very large debug message output. Level 3 should be sufficient for normal usage.
|
Peer-to-Peer disconnect reason add
|
Instructs the gateway under which circumstances to reroute a call to different peer device.
Parameters: Enter a number representing the required H.323 call disconnect reason, as listed in Table 3-6.
|
Peer-to-Peer disconnect reason remove
|
Deletes the H.323 Call Disconnect Reason set by the Peer-to-Peer disconnect reason add advanced command.
Parameters: ALL—Enter a number representing the required H.323 call disconnect reason, as listed in Table 3-6.
|
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the Settings tab.
Step 3 Click the Advanced button.
Step 4 Click Commands.
The Advanced Commands dialog box appears.
Step 5 Configure an advanced command by one of the following methods:
–In the Command field, enter a command.
–In the Parameters field, enter the parameters for the command.
—or—
–In the Available commands field, select one of the advanced commands.
–In the Available parameters field, choose from one of the parameters that appears.
Step 6 Click Send.
In the Response field, the gateway indicates whether it received and executed the command. If you send an invalid command, an "Unknown Command" message appears.
About Gateway Services
Gateway services are the mechanism that allows IP network endpoints to choose the type of connection they want to establish with a terminal or telephone on a circuit-switched network. A gateway service defines the maximum bit rate for each channel, the media content of the stream (voice or data), and the mode of the call (restricted or non-restricted).
A service prefix identifies a service. The service prefix is an identifier string that can have up to 31 characters. Valid characters are 0 to 9, pound (#), asterisk (*), or comma (,). You access a service by dialing the service prefix before the phone number of the destination. For example, 9* would be identified by the gateway as a service prefix if you dialed 9*5673994.
Note If the Ignore caller bearer rate and force service rate setting in the Advanced section of the Settings tab is selected, a service uses the defined bit rate. If the Ignore caller bearer rate and force service rate setting is deselected, the bit rate defined in the service serves as the maximum limit for the service.
The gateway has two types of services: default and user-defined. Default services come pre-configured on the gateway. User-defined services are services that you can define at any time using the gateway interface. Upon registration with a gatekeeper, the gateway provides the gatekeeper with a list of gateway services.
The following topics discuss how you can configure services in the Services tab:
•Viewing Existing Services
•Adding or Editing Services
•Deleting Gateway Services
Viewing Existing Services
The Services tab in the gateway interface displays a list of currently defined services for the gateway in a table format with the following columns and fields:
•Prefix—Displays the prefix that identifies the service.
•Description—Description of the service.
•Call Type—Media type of the call.
•Bit Rate—Total bandwidth requested for the service.
•PRI Port/BRI Port 1 to 4—Indicates whether or not the service is enabled for the specified port.
•Total—Displays the total number of services currently defined in the gateway.
Adding or Editing Services
In the Services tab, you can add a new service or edit an existing one.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the Services tab.
Step 3 To add a new service, click Add. To edit an existing service, select it and then click Edit.
Step 4 In the Prefix field, enter or edit the prefix number of the service. The prefix can be up to 31 characters long. Valid characters are 0 to 9 and pound sign (#), asterisk (*), and comma (,).
Note Since the comma cannot be used in the Party number field of the Cisco MCU Conference Control interface, we recommend that you do not use the comma as a prefix in gateway fields.
Step 5 In the Description field, enter or edit the description of the service (up to 31 characters in length).
Step 6 In the Call type field, select the call type for this service: Video or Voice.
Step 7 In the Bit rate field, select the maximum bit rate you want for this service. If you select Auto, the gateway determines the ISDN call rate according to the bearer capability received in the setup message from the IP network endpoint.
Note The Auto setting is for video calls only.
If the IP network endpoint has a configured bit rate that is not one of the options listed in this field, the gateway uses the default bit rate configured in the Default Service Bit Rate field in the Advanced section of the Settings tab.
Note If the Ignore caller bearer rate and force service rate field is selected when you define a bit rate for a service, the service uses the defined bit rate. If the Ignore caller bearer rate and force service rate is deselected, the bit rate you define serves as the maximum limit for that service.
Related Topics
•Bonding Synchronization
Bonding Synchronization
The Advanced dialog box enables you to configure a bonding synchronization setting for the specified service.
Procedure
Step 1 Send the ServiceOption advanced command with a parameter of enable to activate the Advanced button.
For information on sending advanced commands, see the Configuring Advanced Commands.
Step 2 Click Advanced to configure bonding synchronization settings.
The Advanced dialog box appears.
Step 3 In the Bonding Synchronization field, choose a bonding synchronization setting. Select Prolong only for endpoints that use non-standard synchronization mechanisms.
Step 4 Click OK to save your setting and close the Advanced dialog box.
Step 5 Click the Port Specific tab.
Step 6 In the Enable service in ports section, select the BRI or PRI ports that are enabled for this service.
Step 7 Click OK.
The gateway interface uploads your settings to the services database.
Deleting Gateway Services
In the Settings tab, you can delete existing services.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the Services tab.
Step 3 Select a service and click Delete.
Configuring Port Settings
In the PRI Port or BRI Port tabs, you can configure physical line settings for gateway ports. The following topics discuss the settings you can configure.
•Configuring Basic Port Settings
•Configuring Port Physical Interface Settings
•About Advanced ISDN Settings for PRI Gateways
•Configuring Port Call Policies
•Configuring Port Supported Services
Note Some configuration options are unavailable in gateways that support only one PRI port.
Configuring Basic Port Settings
In the Basics section of the PRI Port or BRI Port tabs, you can configure basic settings for the specified port.
Note (PRI gateways only) A frame alignment failure message will appear when you enable a port that is not in use (no cable is attached to the PRI line connector).
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the applicable PRI Port or BRI Port tab.
Step 3 Select the Port enabled check box to enable this port. For PRI gateways, if this setting is deselected, the CD LED light on the rear panel of the gateway is disabled.
Step 4 (PRI gateways only) In the Port phone numbers section, choose one of the following option buttons:
–Single Number—Defines a single number for this PRI port. Enter a phone number in the field.
–Range—In the two fields, enter a range of numbers for this PRI line. If the line has a range of numbers, you only need to enter the digits necessary to indicate the range. For example, if the phone numbers assigned to this line are 6775380 to 6775411, enter 380-411. You can type a maximum of 31 digits in each text field.
Step 5 (PRI gateways only—optional) In the Local Area Code field, enter the local area code for the phone numbers. You can enter up to 16 digits.
Step 6 (PRI gateways only—optional) Select the Strip Local Area Code check box if you want the gateway to strip local area codes for outbound calls to the ISDN network.
Note The type of line connected to this PRI or BRI port appears in the Physical standard field.
Configuring Port Physical Interface Settings
This section describes the available configuration options for gateway ports.
•PRI Ports
•BRI Ports
PRI Ports
Note This section applies only to Cisco Unified Videoconferencing 3527 PRI Gateway.
In the Physical Interface section of the PRI Port tab, you can configure the physical line properties of the PRI port.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the PRI Port tab.
Step 3 Click the Physical Interface button.
Step 4 Select the Same as Port check box if you want to duplicate physical interface settings from another PRI port that you choose from the field. When selected, you cannot modify any settings in this section. This option is not available in gateways that support only one PRI port.
Step 5 In the Interface field, choose the line interface: T1 or E1.
Step 6 In the Country field, choose the nation where the ISDN service is installed.
Step 7 In the Signaling protocol field, choose the signaling protocol used to set up and tear down the calls through the signaling (D) channel. Depending on the interface used, different signaling protocols are available.
Step 8 In the Network access field, choose the gateway national access type: TE (Terminal Equipment) or NT (Network Terminator) device.
Step 9 In the Clock source field, choose the gateway clock source:
–Master (the gateway provides the clock signal)
–Slave (the gateway receives the clock signal)
Step 10 In the Line Build Out field, choose Long Haul or Short Haul.
Note You can configure this setting only if you select Japan in the Country field. Skip to step 4 otherwise.
Related Topics
•Configuring Fractional Channels
•Configuring Line Coding, Framing and Signaling Type
Configuring Fractional Channels
In the Physical Interface section of the PRI Port tab, you can configure fractional channels as part of the physical line properties of the PRI port.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the PRI Port tab.
Step 3 Click the Physical Interface button.
Step 4 Click Fractional to select fractional channels.
The Fractional dialog box appears.
Step 5 Select the Fractional line check box to enable the fractional selection of channels.
Step 6 In the Select the channels field, select the check boxes for the individual channels you want to use for fractional E1 or T1 distribution. The table contains 24 check boxes for T1 or 31 check boxes for E1.
Note You cannot select channel 24 of the T1 settings and channel 16 of the E1 settings. These are reserved as the signaling (D) channels that are essential for communication.
Note You can click Select All to select all fractional channels or Deselect All to deselect all fractional channels.
Step 7 Click OK to close the Fractional dialog box.
Configuring Line Coding, Framing and Signaling Type
In the Physical Interface section of the PRI Port tab, you can configure coding, framing, and signaling type settings as part of the physical line properties of the PRI port.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the PRI Port tab.
Step 3 Click the Physical Interface button.
Step 4 Click Advanced to configure line coding, framing, and signaling type.
The Advanced dialog box appears.
Step 5 In the Line coding field, choose the type of modulation used to encode the data.
Step 6 In the Framing field, choose the framing and error detection method.
Note The ESF CRC6JT framing option is available only if you select Japan in the Country field and Long Haul in the Line Build Out field.
Step 7 In the Signaling type field, choose the signaling type.
Step 8 Click OK to close the Advanced dialog box.
BRI Ports
Note This section applies only to Cisco Unified Videoconferencing 3522 BRI Gateway.
In the Physical Interface section of the BRI Port tabs, you can configure the physical line properties of the specified BRI port.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the applicable BRI Port tab.
Step 3 Click the Physical Interface button.
Step 4 Select the Same as Port check box if you want to duplicate physical interface settings from another BRI port that you choose from the field. When selected, you cannot modify the Signaling Protocol or Country settings. This setting is selected by default.
Step 5 In the Country field, choose the country where the ISDN service is installed.
Step 6 In the Signaling Protocol field, choose the signaling protocol used to setup and tear down calls through the signaling (D) channel. Depending on the interface used, different signaling protocols are available for selection.
Step 7 In the PCM Audio Format field, choose the desired G.711 audio standard: A-Low or U-Low.
Note You can only configure this setting if you select Taiwan in the Country field. Skip to step 8 otherwise.
Step 8 In the Directory Numbers section, enter the phone numbers for the BRI line in the Number 1 and Number 2 fields.
Step 9 Click Advanced to enable or disable alerting, Layer 1 line hunting, or configure a static Terminal Equipment Identifier (TEI).
The Advanced dialog box appears.
Step 10 Select the Enable Alerting check box for the gateway to connect a voice call that is not rejected (instead of sending alert messages to the caller).
The alerting feature is relevant for incoming voice calls routed directly to an endpoint (through DID) or to a default extension. When you select this option, the gateway sends an alert message to the dialing ISDN terminal if the call is not connected within a few seconds. This informs the ISDN terminal that the call is not yet connected to the local IP endpoint. As a result, the ISDN terminal continues to hear a ringing sound until the gateway connects to the call.
Note The gateway connects the call even if the endpoint on the local IP network has not yet accepted it. If the IP endpoint does not accept the call, the call is rejected and immediately disconnects from the ISDN terminal.
This setting is selected by default. Deselect it to prevent the gateway from sending an alert message.
Step 11 Select the Enable Layer 1 Line Hunting check box if you do not want the gateway to hunt BRI lines whose Layer 1 is not activated. This setting is deselected by default.
Note In European networks, Layer 1 is usually only activated during a call. In such a system, Layer 1 line hunting is not effective and should not be enabled. However, when the gateway BRI port is connected to a private branch exchange (PBX) for some PBXs, Layer 1 always activates.
Step 12 Select the Enable static TEI check box to configure a static TEI. TEI values are supplied by the telecom company. If you select this option, perform step 13. Otherwise, skip to step 14.
Note You can only configure this setting if you select 5ESS PTP or ETSI PTP in the Signaling Protocol field of the Physical Interface section.
Step 13 In the TEI Value (0-63) field, enter a value from 0 to 63 for this BRI line.
Step 14 Click OK to upload your changes to the gateway database and close the Advanced dialog box.
Related Topics
•Configuring Service Profile Identification (SPID) Values
Configuring Service Profile Identification (SPID) Values
In the Physical Interface section of the BRI Port tabs, you can configure Service Profile Identification (SPID) values as part of the physical line properties of the specified BRI port.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the applicable BRI Port tab.
Step 3 Click the Physical Interface button.
Step 4 Click SPIDs to configure Service Profile Identification (SPID) values for this BRI line. The SPID value is provided by the telecom company and indicates which services a specified BRI line supports (for example, phone, fax, or videoconferencing facilities).
Note You can only configure SPID values if you select DMS100, National ISDN, or 5ESS Custom/Multipoint options in the Signaling Protocol field of the Physical Interface section, and when the Country field is set to US. Skip to step 9 otherwise.
The SPIDs dialog box appears.
Step 5 In the Number of SPIDs field, choose the required number of SPID values.
Step 6 In the SPID 1 field, enter the first SPID value.
Step 7 In the SPID 2 field, enter the second SPID value.
Step 8 Click OK to upload these changes to the gateway database and close the SPIDs dialog box.
About Advanced ISDN Settings for PRI Gateways
Note This section applies only to Cisco Unified Videoconferencing 3527 PRI Gateway.
In the Advanced ISDN section of the PRI Port tab, you can view and configure ISDN settings for Cisco Unified Videoconferencing 3527 PRI Gateway. Table 3-19 explains the information that this tab displays.
Table 3-19 Advanced ISDN Tab Details
Column or Field
|
Description
|
Prefix
|
Displays the prefix of the advanced ISDN entry.
|
Description
|
Displays a brief description of the advanced ISDN entry.
|
NPI
|
Displays the Numbering Plan Identification (NPI) classification for the ISDN phone number.
|
TON
|
Displays the Type of Number (TON) code for the advanced ISDN entry.
|
NSF
|
Indicates whether the Network Specific Facility feature is enabled or disabled for the Advanced ISDN entry.
|
Max Digits
|
Displays the maximum number of digits allowed for outbound dialing.
|
DN Manipulation
|
Indicates whether advanced ISDN prefix number is enabled. For default prefix entries where TON is local, this field indicates whether the DN Manipulation setting is set to Append Local Area Code in the Add or Edit ISDN Information Elements dialog box (see the "Adding or Editing ISDN Information Elements" section for more information).
|
Total
|
Displays the total number of ISDN information elements currently listed in the gateway database.
|
The following topics discuss how you can configure Advanced ISDN Settings:
•About NSF Settings
•Adding or Editing ISDN Information Elements
•Deleting ISDN Information Elements
Note You can select the Same as Port check box and select another PRI port to duplicate advanced ISDN settings from that port. When you select this option, you cannot make any edits to the configuration settings. This option is unavailable in gateway that support only one PRI port.
About NSF Settings
The NSF Information Element (IE) feature enables system administrators to coordinate network and service requirements with service providers. Service providers supply the information that you enter in the NSF Configuration dialog box. System administrators can either select any of the pre-configured NSF settings, or choose to configure their own NSF Information Element using service provider information.
You can specify the following information in the NSF:
•The service providers with which you want their network to work.
•The specific network plan and equipment with which you want your network to work (for example, switches and bandwidth).
•The specific services available to their network (for example,1-800 phone numbers).
Instructions are contained in the NSF IE fields of outgoing Q.931 setup messages in the format shown in Figure 3-5.
Figure 3-5 Network Specific Facility Information Element Format
NSF Information Elements contain a number of configurable Octet fields. The values entered in these fields represent instructions contained in outgoing Q.931 Setup messages. Table 3-19 represents the format of such instructions. Table 3-20 describes the function of each of the Octet fields.
Table 3-20 Octet Field Functions
Octet
|
Function
|
Octet 3
|
Octet 3 represents the total number of Octet 3.X fields required for the specific information element, including the Octet 3 field itself.
|
Octet 3.1
|
Octet 3.1 is used to hold Numbering Plan Identification (NPI) and Type of Network (TON) values. The octet contains eight bits numbered from 1 to 8 and from right to left, so that Bit 1 is rightmost and Bit 8 is leftmost.
The bits contain binary values representing the following functions:
•Bits 1-4 = NPI
•Bits 5-7 = TON
•Bit 8 is always set to 1 when Octet 3.1 is used and populated.
Note The Numbering Plan Identification (NPI) and Type of Network (TON) fields appear in the Add ISDN Information Elements dialog box
The standard NPI values are:
•For an NPI setting of Unknown, the standard integer value is 0 and the standard binary value is 0.
•For an NPI setting of ISDN/Public, the standard integer value is 1 and the standard binary value is 0001.
•For an NPI setting of Private, the standard integer value is 9 and the standard binary value is 1001.
The standard TON values are:
•For a TON setting of unknown, the standard integer value is 0 and the standard binary value is 0.
•For a TON setting of International, the standard integer value is 1 and the standard binary value is 0001.
•For a TON setting of National, the standard integer value is 2 and the standard binary value is 0010.
•For a TON setting of Network, the standard integer value is 3 and the standard binary value is 0011.
•For a TON setting of Local, the standard integer value is 4 and the standard binary value is 0100.
|
Octet 3.2
|
Octet 3.2 is used to hold information including Carrier Identification Codes (CIC). A CIC is three-digit number used to access the switched services of a particular long-distance carrier from a local exchange line. All long-distance carriers, and many long-distance resellers, have their own unique CIC. One or more CIC codes are assigned to each carrier.
Some examples of CIC are:
•MCI VNET: 222
•AT&T Communications: 288
•Sprint: 333
|
Octet 4
|
Octet 4 is used to hold information representing coding values for features and services. Service providers supply the coding values.
The octet contains eight bits numbered from 1 to 8 and from right to left, so that Bit 1 is rightmost and Bit 8 is leftmost.
The bits contain values representing the following functions:
•Bits 1-5=The binary Facility Coding Value for the specified feature or service.
•Bit 6 indicates whether the facility is a feature or a service:
–0=The requested facility is a feature.
–1=The requested facility is a service.
•Bit 7 is always set to 1
•Bit 8 indicates whether the requested facility has associated parameters or is binary:
–0=There are parameters associated with the requested facility and they are specified in Octet 5.
–1=The requested facility is a binary facility. There are no parameters.
|
Octet 5
|
Octet 5 is used to hold information representing coding values for parameterized facilities.
The octet contains eight bits numbered from 1 to 8 and from right to left, so that Bit 1 is rightmost and Bit 8 is leftmost.
The bits contain values representing the following functions:
•Bits 1-7 represents the parameterized field coding value.
•Bit 8 is for future use.
|
Table 3-21 shows Octet 4 binary facility coding values for specified features when Bit 6 is set to 0. Table 3-22 shows binary facility coding values for specified services when Bit 6 is set to 1.
.
Table 3-21 Feature Binary Facility Coding Values
Bits
|
Feature
|
5
|
4
|
3
|
2
|
1
|
|
0
|
0
|
0
|
0
|
1
|
Calling party number preferred
|
0
|
0
|
0
|
1
|
0
|
Billing number preferred
|
0
|
0
|
0
|
1
|
1
|
Calling party number only
|
0
|
0
|
1
|
0
|
0
|
Billing number only
|
0
|
0
|
1
|
0
|
1
|
Operator
|
0
|
0
|
1
|
1
|
0
|
Pre-subscribed Common Carrier Operator
|
0
|
0
|
1
|
1
|
1
|
Reserved
|
0
|
1
|
0
|
0
|
1
|
Call-Associated Temporary Signaling Connection (TSC)
|
0
|
1
|
0
|
1
|
0
|
Notification of Call-Associated TSC clearing
|
0
|
1
|
0
|
1
|
1
|
Reserved
|
0
|
1
|
1
|
0
|
0
|
Reserved
|
1
|
0
|
0
|
0
|
0
|
Reserved
|
Table 3-22 Service Binary Facility Coding Values
Bits
|
Feature
|
5
|
4
|
3
|
2
|
1
|
|
0
|
0
|
0
|
0
|
1
|
Software Defined Network (SDN). Includes Global SDN)
|
0
|
0
|
0
|
1
|
0
|
AT&T Megacom
|
0
|
0
|
0
|
1
|
1
|
AT&T Megacom
|
0
|
0
|
1
|
0
|
0
|
Reserved
|
0
|
0
|
1
|
0
|
1
|
Wide Area Telecommunications Service (WATS)
|
0
|
0
|
1
|
1
|
0
|
AT&T Accunet Switched Data Video Gateway (SDVG)
|
0
|
0
|
1
|
1
|
1
|
Long Distance Service
|
0
|
1
|
0
|
0
|
0
|
International 800 (1800)
|
0
|
1
|
0
|
0
|
1
|
Reserved
|
0
|
1
|
0
|
1
|
0
|
Reserved
|
0
|
1
|
0
|
1
|
1
|
Reserved
|
0
|
1
|
1
|
0
|
0
|
Reserved
|
1
|
0
|
0
|
0
|
0
|
Multiquest
|
1
|
0
|
0
|
0
|
1
|
Reserved
|
1
|
0
|
0
|
1
|
0
|
800
|
1
|
0
|
0
|
1
|
1
|
Test call
|
1
|
0
|
1
|
0
|
0
|
Inward Wide Area Telecommunications Service (INWATS)
|
1
|
0
|
1
|
0
|
1
|
SDN-K (Key Service Protection)
|
1
|
0
|
1
|
1
|
1
|
Call Redirection Service
|
Table 3-23 shows Octet 5 parameterized facility coding values.
Table 3-23 Parameterized Field Binary Coding Values
Bits
|
Parameterized Field
|
7
|
6
|
5
|
4
|
3
|
2
|
1
|
|
0
|
0
|
0
|
0
|
0
|
0
|
1
|
Alternate handling on Ring/No Answer
|
0
|
0
|
0
|
0
|
1
|
1
|
0
|
Sponsor Flexible Rating (SFR)
|
0
|
0
|
0
|
1
|
1
|
0
|
0
|
Out-of-band triggers allowed—data allowed
|
0
|
0
|
0
|
1
|
1
|
0
|
1
|
Out-of-band triggers allowed—data not allowed
|
0
|
0
|
0
|
1
|
1
|
1
|
0
|
Network Managed Data
|
0
|
0
|
0
|
1
|
1
|
1
|
1
|
Switched Data Video Gateway (SDVG) Service
|
Adding or Editing ISDN Information Elements
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the applicable PRI Port tab.
Step 3 Click the Advanced ISDN button.
Step 4 Click Add to add a new ISDN information element or select an existing one and click Edit to modify it.
The Add or Edit ISDN Information Elements dialog box appears.
Step 5 In the Prefix field, enter or edit the prefix for the ISDN information element. If you set this field to Default, it cannot be edited after you create the element.
Step 6 In the Description field, enter or edit the description of the ISDN information element. If you set this field to Default, it cannot be edited after you create the element.
Step 7 In the Numbering Plan Identification (NPI) field, choose an NPI code for the ISDN information element.
Step 8 In the Type of Number (TON) field, choose a TON code for the ISDN information element.
Step 9 In the Maximum digits send field, enter the number of digits (up to a maximum of 32) allowed for outbound dialing.
Step 10 In the DN Manipulation field, you can configure the stripping of the ISDN information prefix number from the outbound dialed number.
The options in this field vary according to the options set in the Prefix and Type of Number (TON) fields. Table 3-24 details the possible variations
Table 3-24 DN Manipulation Option Variations
Prefix Field
|
Type of Number (TON) Field
|
DN Manipulation Options
|
Default
|
Local
|
None, Append Local Area Code
|
Default
|
Any except Local
|
None
|
Any except Default
|
Any
|
None, Strip Prefix
|
You are now ready to configure your required Network Specific Facility settings (see the Configuring Network Specific Facility Settings).
Configuring Network Specific Facility Settings
This section describes how to complete the procedure that you began in the Adding or Editing ISDN Information Elements.
Procedure
Step 1 In the Network Specific Facility (NSF) field, make one of the following selections:
–Choose one of the pre-configured settings or choose None to not configure any NSF information elements. Table 3-25 lists the pre-configured settings.
Table 3-25 Pre-configured NSF Settings
Pre-configured Setting
|
Information Element (IE) Octets
|
| |
IE 1 Octets
|
IE 2 Octets
|
| |
3
|
3.1
|
3.2
|
3.2
|
3.2
|
4
|
3
|
4
|
5
|
AT&T Accunet
|
4
|
A1
|
32
|
38
|
38
|
E6
|
|
|
|
AT&T Megacom
|
4
|
A1
|
32
|
38
|
38
|
E3
|
|
|
|
AT&T Megacom 800
|
4
|
A1
|
32
|
38
|
38
|
E2
|
|
|
|
AT&T SDDN
|
4
|
A1
|
32
|
38
|
38
|
E1
|
|
|
|
AT&T Accunet + SDVG
|
4
|
A1
|
32
|
38
|
38
|
E6
|
0
|
49
|
0F
|
AT&T Megacom + SDVG
|
4
|
A1
|
32
|
38
|
38
|
E3
|
0
|
49
|
0F
|
AT&T Megacom 800 + SDVG
|
4
|
A1
|
32
|
38
|
38
|
E2
|
0
|
49
|
0F
|
AT&T SDDN + SDVG
|
4
|
A1
|
32
|
38
|
38
|
E1
|
0
|
49
|
0F
|
MCI VNET
|
4
|
A9
|
32
|
32
|
32
|
E1
|
|
|
|
Sprint VPN
|
4
|
A9
|
33
|
33
|
33
|
E1
|
|
|
|
—or—
–Choose Custom.
–Click Configure.
The NSF Configuration dialog box appears. You can configure up to four NSF information elements.
Note You can only configure the NSF information elements (NSF IEs) if you set the Interface field in the Physical Interface section of the PRI Port tab to T1 and set the Country field to US. All outgoing Q.931 setup messages will contain the NSF IE.
–Select the Enable check box.
–In the Octet 3 field, choose a value. When the value is greater than 0, that number of fields appears beneath the Octet 3 field. If this field is set to 0, the Octet 3.1 and Octets 3.2 fields are not available. If this field is set to 1, only the Octet 3.1 field is available.
–In the Octet field(s), choose settings.
–In the Type field, choose Binary feature or Binary service and then in the Facility Coding Value field, enter a value.
—or—
In the Type field, choose Parameterized and then in the Parameterized Field field, enter a value.
—or—
In the Type field, choose Custom and then in the Octet 4 and Octet 5 field (if applicable), enter a value.
Note When you select Binary feature or Binary service in the Type field, the Facility Coding Value field is for Octet 4, Bits 5-1. When you select Parameterized in the Type field, the Parameterized Field field is for Octet 5, Bits 7-1. When you select Custom in the Type field, the values entered in the Octet 4 or Octet 5 fields are not subject to bit restriction.
–Repeat step 1 for as many additional NSF information elements as necessary.
Deleting ISDN Information Elements
In the Advanced ISDN section of the PRI Port tab, you can delete an ISDN information element.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the PRI Port tab.
Step 3 Click the Advanced ISDN button.
Step 4 Select an ISDN information element and click Delete.
Configuring Port Call Policies
In the Call Policies section of the PRI Port or BRI Port tabs, you can configure the incoming call routing methods available in the gateway for each specified port. You can define each port with different settings.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the applicable PRI Port or BRI Port tab.
Step 3 Click the Call Policies button.
Step 4 Select the Same as Port check box to duplicate call policies settings from another gateway port that you choose from the field. When selected, you cannot modify any settings in this section. This option is unavailable in gateways that support only one PRI port.
Step 5 In the Enable inbound routing methods section, you can select incoming call routing methods in the following order of priority:
–DID—When selected, enables Direct Inward Dialing to an endpoint.
–TCS4—When selected, enables TCS4 dialing. This setting does not apply to voice calls.
–IVR—When selected, enables the Interactive Voice Response operator.
–Default extension—When selected, enables the use of the default extension number that you enter in the field.
Step 6 Select the Overlap Receiving check box to enable overlap receiving functionality. In this functionality, the gateway can receive consecutive digits until the dialing is complete, instead of receiving the entire phone number as a block of digits. The gateway recognizes that an overlap receiving dialing is completed when it receives a fixed, predefined, incoming number of digits. If the gateway receives a complete indication notification from the switch (PSTN) or a timeout before all the digits have been dialed, the call might connect to a different address or rejected. If you select this setting, perform step 7, otherwise skip to step 8.
Step 7 In the Incoming number of digits field, enter the number of digits you want the gateway to expect during overlap receiving. The gateway waits until this number of specified digits is received and then processes the whole number. You can enter any value up to 32.
Step 8 In the Outgoing Calling Party Number field, enter a number that the gateway automatically provides if the calling IP network endpoint does not provide a calling party number. Valid digits are 0 through 9 You can enter up to 11 digits.
Configuring Port Supported Services
In the Supported Services section of the PRI Port or BRI Port tabs, you can enable or disable specific gateway services on each port. The Supported Services section displays the following information in table form:
•Prefix—Displays the prefix for this service.
•Description—Displays a brief description of the service.
•Call Type—Displays the call media type: Voice or Video.
•Bit Rate—Displays the maximum total bit rate allowed for this service.
•Support—Displays the status of the service: enabled or disabled.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 Click the applicable PRI Port or BRI Port tab.
Step 3 Click the Supported Services button.
Step 4 Select the Same as Port check box if you want to duplicate settings from another gateway port that you choose from the field. When selected, you cannot modify any settings in this section. This option is unavailable in gateways that support only one PRI port.
Step 5 To enable or disable a service for this port, select it and click Enable or Disable.
Viewing Call Information
The Calls tab displays a list of the calls currently defined in the gateway and the basic details of each call. The Calls tab displays the following information in table format:
•Call ID—Displays the call identifier.
•Source Party Number—Displays the alias that identifies the source endpoint of the call.
•Destination Party Number—Displays the alias that identifies the destination endpoint of the call.
•Start Time—Displays the time at which the call began.
•Total Call Bandwidth—Displays the total bandwidth (in Kbps) used for this call on both sides.
•Encryption—Indicates the level of encryption currently in use for the specified participant: best effort, encryption required, or strong encryption required.
•Total—Field indicates the total number of calls currently defined in the gateway.
The following topics discuss the tasks you can perform in this tab:
•Refreshing Call Information
•Viewing Call Details
•Disconnecting Calls
Refreshing Call Information
You can configure the gateway interface to refresh information that appears in the Calls tab every ten seconds.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 In the Calls tab, select the Auto Refresh check box.
Viewing Call Details
In the Calls tab, you can view detailed information for each call currently defined in the gateway.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 In the Calls tab, select a call and click Details.
The Call Details window appears. Table 3-26 explains the information that this window provides.
Table 3-26 Call Details Window Fields
Field
|
Description
|
Start
|
Displays the time at which the call began.
|
Duration
|
Displays the length of time that the call has been in progress.
|
Bandwidth (Kbps)
|
Displays the total bandwidth (in Kbps) used for this call on both sides.
|
Source
|
Source
|
Indicates whether the source endpoint of the call is located on an ISDN or IP network.
|
Number
|
Displays the alias that identifies the source endpoint of the call.
|
B channels
|
Displays the B channels currently in use for this call.
|
Resync B channels
|
In mid-call, you can click this button to resynchronize B channels in cases of poor call quality.
Use this option with extreme caution. Resynchronizing B channels can cause a call to disconnect.
|
Audio
|
Displays the audio transcoding protocol and the bandwidth of the voice calls in both directions between the source endpoint and the gateway.
|
Video
|
Displays the video transcoding protocol, the frame format, and the bandwidth of the video calls in both directions between the source endpoint and the gateway.
Note The Video 2 stream is active when dual video streams for a single call are in use.
|
Data
|
Displays the bandwidth of the data calls in both directions between the source endpoint and the gateway.
|
Gateway
|
Transcoded
|
Indicates that a call is transcoded.
|
Destination
|
Destination
|
Indicates whether the destination endpoint of the call is located on an ISDN or IP network.
|
Number
|
Displays the alias that identifies the destination endpoint of the call.
|
Name
|
Displays the name that identifies the destination endpoint of the call.
|
IP
|
Displays the IP address of the destination endpoint of the call.
|
Packet Loss (%)
|
Displays the rate of packet loss in communication from the IP side of the call to the gateway, regardless of whether the source endpoint is located on an ISDN or IP network.
|
Encryption
|
Indicates the encryption algorithm in use for the call (if any).
|
Audio
|
Displays the audio transcoding protocol and the bandwidth of the voice calls in both directions between the gateway and the destination endpoint.
|
Video
|
Displays the video transcoding protocol, the frame format, and the bandwidth of the video calls in both directions between the gateway and the destination endpoint.
Note The Video 2 stream is active when dual video streams for a single call are in use.
|
Data
|
Displays the bandwidth of the data calls in both directions between the gateway and the destination endpoint.
|
Disconnecting Calls
In the Calls tab, you can disconnect a currently active call or disconnect all active calls.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway (if not already selected).
Step 2 In the Calls tab, select a call and click Disconnect, or to disconnect all calls, click Disconnect All Calls.
Viewing Gateway Alarm Events
In the Event Log tab, you can view a list of reported alarm events. The Event Log tab displays the following information:
•Event ID—Displays the identifier for the specified alarm event.
•Type—Displays the type of event.
•Time—Displays the time at which the reported event occurred.
•Severity—Displays the severity of the reported event.
•Message—Displays the error message used to report the event.
•Total—Displays the total number of reported alarm events.
•Clear All—Click to clear all events from the Event Log tab.
See Table 3-8 for a list of PRI gateway SNMP events. See Table 3-9 for a list of BRI gateway SNMP events.
Viewing Gateway Statistics
In the Statistics tab, you can view system-specific information such as call traces and debugging details. The Statistics tab displays the following:
•Gateway start-up counter—Displays the number of times that the gateway has reset.
•Details button—Click to display the Details window, which lists the last three reasons for gateway power failure.
•ISDN LOF event counter (PRI gateways only)—Displays the total number of ISDN Loss of Frame (LoF) errors recorded on the gateway PRI port.
•CRC error/event counter on ISDN (PRI gateways only)—Displays the total number of CRC errors on the ISDN network recorded on the gateway PRI port.
•ICMP-in-message counter—Displays the number of Internet Control Message Protocol (ICMP) packets received.
•UDP-in-datagram counter—Displays the number of User Datagram Protocol (UDP) packets received.
•Packet loss counter—Displays the number of lost packets.
•Packet late counter—Displays the number of late packets.
•Accumulated time of B channel usage—Displays the total B channel usage (in minutes).
•Counter reset time—Displays the last time at which the counters were reset.
•Reset Counters button—Click to reset all counters to zero.
Configuring Gateway Maintenance Tasks
In the Maintenance tab, you can enter maintenance mode. In maintenance mode, you can perform maintenance work on the gateway, such as upgrading software. In maintenance mode, the gateway cannot accept new calls. You can disconnect all calls currently active in the gateway, or wait for them to disconnect. In maintenance mode, you can only modify the following configuration settings:
•Services (see the "About Gateway Services" section for more information)
•Fractional B channel status (PRI gateways only) (see the "Viewing B Channel Status" section for more information)
•Gatekeeper IP connectivity (see the "Configuring IP Connectivity Settings" section for more information).
•Resource allocation
•IVR (see the "Configuring IVR Settings" section for more information)
To enter maintenance mode, click Enter Maintenance Mode. To exit maintenance mode, click Exit Maintenance Mode.
Saving Configuration Settings
You can save configuration settings to a file and then export this file to a storage device on your network. You can use the saved configuration file to restore the settings to the current unit or to configure a similar unit.
An exported configuration file saves most of the current Device section settings and all of the current Gateway section settings.
Note You cannot save configuration settings in the System category.
You must use the Export button on the toolbar to save the configuration settings to a file. The Export button appears only when Gateway section settings are activated. When you save a configuration file, the current Device section settings are saved in the file. If you want to change these settings for export, click Upload on the toolbar to save these settings to configuration memory prior to saving the configuration file.
Procedure
Step 1 In the gateway interface, on the sidebar, click Device.
Step 2 Make sure that the settings in the Basics, Addressing, Web and Users tabs are correct.
Note Date parameters are not saved to the configuration file.
Step 3 Click Upload to save these settings.
Step 4 On the sidebar, click Gateway.
Step 5 Make sure that the settings in the Status, Settings, PRI or Serial Ports, Calls, Event Log and Statistics tabs are correct.
Step 6 Click Upload to save these settings.
Step 7 On the toolbar, click Export.
Note A dialog box appears indicating that you are navigating away from the page without saving the changes. Select the option to continue.
The File Download dialog box appears.
Step 8 Save the configuration settings file to your chosen location. The file extension .ini is automatically appended to the file name.
Importing Configuration Files
You can import the settings of a saved unit configuration file from a storage device on your network. You can use the saved configuration file to restore the settings to the current unit or to configure another unit.
Procedure
Step 1 In the gateway interface, on the sidebar, click Gateway.
Step 2 On the toolbar, click Import.
The Import a Configuration File page appears.
Step 3 Click Browse.
The Choose file dialog box appears.
Step 4 Navigate to and select the configuration file you want to import.
Note The file must have an .ini extension.
Step 5 Click Open.
The file path appears in the File Name field.
Step 6 Click Import.
The file appears in the gateway category window, and the Upload button is active.
Note You can open and change settings in any of the gateway category options without losing the original settings in the configuration file. However, you must click Upload on the toolbar to retain these setting before selecting another category.
Step 7 Click Upload to save the settings in configuration memory.
Note Uploading the file resets the device.
