Rune - what is your call flow?

What is your voicemail system?

Charles

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

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.