Cisco Cisco IOS Software Release 15.0(1)XA
11
Release Notes for Cisco 2800 Series Integrated Services Routers with Cisco IOS Release 15.0(1)XA
OL-20857-06
New and Changed Information
Support for PAI, PPI, and Privacy Headers on the SIP Trunk of Cisco Unified Communications
Manager Express
Manager Express
Support for PAI, PPI, and Privacy Headers on the Cisco Unified CME SIP trunk. When enabled, Calling
Number, Calling Name, and Privacy information is sent using PAI, PPI, and Privacy headers over the SIP
trunk of Cisco Unified CME. This feature also enables interworking between the Remote-Party-ID
(RPID) information contained in SIP line-side messages to PAI, PPI, and Privacy header information on
the SIP trunk.
Number, Calling Name, and Privacy information is sent using PAI, PPI, and Privacy headers over the SIP
trunk of Cisco Unified CME. This feature also enables interworking between the Remote-Party-ID
(RPID) information contained in SIP line-side messages to PAI, PPI, and Privacy header information on
the SIP trunk.
Support for Stripping off Progress Indicator from Incoming Q.931 CALL-PROCEEDING Messages on
Cisco IOS SIP Gateways, Cisco IOS H.323 Gateways, and Cisco UBEs
Cisco IOS SIP Gateways, Cisco IOS H.323 Gateways, and Cisco UBEs
Support for stripping off progress indicator (PI) from incoming Q.931 CALL-PROCEEDING message
on Cisco IOS SIP and H.323 gateways and on Cisco UBEs. Configuration of this feature determines
whether an incoming Q.931 CALL-PROCEEDING message with a PI value results in a SIP 183 message
or H.323 Progress message. This behavior allows interworking with third-party SIP and H.323 servers.
For details about enabling this feature, see the progress_ind command in the Cisco IOS Voice Command
Reference at
on Cisco IOS SIP and H.323 gateways and on Cisco UBEs. Configuration of this feature determines
whether an incoming Q.931 CALL-PROCEEDING message with a PI value results in a SIP 183 message
or H.323 Progress message. This behavior allows interworking with third-party SIP and H.323 servers.
For details about enabling this feature, see the progress_ind command in the Cisco IOS Voice Command
Reference at
IEEE 802.1ag - D8.1 standard Compliant CFM, Y.1731 multicast LBM / AIS / RDI / LCK, IP SLA for
Ethernet
Ethernet
The ITU-Y.1731 Fault Management Functions feature adds to IEEE CFM the ETH-AIS and ETH-RDI
functions for fault detection, fault verification, and fault isolation in large metropolitan-area networks
(MANs) and WANs. For more information, see:
functions for fault detection, fault verification, and fault isolation in large metropolitan-area networks
(MANs) and WANs. For more information, see:
Support for interworking between RSVP and non-RSVP call legs for SIP calls. Support for non-RSVP
H.323 call leg to RSVP SIP call leg
H.323 call leg to RSVP SIP call leg
The Support for Interworking Between RSVP Capable and RSVP Incapable Networks feature provides
precondition-based Resource Reservation Protocol (RSVP) support for basic audio call and
supplementary services on Cisco Unified Border Element (UBE). This feature improves the
interoperability between RSVP and non-RSVP networks. RSVP functionality added to Cisco UBE helps
you to reserve the required bandwidth before making a call.
precondition-based Resource Reservation Protocol (RSVP) support for basic audio call and
supplementary services on Cisco Unified Border Element (UBE). This feature improves the
interoperability between RSVP and non-RSVP networks. RSVP functionality added to Cisco UBE helps
you to reserve the required bandwidth before making a call.
Support for dynamic payload type interworking for DTMF and codec packets for SIP-to-SIP calls
The Support for Dynamic Payload Type Interworking for DTMF and Codec Packets for SIP-to-SIP Calls
feature. This feature allows the Cisco Unified Border Element interwork between different dynamic
payload type values across the call legs for the same codec. Also, Cisco UBE supports any payload type
value for audio, video, named signaling events (NSEs), and named telephone events (NTEs) in the
dynamic payload type range.
feature. This feature allows the Cisco Unified Border Element interwork between different dynamic
payload type values across the call legs for the same codec. Also, Cisco UBE supports any payload type
value for audio, video, named signaling events (NSEs), and named telephone events (NTEs) in the
dynamic payload type range.