Lync 2013, IPv6 and Directaccess

 
Hi everyone,
This is my first post about Lync and my last about Directaccess

With Lync 2013 Preview, ipv6 is fully supported, so directaccess should work with Lync. Let’s check!

Firstly, we need to configure the lync topology. There is only one standard front-end server.
My sip domain is labda.local. Directaccess clients are configured to send every packet to labda.local domain in the IPsec tunnel.


My environment is full ipv6 so I disable IPv4 and enable IPv6 in the topology builder.


I activate the enterprise voice and the conferencing service on this server.

Ok now let’s check that Lync 2013 is working on the client!
Firstly, the dns resolution for the automatic configuration (2abc::11 is the dns server on my nrpt table, it’s the directaccess server):


Great, now let’s connect the lync client.


And a call? (i have only one user ). It’s working.


And a meet now?


So every thing is working is IPV6. Even Location services!


Even location services? Maybe not… Let’s check on the client…


No proposition, what is my ipv6 address?


Mmmm, very weird… Snooper is my friend!! So firstly, turn on tracing on my client


I get a log file on the client, stored in
%userprofile%\AppData\Local\Microsoft\Office\15.0\Lync\Tracing
Let’s analyze the log with snooper, and search the keyword subnet



So the subnet information sent by the client contains the ipv4 address, that’s why i don’t get my location information. So Lis doesn’t work with directaccess ip. I thing that it’s a normal behavior, we cannot predict where my client will be with directaccess. The best location with directaccess is somewhere!

Bye
Tweeter