|
|
These release notes describe newly incorporated features, resolved issues, and open issues for the Cisco Analog Telephone Adaptor (ATA) 186 Release 2.14.ms.
These release notes provide the following information:
Before you can take advantage of the features of Release 2.14.ms, you must first download and upgrade the Cisco ATA 186 software. You can download the software at:
http://www.cisco.com/cgi-bin/tablebuild.pl/ata186
For more information about downloading and upgrading, see the SCCP Quickstart Guide, available in the v2.14 software for SCCP & MGCP zip file (ata186-v2-14-ms-020415a.zip), and the Cisco ATA 186 Installation and Configuration Guide .
Release 2.14.ms of the Cisco ATA 186 software includes support for Media Gateway Control Protocol (MGCP) and Skinny Client Control Protocol (SCCP).
This document contains information about configuring the Cisco ATA 186 to use both these protocols. As with previous versions of the Cisco ATA 186 software, there are three methods for configuring a Cisco ATA 186 including:
Basic information about using these methods is in the Cisco ATA 186 Installation and Configuration Guide .
 |
Note SCCP uses a different autoprovisioning method. See the "About SCCP" section for details. |
To prevent tampering and unauthorized access to the Cisco ATA 186 configuration, the Cisco ATA 186 built-in web server can now be disabled.
Once the web server is disabled, you may only configure the Cisco ATA 186 through TFTP or IVR.
|
Note When configuring the ATA 186 through the IVR, hexadecimal values must be entered as decimal values. This may be awkward, and it is recommended that TFTP configuration be used. |
1. Assuming an existing OpFlags value of 0x2, to disable the web server, select menu option 323 from the IVR and enter the value 130 (0x82).
When you attempt to access the ATA 186 through the web, the following error messages will be displayed.
2. Assuming an existing OpFlags value of 0x82, to enable the web server, select menu option 323 from the IVR and enter the value 2 (0x2).
The Cisco ATA 186 hardware information is now displayed in the lower left corner of the web interface.
This section contains information about MGCP as implemented for the Cisco ATA 186.
The MGCP gateways interact with a call agent (CA), also called a media gateway controller (MGC), that performs signal processing and call processing on gateway calls.
The Cisco ATA 186 implementation of MGCP complies with the following specifications:
|
Note Security features in NCS 1.0 profile are not supported in this release. |
This release of the Cisco ATA 186 supports the following features with MGCP:
The Cisco ATA 186 has two telephone foreign exchange station (FXS) ports. These ports are called port 0 and port 1. Port 0 is labeled Phone 1 and port 1 is labeled Phone 2. Each port is an MGCP endpoint: Port 0 (Phone 1) is MGCP endpoint 0, while port 1 (Phone 2) is MGCP endpoint 1.
Each MGCP endpoint supports one device, either an analog phone set or a Fax machine, and up to 2 connections per device.
The Cisco ATA 186 supports Fax for most fax machine makes and models for transmission speeds up to and including 9.6 Kbps. Version 2.14 of the Cisco ATA 186 currently does not support Fax at transmission speeds of 14.4 Kbps or faster.
Each connection has a fixed ID, either 0, 1, 2, or 3. Connections 0 and 2 are assigned to MGCP endpoint 0 while connections 1 and 3 are assigned to MGCP endpoint 1.
The IP address part in each MGCP endpoint's identifier can be enclosed by a square bracket [ ] by setting the bit in the ConnectMode parameter that corresponds to square brackets.
This example shows brackets enabled:
This example shows brackets not enabled:
The default is brackets not enabled.
On power up, each MGCP endpoint assumes a disconnected state. The Cisco ATA 186 sends a Restart in Progress (RSIP) command for each MGCP endpoint to the preconfigured CA in one of the following syntaxes (selected by using one of the bits in ConnectMode). The Cisco ATA 186 supports two methods, disconnected and restart.
After a response is received from the CA for the RSIP, the MGCP endpoint is placed in the connected state and resumes normal operation. Subsequent commands are sent according to the NotifiedEntity parameter. Responses are always sent to the source address of the corresponding commands.
If a response to a subsequent command is not received after the maximum number of retransmission attempts, the Cisco ATA 186 assumes that the connection with the CA has been lost and both MGCP endpoints go back into the disconnected state. In this case, the Cisco ATA 186 sends the same message, but the restart keyword is replaced by the disconnected keyword. For example:
The Cisco ATA 186 then sends RSIP messages to the current NotifiedEntity.
To request the device-type from the Cisco ATA 186, the CA must include X-UA in the RequestedInfo (F:) parameter line in an AUEP command. For example:
The Cisco ATA 186 responds with the following device-type:
This release of the Cisco ATA 186 supports the following commands for MGCP:
The Cisco ATA 186 supports the following MGCP connection modes:
The Cisco ATA 186 supports the following local connection options:
Persistent events supported are on-hook transition (hu), off-hook transition (hd), and hookflash (hf). All other notified events must be requested by the CA.
ES: Event with auditable event state
C: Event or signal applicable to a connection
|
Note By default, hu, hd, and hf are set as persistent events. These events can be removed by setting the applicable bits in ConnectMode. |
The parameters listed in Table 5 apply to the Cisco ATA 186 when using MGCP. Some of these parameters are new for this release; some change when MGCP is used.
Table 5 Configuration Parameters for the Cisco ATA 186 with MGCP
| Parameter | IVR Menu | Usage | Default |
|---|---|---|---|
Indicates the version of MGCP to use: Note Spaces are not permitted in the MGCPVer parameter. |
|||
Sets the first retransmission interval of MGCP commands in milliseconds. Subsequent retransmission periods double the previous retransmission interval. |
|||
The maximum number of times the Cisco ATA 186 retransmits commands. After this number, the Cisco ATA 186 assumes that the connection is lost and restarts. |
|||
The port where the Cisco ATA 186 listens for and sends MGCP messages. Using the same port for sending and receiving messages can facilitate passage through a network address translation (NAT) device. |
|||
The port where the Cisco ATA 186 transmits and receives RTP messages. This must be an even number. Each connection uses the next available even-numbered port for RTP. |
|||
Specifies the names of the encoder/decoder as used in LocalConnectionOption in the following order: G.711u-law, G.711A-law, G.723.1, and G.729. Each codec name is separated by a comma with no white space in between. If a name is empty, the default standard-based name is used.
The number of alphanumeric characters in a codec name is limited as follows: If a codec name is longer than the maximum, the default standard-based name is used. |
|||
The G.711u-law and G.711A-law codecs are always available on each connection in the Cisco ATA 186. Additionally, you can select one of two low bit-rate codecs, G.723.1 or G.729a. If LBRCodec is 0, G.723.1 is the low bit-rate codec; if LBRCodec is 3, G.729a is used. G.723.1 is available on both lines without restriction. G.729a is available only on the line specified in ConnectMode bit 21 and when LBRCodec is set to 3. |
|||
Specifies the default preferred codec: |
|||
The 32-bit AudioMode parameter allows fine control of the audio component to suit certain applications. The lower 16 bits control MGCP endpoint 0 while the upper 16 bits controls MGCP endpoint 1. 0 (16): Default value of silence suppression: 1 (17): Use G.711 codec only for this MGCP endpoint, regardless of the value of LBRCodec and PrfCodec. 2 (18): Enable detection of Fax CED (answer) tones. If the tone is detected, switch to Fax mode for the rest of the call. 4-5 (20-21): DTMF transmission method: 1=send AVT tone if remote SDP supports it; otherwise send DTMF in-band |
|||
Connection Mode controls a 32-bit bitmap to control the connection mode of the selected call-signaling protocol. The bitmap definition for this parameter is: 8-12: offset to NSE payload number 96 (0-23). The default is 4. 13: 0 use G.711u-law; 1 use G.711A-law for Fax passthrough. 14: 0 to enable the Cisco proprietary auto codec switch method to support Fax passthrough when a Fax tone is detected; 1 to disable it. In either case, the "FT" event can be reported to the CA. 15: 0/1 enable or disable detecting the Cisco proprietary codec switch method when a Cisco ATA 186 acts as an originating terminal for a Fax call. 16: 1 to use NCS-compliant SDP; 0 to use minimal SDP. 17: 1 to enable dynamic versioning based on CA's version string; 0 to use static MGCP version as provisioned. 18: 1 to disable persistent on-hook and off-hook events. 19: 1 to disable persistent hookflash events. 20: 1 to enable a pair of brackets [ ] to enclose the IP address in the endpoint identifier. 21: 0 to allocate the G.729 LBRC resource to line 0; 1 to allocate it to line 1. 22: 1 to use step mode for quarantine handling; 0 to use loop mode. 23: 1 to enable support for conference connection mode. 24: 1 to disable support for the RSIP *@ipaddress syntax. 28-29: 0 selects the Cisco ATA 186 Style; 1 selects the Bellcore Style; 2 selects the Chalice (VG248) Style of mid-call supplementary services when using SCCP. 30: 0/1 to disable or enable Cisco IP Key Switch (KS) support to handle the differences between CM and KS. 31: 0/1 to disable or enable .xml file support. See the "XML Support" section. |
|||
The 32-bit CallerIdMethod parameter specifies the signal format when generating on-hook and off-hook Caller ID format to use for both FXS lines: Bit 0: Method - 0=Bellcore (FSK); 1=DTMF. 3-8: Maximum number of digits in the telephone number part. Valid values are 1 to 20. 9-14: Maximum number of characters in the name part. Valid values are 1 to 20. 3-6: Start digit. Valid values are: 12="A", 13="B", 14="C", and 15="D". 7-10: End digit. Valid values are: 11="#", 12="A", 13="B", 14="C", and 15="D". 11: Polarity reversal before and after a Caller-ID signal. 0=no reversal, 1=reversal. 12-16: Maximum number of digits in a telephone number. Valid values are 1 to 20. Sweden, Caller ID method=0x0ff6 |
|||
IP address of the primary and secondary domain name system (DNS). If DHCP provides DNS, DNS1IP and DNS2IP overwrites the DHCP supplied values if they are neither 0 nor 0.0.0.0. Do not specify a port parameter. The Cisco ATA 186 uses the default DNS port only. |
|||
Sets the default RTP packet size in number of frames per packet. For the G.711 and G.729 codecs, a frame is 10 ms. For the G.723.1 codec, a frame is 30 ms. |
|||
Specifies the default IP precedence of user datagram protocol (UDP) packets. You can override this value by using the CA LocalConnectionOption. |
|||
This is a 32-bit value divided into several bit fields. Each bit field contains a timeout value that controls the start or stopping of a signaling event. When the ATA 186 has not received any response or command from the call agent, it can periodically send a notify command with the experimental observed event "O: X-NET/ping" to the call agent. This provides a method for the ATA 186 to check the network and to tell the call agent that it is alive. Period between each burst of a call-waiting tone. Range=0 to 255 in 0.1 seconds. Period to wait for a response or command before the ATA goes into a failure-recovery mode. The ATA continues to send the NTFY command for a certain number of times before it declares itself "disconnected" from the call agent and begins to send RSIP commands with restart mode value "disconnected". |
|||
This parameter is not used for MGCP. The MGCP ringing pattern follows the description in the MGCP specification. |
|||
Each parameter is specified with 9 integers; i1-i9 Note Only positive values can be provisioned. For negative values, use the 16-bit 2's complement value. For example, enter -1 as 65535 or 0xffff. i1: Number of frequency components (0, 1, or 2). i2: Transformed frequency of the first frequency component (-32768 to 32767). i3: Transformed frequency of the second frequency component (-32768 to 32767). i4: Transformed amplitude of the first frequency component (-32768 to 32767). i5: Transformed amplitude of the second frequency component (-32768 to 32767). i6: 1 for a continuous tone; 0 for an on-off pattern. i7: Tone on-time (0 to 0xffff sample at 8000 samples/second). i8: Tone off-time (0 to 0xffff sample at 8000 samples/second). |
|||
For DialTone, BusyTone, ReorderTone, and RingBackTone, the unit is a number of 10 ms (so 100=1 second); for the other tones, the value is the number of samples at 8000 samples/second), where: Transformed Frequency=32767·cos (2p·Frequency/8000) Transformed Amplitude=Amplitude·sin (2p·Frequency/8000) Frequency ranges from 0 to 4000 (Hz) Amplitude ranges from 0 to 32767 DialTone=dial tone (dl MGCP signal) BusyTone=busy tone (bz MGCP signal) ReorderTone=reorder tone (also called fast busy or congestion tone) (ro, nbz, cg, or MGCP signals) RingBackTone=ringback tone (rbk, rt MGCP signals) CallWaitTone=call-waiting tone (wt MGCP signals) ConfirmTone=confirmation tone (cf MGCP signal) The following settings are suitable for the US: DialTone=2,31538,30831,3100,3885,1,0,0,0 (equal to -10 dBm) BusyTone=2,30467,28959,1191,1513,0,4000,4000,0 (equal to -21 dBm) ReorderTone="2,30467,28959,1191,1513,0,2000,2000,0 (equal to -21 dBm) RingBackTone=2,30831,30467,1943,2111,0,16000,32000,0 (equal to -16 dBm) CallWaitTone=1,30831,0,5493,0,0,2400,2400,4800 (equal to -10 dBm) ConfirmTone=1,30467,0,5970,0,0,480,480,1920 (equal to -10 dBm) |
|||
The following settings are suitable for Sweden: DialTone=1,30959,0,4253,0,1,0,0,0 (equal to -5 dBm) BusyTone=1,30959,0,2392,0,0,2000,2000,0 (equal to -10 dBm) ReorderTone=1,30959,0,2392,0,0,2000, 6000, 0 (equal to -10 dBm) RingBackTone=1,30959,0,2392,0,0,8000,40000,0 (equal to -10 dBm) CallWaitTone=1,30959,0,2392,0,0,1600,4000,11200 (equal to -10 dBm) ConfirmTone=1,30959,0,2392,0,0,480,480,1920 (equal to -10 dBm) Set the total duration to 0 for the dial, busy, reorder, and ring-back tones so that the duration of these tones follows the MGCP specification or is according to the control of the CA. An intermittent dial tone has the same frequency and level as a regular dial tone; the cadence is fixed internally. The wt1, wt2, wt3, and wt4 signals have the same frequency and level as wt; the cadence is fixed according to the MGCP specification. |
|||
The Domain parameter determines how the domain-name portion of the endpoint identifier "local-endpoint-name@domain-name" is constructed. The following show the valid DOMAIN parameter values. alphanumeric string - alphanumeric string 0 - DHCP-provided domain name, if available; otherwise, IP address is used. |
In MGCP, call agent (CA) redundancy is supported in two ways. Two sets of parameters allow you to configure the primary and secondary CA IP addresses or URL. These parameters are:
|
Note If the CA is identified using the format CallAgentName@HostName, enter the CA name in the CAxUID parameter. Enter the HostName in the CAxorCMx parameter (x is 0 or 1). If the CA is identified using a URL, enter the URL in the CAxorCMx parameter. An optional port number can also be entered in the format CAx:Port# or CMx:Port# (x is 0 or 1). |
On power up or after a configuration update, the Cisco ATA 186 tries to contact the primary CA at CA0orCM0. If there is no response or the address is not reachable, the Cisco ATA 186 then tries to contact the secondary CA. The Cisco ATA 186 continues to alternate attempts to contact the primary and secondary CAs until a response is received.
If the CAxorCMx parameter is configured with a URL, the Cisco ATA 186 contacts the DNS server to resolve the name. The Cisco ATA 186 accepts up to four IP addresses from the DNS server. During operation if contact is lost between the Cisco ATA 186 and its CA, the Cisco ATA 186 uses an exponential timeout period on each attempt to reach the CA at the IP addresses. The Cisco ATA 186 cycles through the IP addresses until a response is received.
To select the Skinny Client Control Protocol (SCCP) mode, set the UseMGCP parameter to 0.
The Cisco ATA 186 implementation of SCCP complies with the following specifications:
The method of provisioning the Cisco ATA 186 by using TFTP is different when using SCCP than it is when using other protocols.
Release 2.14.ms supports t Cisco CallManager versions 3.0 and 3.1.
|
Note The Cisco ATA 186 registers as a Cisco 7960 IP phone in the Cisco CallManager Administration configuration. |
To configure the Cisco ATA 186 for use with Cisco CallManager, follow these steps:
Step 2 Install the Cisco ATA 186. See "Installing the Cisco ATA 186" in the Cisco ATA 186 Installation and Configuration Guide.
Step 3 Make a call. See "Making a Call" in the Cisco ATA 186 Installation and Configuration Guide .
For more information about the Cisco CallManager, see the Cisco CallManager System Guide .
Like other IP devices, the Cisco ATA 186 receives its configuration file and list of Cisco CallManagers from the TFTP server. If the TFTP server does not have a configuration file, the Cisco ATA 186 uses the TFTP server name or IP address and port number as the primary Cisco CallManager name or IP address and port number.
After the Cisco ATA 186 initializes, both ports on the Cisco ATA 186 (SCCP clients) then attempt to connect with the primary call manager. If the connection or registration fails, the Cisco ATA 186 SCCP clients then attempt to register with the next call manager in the call manager list. If that connection fails, the Cisco ATA 186 SCCP clients then attempt to register with the last call manager in the list. If all attempts to connect and register with a call manager fail, the client attempts to connect at a later time.
Upon successful registration, the Cisco ATA 186 clients requests the Cisco CallManager software version, current time and date, line status, and call forward status from Cisco CallManager. If the Cisco ATA 186 loses connection to the active call manager, it attempts to connect to a backup call manager in the call manager list. When the primary call manager comes back online, the Cisco ATA 186 attempts to reconnect to it.
For more information about initialization and registration, see the "Skinny Initial Connection and Registration" section.
The Cisco ATA 186 offers optional support of .xml files. Use ConnectMode Bit 31: 0/1 to disable or enable .xml file support. Cisco CallManager 3.1 supports both .cnf and .cnf.xml file formats, while Cisco CallManager 3.0 supports only the .cnf file format. Configure the Cisco ATA 186 appropriately for the Cisco CallManager version used.
The Cisco ATA 186 tries to download the following files in the order listed by using the TFTP method. After it finds one of these files, it exits the file search:
The Cisco ATA 186 extracts a list of call managers from the downloaded file. Each call manager entry contains the call manager's name, IP address, and port number.
If the Cisco ATA 186 downloads an ATAmacaddress.cnf.xml file, it also extracts the name of the most recent software version from the download file. It then compares this name to the name of the image it is currently using. If the names are different, Cisco ATA 186 downloads the later software release from the TFTP server.
The Cisco ATA 186 attempts to download the following files in the order listed by using the TFTP method. After it finds one of these files, it exits the file search
The Cisco ATA 186 extracts a list of call managers from the downloaded file. Each call manager entry contains the call manager's name, IP address, and port number.
If UseTftp is set to 1, after the Cisco ATA 186 successfully downloads a .cnf or .cnf.xml file, it tries to download the configuration file atadefault.cfg from the TFTP server. If UseTftp is set to 0, the Cisco ATA 186 does not download atadefault.cfg.
The Cisco ATA 186 sends out three CDP messages at one-second intervals to the CDP multicast MAC address 0x01000CCCCCCC before sending any DHCP messages. Each CDP message has the CDP trigger type length value (TLV) for VOIP's VLAN ID (TLV tag 0x000F, value 0x20020001). If the Cisco ATA 186 sees a return CDP message with the TLV tag of 0x000E and the desired VLAN-ID within three seconds of its first sent message, the Cisco ATA 186 begins tagging all IP packets with the 802.1Q VLAN tag. After three CDP messages have been sent with no response to the trigger, the Cisco ATA 186 proceeds as if it is not operating in VLAN environment.
After power up initialization, both Cisco ATA 186 Skinny clients initiate a thread to connect with the primary call manager. If the connection fails, the Cisco ATA 186 retries after an interval computed with an exponential back-off algorithm with the following parameters:
After a successful connection, each client sends a registration message to the call manager. If an acknowledgement (ACK) to the registration is not received within five seconds, the client resends the registration message up to three times until an ACK is received. If no ACK is received, the Cisco ATA 186 attempts to connect with the call manager.
During the course of normal operation, if the TCP connection with the call manager is closed by the call manager or the connection is lost for any other reason, the Skinny client automatically retries to connect and register with the given list of call managers.
After successful registration, the Cisco ATA 186 client:
Depending on the deployment requirement, the Cisco ATA 186 reports the following audio compression and decompression capabilities:
If LBRCodec=0, then for both Cisco ATA 186 Skinny clients:
Codec[0]=G.711u-law, maxFramesPerPacket=60
Codec[1]=G.711A-law, maxFramesPerPacket=60
Codec[2]=G.723.1 at 6.4 kbps, maxFramesPerPacket=20
Codec[0]=G.711u-law, maxFramesPerPacket=60
Codec[1]=G.711A-law, maxFramesPerPacket=60
Codec[2]=G.729, maxFramesPerPacket=48
Codec[3]=G.729A, maxFramesPerPacket=48
Codec[0]=G.711u-law, maxFramesPerPacket=60
Codec[1]=G.711A-law, maxFramesPerPacket=60ar
Cisco ATA 186 reports a device type of 7960 for each Skinny client.
The following call features are supported:
|
Note The mid-call services depend on the style used to invoke the services, Bellcore (default), ATA, or Chalice (VG248). |
The parameters listed in Table 10 apply to the Cisco ATA 186 when using SCCP. Some of these parameters are new for this release; some change when SCCP is used.
Table 10 Configuration Parameters for the Cisco ATA 186 with SCCP
| Parameter | IVR Menu | Usage | Default |
|---|---|---|---|
Specifies the VLAN ID and 802.1Q priority to be used for Voice Audio IP Packet and Signaling IP packet. 0-2: Signaling IP packet priority (000-111). The values are 0 to 10 and the default value is 3. 3-5: Audio IP packet priority (000-111). The values are 0 to 10 and the default value is 5. 18-29: User-specified VLAN ID. Default value is 0. Note VLAN IDs acquired by using CDP discovery overwrite statically configured values. |
|||
Selects which low bit-rate codec resource (either G.723.1 or G.729A) the Cisco ATA 186 will use. |
|||
Specifies the IP address of the primary and secondary DNS servers. If these parameters are set to 0 or 0.0.0.0, the Cisco ATA 186 uses values supplied by its DHCP server; otherwise, the configured values overwrite the DHCP-supplied values. |
|||
Defines IP precedence for UDP packets. A higher value increases the routing priority of the data packets, resulting in less latency. 2: Reliability bit—1=request high reliability 3: Throughput bit —1=request high throughput 4: Delay bit—1=request low delay 5-7: Specifies datagram precedence. Values range from 0 (normal precedence) to 7 (network control). |
|||
|
1: Probe gateway router for network connectivity when using a static IP address Note If Internet Control Message Protocol (ICMP) and echo port is disabled on the router, set this bit to "1" to avoid unnecessary delay at boot time. 3: Specifies whether to use DHCP Option 150. 0 = Include a request in the DHCPDISCOVER packet. 1 = Exclude a request in the DHCPDISCOVER packet. 4: Specifies whether the Cisco ATA 186 will operate in a VLAN environment. 0 = Cisco ATA 186 does not operate in a VLAN environment. 1 = Cisco ATA 186 operates in a VLAN environment. 5: Specifies whether to use VLAN. 6: Specifies whether to use the Cisco Discovery Protocol (CDP). |
|||
|
Specifies the IP address of the TFTP server. If the required call manager IP address and port number cannot be obtained from the TFTP server, CA0orCM0 specifies the IP address and port number of the primary call manager that the Cisco ATA 186 should register to as a Skinny Client upon power up. If a port is specified, it must be separated from the host part with a colon (:). For example, 192.168.1.2:2727, or ca.cisco.com. CA0UID is not used in SCCP mode. If the required call manager IP address and port number were obtained by using the TFTP server, CA1orCM1 is not used in SCCP. Otherwise, CA1orCM1 specifies the IP address and port number of the secondary call manager that the Cisco ATA 186 should register to. If a port is specified, it must be separated from the host part with a colon (:). For example, 192.168.1.2:2727 or ca.cisco.com. The default call manager TFTP server is obtained from DHCP option 150. If 0 is specified in CA0orCM0, the Cisco ATA 186 tries to use the default TFTP server. |
|||
|
The EPIDx or SIDx parameter stores the alphanumeric identifier, to a maximum of 19 characters, of the Cisco ATA 186. In an SCCP environment, EPIDx or SIDx specifies the Skinny ID (SID) of each client that the Cisco ATA 186 registers with the call manager. Because the Cisco ATA 186 has an automated means of creating an SID, the entry in each SIDx field should be either 0 or a dot (.). The default SID for port 0 is the MAC address of the Cisco ATA 186. The default SID for port 1 is the last 5 bytes of the Cisco ATA 186's MAC address with byte 01 appended. For example, if the MAC address of the Cisco ATA 186 is 00 01 2D 01 07 3D: |
|||
If UseTftp is set to 1, the Cisco ATA 186 uses the statically defined value in TftpURL. If UseTftp is set to 0 and CA0orCM0 is nonzero, CA0orCM0 specifies the IP address of TFTP server. If UseTftp and CA0orCM0 are set to 0, the Cisco ATA 186 acquires its TFTP server IP address from DHCP option 150. |
|||
If TftpURL is set to 0, the Cisco ATA 186 uses the value of CA0orCM0 or DHCP 150 as its TFTP IP address. |
|||
Controls the connection mode of the selected call-signaling protocol. The bitmap definition for this parameter is as follows: 8-12: Offset to NSE payload number 96 (2-23). The default is 4. 14: Cisco proprietary codec switch method to support Fax Passthrough when Fax tone is detected. In either case the "ft" event can be reported to the CA if requested. 15: Detect the Cisco proprietary codec switch method (when the Cisco ATA 186 acts as an originating terminal for a fax call). 28-29: Select Cisco ATA 186 Feature Style for invocation of mid-call supplementary services; 0=select ATA style 1=select Bellcore Style (default) 2=select VG248 (Chalice) style. 30: Cisco IP Key Switch (KS) support (to handle differences between CM and KS) 31: .xml file support. (See the "XML Support" section.) |
|||
Allows the user to selectively control the Cisco ATA 186 audio component to suit certain applications. The lower 16 bits control Phone 1, while the upper 16 bits control Phone 2. Bit 2 (18): Enable detection of Fax CED (answer) tone and switch to Fax mode for the rest of the call if the tone is detected. |
|||
Control configuration access to the Cisco ATA 186. When set to a nonzero value, when a user attempts to access the web configuration page or IVR configuration menu, a prompt to enter the correct password appears. The maximum number of characters is 9. |
|||
Controls how the Cisco ATA 186's networking parameters are defined: The parameters affected are the Cisco ATA 186's IP address; subnet mask; network gateway; and the IP addresses for the DNS, NTP, and TFTP servers. |
|||
When DHCP is set to 0, this parameter contains the statically defined IP address used by the Cisco ATA 186. |
|||
When DHCP is set to 0, this parameter contains the statically defined IP address of the network gateway used by the Cisco ATA 186. |
|||
When DHCP is set to 0, this parameter contains the statically defined subnet mask used by the Cisco ATA 186. |
|||
Specifies the signal format when generating on-hook and off-hook caller ID format for both FXS lines. 0: Caller ID Transmission method: If Method=0 (Bellcore method): 3-8: Maximum number of digits in the telephone number portion of the caller ID message. Valid values are from 1 to 20. 9-14: Maximum number of characters in the name portion of the caller ID message. Valid values are from 1 to 20. 3-6: Start digit. Valid values are: 12=A, 13=B, 14=C, 15=D 7-10: End digit. Valid values are: 11=#, 12=A, 13=B, 14=C, 15=D 11: Polarity reversal before and after caller-id signal. 12-16: Maximum number of digits in the telephone number. Valid values are from 1 to 20. 28: Set to 1/0 to disable or enable Caller Waiting Caller ID on Phone 1. 2:9 Set to 1/0 to disable or enable Caller Waiting Caller ID on Phone 2. 30: Set to 1/0 to disable or enable Callee ID on Phone 1. 31: Set to 1/0 to disable or enable Callee ID on Phone 2. Select signal format for generating Caller ID for both lines. |
|||
Controls the on/off period of call progress tone bursts. See the Cisco ATA 186 Installation and Configuration Guide , Appendix F, for more information. |
|||
Enter the IP address and port number of the PC to which debug command messages are to be sent. Syntax: IP_Address.Port Number For example, 192.168.2.159.9000 Note If set to 0 or 0.0.0.0.0, the Cisco ATA 186 does not send any debug messages. |
|||
For each of the six call progress tone parameters listed here, you can specify the frequency components, volume, on/off cadence, and total time the tone is played. See the Cisco ATA 186 Installation and Configuration Guide , Appendix F, for more information. Note In SCCP mode, the ringback cadence is fixed at 2 seconds on, 4 seconds off, and the call waiting period is fixed at 6 seconds. |
See the Cisco ATA 186 Installation and Configuration Guide, Appendix F, for defaults. |
||
The Base port that the Cisco ATA 186 uses to receive and transmit RTP. The Port number must be an even number. Ports are evenly numbered from the base port. The Cisco ATA 186 uses four media ports to handle conference calls on both lines. For example, if port 16384 is used for one connection, the next connection uses port 16386, while other connections use ports 16388 and 16390. |
|||
In SCCP, two levels of logging are available through the TraceFlags parameter. In simplified logging mode, a limited amount of debugging messages are printed. In detailed logging mode, all debugging messages are printed. |
In SCCP mode, the Cisco ATA 186 offers the services described in this section when a dial tone is heard.
The Redial feature allows you to call the last number dialed. To activate Redial, enter *#.
To access your voice-mail box, enter *0.
Speed Dial commands are preset at the call manager by using the Cisco CallManager web page. See the Cisco CallManager documentation shown in "Related Documentation" section for more information. To activate speed dialing, enter *1, *2, *3, or *4.
The Call-forward-all feature allows you to send all calls incoming to one telephone number to another telephone. To activate Call-forward-all, follow these steps:
Step 2 Enter the telephone number to which you want to send the calls. You will hear a confirmation tone.
Step 3 Hang up.
To cancel Call-Forward-all, follow these steps:
Step 2 Hang up.
The method of initiating and using supplementary services that can be used during a call when using SCCP differs according to the mode. There are three methods of invoking supplementary services:
There are two supplementary services unique to the (default) Bellcore style:
For a description of additional supplementary services, see the "Additional Supplementary Services for SCCP" section.
When you hear the call waiting tone while engaged in a call, follow these steps:
Step 2 Press R again to switch between the two calls. If the active remote party hangs up, the other waiting call is resumed automatically. If you hang up, the current call is ended. If the other call is holding, the telephone rings.
To transfer a call or begin a conference call, follow these steps:
Step 2 At the dial tone, enter the telephone number or speed dial of the third party and wait for the call to be answered.
Step 3 If you hang up when the third party answers or rings, the call is transferred. If you press R before the third party answers, it reverts back to the original call. If you press R after the third party answers, the party is added to the conference. If you press R before you hear ringback, the third call is dropped and you revert to the original call.
There are two supplementary services unique to Chalice (VG248) style:
For a description of additional supplementary services, see the "Additional Supplementary Services for SCCP" section.
Call waiting is the same as for Bellcore style.
To initiate three-way calling, transfer, or conference calls.
Step 2 Enter the telephone number or speed dial of the third party and wait for an answer. If you hang up before the third party answers, the new call is dropped. If the original call is still holding, the telephone rings. If you press another R before the third party answers, the new call is dropped and the original call is resumed.
Step 3 After the third party answers, you can press R to obtain a third dial-tone. Then you can press one of the following:
a. R to switch to the other party. You can then switch back and forth.
b. #2 to transfer holding party to the currently active party.
c. #3 to conference with both parties.
d. Any other digit or let it time out (in 4 seconds by default) to maintain the current state.
Step 4 If you hang up while talking to one of the remote parties, the currently active call is ended. If the other remote party is still holding, the telephone rings. If the currently active remote party hangs up, the holding party is resumed automatically.
There are four supplementary services unique to ATA style:
For a description of additional supplementary services, see the "Additional Supplementary Services for SCCP" section.
Call Waiting is the same as for Bellcore style.
To place the current call on hold, press R1 (hookflash followed by 1).
To resume the call, press R again.
To activate Call Transfer, follow these steps:
Step 2 After you hear the dial tone, enter the telephone number.
Step 3 When the other party answers or the remote telephone rings, hang up to transfer the call. You can press R at any time to halt the operation and resume the original call.
To activate conference calling, follow these steps:
Step 2 When you hear the dial tone, enter the telephone number.
Step 3 When the other party answers or the remote telephone rings, press R. You can hang up at any time to halt adding the new party to the conference.
Step 4 After you hang up, the telephone rings if the original party is still holding.
This feature allows the user to receive basic incoming calls even if the telephone is off the hook. In this case, the Cisco ATA 186 plays the standard call-waiting tone to alert the user.
With this feature enabled, if the user hangs up while a party is being placed on hold, the telephone rings. When the handset is picked up, the user is reconnected to the holding party.
This feature allows the Cisco ATA 186 to play an intermittent dial tone if there is a message in the user's voice-mail box.
When the telephone rings, the Cisco ATA 186 sends Caller ID signal to the telephone between the first and second ring (with name, telephone number, time, and date information, if these are available)
With this feature enabled, when the Cisco ATA 186 plays a call waiting tone, it sends an off-hook Caller ID signal to the telephone immediately after the first tone burst. Information included is the name, telephone number, time, and date information, if these are available.
With Callee ID, when the Cisco ATA 186 plays a ringback tone, it sends an off-hook Callee ID signal to the telephone immediately after the first tone burst. Information included is the name, telephone number, time, and date information, if these are available. Enable this feature by changing the Caller ID method parameter. (See Table 10.)
This section lists the issues in previous releases of the Cisco ATA 186 that are resolved in Release 2.14.ms. There are two additional sections for SCCP and MGCP resolved issues, so as to clarify where the issues are.
Spurious DTMF tones can be heard in a conversation by either party.
This problem is caused by the aggressive criteria to detect even a very weak DTMF signal. The DTMF detection algorithm has been enhanced to improve the rejection of false DTMF digits by tracking changes in the signal level.
Audio breaks up after a connection has been up for a very long period. This problem is caused by ARP messages being sent during an active RTP session which slows down the audio process to wait for ARP responses. The Cisco ATA 186 no longer sends unnecessary ARP requests during a RTP session.
If silence suppression is turned on in a G.729 call, loud hissing noises can be heard. The algorithm has been optimized to filter the hissing noises.
If silence suppression is turned on in a G.711 call, the remote end may generate a high level of comfort noise when the Cisco ATA 186 has a low noise level. The Cisco ATA 186 now informs the remote end when the noise level is low so the comfort noise level can be adjusted to the correct level.
Expired IP address continued to be used when DHCP server does not renew it. In rare circumstances, some DHCP servers may refuse IP address renewal requests. If the IP address lease time expires, the Cisco ATA 186 would continue to use it. This causes network instability if the IP address has been assigned to another device. The Cisco ATA 186 now resets if the DHCP server refuses to renew its IP address.
Corrupted DHCP OFFER packet causes Cisco ATA 186 to misinterpret network-related parameter values; for example, IP address, subnet mask, and so on.
Some older DHCP servers may not terminate, if at all, an OFFER packet correctly. When a corrupted packet is not terminated, the Cisco ATA 186 continues to parse the packet indefinitely until the termination value is encountered. The web interface may show illegal network-related values such as IP address, subnet mask, and network router IP address. Calls may not be placed.
The Cisco ATA 186 will now parse only up to the size of the data segment as specified in the UDP packet header. However, corrective actions must be taken on the DHCP server.
The domain name is not automatically added to the DNS query. If the name to be resolved by the DNS server is not a fully qualified domain name (FQDN), the Cisco ATA 186 DNS client does not automatically append the domain name in its DNS query. This can result in an unresolved DNS query if the DNS server does not have the non-fully qualified name in its database.
The Cisco ATA 186 now appends the name to be resolved with the domain name obtained from the DHCP server if it is not a fully qualified domain name.
DHCP server IP address is not obtained from DHCP option 54. The Cisco ATA 186 DHCP client assumes that the DHCP IP address is available from the DHCP header. In some network environments, the information may not be available in the DHCP header, causing DHCP lease time extension to fail.
The Cisco ATA 186 now processes DHCP option 54 to obtain the DHCP server IP address.
A leakage of the out-of-band DTMF into the RTP audio stream causes the DTMF tone to be heard twice and sound garbled on the receving end of a PSTN call. This can cause a problem dialing to a PSTN network through any Cisco gateway's FXO ports.
There is a security hole in the web server of pre-020514 Cisco ATA 186 releases that allows bypass of the UI Password. This issue has been resolved. In addition, a configuration option allowing the user to disable web-based configuration. Users may invoke this feature by setting bit 0x80 of the "OpFlags" configuration parameter to 1.
After an upgrade from Cisco ATA 186 Release 2.14 H.323/SIP software image to Cisco ATA 186 Release 2.14 Skinny/MGCP image, the Cisco ATA 186 may use an incorrect VLAN due to a problem with cookie handling. The workaround is to power-cycle the ATA 186. This issue has been resolved.
In pre-020514 releases, the Cisco ATA 186 does not implement the DHCP REBINDING state. When timer T2 expires, the ATA will request a lease extension by unicast DHCPREQUEST to its original DHCP server. RFC 2131 dictates that an endpoint must broadcast its DHCPREQUEST message. Some DHCP servers will not accept the unicast DHCPREQUEST. Refer to RFC 2131 for details and definitions. This issue has been resolved.
This section lists the SCCP issues in previous releases of the Cisco ATA 186 that are resolved in Release 2.14.ms.
Three-way conference cannot be started. When a three-way conference call is attempted, all parties hear the reorder tone.
IVR configuration is not possible after upgrading from H.323/SIP to MGCP/SCCP.
Each time the IVR is accessed, the voice prompt can be heard initially. During the configuration process, the voice prompt may play partially before ending in complete silence. From this point forward, IVR configuration can no longer be conducted. However, the Cisco ATA 186 can still be configured using the web interface.
After an upgrade from a H.323/SIP image, the default protocol is SCCP. As part of the SCCP startup process, Cisco ATA 186 would attempt to establish a TCP connection with a call manager. This process interfered with the operation of the IVR and caused the abrupt silence and an end to the configuration process.
The Cisco ATA 186 no longer attempts to establish the TCP connection when IVR is in operation.
Call drops when TCP connection between the Cisco ATA 186 and call manager is lost.
In previous releases, if the TCP connection is lost, the Cisco ATA 186 would immediately reset to reestablish the TCP connection with the call manager. This behavior would cause any existing calls to drop.
The Cisco ATA 186 now waits until a call has ended before attempting to reestablish the TCP connection with the call manager every 90 seconds.
Parameter AudioMode bits 1 and 17 for enabling the use of G711-only codec are not implemented. The ATA 186 would report low-bit rate codec capability to the Cisco Call Manager even when it is configured with the the bits set to use G711 only. This feature is now available.
This section lists the MGCP issues in previous releases of the Cisco ATA 186 that are resolved in Release 2.14.ms.
Digit map containing the period '.' may not be processed correctly.
Dial-string is not sent to the call agent after pressing the pound "#" key.
The Cisco ATA 186 no longer includes an empty I: parameter line in an AUEP response. All events are now reported with the corresponding package name.
Response code 250 is not returned for DLCX command. In previous releases, a 200 generic response code is returned to the call agent upon successful execution of the DLCX command. This may cause problems for some call agents that expect a 250 response code.
The Cisco ATA 186 now sends a 250 response code upon successful execution of the DLCX command. Successful executions of other commands are still responded to with a 200 generic response code.
Operation complete (L/oc) event is not sent to the call agent after a signal expires.
In earlier releases, if a call agent sends a digit map whose size is 200 bytes or more, the Cisco ATA 186 would hang, reboot, or both. If the digit map is less than 200 bytes, the problem does not occur. The Cisco ATA 186 now accepts digit maps up to 1024 bytes reliably.
In earlier releases, if a call agent sends the digit map (x.T), the Cisco ATA 186 would hang, reboot, or both. If the digit map does not include (x.T), the problem does not occur. The Cisco ATA 186 now processes the digit map (x.T) correctly.
This section lists open issues for Cisco ATA 186 Release 2.14.ms.
Fax passthrough fails when operating the Cisco ATA 186 in fax passthrough or fax mode at a transmission rate of 14.4 Kbps or V.17 with a Cisco IOS-based gateway.
This fax passthrough issue affects all VoIP protocols (H.323, SIP, MGCP, SCCP) when the fax transmission rate is higher than 9.6 Kbps.
Fax passthrough enhancements have been made in the software but new hardware revisions of the Cisco ATA 186 (ATA186-I1 and ATA186-I2) are required for fax transmission up to 14.4 Kbps.
Success of fax passthrough transmissions depends on network conditions and the fax modem or fax machine tolerance to those conditions. Network must have reasonably low network jitter, network delay, and packet loss rate.
MAC address is displayed in decimal instead of hex format.
Use a scientific calculator to convert the decimal value to hexadecimal value.
This section lists open issues for the SCCP protocol in Cisco ATA 186 Release 2.14.ms.
DTMF tones are not sent out to the FXS ports.
There are no open issues for the MGCP protocol in Cisco ATA 186 Release 2.14.ms.
Use these release notes in conjunction with these documents:
For information about setting up your CA, see your Call Agent documentation.
If you are using the Cisco CallManager, see the Cisco CallManager documentation, which includes:
For information about configuring the gateway for use with either MGCP or SCCP, see the documentation for Cisco IOS 12.2 or later releases.
The following sections explain how to obtain documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at the following URL:
Translated documentation is available at the following URL:
http://www.cisco.com/public/countries_languages.shtml
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Cisco documentation is available in the following ways:
http://www.cisco.com/cgi-bin/order/order_root.pl
http://www.cisco.com/go/subscription
If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click Leave Feedback at the bottom of the Cisco Documentation home page. After you complete the form, print it out and fax it to Cisco at 408 527-0730.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to
You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Inquiries to Cisco TAC are categorized according to the urgency of the issue:
Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:
All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:
http://www.cisco.com/register/
If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered user, you can open a case online by using the TAC Case Open tool at the following URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.
The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer will automatically open a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled; for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). In addition, please have available your service agreement number and your product serial number.
Posted: Thu Apr 24 08:36:18 PDT 2003
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.