Mino – The UC Guy

Microsoft Unified Communications Blog

Posts Tagged ‘Communicator ID 11’

A SIP request made by Communicator failed in an unexpected manner (status code 80ef01f4)

Posted by Mino on March 23, 2009

Rami Calache, One of my very good team members faced this problem and I thought to share it with you

After installing Office Communications Server 2007 R2, one user using Office Communicator R2 was unable to receive IM messages or communicator calls although he was logged in successfully,

However If he initiates an IM conversation then he can receive IM’s through the same session with no problem, he can also call anyone successfully in the list but no one can call him .

When turning on logging on any other client trying to call him the following warning is logged in the event viewer.


Communicator ID 11

A SIP request made by Communicator failed in an unexpected manner (status code 80ef01f4). More information is contained in the following technical data:

RequestUri: _sip:imohamed@mydomain.com

From: _sip:hamdim@mydomain.com;tag=4fec8f509b

To: _sip:imohamed@mydomain.com;tag=808EDC4E808A77850A6B03B82AC60800

Call-ID: 70a7871eed87478f8b2e3fbb770d3dc5

Content-type: application/sdp;call-type=im


o=- 0 0 IN IP4


c=IN IP4

t=0 0

m=message 5060 sip null

a=accept-types:text/plain multipart/alternative image/gif text/rtf text/html application/x-ms-ink application/ms-imdn+xml text/x-msmsgsinvite

Response Data:

500 The server encountered an unexpected internal error

ms-diagnostics: 1;reason=”Service Unavailable”;source=”HO-OCS-FE.mydomain.com”;AppUri=”_http://www.microsoft.com/LCS/ApiModule”;reason=”The application specified an invalid static forwarding url”


If this error continues to occur, please contact your network administrator. The network administrator can use a tool like winerror.exe from the Windows Resource Kit or lcserror.exe from the Office Communications Server Resource Kit in order to interpret any error codes listed above.


This is a strange error only with R2 communicator and the reason was because that this user had a record inside the active directory under the below:

 AD user……Telephones tab…….IP Phone……..Other—–> an additional entry was added.

Once this entry inside others was removed, the client worked fine.



Posted in communicator client, OCS 2007 R2 | Tagged: , , , , | 16 Comments »