Hello:
We have having an issue with our Lync setup, specifically when external users are trying to make a phone call. For example, if someone at home tries to call someone here at corporate thru Lync what is happening is:
1) Call is placed
2) Signal is getting to the phone and it rings
3) Callee tries to answer the phone and the audio is never established.
Running packet traces finds that the traffic at the point of answering is trying to go back out using the private address of the home user (ie if the users WAN address is 70.80.90.100 and their private address is 192.168.1.100) the traffic. Obviously
this doesnt work as its not routable and there is a Deny error in the Cisco confirming this. In the Lync Edge Server setup I see the Audio/Video Edge service external FQDN and internal FQDN say not set. Is this related? Ive found an article
that states these need to be set to "av.yourdomainname.org" for the external and the internal should be "srv-lyncedge.yourdomainname.org". IM, desktop sharing, etc all seem to work fine. The article also states that this is
possibly a bug and should always be set to Not Set. I have also gone into the Topology Builder and for the A/V Edge service i am seeing:
FQDN: av.yourdomain.org, NAT Enabled, IP 192.168.X.9, NAT-Enabled public IPv4 address 98.XXX.XXX.128 (which is outside of our assigned range, which starts at 98.xxx.xxx.129), Port 443, Protocol TCP.
Thanks,
Joe
- Edited by Joseph Bucar Wednesday, April 15, 2015 3:50 PM