---
Updated 23 June 2009
Verified this issue with another client. Same symptoms, same fix. This time there was a valid VOIP extension in the “OtherIPPHone” list.
---
Just ran across a strange problem.
One user could not be contacted by other users even though their presence was good.
This user could initiate conversations, and then things worked normally.
logging revealed the following:
TL_INFO(TF_PROTOCOL) [2]0AAC.0F60::02/10/2009-00:06:40.517.0000cb04 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(122))$$begin_record
Instance-Id: 00013F2B
Direction: outgoing;source="local"
Peer: 1.2.3.4:56634
Message-Type: response
Start-Line: SIP/2.0 500 The server encountered an unexpected internal error
From: "user"<sip:user@domain.org>;tag=3703bcb871;epid=de577344ca
To: <sip:user2@domain.org>;tag=A1D2F034A80C8DC2C22BC2B0BB538B47
CSeq: 1 INVITE
Call-ID: 4f0e2c32a0ac42b8a3ebfa96c1704671
Proxy-Authentication-Info: Kerberos rspauth="602306092A864886F71201020201011100FFFFFFFF5A639D1C74445CDE716249160B5E67D5", srand="99E853C4", snum="27", opaque="753DF002", qop="auth", targetname="sip/OCS1.domain.org", realm="SIP Communications Service"
Via: SIP/2.0/TLS 1.2.3.4:56634;ms-received-port=56634;ms-received-cid=1F9900
ms-diagnostics: 1;reason="Service Unavailable";source="OCS1.domain.org";AppUri="http://www.microsoft.com/LCS/ApiModule";reason="The application specified an invalid static forwarding url"
Content-Length: 0
Message-Body: –
$$end_record
Resolution: removed a bogus entry in AD user object.
Telephones| IP Phones | Other
There was a text entry there rather than numeric. This is not to say that a numeric entry would have resulted in the same behavior, just that in this case there was a text entry and we had the problem and that removing the entry solved the problem.
Question: What is the mechanics of the UR stuffing this bogus value into somewhere that caused this failure? I doubt I will ever know. One of these days I will find the time to lab this out and find out what is happening under the covers.