Hi all,
We are in the process of implementing CMS with Expressway and Skype Integration.
The current configuration is working as expected when connecting from Skype Endpoints on the Local LAN, the SIP Traffic is traversing from the FE over to the Expressway and then being sent to the CMS and down to either Spaces or UCMC Endpoints and we can see A/V being transfered over to the CMS using UDP.
Now our issue is that we are also utilizing DirectAccess for external users and we are not using Split-DNS, i.e everything is being forced through the DirectAccess Tunnel. This is then being NAT64 over to whatever resources that needs to be access and is working fine for Skype <-> Skype interactions but fails towards the Cisco Integration.
We can see that the SIP Invites are being sent, a call is answered and then by the looks of it it fails the ICE process and hangs up after 10 seconds. As DirectAccess utilizes NAT64 this issue might be due to UDP not working and STUN not being able to punch a hole.
From our understanding we need to utilize TURN to get this working as these in theory could be seen as "External" Clients (No UDP, NAT without STUN) but are a bit puzzled on which TURN Deployment to use.
1) Can this be done without using a Dedicated Expressway-C for Microsoft Interop. and using Expressway-E as TURN?
2) Would a CMS Integrated Setup with Skype Edge as TURN Server be needed for this?
We are using one SIP Domain with Subdomain for everything on the Cisco side (I.e Spaces, UCMC Devices)
Any help or tips are much appreciated.
