« Back to SIP Transparency and Normalization Questions

Delete the top-most diversion header or change order of Multiple Diversion

Combination View Flat View Tree View
Threads [ Previous | Next ]
Delete the top-most diversion header or change order of Multiple Diversion
Answer
11/8/11 5:22 AM
I want to change how a voicemail system treats a diverted call.

Calls that are diverted multiple times and eventually sent to a voicemail system are presented with the mailbox for the last forwarding party.
I need a script that makes the voicemail system play the original called numbers mailbox.

For INVITEs received on a SIP trunk, the following behavior applies:
¿ If multiple diversion headers are present in the incoming message, the bottom-most diversion header determines the original called number. The top-most diversion header determines the last forwarding party and diversion reason.

 
I need to either change the order, or to delete all Diversion headers but the bottom-most diversion header.

Diversion: "nn" <sip:4981@172.29.1.12>;reason=unconditional;privacy=off;screen=yes
Diversion: "nn" <sip:4983@172.29.1.12>;reason=unconditional;privacy=off;screen=yes
Diversion: "nn" <sip:4986@172.29.1.12>;reason=unconditional;privacy=off;screen=yes
Flag

RE: Delete the top-most diversion header or change order of Multiple Divers
Answer
11/8/11 6:13 AM as a reply to Rune Heggelund.
Rune - what is your call flow?

What is your voicemail system?

Charles
Flag

RE: Delete the top-most diversion header or change order of Multiple Divers
Answer
11/8/11 2:14 PM as a reply to Charles Ragan.
Hi!

This is an attendant system (Trio Enterprise).
The system is not able to interoperate the diversion header different. I need a SIP Normalization Scripts that change the header.
Support both diversion and history header.
Flag

RE: Delete the top-most diversion header or change order of Multiple Divers
Answer
11/8/11 6:59 PM as a reply to Rune Heggelund.
Okay, but the call flow is what?

pstn-----sip----cucm-----sip?------trio-vmail


Is your integration from cucm to trio a sip trunk as well?

Obviously, this will determine where you apply your script.

Also, the next thing you need to do is set up a place where you can make packet captures. This will give you an idea of what values you have for attempting to repopulate the dh with the original called number.

For example, a way to reach back into the originally called number, may be the PAI header. At this point, you could possibly do logic similar to:

-gather pai header
-remove dh
-add dh
-repopulate dh with pai

A lot will depend on your call flow.
Charles
Flag

RE: Delete the top-most diversion header or change order of Multiple Divers
Answer
11/8/11 7:30 PM as a reply to Charles Ragan.
Thank you for replying.

The setup is as follow;
pstn-----sip----cucm-----sip------trio-vmail

I can apply the script at the outgoing invite to the trio-vmail.
I still need some help to create the script.

Here is what sendt in the Invite header;
Diversion: "nn" <sip:4981@172.29.1.12>;reason=unconditional;privacy=off;screen=yes
Diversion: "nn" <sip:4983@172.29.1.12>;reason=unconditional;privacy=off;screen=yes
Diversion: "nn" <sip:4986@172.29.1.12>;reason=unconditional;privacy=off;screen=yes

If I convert the diversion headers into History-Info headers for outbound INVITE messages. And then remove the Diversion header. This is what I got;

M = {}
function M.outbound_INVITE(msg)
if msg:getHeader("Diversion")
then
msg:convertDiversionToHI()
msg:removeHeader("Diversion")
end
end
return M

History-Info: <sip:4980@172.29.1.12?Reason=sip;cause=302;text="unconditional">;index=1
History-Info: <sip:4981@172.29.1.12?Reason=sip;cause=302;text="unconditional">;index=1.1
History-Info: <sip:9999@172.29.1.17:5060>;index=1.1.1

The Trio System understands both diversion headers and History-Info headers.

If I first convert the diversion headers into History-Info headers, then I got information I need in index=1.
If I now remove all other index lines everything should be ok.
Flag

RE: New Message from Rune Heggelund in Cisco Unified Communications Manager
Answer
11/8/11 8:28 PM as a reply to Rune Heggelund.
Ahh..okay. So trio can¿t choose between 1st redirect or last redirect? ¿

In the values below ¿ what is the numbering scheme for the ¿nn¿ on the dh¿s?



