SIP UPDATE Message per RFC 3311

Last Updated: December 20, 2011

The SIP UPDATE Message per RFC 3311 feature provides Session Description Protocol (SDP) support for Session Initiation Protocol (SIP)-to-SIP calls. The SIP Service Provider Interface (SPI) is modified to support the following media changes using the UPDATE message:

  • Early dialog SIP-to-SIP media changes.
  • Mid dialog SIP-to-SIP media changes.

The Support for SIP UPDATE Message Per RFC 3311 feature is enabled by default on the Cisco Unified Border Element (UBE) and no configuration is required.

Finding Feature Information

Your software release may not support all the features documented in this module. For the latest feature information and caveats, see the release notes for your platform and software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the Feature Information Table at the end of this document.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

Prerequisites for SIP UPDATE Message per RFC 3311

  • At least one offer or answer negotiation must be completed for Cisco UBE to handle the UPDATE message with SDP.
  • An early dialog UPDATE message with SDP is processed only when both endpoints support the UPDATE message.

Cisco Unified Border Element

  • Cisco IOS Release 15.1(3)T or a later release must be installed and running on your Cisco Unified Border Element.

Cisco Unified Border Element (Enterprise)

  • Cisco IOS XE Release <TBD> or a later release must be installed and running on your Cisco ASR 1000 Series Router.

Restrictions

  • An UPDATE message with SDP is not supported for SIP-to-H323 calls.
  • An UPDATE message with SDP with a fully qualified domain name (FQDN) is not supported.
  • Contact information in the UPDATE message is not supported.
  • A retransmitted UPDATE message with SDP is ignored by the SIP stack. No response is sent for retransmitted UPDATE messages.

Feature Information for the SIP UPDATE Message per RFC 3311

The following table provides release information about the feature or features described in this module. This table lists only the software release that introduced support for a given feature in a given software release train. Unless noted otherwise, subsequent releases of that software release train also support that feature.

Use Cisco Feature Navigator to find information about platform support and Cisco software image support. To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.

The table below lists the release history for the ISR.

Table 1 Feature Information for Support for SIP UPDATE Message per RFC 3311

Feature Name

Releases

Feature Information

Support for SIP UPDATE Message per RFC 3311

15.1(3)T

The Support for SIP UPDATE Message per RFC 3311 feature provides Session Description Protocol (SDP) support for Session Initiation Protocol (SIP)-to-SIP calls. The SIP Service Provider Interface (SPI) is modified to support the following media changes using the UPDATE message:

  • Early dialog SIP-to-SIP media changes.
  • Mid dialog SIP-to-SIP media changes.

The table below lists the release history for the ASR.

Table 2 Feature Information for Support for SIP UPDATE Message per RFC 3311

Feature Name

Releases

Feature Information

Support for SIP UPDATE Message per RFC 3311

TBD

The Support for SIP UPDATE Message per RFC 3311 feature provides Session Description Protocol (SDP) support for Session Initiation Protocol (SIP)-to-SIP calls. The SIP Service Provider Interface (SPI) is modified to support the following media changes using the UPDATE message:

  • Early dialog SIP-to-SIP media changes.
  • Mid dialog SIP-to-SIP media changes.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

© 2011 Cisco Systems, Inc. All rights reserved.