2012년 7월 31일 화요일 오전 11:37
We have a Lync Deplyoment with one standard edition server and a single consolidated edge server. The edge server has two nic's. The external nic has 3 IP-Nr from the private range (x.x.x.213 / 214 / 215). The traffic to this nic get's nated by the outer firewall. In the topology builder I have configured the "NAT enabled public IP address used" with 188.8.131.52. All DNS entries in the external DNS for access, webconf und avconf are correct and can be verrified.
access.domain = 184.108.40.206 -> x.x.x.213
webconf.domain = 220.127.116.11 -> x.x.x.214
avconf.domain = 18.104.22.168 -> x.x.x.215
The Edge Server is behind an outer firewall and the traffic flows thru a TMG Server to get to the LAN.
If I try to call a federated partner the ringing does work but the the media path does not work. When I check the log file I can see that the candidate list contains the wrong IP-Nr for the avedge.
a=candidate:2 1 TCP-PASS 6556159 22.214.171.124 52745 typ relay raddr 126.96.36.199 rport 10701
a=candidate:2 2 TCP-PASS 6556158 188.8.131.52 52745 typ relay raddr 184.108.40.206 rport 10701
a=candidate:3 1 TCP-ACT 7077119 220.127.116.11 52745 typ relay raddr 18.104.22.168 rport 10701
a=candidate:3 2 TCP-ACT 7076606 22.214.171.124 52745 typ relay raddr 126.96.36.199 rport 10701
instead of 188.8.131.52 there should be 184.108.40.206
The snooper tools shows me, that the MRAS Host Name in the sip Message "200 Ok" is correct - avconf.siga.ch. The www.testocsconnectivity.com shows no error and I can do a Lync call as a remote User to an internal User.
Can you help me
Best Regards - Bueschu
2012년 7월 31일 화요일 오후 12:25
The topic of this forum is Exchange and not Lync.
Ask in the Lync Forum instead.
2012년 7월 31일 화요일 오후 1:06
sorry for my mistake
best regards Bueschu
- 답변으로 표시됨 Bueschu 2012년 7월 31일 화요일 오후 1:11