I have a working Lync 2010 environment which is currently successfully making PSTN calls through a SIP trunk on a OCS 2007R2 Mediation server which is in co-existence.

The problem I have is with external Direct Access clients, PSTN calls fail. I have verified that the Lync client is logging on through the edge server as an external client. I have also verified that in the same remote location a non-DirectAccess client works perfectly.

I have blocked the relevant DNS records on the UAG server so they correctly get resolved by our external DNS, not the internal.

The following could be relevant;

• I don't recall this happening when the OCS 2007 R2 Edge server was in co-existence. (We now use Lync Edge server).
• I need to do more tests but I suspect that this is only happening when DA is using IPHttps, not ISATAP.

I have resolved this.

I needed to exclude the Lync Pool internal fqdn from being resolved by UAG DNS, this way the Lync Client didn't pick up the internal pool from _sipinternaltls and try and logon as an internal user.

 

• Marked as answer by Tim Chapman Sunday, December 26, 2010 8:16 PM

I have resolved this.

I needed to exclude the Lync Pool internal fqdn from being resolved by UAG DNS, this way the Lync Client didn't pick up the internal pool from _sipinternaltls and try and logon as an internal user.

 

• Marked as answer by Tim Chapman Sunday, December 26, 2010 8:16 PM

I have resolved this.

I needed to exclude the Lync Pool internal fqdn from being resolved by UAG DNS, this way the Lync Client didn't pick up the internal pool from _sipinternaltls and try and logon as an internal user.

 

• Marked as answer by Tim Chapman Sunday, December 26, 2010 8:16 PM

I have resolved this.

I needed to exclude the Lync Pool internal fqdn from being resolved by UAG DNS, this way the Lync Client didn't pick up the internal pool from _sipinternaltls and try and logon as an internal user.

 

• Marked as answer by Tim Chapman Sunday, December 26, 2010 8:16 PM

Hi Tim,

I know this is an old post, but i'm having the same/similar issue. I'm using 2012R2 DirectAccess with Windows 8 and 8.1 clients. I've tried adding the internal Lync server DNS names to the exclusions list on the client via the DA client GPO, but I still get the problem where an external client can login to lync, send IM's but cannot connect a voice call (either PSTN or Lync to Lync). It'll ring at the other end, but when they answer it says "connecting" and then drops after 10 seconds or so. Any ideas?

Cheers

Darren

Same here... early days but it appears to have only started happening since going to Lync 2013 Feb 2015 CU update. DA config and patch levels haven't changed... nor have any firewall rules or IP changes. Although I guess it could also be a client patch but if I connnect via edge with no DA client involved it works fine

• Edited by GeeGeeGeeGee 22 hours 5 minutes ago More info

it appears to be client related, just installed a new win 8.1 machine with Lync2013 (from the office 2013 32bit ISO) and with no patches calls are working just fine when connected to DirectAccess. I also noticed that if I delete the DA config from my broken clients by deleting the NRPT registry settings, reboot, run gpupdate to download the DA settings again, reboot and let DA connect, Lync will be able to make calls for a few minutes before it stops again... strange...

Same here... early days but it appears to have only started happening since going to Lync 2013 Feb 2015 CU update. DA config and patch levels haven't changed... nor have any firewall rules or IP changes. Although I guess it could also be a client patch but if I connnect via edge with no DA client involved it works fine

• Edited by GeeGeeGeeGee Friday, May 01, 2015 9:18 AM More info

Same here... early days but it appears to have only started happening since going to Lync 2013 Feb 2015 CU update. DA config and patch levels haven't changed... nor have any firewall rules or IP changes. Although I guess it could also be a client patch but if I connnect via edge with no DA client involved it works fine

• Edited by GeeGeeGeeGee Friday, May 01, 2015 9:18 AM More info

Same here... early days but it appears to have only started happening since going to Lync 2013 Feb 2015 CU update. DA config and patch levels haven't changed... nor have any firewall rules or IP changes. Although I guess it could also be a client patch but if I connnect via edge with no DA client involved it works fine

• Edited by GeeGeeGeeGee Friday, May 01, 2015 9:18 AM More info

Fixed it! it was down to a client side patch that came out at the beginning of this year. Had to remove the edge servers FQDN from my internal DNS servers et voila! details in the thread below

https://social.technet.microsoft.com/Forums/office/en-US/c9651cfe-3c40-4900-a875-28aa3f15ed0e/lyncskype-client-not-sending-voice-via-edge-when-connected-to-directaccess?forum=lyncvoice&prof=required