|
|
Table Of Contents
Basic and Additional H.323 Services
Important Basic H.323 Services
Setting Up User IDs for the Cisco ATA
Using the Cisco ATA with an H.323 Gatekeeper
Using the Cisco ATA Without an H.323 Gatekeeper
Configurable Reboot of Cisco ATA
Configuring Audio Packet Settings
Configuring the Call Waiting Permanent Default Setting
Configuring the Cisco ATA Refresh Interval
Configuring the Mixing of Call Waiting Tone and Audio
Configuring Network Ringback Tone
Configuring Reverse Audio Cut-Through Behavior
Configuring Supplementary Service Behavior and Parameters
Selecting DTMF and Hookflash Transmission Methods
Selecting H.323 Connection and H.245 Transmission Methods
Complete Reference Table of all Cisco ATA H.323 Services
Basic and Additional H.323 Services
This section provides information about key basic and additional H.323 services that the Cisco ATA supports:
•
Important Basic H.323 Services—This section includes a list of parameters that you must configure in order for the Cisco ATA to function in an H.323 environment.
•
•
Note
Important Basic H.323 Services
This section provides descriptions and cross references for configuring required H.323 parameters and also for configuring important H.323 services:
•
•
•
Required Parameters
You need to supply values for the required H.323 parameters shown in Table 4-1. The Parameter column provides the name of the parameter and a cross reference which provides a more-detailed description of the parameter.
Note
Setting Up User IDs for the Cisco ATA
Each Cisco ATA can support two FXS ports. You can assign a user ID, which is usually an E.164 phone number, to each port. Use the Cisco ATA parameter UID0 to configure an ID for the Phone 1 port, and use the UID1 parameter for the user ID of the Phone 2 port.
Related Configuration Parameters
Using the Cisco ATA with an H.323 Gatekeeper
The Cisco ATA can function with an H.323 gatekeeper to enable Cisco ATA registration, admission, and use of directory services on an H.323 network. To use the Cisco ATA with a primary H.323 gatekeeper, you need to configure the GkOrProxy parameter with the IP address assigned to the primary H.323 gatekeeper. Optionally, you can specify the primary gatekeeper identifier using the GkId parameter if this identifier is required for the Cisco ATA to successfully register with the H.323 network.
This section contains the following topics:
•
•
•
•
Related Configuration Parameters
Choosing Cisco ATA Registration Mode with an H.323 Gatekeeper
The Cisco ATA can register with an H.323 gatekeeper in one of two modes:
•
•
To configure single-mode registration, you need to set the UseLoginID parameter to 1, and then configure the LoginID1 and LoginID2 parameters with identical values. The LoginID1 and LoginID2 parameters are used for the H.323 ID, whereas the UID0 and UID1 parameter values are used as E.164 phone numbers.
If LoginID1 and LoginID2 are not used or are not set to identical values, the Cisco ATA uses dual-registration mode.
Related Parameters
Setting Up Gatekeeper Time-To-Live Value
You can specify the valid duration of the H.323 gatekeeper registration, in seconds, by using the GkTimeToLive parameter.
Related Configuration Parameter
Setting Up an Alternate H.323 Gatekeeper
To provide redundancy in systems that use an H.323 gatekeeper, the Cisco ATA allows you to either statically configure an alternate H.323 gatekeeper or dynamically assign an H.323 gatekeeper.
To enable the static alternate gatekeeper feature, you need to configure the AltGk parameter with the IP address assigned to the alternate H.323 gatekeeper. To enable the Cisco ATA to perform full gatekeeper registration when it switches to a statically configured alternate H.323 gatekeeper, configure Bit 3 of the ConnectMode parameter to the value of 1.
To enable the dynamic alternate gatekeeper feature, you need to configure the primary H.323 gatekeeper so that the list of alternate gatekeepers is included in the H.225 RAS messages that the H.323 gatekeeper sends to the Cisco ATA. The Cisco ATA can accept as many as four dynamic alternate gatekeepers configured in the H.225 RAS messages. (The Cisco ATA supports the alternate gatekeeper list in GCF/GRJ, ACF/ARJ, RCF/RRJ, and DRJ RAS messages.)
Dynamic alternate gatekeepers and static alternate gatekeepers can co-exist. When the Cisco ATA receives an alternate gatekeeper list in an H.225 RAS message, the static alternate gatekeeper is merged with the dynamic alternate gatekeepers. The static alternate gatekeeper is kept and given the lowest priority.
You can configure the AltGkTimeout parameter to specify the number of seconds the Cisco ATA should wait before it automatically switches back to the primary H.323 gatekeeper after being moved to an alternate gatekeeper. By default, the switch-back procedure is disabled (the AltGkTimeout parameter value is set to 0).
Related Configuration Parameters
Establishing Authentication with Cisco H.323 Gatekeeper
You can configure the Cisco ATA to establish authentication with a Cisco H.323 Gatekeeper. The Cisco ATA supports two authentication methods:
•
•
To configure either authentication method, use the following procedure:
Procedure
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Note
Related Configuration Parameters
Using the Cisco ATA Without an H.323 Gatekeeper
You can use the Cisco ATA without using an H.323 gatekeeper, as this section describes with the following topics:
•
•
Using the Cisco ATA With an H.323 Gateway but Without an H.323 Gatekeeper
You can use a Cisco ATA with an H.323 network that does not contain an H.323 gatekeeper. In this scenario, all calls initiated from the Cisco ATA are directed to a specified H.323 gateway. To specify this H.323 gateway, you configure its IP address using the Gateway parameter, and you disable the H.323 gatekeeper feature by setting the GkorProxy parameter to 0.
Note
Related Configuration Parameters
Using Multiple Cisco ATAs Without an H.323 Gatekeeper
You can make calls from one Cisco ATA to another Cisco ATA in an H.323 network that does not contain an H.323 gatekeeper.
For one Cisco ATA to access a specific FXS port on another Cisco ATA, you use an IP dialing procedure. The Cisco ATA originating the call must have the following information about the destination Cisco ATA:
•
•
To enable the IP dialing procedure, you need to set the IPDialPlan parameter to 1 to instruct the Cisco ATA to look for the destination IP address in the dialed digits.
Example
Cisco ATA X is going to initiate a call to Cisco ATA Y (with the following pertinent information):
•
•
•
To call the Phone 1 port on Cisco ATA Y, you would dial 5556666**192*168*2*112#.
To call the Phone 2 port on Cisco ATA Y, you would dial 5558888**192*168*2*112#.
Related Configuration Parameters
Setting the Audio Codecs
You can configure the following codec-related settings:
•
When G.723.1 is the low-bit-rate codec, each FXS port is allocated one G.723.1 connection. When G.729 is used, only one FXS port can use G.729. The G.729 resource is allocated in a dynamic manner. When a call begins, the FXS port requests and takes an available G.729 resource. The Cisco ATA releases this resource when the call is completed.
Use Bit 1 of the AudioMode parameter to disable and enable the use of the low-bit-rate codec.
Related Configuration Parameters
•
Related Configuration Parameters
•
Related Configuration Parameter
Additional H.323 Services
This section describes additional H.323 services and, where applicable, provides configuration information and cross references to the parameters for configuring these services, described in alphabetical order:
•
•
•
•
•
•
•
•
•
•
•
•
•
Configurable Reboot of Cisco ATA
The Cisco ATA continuously monitors its Ethernet connection to the switch or hub. If this connection is broken, the Cisco ATA starts an internal timer that runs until a configurable timeout period expires. Once the timeout value is reached, the Cisco ATA automatically reboots. This timeout value is configured by using the FeatureTimer2 configuration parameter. For more information, see the "FeatureTimer2" section on page 5-31.
Configuring Audio Packet Settings
Table 4-2 lists configurable audio-packet settings and their related configuration parameters.
Configuring Billable Features
You can customize specific features on a subscription basis by changing the values of specific bits in several different parameters. Table 4-3 contains a list of billable features and their related parameters:
Table 4-3 Billable Features and Related Parameters
Call Conferencing
Call Waiting
PaidFeatures, page 5-28, CallFeatures, page 5-27, SigTimer, page 5-31
Caller ID
PaidFeatures, page 5-28, CallFeatures, page 5-27, CallerIdMethod, page 5-38
Polarity
Note
Configuring the Call Waiting Permanent Default Setting
This feature allows you to specify the default call-waiting setting for every call on a permanent basis by means of the service activation and deactivation codes.
Related Parameter
ConnectMode, page 5-32—Bit 23
Configuring the Cisco ATA Refresh Interval
When the value specified in the CfgInterval parameter is reached, the Cisco ATA attempts to refresh its configuration file from the TFTP server. Set the CfgInterval parameter to an interval value (in seconds) for refreshing the Cisco ATA configuration file. Cisco recommends that the interval be semi-random to prevent many simultaneous contacts with the TFTP server. For more information, see the "CfgInterval" section on page 5-6.
When the Cisco ATA contacts the TFTP server, it also checks to see if an upgrade signaling image has been placed on the TFTP server. If such an image exists, the Cisco ATA will download this image.
Configuring Hook Flash Timing
This feature provides the ability to adjust the hook-flash timing to meet local requirements.
Related Parameter
SigTimer, page 5-31—Bits 26 and 27 are for configuring the minimum on-hook time required for a hook flash event, and bits 28 through 31 are for configuring maximum on-hook time.
Configuring the Mixing of Call Waiting Tone and Audio
This feature allows the call-waiting tone to be mixed with the audio in an active call. This mixing causes the call-waiting tone to sound without a pause in the audio.
Related Parameter
Configuring Network Ringback Tone
You can configure the Cisco ATA to send a ringback tone to a caller by using bit 19 of the ConnectMode parameter.
Related Configuration Parameter
Configuring Reverse Audio Cut-Through Behavior
You can configure the reverse audio cut-through behavior of the Cisco ATA by using Bit 5 of the ConnectMode parameter.
Related Configuration Parameter
Configuring Supplementary Service Behavior and Parameters
Service providers can offer many supplementary services, which can be activated, configured, or deactivated in more than one way.
The behavior and activation/deactivation of call supplementary services can be different from one country to another. You can use the CallCmd parameter to define the behavior and the activation/deactivation access code for the supplementary services that the Cisco ATA supports.
Related Configuration Parameter
Debugging Diagnostics
You can use the following parameter to troubleshoot operation issues:
•
Hardware Information Display
Cisco ATA hardware information is displayed in the lower-left corner of the Cisco ATA Web configuration page.
Network Timing
You can fine-tune your network timing with the following parameters:
•
•
•
•
Polarity Settings
You can control line polarity of the Cisco ATA FXS ports when a call is connected or disconnected by configuring the Polarity bitmap parameter (see the "Polarity" section on page 5-39).
Progress Tones
Values for the following parameters (all defined in the "Tone Configuration Parameters" section on page 5-41) must be determined based on the country in which the Cisco ATA is located:
•
•
•
•
•
•
Selecting DTMF and Hookflash Transmission Methods
The Cisco ATA is designed to use H.245 messages to relay DTMF and hookflash events. Both the H.245 alphanumeric IE method and the H.245 signal IE method are supported for transporting DTMF events. The H.245 signal IE method has higher precedence if the far end also supports this method.
Use bits 4-5 (Phone 1 port) and 20-21 (Phone 2 port) of the AudioMode parameter to configure the DTMF transmission method.
Use bit 6-7 (Phone 1 port) and 22-23 (Phone 2 port) of the AudioMode parameter to configure the hookflash transmission method.
Related Configuration Parameter
Selecting H.323 Connection and H.245 Transmission Methods
You can configure the H.323 connection method and the H.245 transmission method. Use Bit 0 of the ConnectMode parameter to select either the slow-start procedure or the fast-start procedure for the H.323 connection. Use Bit 1 of the ConnectMode parameter to select either a separate H.245 connection or H.245 tunneling for H.245-message transmission.
Related Configuration Parameter
ConnectMode, page 5-32—Bits 0 and 1
Setting Dial Plans
You can set specific dial plan rules and timeout values. Many of these values are determined on a country-by-country basis.
Related Parameter
Complete Reference Table of all Cisco ATA H.323 Services
Table 4-4 is a reference table that lists all configurable features for the Cisco ATA (using H.323), and includes links to the detailed descriptions of the parameters used for configuring these features.
Table 4-4 Configurable Features and Related Parameters
Audio Media Features
•
•
•
•
•
Audio Media Parameters
•
Audio cut-through configuration
Caller ID format
DTMF and hookflash transmission methods
Debug and Diagnosis
Dial plans
Fax Services Features
•
•
Fax Services Parameters
•
H.323 connection method and H.245 transmission method
H.323 endpoint configuration:
•
•
•
•
•
H.323 endpoint parameters:
•
•
•
•
Hook-flash detection timing configuration
Warmline/hotline support (PLAR feature)
Network ringback tone feature
Network-related features:
•
•
•
•
•
Network-related Parameters:
•
•
•
Network timing configuration
User Interface and TFTP Features:
•
•
•
•
•
•
•
User Interface and TFTP Parameters:
•
•
•
Packet Precedence Features:
•
•
Packet Precedence Parameters:
Polarity settings for FXS ports
Ring-cadence format
Supplementary services configuration
CallCmd, page 5-29, CallFeatures, page 5-27, PaidFeatures, page 5-28
Tone format: BusyTone, CallWaitTone
ConfirmTone, DialTone, ReorderTone, and RingBackTone parametersTone Configuration Parameters, page 5-41, SigTimer, page 5-31
Posted: Fri Apr 2 13:00:57 PST 2004
All contents are Copyright © 1992--2004 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
