Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 830541 - Last Review: October 17, 2003 - Revision: 1.1
Live Communications Server Returns a "504 - Server Timeout" Result When You Send a Request by Using the OPTIONS Method
When you programmatically send a request to a Microsoft Office Live Communications Server 2003 server by using the Session Initiation Protocol (SIP)
OPTIONS method, and you direct that request to a registered endpoint, the server returns a "504 - Server Timeout" result.
This problem occurs because Live Communications Server 2003 does not correctly forward the SIP
OPTIONS method to the destination endpoint.
To resolve this problem, add the
OPTIONS method to the Routing.am request filter file. The request is then proxied correctly.
To do this, follow these steps:
- Open the Routing.am file by using a text editor such as Notepad. By default, this file is located in the following folder:
C:\Program Files\Microsoft LC\Server
- Type OPTIONS in the following portion of XML code that appears in this file; make sure that you separate it from the other method names by using a comma:
<r:requestFilter methodNames="INVITE,MESSAGE,NOTIFY,INFO,REFER,ACK,BYE,OTHER"
strictRoute="false"
registrarGenerated="false"
domainSupported="true"/> - Save the changes to the file, and then quit the text editor.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
For additional information about SIP methods and options, visit the following IANA Web site:
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.
APPLIES TO
- Microsoft Office Live Communications Server 2003
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate