Hi Solomon,
As per the Features and services guide for cucm:
Example RDNIS/Diversion Header Use Case
Consider a user that has the following setup:
Desk phone number specifies 89012345.
Enterprise number specifies 4089012345.
Remote destination number specifies 4088810001.
User gets a call on desk phone number (89012345) that causes the remote destination (4088810001) to ring as well.
If the user gets a call from a nonenterprise number (5101234567) on the enterprise number (4089012345), the user desk phone (89012345) rings, and the call gets extended to the remote destination (4088810001) as well.
Prior to the implementation of the RDNIS/diversion header capability, the fields populated as follows:
Calling Party Number (From header in case of SIP): 5101234567
Called Party Number (To header in case of SIP): 4088810001
After implementation of the RDNIS/diversion header capability, the Calling Party Number and Called Party Number fields populate as before, but the following additional field gets populated as specified:
Redirect Party Number (Diversion Header in case of SIP): 4089012345
Thus, the RDNIS/diversion header specifies the enterprise number that is associated with the remote destination.
Configuration of RDNIS/Diversion Header in Cisco Unified Communications Manager Administration
To enable the RDNIS/diversion header capability for Mobile Connect calls, ensure the following configuration takes place in Cisco Unified Communications Manager Administration:
All gateways and trunks must specify that the Redirecting Number IE Delivery — Outbound check box gets checked.
In Cisco Unified Communications Manager Administration, you can find this check box by following the following menu paths:
•
For H.323 and MGCP gateways, execute Device > Gateway and find the gateway that you need to configure. In the Call Routing Information - Outbound calls pane, ensure that the Redirecting Number IE Delivery - Outbound check box gets checked. For T1/E1 gateways, check the Redirecting Number IE Delivery - Outbound check box in the PRI Protocol Type Information pane.
•For SIP trunks, execute Device > Trunk and find the SIP trunk that you need to configure. In the Outbound Calls pane, ensure that the Redirecting Diversion Header Delivery - Outbound check box gets checked.
HTH
Manish
Outbound Calls
 | |
| |
| |
| |
Please find the out put from CUCM, I did enabled redirecting diversion header delivery - outbound under Outbound calls section of my SIP Trunk. But calls are not rolling over to my mobile. I ran the SIP Traces in the gateway and pasted below (also attached). Actually Service Provider said that they look P-Asserted-Identity as UK number 441133015191 instead of +914066164039, to allow the outgoing calls from Verizon's soft switch.
INVITE sip:900919959470707@10.199.0.253:5060 SIP/2.0
Via: SIP/2.0/TCP 10.199.14.22:5060;branch=z9hG4bK2ac6c2d8fd2
From: <sip:+914066164039@10.199.14.22>;tag=54437~b00d5e83-0416-4694-8957-d52f1f3c809f-18905874
To: <sip:900919959470707@10.199.0.253>
Date: Thu, 19 Feb 2015 09:44:38 GMT
Call-ID: ea200c80-4e51b086-ba9-160ec70a@10.199.14.22
Supported: 100rel,timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM10.5
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Cisco-Guid: 3927968896-0000065536-0000001710-0370067210
Session-Expires: 1800
Diversion: "Solomon Kavala - 4105191" <sip:901133015191@10.199.14.22>;reason=follow-me;privacy=off;screen=yes
P-Asserted-Identity: <sip:+914066164039@10.199.14.22>
Remote-Party-ID: <sip:+914066164039@10.199.14.22>;party=calling;screen=yes;privacy=off
Contact: <sip:+914066164039@10.199.14.22:5060;transport=tcp>
Max-Forwards: 67
Content-Type: application/sdp
Content-Length: 201
