Cisco Cisco Expressway
Microsoft Rejects Expressway Zone OPTIONS Checks with ‘401 Unauthorized’ and
INFO Messages with ‘400 Missing Correct Via Header'
INFO Messages with ‘400 Missing Correct Via Header'
■
A response "400 Missing Correct Via Header" is an indication that Lync does not trust the sender of the
message.
message.
■
A response "401 Unauthorized" response to OPTIONS is another indication that Lync does not trust the
sender of the OPTIONS message.
sender of the OPTIONS message.
Ensure that Lync environment has been configured to trust the Expressway which is sending these messages, as
described previously in this document.
described previously in this document.
Note, this can also be seen if a load balancer is used in front of the Lync, and Lync is configured to authorize the
Expressway (Lync sees calls coming from the hardware load balancer rather than from the Expressway).
Expressway (Lync sees calls coming from the hardware load balancer rather than from the Expressway).
B2BUA Problems
Microsoft Interoperability Service Status Reports Microsoft Server "Unknown" or "Unknown
failure"
failure"
Check that the Expressway application has been added to the Microsoft trusted application pool and is configured to
contact the Expressway B2BUA via port 65072 . See
contact the Expressway B2BUA via port 65072 . See
information.
Microsoft Client
Client Stuck in "Connecting..." State
This could be because the client is not receiving media. The client cannot change into the "Connected" state until it
receives RTP (media) from the other party.
receives RTP (media) from the other party.
Presentation Handover Fails in TelePresence Server Conference
Symptom: A participant cannot share their screen when another participant has been sharing.
Note:
This issue was seen in a test of an unsupported Expressway and Microsoft scenario, but the solution applies
more generally. You could see this symptom whenever endpoints are sharing in a TelePresence Server conference,
or if endpoints that are sharing are registered to Cisco Unified Communications Manager. If you are seeing
presentation issues, check the solution shown here (even if your conditions are different).
or if endpoints that are sharing are registered to Cisco Unified Communications Manager. If you are seeing
presentation issues, check the solution shown here (even if your conditions are different).
Conditions:
■
Gateway Expressway deployed with Lync 2013 Front End Server and Lync 2013 for Windows clients.
■
Gateway Expressway configured for screen sharing.
■
The Gateway Expressway is trunked to Cisco Unified Communications Manager.
■
TC endpoints are registered to Unified CM.
■
TC endpoints and Microsoft clients are in a conference on TelePresence Server.
■
The conference is registered to the Gateway Expressway (The TelePresence Server is in locally managed
mode - no TelePresence Conductor in this scenario).
mode - no TelePresence Conductor in this scenario).
Possible Root Causes:
■
The TelePresence Server is not configured to allow participants to steal the floor.
■
The neighbor zone from Expressway to Unified CM does not support BFCP.
57
Cisco Expressway with Microsoft Infrastructure Deployment Guide
Appendix 1: Troubleshooting