 the allocated DID number in the Remote Party header of the invite message. Another option to preserve the Originator Caller ID is to check the Redirecting Diversion Header option. In this case, a Diversion header is inserted in the SIP INVITE message, which is used to authenticate the calling party DID. The problem with this approach is Chapter 12: Case Studies 285 that the Diversion header has the original four-digit DN as the calling party and is not recognized by the SP. You need to tell the CUCM where to send the SIP INVITE, or the IP address of the CUBE (as the CUBE is the connecting point for this trunk). To do this, you need to provide the information shown in Figure 12-18: Destination Address 10.10.1.1 (IP Address of remote site gateway or CUBE) SIP Trunk Security Profile: CUBE SIP Trunk Sec Profile SIP Profile: CUBE SIP Trunk Profile After you fill in the previous values, click Save. Figure 12-18 shows the CUBE configuration in the CUCM system. SIP Information Destination Address 10.10.1.1 Destination Address is an SRV Destination Port* MTP Preferred Originating Codec* 711ulaw Presence Group * Standard-Presence-group SIP Trunk Security Profile * CUBE_SIP_Trunk_Sec_Profile Rerouting Calling Search Space < None Out-Of-Dialog Refer Calling Search Space SUBSCRIBE Calling Search Space SIP Profile* CUBE_SIP_Trunk_Profile DTMF Signaling Method No Preference Figure 12-18 CUBE Address 286 SIP Trunking Now, we have to tell CUCM how to route the outbound calls via this newly configured trunk. Follow these steps: Step 1. First, before you can add the route, you need to create the route group. Choose Call Routing > Route/Hunt > Route Group in the CUCM Administration web page. Figure 12-19 shows how to select Route Group from the main menu of Administration web page. Cisco Unified CM Administration CISCO For Cisco Unified Communications Solutions System Call Routing Media Resources Voice Mail Device Application User Ma AAR Group Trunk Coi Dial Rules Route Filter Caller ID Route/Hunt Route Group Caller N SIP Route Pat