Table Of Contents
Release Notes for Cisco IPVC 3521 BRI Gateway, Cisco IPVC 3526 PRI Gateway, and Cisco IPVC 3540 PRI Gateway Release 4.0
Contents
New and Changed Information
New Software Features for all Cisco IPVC 3500 Series Gateways
New Software Features for Cisco IPVC 3521 BRI Gateway
New Software Features for the Cisco IPVC 3526 PRI Gateway and Cisco IPVC 3540 PRI Gateway
Important Notes
Resolved Caveats - Release 4.0
Known Issues
Related Documentation
Release Notes for Cisco IPVC 3521 BRI Gateway, Cisco IPVC 3526 PRI Gateway, and Cisco IPVC 3540 PRI Gateway Release 4.0
June 3, 2005
This document describes all of the notable fixes, outstanding issues, features, and capabilities for the Cisco IPVC Gateway Release 4.0 for the following Cisco products:
•
Cisco IPVC 3521 BRI Gateway
•Cisco IPVC 3526 PRI Gateway
•Cisco IPVC 3540 PRI Gateway
Use these release notes with Administrator's Guide for Cisco IPVC 3526 PRI Gateway and Cisco IPVC 3540 PRI Gateway Module Release 2.0 and Administrator's Guide for Cisco IPVC 3521 BRI Gateway Release 1.0.
Contents
These release notes cover the following topics:
• New and Changed Information
• Important Notes
• Resolved Caveats - Release 4.0
• Known Issues
• Related Documentation
New and Changed Information
New Software Features for all Cisco IPVC 3500 Series Gateways
The Cisco IPVC 3500 Series Gateways include the following new features:
• H.239 Support
• H.235 Media Encryption
• Peer-to-Peer Dialing
• Additional SNMP Trap Server Configuration
• Factory Defaults Reset
• Ethernet Notification
H.239 Support
The Cisco IPVC 3500 Series Gateways now support the H.239 standard.
H.235 Media Encryption
The Cisco IPVC 3500 Series Gateways now support encrypted calls over Internet Protocol (IP) networks. The encryption conforms to the H.235 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 be either AES 128 or DES 56. Non-encrypted calls are not allowed to connect.
•Strong encryption required—Only allows AES 128 encrypted calls. Endpoints that do not support AES 128 are not allowed to connect.
Note An encrypted call in the Cisco IPVC 3526 PRI Gateway and Cisco IPVC 3540 PRI Gateway uses double the resources of a regular call for all bandwidth rates. PRI Gateway capacity when encryption is supported is therefore half of regular gateway capacity, rounded up to the nearest whole call.
Table 1 summarizes the encryption-related capabilities that the gateway offers.
Table 1 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)
You can configure encryption in the Security section of the Settings tab in the Gateway interface.
Procedure
Step 1 In the Gateway interface, click the Settings tab.
Step 2 Click the Security button.
Step 3 Select the Support encryption check box.
Step 4 In the Encryption mode field, choose the required encryption mode:
•Best effort
•Encryption required
•Strong encryption required
Peer-to-Peer Dialing
The Cisco IPVC 3500 Series Gateway now supports peer-to-peer dialing. This involves IP connectivity directly to a peer device such as Cisco CallManager without the need for a gatekeeper. You can configure peer-to-peer dialing in the Settings tab in the Gateway interface.
Procedure
Step 1 In the Gateway interface, click the Settings tab.
Step 2 Click the IP Connectivity button.
Step 3 In the IP connectivity mode field, choose Peer-to-Peer.
Caution Changing this setting causes the gateway to reset.
Step 4 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, 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, 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 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 is triggered by any of the following events: 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 5 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:
a. In the IP Address field, enter or edit the peer IP address.
Note For the Cisco IPVC 3526 PRI Gateway and Cisco IPVC 3540 PRI Gateway, two peers cannot have the same IP address or host name/Uniform Resource Locator (URL).
b. In the IP Port field, enter or edit the peer IP port number.
c. In the Description field, enter or edit the description of the peer.
d. Click Upload.
Note For the Cisco IPVC 3526 PRI Gateway and Cisco IPVC 3540 PRI Gateway, 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 route 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 then 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 6 In the Peer hunting timeout (sec) field, enter the length of time (between 1 and 10 seconds) for which the gateway waits for a TCP response from each peer device contacted. The default value is 5 seconds.
Step 7 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.
Additional SNMP Trap Server Configuration
The Cisco IPVC 3500 Series Gateways now support the configuration of up to three Simple Network Management Protocol (SNMP) servers.
Factory Defaults Reset
The Cisco IPVC 3500 Series Gateways now support faculty default resets using the web, SNMP, or Command Line Interface (CLI).
Ethernet Notification
The Cisco IPVC 3500 Series Gateways now support notification when the Ethernet is not 100 full-duplex.
New Software Features for Cisco IPVC 3521 BRI Gateway
The Cisco IPVC 3521 BRI Gateway includes the following new features added on since Release 3.0:
• New Audio Transcoding Standards
• New Video Modes
• H.263+ and H.263++ Video Protocol Support
• Dual Video
• Automatic gatekeeper discovery and registration
• H.323 Alternate Gatekeeper
• DNS Support for Gateway Configuration
• H.323 Stack Version 4.0
• Reporting
• SNMP Trap Alert Indications
• Configurable Security Access Levels
• Downspeeding
• NTT Japan Switched Protocol
• H.323 Fast Start
• Caller ID Concealment
• H.264 Transparent Support
New Audio Transcoding Standards
The Cisco IPVC 3521 BRI Gateway now supports G.711, G.722, G.723.1, and G.728 audio coding.
Note When your gateway unit includes both a gateway and a Cisco IPVC 35xx MCU, G.728 transcoding i supported on the MCU only.
New Video Modes
The Cisco IPVC 3521 BRI Gateway now supports QCIF, CIF, 4CIF, VGA, SVGA, XGA, and NTSE video modes.
H.263+ and H.263++ Video Protocol Support
The Cisco IPVC 3521 BRI Gateway now supports H.263+ and H.263++ video protocols.
Dual Video
The Cisco IPVC 3521 BRI Gateway now supports dual video streams for a single call using TANDBERG Duo Video™ technology.
Automatic gatekeeper discovery and registration
The Cisco IPVC 3521 BRI Gateway now supports automatic gatekeeper discovery and registration.
H.323 Alternate Gatekeeper
The Cisco IPVC 3521 BRI Gateway now supports an H.323 Alternate Gatekeeper for redundancy.
DNS Support for Gateway Configuration
The Cisco IPVC 3521 BRI Gateway now features Domain Name Server (DNS) support for gateway configuration.
H.323 Stack Version 4.0
The Cisco IPVC 3521 BRI Gateway is now based on H.323 Stack version 4.0 with full backward compatibility.
Reporting
The Cisco IPVC 3521 BRI Gateway now features call detail, statistics, resource utilization status, debugging, and tracing reporting.
SNMP Trap Alert Indications
The Cisco IPVC 3521 BRI Gateway now features SNMP traps for alert event indications.
Configurable Security Access Levels
The Cisco IPVC 3521 BRI Gateway now features configurable security access levels.
Downspeeding
The Cisco IPVC 3521 BRI Gateway now features downspeeding at call setup and in mid-call.
NTT Japan Switched Protocol
The Cisco IPVC 3521 BRI Gateway now supports the NTT Japan switched protocol.
H.323 Fast Start
The Cisco IPVC 3521 BRI Gateway now features H.323 Fast Start on voice calls.
Caller ID Concealment
The Cisco IPVC 3521 BRI Gateway now features caller ID concealment.
H.264 Transparent Support
The Cisco IPVC 3521 BRI Gateway now features transparent support for the H.264 video protocol.
New Software Features for the Cisco IPVC 3526 PRI Gateway and Cisco IPVC 3540 PRI Gateway
The Cisco IPVC 3526 PRI Gateway and Cisco IPVC 3540 PRI Gateway include the following new features added on since Release 3.0:
• Q.931 Redirect Information Element
• Common Administrator User Name for Web, Telnet, and FTP Access
• New User Types
Q.931 Redirect Information Element
The Cisco IPVC 3526 PRI Gateway and Cisco IPVC 3540 PRI Gateway now support forwarding caller ID and redirecting endpoint details to the destination IP terminal using the Q.931 Redirect Information Element.
Common Administrator User Name for Web, Telnet, and FTP Access
The Cisco IPVC 3526 PRI Gateway and Cisco IPVC 3540 PRI Gateway now support a common administrator user name for web, Telnet, and File Transfer Protocol (FTP) access.
New User Types
In addition to the existing Administrator user type, the Cisco IPVC 3526 PRI Gateway and Cisco IPVC 3540 PRI Gateway now support the following user types:
•Operator—This user type has read-only access to the entire Gateway interface, and can monitor and disconnect calls.
•Read only—This user type has read-only access to the entire Gateway interface, but cannot modify any gateway settings.
Important Notes
This section contains important information regarding the insertion of an Rear Transmission Module (RTM) board into the Cisco IPVC 3544 Chassis. The Cisco IPVC 3540 PRI Gateway has two components that you must install in the Cisco IPVC 3544 Chassis: the gateway board and the RTM. These components compliment each other. You must install these components in corresponding slots in the front and at the rear of the Cisco IPVC 3544 Chassis.
When you install the gateway board in the system slot (the top slot) in the front of the chassis, you must insert the RTM in the top slot at the rear of the chassis. When you insert the gateway board in any of the lower three non-system slots in the front of the chassis, you must insert the RTM in the corresponding slot at the rear of the chassis.
Before you insert the gateway RTM board in the top slot at the rear of the chassis, you must first remove the existing RTM and then insert the new RTM.
Procedure
Note This procedure only applies to inserting the gateway RTM board into the top slot of the Cisco IPVC 3544 Chassis.
Step 1 Remove the rear panel covering the slot by loosening the two fastening screws and opening the latches.
Step 2 Unlock the latches at the sides of the board by pulling the latches outwards to the sides.
Step 3 Slowly pull the board halfway out.
Step 4 Detach the flat cable 16-pin connector.
Step 5 Remove the board completely.
Step 6 Slide the new gateway RTM board into the guide railings of the top slot at the rear of the chassis unit until the RTM board is halfway in.
Step 7 Attach the flat cable 16-pin connector to the socket in the middle of the RTM board.
Step 8 Continue to slide the gateway RTM board into the guide railings of the top slot at the rear of the chassis until the board makes the initial contact with the backplane. Be careful not to use unnecessary force.
Step 9 Push the latches in toward the center of the RTM until they lock.
Caution Failure to implement this procedure can damage the Cisco IPVC 3544 Chassis and render it inoperable.
Resolved Caveats - Release 4.0
The following caveats have been resolved since Cisco IPVC 3500 Series Gateway Release 3.0:
•The gateway correctly handles an Empty Capability Set to enable muting or transferring of an IP call (DDTS CSCuk56157).
•The gateway IP address can be modified through the installation menu.
•Gateway interoperability with the Polycom MCU when using G.722 audio in IP calls at 256 Kbps can be configured by setting the RemoveG722ForAccord256K advanced command to Enable.
•On U.S. ISDN networks only, the gateway first attempts to redial a failed video call as a restricted video call. If unsuccessful, the gateway attempts to reconnect the call as a voice call. On all other ISDN networks, the gateway does not use the restricted option.
•When using the improved G.722.1 and H.264 capability policy, G.722.1 and H.264 capabilities are not published to the ISDN or to the IP legs to prevent some legacy equipment crashing.
•2*B calls through the gateway operate correctly.
•Improved interoperability between the gateway and Cisco CallManager when downspeeding is enabled. Set the ConvertClearCauseTowardsIP advanced command to enable to instruct the gateway to send the "Normal Call Clearing" clearing cause to the Cisco CallManager when a downspeeded call terminates. "Normal Call Clearing" enables the Cisco CallManager to correctly close the call. When the ConvertClearCauseTowardsIP advanced command is set to disable, the gateway sends the "Temporary failure" clearing cause to the Cisco CallManager when a downspeeded call terminates. The "Temporary failure" clearing cause prevents the Cisco CallManager closing the call correctly (DDTS CSCuk52284).
•The correct ISDN-to-IP video channel bit rate appears in the Call Details window.
•Interactive Voice Response (IVR) enhancements, including improved recording quality.
•Interoperability with the Cisco IPVC 35xx MCU for calls using G.728 at 128 Kbps.
•You can determine whether or not the gateway automatically strips the leading zeros from the phone number range when using the bonding protocol by using the AddLeadingZerosToPriRange advanced command.
•"N/A" appears in the Hardware version field of the Board Basics tab if an invalid version number is used.
•One-way video from Cisco IPVC 3521 Gateway to Cisco VTA resolved (DDTS CSCuk55871).
Known Issues
The following is a known list of issues for the Cisco IPVC 3500 Series Gateway Release 4.0:
•Downspeeding does not work with Polycom VSX endpoints.
•The start of the IVR message is missing in calls from a WAN Polycom VSX endpoint.
•Difficulties might occur when using Fast Start. We recommend that you do not activate Fast Start.
•H.239 interoperability issues might occur when working with eConf.
•H.239 interoperability issues occur in calls between a TANDBERG ISDN 990MXP endpoint and a Polycom VSX LAN endpoint.
•H.239 is not supported in 2*B calls.
•H.239 supports only the H.263 codec in the second channel. H.264 is not supported.
•We recommend that you use an Enhanced Media Processor (EMP) when working with a Cisco IPVC 35xx MCU in H.239 mode.
•(Cisco IPVC 3526 PRI Gateway and Cisco IPVC 3540 PRI Gateway only) When working with Sony PCS-G70, use version 3.0 or later only.
Related Documentation
For additional information about Cisco MeetingPlace products or about obtaining documentation or technical support, see the Guide to Cisco MeetingPlace Conferencing Documentation and Support at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/conf/mtgplace/roadmap.htm
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
© 2005 Cisco Systems, Inc. All rights reserved.
