SIP Diversion Header Enhancements

Table Of Contents

SIP Diversion Header Enhancements

Prerequisites

Information about SIP Diversion Header Enhancements

How to Configure SIP Diversion Header Enhancements

SIP Diversion Header Enhancements

The SIP Diversion Header Enhancements feature enables time-division multiplex (TDM) gateways and Cisco Unified Communications Manager Express to populate the SIP Diversion Header with a domain name. Localhost command-line interface commands can be used to configure the domain name globally or at the dial peer level. This feature also provides choice of transparent pass through or application of address hiding to the SIP Diversion Header on Cisco UBE platforms.

Prerequisites

Cisco Unified Border Element

•Cisco IOS Release 12.4(22)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 3.1S or a later release must be installed and running on your Cisco ASR 1000 Series Router.

Information about SIP Diversion Header Enhancements

To enable this feature, you must first configure the sip-ua command to place the router in SIP user-agent configuration mode before you can use the host-registrar command.

By default, the Session Initiation Protocol (SIP) gateway and Cisco Unified Communications Manager Express (Cisco Unified CME) populate the host portion of the diversion header with the domain name or IP address of the gateway that generates the request or response. The SIP gateway and Cisco Unified CME also populate the host portion of the redirect contact header with the session target IP address or hostname of the matching dial peer.

When the host-registrar command and the registrar command are both configured in SIP user-agent configuration mode, the SIP gateway or Cisco Unified CME populate the host portion of both the diversion and redirect contact headers with the domain name or IP address configured by the registrar command.

The host-registrar command should be configured along with the registrar command in SIP user-agent configuration mode. If the host-registrar command is configured without the registrar command, the host portion of the diversion header is populated with the domain name or IP address of the gateway and the host portion of the redirect contact header is populated with the session target IP address or hostname of the matching dial peer.

How to Configure SIP Diversion Header Enhancements

To configure the SIP Diversion Header Enhancements feature, complete this task in this section.

---

Note Some keywords and arguments have been omitted from the command syntax shown here. For complete command syntax information, see the Cisco IOS Voice Command Reference.

---

SUMMARY STEPS

1. enable

2. configure terminal

3. sip-ua

4. registrar registrar-server-address

5. host-registrar

DETAILED STEPS

	Command or Action	Purpose
Step 1	enable Example: Router> enable	Enables privileged EXEC mode. •Enter your password if prompted.
Step 2	configure terminal Example: Router# configure terminal	Enters global configuration mode.
Step 3	sip-ua Example: Router(config)# sip-ua	Enters SIP User Agent configuration mode.
Step 4	registrar registrar-server-address Example: Router(config-sip-us)# registrar ipv4:10.1.1.1	The SIP registrar server address to be used for endpoint registration. This value can be entered in one of three formats: •dns:address—the Domain Name System (DNS) address of the primary SIP registrar server (the dns: delimiter must be included as the first four characters). •ipv4:address—the IP address of the SIP registrar server (the ipv4: delimiter must be included as the first five characters). •ipv6:[address]—the IPv6 address of the SIP registrar server (the ipv6: delimiter must be included as the first five characters and the address itself must include opening and closing square brackets).
Step 5	host-registrar Example: Router(config-sip-ua)# host-registrar	Populates the SIP User Agenet registrar domain name or IP address value in the host portion of the diversion header and redirects the contact header of the 302 response.