quest INVITE sip-header Supported remove request INVITE sip-header Min-SE remove request INVITE sip-header Session-Expires - remove request INVITE sip-header Unsupported modify "Unsupported: "timer" dial-peer voice 555 voip voice-class - sip-profiles 100 (3) Chapter 10: Deployment Scenarios 239 Note the following: 1. This command applies the rules to all SIP traffic on a global basis. 2. This block of commands defines the SIP header manipulation rules. This command applies the rules to SIP traffic passing through a particular dial-peer. Because the rules were already applied on a global basis in (1), this command has no effect here, but if multiple profiles were defined in (2), for example 100 and 101, then profile 100 could be applied globally, as done in (1), and profile 101 could be applied on the dial-peer. Dual Digit Drop RFC-2833 DTMF relay travels in the media (in-band) path of the call, unlike most other DTMF relay mechanisms that travel in the signaling (out-of-band) path. To avoid sending both in-band and out-of band DTMF relay indications to the outgoing leg when CUBE converts from in-band to out-of band methods, use the dtmf-relay rtp-nte digit-drop command on the incoming SIP dial-peer. Example 10-22 shows how to configure dual digits to be dropped. Example 10-22 Dual Digit-Drop Configuration dial-peer voice 100 voip dtmf -relay p-nte digit- - drop SIP Registration Some SIP trunk providers require a SIP registration sequence to be initiated before any calls are routed. CUBE can be used to do the registrations on behalf of the CUCMs or other IP-PBXs in the enterprise. Example 10-23 shows how to configure CUBE to initiate a SIP registration. Example 10-23 SIP Trunk Registration sip-ua registrar ipv4:10.x.x.x registrar dns:csps.cisco.com authentication username xyz password xyz realm cisco.com SIP Transport Choices SIP traffic can use TCP or UDP as the transport protocol. Cisco IOS uses UDP by default, but the desired transport protocol can be configured as shown in Example 10-24. 240 SIP Trunking Examp