The port number is actually something entirely different.  In this case, I have 
70 SIP trunks between UCM and Lync for a global egress point access (CSS 
different for each SIP trunk).  The ports are actually in the 5020-5050 range.

UCM puts this request in the SIP Start Line (Invite) with 5060 regardless of 
what the SIP trunk uses.

Everything works fine if the user is part of the Lync pool that is associated 
with the Mediation server.  If they are on a different pool, this port of 5060 
(not talking transport here, just SIP message adjustment) causes Lync to drop 
the invite.  When this port reads 5061 in the SIP invite, the calls flow 
properly.



From: Florian Kroessbacher [mailto:[email protected]]
Sent: Friday, March 14, 2014 9:24 AM
To: Matt Slaga (AM)
Cc: 'Cisco-Voip-Puck' ([email protected])
Subject: Re: [cisco-voip] UCM 9.1 SIP Normalization Rules



what about to change the destination port in the siptrunk config ??
--
Florian Kroessbacher
gmail: [email protected]<mailto:[email protected]>


On Fri, Mar 14, 2014 at 2:20 PM, Matt Slaga (AM) 
<[email protected]<mailto:[email protected]>> wrote:
I’m attempting to apply a SIP Normalization rule to make a port adjustment on 
SIP calls between UCM and Lync 2013.


In the header, UCM sends the port number as 5060.  Lync has problems digesting 
this when referring the call to another pool and wants to see the header at 
5061.


The script we are attempting to use is below.  It has been applied to the 
various SIP trunks between UCM and Lync.


When reviewing traces, the port is not being adjusted.  Either the LUA script 
is wrong below, or for some reason it is not being applied.


Any thoughts?




M = {}
function M.outbound_INVITE(msg)
local method, ruri, ver = msg:getRequestLine()
local uri = string.gsub(ruri, "5060", "5061")
msg:setRequestUri(uri)
end
return M




<image001.png>


<image002.png>






Matt Slaga
Dimension Data
Tel:+1-571-203-4132
[email protected]<mailto:[email protected]>





itevomcid
_______________________________________________
cisco-voip mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/cisco-voip

Reply via email to