From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Tuesday, November 08, 2011 1:30 PM
To: cdicuser@developer.cisco.com
Subject: New Message from Rune Heggelund in Cisco Unified Communications Manager SIP (SIP) - SIP Transparency and Normalization Questions: RE: Delete the top-most diversion header or change order of Multiple Divers

Rune Heggelund has created a new message in the forum "SIP Transparency and Normalization Questions":

--------------------------------------------------------------
Thank you for replying.

The setup is as follow;
pstn-----sip----cucm-----sip------trio-vmail

I can apply the script at the outgoing invite to the trio-vmail.
I still need some help to create the script.

Here is what sendt in the Invite header;
Diversion: "nn" <sip:4981@172.29.1.12>;reason=unconditional;privacy=off;screen=yes
Diversion: "nn" <sip:4983@172.29.1.12>;reason=unconditional;privacy=off;screen=yes
Diversion: "nn" <sip:4986@172.29.1.12>;reason=unconditional;privacy=off;screen=yes

If I convert the diversion headers into History-Info headers for outbound INVITE messages. And then remove the Diversion header. This is what I got;

M = {}
function M.outbound_INVITE(msg)
if msg:getHeader("Diversion")
then
msg:convertDiversionToHI()
msg:removeHeader("Diversion")
end
end
return M

History-Info: <sip:4980@172.29.1.12?Reason=sip;cause=302;text="unconditional">;index=1
History-Info: <sip:4981@172.29.1.12?Reason=sip;cause=302;text="unconditional">;index=1.1
History-Info: <sip:9999@172.29.1.17:5060>;index=1.1.1

The Trio System understands both diversion headers and History-Info headers.

If I first convert the diversion headers into History-Info headers, then I got information I need in index=1.
If I now remove all other index lines everything should be ok.
--
To respond to this post, please click the following link:

<http://developer.cisco.com/web/sip/forums/-/message_boards/view_message/4725147>

or simply reply to this email.
Flag

RE: New Message from Charles Ragan in Cisco Unified Communications Manager
Answer
11/8/11 8:56 PM as a reply to Charles Ragan.
Rune ¿ if the pai is there (it would be the original To: I believe) ¿ you should be able to do something similar to...

M = {}
function M.outbound_INVITE(msg)
local uri = msg:getUri("P-Asserted-Identity")
msg:removeHeader("Diversion")
msg:addHeader("Diversion", uri)
end
return M

Rune Heggelund has created a new message in the forum "SIP Transparency and Normalization Questions":

--------------------------------------------------------------
Thank you for replying.

The setup is as follow;
pstn-----sip----cucm-----sip------trio-vmail

I can apply the script at the outgoing invite to the trio-vmail.
I still need some help to create the script.

Here is what sendt in the Invite header;
Diversion: "nn" <sip:4981@172.29.1.12>;reason=unconditional;privacy=off;screen=yes
Diversion: "nn" <sip:4983@172.29.1.12>;reason=unconditional;privacy=off;screen=yes
Diversion: "nn" <sip:4986@172.29.1.12>;reason=unconditional;privacy=off;screen=yes

If I convert the diversion headers into History-Info headers for outbound INVITE messages. And then remove the Diversion header. This is what I got;

M = {}
function M.outbound_INVITE(msg)
if msg:getHeader("Diversion")
then
msg:convertDiversionToHI()
msg:removeHeader("Diversion")
end
end
return M

History-Info: <sip:4980@172.29.1.12?Reason=sip;cause=302;text="unconditional">;index=1
History-Info: <sip:4981@172.29.1.12?Reason=sip;cause=302;text="unconditional">;index=1.1
History-Info: <sip:9999@172.29.1.17:5060>;index=1.1.1

The Trio System understands both diversion headers and History-Info headers.

If I first convert the diversion headers into History-Info headers, then I got information I need in index=1.
If I now remove all other index lines everything should be ok.
--
To respond to this post, please click the following link:

<http://developer.cisco.com/web/sip/forums/-/message_boards/view_message/4725147>

or simply reply to this email.
--
To respond to this post, please click the following link:

<http://developer.cisco.com/web/sip/forums/-/message_boards/view_message/4727040>

or simply reply to this email.
Flag