dino_alexandratos
asked on
Lync SIP Packets Contain Internal IP Address Preventing External Routing
Hi,
We have signed up with a Microsoft certified Lync SIP Trunk provider. The issue we are having is the SIP packets sent from Lync contain the internal IP address of the Lync server not the routable WAN IP address and calls fail as a result.
Our setup is a Lync 2010 Standard server with co-located mediation server. We are using a Fortigate 80c Router / Firewall which is doing NAT / PAT for Lync. We have implemented SIP ALG on the Fortigate.
Our setup has worked but is intermittently dropping out the calls, our provider says this is due to the information Lync is sending.
Can you please advise how to change the SIP packet information to send the WAN IP and not the internal.
Packet traces attached (images anyway, couldn't upload the Wireshark capture)
Thank
Liam
200-OK-RTP-Issue.png
Call-To-0280046323.png
Call-To-0280046509-0280077270.png
We have signed up with a Microsoft certified Lync SIP Trunk provider. The issue we are having is the SIP packets sent from Lync contain the internal IP address of the Lync server not the routable WAN IP address and calls fail as a result.
Our setup is a Lync 2010 Standard server with co-located mediation server. We are using a Fortigate 80c Router / Firewall which is doing NAT / PAT for Lync. We have implemented SIP ALG on the Fortigate.
Our setup has worked but is intermittently dropping out the calls, our provider says this is due to the information Lync is sending.
Can you please advise how to change the SIP packet information to send the WAN IP and not the internal.
Packet traces attached (images anyway, couldn't upload the Wireshark capture)
Thank
Liam
200-OK-RTP-Issue.png
Call-To-0280046323.png
Call-To-0280046509-0280077270.png
You are looking at some network changes. A colocated mediation server is not supported with SIP trunking. You'll need to set up a separate mediation server with two NICs. One NIC will be internal to your LAN and connect to your front-end server/pool and the other will have an externally routable IP address and will connect to your SIP trunk provider.
ASKER
Hi,
You are incorrect a collocated mediation server is supported, this is not a resolution to our issue (see below and link). Please look further into the issue, this is very common with Lync surely someone has worked out an acceptable solution.
Collocation
We also recommend that you collocate the Mediation Server on a Front End pool when you have deployed IP-PBXs or connect to an Internet Telephony Server Provider’s Session Border Controller....
http://technet.microsoft.com/en-us/library/gg398537.aspx
BTW, we did not "Accept as Solution" and this issue has not been resolved.
You are incorrect a collocated mediation server is supported, this is not a resolution to our issue (see below and link). Please look further into the issue, this is very common with Lync surely someone has worked out an acceptable solution.
Collocation
We also recommend that you collocate the Mediation Server on a Front End pool when you have deployed IP-PBXs or connect to an Internet Telephony Server Provider’s Session Border Controller....
http://technet.microsoft.com/en-us/library/gg398537.aspx
BTW, we did not "Accept as Solution" and this issue has not been resolved.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Cliff