Remove second Diversion header from CUBE using SIP profile

[Tibin Thomas]

Hi

My service provider doesn't support the second diversion header, but needs the first diversion header to process the forwarded calls from IP phone. Please help me to get rid second diversion header using sip-profile in CUBE. Both these diversion headers are passing from call manager to CUBE and the second diversion header is added by the peterconnect attendant system using by Call Operator.

Wants to remove the Diversion header "Diversion: <sip:0063902XXXX@153.xxx.yyy.zzz>;reason=unknown;privacy=off;screen=yes" from below INVITE request received on CUBE from Callmanager.

Received:
INVITE sip:0063902XXXX@10.xxx.yyy.zzz:5060 SIP/2.0
Via: SIP/2.0/TCP 153.xxx.yyy.zzz:5060;branch=z9hG4bK33e10174434615
From: <sip:+6681428XXXX@153.xxx.yyy.zzz>;tag=12704042~7a033af2-6007-41ab-b6ae-4c7743e8637d-64382610
To: <sip:0063902XXXX@10.xxx.yyy.zzz>
Date: Wed, 22 Mar 2017 02:58:10 GMT
Call-ID: 60841280-8d11e842-2729f6-8b667099@153.xxx.yyy.zzz
Supported: 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
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=MIXED
Cisco-Guid: 1619268224-0000065536-0000097860-2338746521
Session-Expires:  1800
Diversion: "Reception" <sip:2021XXXX@153.xxx.yyy.zzz>;reason=unknown;privacy=off;screen=yes
Diversion: <sip:0063902XXXX@153.xxx.yyy.zzz>;reason=unknown;privacy=off;screen=yes

Regards\Tibin

[kcastillo22]

Hello Tibin,

You can try with:

voice class sip-profiles 100
request INVITE sip-header Diversion copy "<sip:2021(.*)@" u01
request INVITE sip-header Diversion modify "<sip:0063902(.*)@" "<sip:2021\u01@"
request INVITE sip-header Diversion remove

Pretty much what it would do is to make the second diversion look just like the primary one and then it would remove the first one. You could test it at: https://cway.cisco.com/tools/SipProfileTest/

Another way to do this would be to apply a Normalization Script (on the SIP trunk that goes from CUCM to CUBE) to remove the second Diversion on the SIP packet before sending it to CUBE (You will need to do some research on LUA scripting since TAC does not assist with that, Cisco has some good documentation under their developers section)

I hope this can help you to address your issue. Have a lovely day.