Hi , 

Any idea if internal different subnet network is block and only server subnet is allow.

Can we put internal call traffic to front end server bypass internal P2P call?

Thanks

No, audio call can not be routed by FE server.

If P2P is blocked, you need to deployed edge server. Internal audio call can be routed by the edge server via the internal interface.

• Proposed as answer by Li Zhen Wednesday, August 19, 2015 11:06 AM
• Marked as answer by Jo Tse Wednesday, August 19, 2015 11:08 AM
• Unmarked as answer by Jo Tse 22 hours 27 minutes ago

Yes , we will deploy edge server for external access. Any setting can route internal P2P call traffic to edge server?

Thanks.

• Edited by Jo Tse Tuesday, August 18, 2015 2:54 PM change

Hi Jo Tse,

 

If P2P is blocked, the clients will connect to the internal Edge NIC over either UDP 3478 or TCP 443. 

The Interactive Connectivity Establishment (ICE) Extensions protocol is used to establish media flow between two endpoints.  ICE has a mechanism where it will test a lot of candidates to see where connections should be made. Candidates list is simply a list of IP-addresse(S), Ports and Protocols (wither UDP or TCP) that is shared between the call endpoints to tell each other what is the possible media path can be used in this call, and is sent in the INVITE request.

 

You only need to deploy an Edge Server and make sure all the internal subnets where a Lync client resides will need to be able to communicate with the Edge Servers internal NIC.

 

Best regards,

Eric

It works by default. If the 2 PCs fail to communicate with each other. They will automatically connect to internal interface of the edge server.

• Proposed as answer by Li Zhen Wednesday, August 19, 2015 11:06 AM
• Marked as answer by Jo Tse Wednesday, August 19, 2015 11:08 AM
• Unmarked as answer by Jo Tse 22 hours 27 minutes ago

Hi , I just deploy edge server

does it need DMZ network ready for connect?

I have same network issue after deploy edge server internal network face.

22;  reason="Call failed to establish due to a media connectivity failure when both endpoints are internal"; CalleeMediaDebug="audio:ICEWarn=0x40003a0

• Edited by Jo Tse 20 hours 55 minutes ago update

all client can access to edge internal face and edge service is up.

the connection still have network error.

22;  reason="Call failed to establish due to a media connectivity failure when both endpoints are internal"; CalleeMediaDebug="audio:ICEWarn=0x40003a0,LocalSite=192.20.0.0(internal):19662,LocalMR=202.0.0.0(external):57752,RemoteSite=192.10.100.55(internal):30553,RemoteMR=202.0.0.0(External):54909,PortRange=1025:65000,LocalMRTCPPort=56660,RemoteMRTCPPort=54909,LocalLocation=2,RemoteLocation=2,FederationType=0,NetworkName=domain.local,Interfaces=0x4,BaseInterface=0x4,BaseAddress=192.20.0.0(Internal):33386"

• Edited by Jo Tse 20 hours 52 minutes ago update

Edge server must have 2 NICs in 2 different subnets. Since you don't need external access or federation, the external NIC can be connected to internal network but it has to be in a different subnet of the internal NIC.

• Proposed as answer by Li Zhen 2 hours 37 minutes ago

Yes, there have two NIC card, one is on internal another is on DMZ. but DMZ network is not ready.

Internal NIC is ready and add static route to internal Network.