Cisco Cisco Expressway
Call between endpoint and Microsoft client fails with reason 'ice processing failed'
If the search history on Expressway shows calls failing with 'ice processing failed', this means that all ICE connectivity
checks between the B2BUA and the remote Microsoft client have failed.
checks between the B2BUA and the remote Microsoft client have failed.
Verify that the TURN server on Expressway-E has been enabled and that the TURN user credentials on Expressway-E
and B2BUA configuration match properly. This failure could also indicate a network connectivity issue for
STUN/TURN packets between B2BUA, Expressway-E/TURN server and the far end TURN server/Microsoft Edge.
and B2BUA configuration match properly. This failure could also indicate a network connectivity issue for
STUN/TURN packets between B2BUA, Expressway-E/TURN server and the far end TURN server/Microsoft Edge.
One Way Media: Microsoft Client to Expressway-registered Endpoint
When using Microsoft Edge Server
When Microsoft clients register to Microsoft FE Server through a Microsoft Edge Server, the local IP address and port
that the Microsoft client declares is usually private and un-routable (assuming that the Microsoft client is behind a
firewall and not registered on a public IP address). To identify alternate addresses to route media to, the Microsoft
client uses SDP candidate lines.
that the Microsoft client declares is usually private and un-routable (assuming that the Microsoft client is behind a
firewall and not registered on a public IP address). To identify alternate addresses to route media to, the Microsoft
client uses SDP candidate lines.
Calls traveling through the Microsoft Edge server are supported when using the B2BUA with the Microsoft
Interoperability option key applied to the Gateway Expressway, and where the video architecture includes a
Expressway-E with TURN enabled and the B2BUA is configured to use that TURN server.
Interoperability option key applied to the Gateway Expressway, and where the video architecture includes a
Expressway-E with TURN enabled and the B2BUA is configured to use that TURN server.
When using a Hardware Load Balancer in front of FE Servers
Expressway modifies the application part of INVITEs / OKs received from Microsoft clients to make them compatible
with traditional SIP SDP messaging. Expressway only does this when it knows that the call is coming from Microsoft. If
there are problems with one-way media (media only going from Microsoft client to the Expressway registered
endpoint), check the search history and ensure that the call is seen coming from a Microsoft trusted host. Otherwise,
the call may be coming from a FE Server rather than the load balancer. See
with traditional SIP SDP messaging. Expressway only does this when it knows that the call is coming from Microsoft. If
there are problems with one-way media (media only going from Microsoft client to the Expressway registered
endpoint), check the search history and ensure that the call is seen coming from a Microsoft trusted host. Otherwise,
the call may be coming from a FE Server rather than the load balancer. See
Microsoft Clients Try to Register with Expressway-E
SIP video endpoints usually use DNS SRV records in the following order to route calls to Expressway:
1.
_sips._tcp.<domain>
2.
_sip._tcp.<domain>
3.
_sip._udp.<domain>
Microsoft clients use:
■
_sipinternaltls._tcp.<domain> - for internal TLS connections
■
_sipinternal._tcp. <domain> - for internal TCP connections (only if TCP is allowed)
■
_sip._tls. <domain> - for external TLS connections
If Microsoft clients are trying to register with Expressway-E, it could be because the wrong SRV record points to it.
You must make sure that the six DNS records above do not resolve to overlapping addresses.
Microsoft clients only support TLS connection to the Microsoft Edge Server, so use the _sip._tcp.<domain> DNS SRV
for the Expressway-E.
for the Expressway-E.
Call to PSTN (or Other Devices Requiring Caller to be Authorized) Fails With "404
not found"
not found"
In some Microsoft configurations, especially where Microsoft PSTN gateways are used, calls are only allowed if the
calling party is authorized. Thus, the calling party’s domain must be the Microsoft Server domain. This means that the
endpoints must register to the video network with a domain that is the same as the Microsoft domain.
calling party is authorized. Thus, the calling party’s domain must be the Microsoft Server domain. This means that the
endpoints must register to the video network with a domain that is the same as the Microsoft domain.
56
Cisco Expressway with Microsoft Infrastructure Deployment Guide
Appendix 1: Troubleshooting