Lync wrong IP-Nr. in candidate list for avedge

• 2012년 7월 31일 화요일 오전 11:37

   

   
  

  0

  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 217.192.57.86. All DNS entries in the external DNS for access, webconf und avconf are correct and can be verrified.

  access.domain = 217.192.57.84 -> x.x.x.213

  webconf.domain = 217.192.57.85 -> x.x.x.214

  avconf.domain = 217.192.57.86 -> 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 217.192.57.84 52745 typ relay raddr 83.144.247.132 rport 10701

  a=candidate:2 2 TCP-PASS 6556158 217.192.57.84 52745 typ relay raddr 83.144.247.132 rport 10701

  a=candidate:3 1 TCP-ACT 7077119 217.192.57.84 52745 typ relay raddr 83.144.247.132 rport 10701

  a=candidate:3 2 TCP-ACT 7076606 217.192.57.84 52745 typ relay raddr 83.144.247.132 rport 10701

  instead of 217.192.57.84 there should be 217.192.57.86

  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

  ---

  Bueschu

  • 응답
  • 인용