In an OCS VOIP deployment, call routing works fine. But it breaks down when the caller ID is blocked in certain circumstances.
I was working with one of the customers, everything was working just fine when caller ID was not blocked at the gateway end. When caller ID was blocked at the gateway end, the call routing was failing for the caller, whose ID was blocked.
Took mediation server log and could see following SIP log...
05/01/2009|15:42:42.693 19C:958 INFO :: Sending Packet - 10.129.3.43:5061 (From Local Address: 10.128.99.40:1165) 1271 bytes:
05/01/2009|15:42:42.693 19C:958 INFO :: SIP/2.0 488 Not Acceptable Here
Via: SIP/2.0/TLS 10.129.3.34:5061;branch=z9hG4bK348BF8E1.9C327907F0A24A00;branched=TRUE;ms-internal-info="cvrvQTOYB3PPrJyrA8PyG00ZaDTm0HeTKck0nEAgAA"
Via: SIP/2.0/TLS 10.129.2.57:52753;branch=z9hG4bKb35a8c7f;received=10.129.3.4;ms-received-port=52753;ms-received-cid=7E55B00
CSeq: 37918 INVITE
User-Agent: UCCAPI/3.5.6907.9 OC/3.5.6907.9 (Microsoft Office Communicator 2007 R2)
Ms-client-diagnostics: 52001; reason="General processing error"
Proxy-Authorization: Kerberos qop="auth", realm="SIP Communications Service", opaque="A2019AEB", targetname="sip/BOS1FE02.contoso.com", crand="89df02b3", cnum="19", response="602306092a864886f71201020201011100ffffffff46902b6f0190b95825dfcf471ad19783"
05/01/2009|15:42:42.693 19C:958 INFO :: End of Sending Packet - 10.129.3.43:5061 (From Local Address: 10.128.99.40:1165) 1271 bytes
Everything in the above log was just fine except following line...
Actually when the Gateway was blocking the caller ID, it was adding "+1" to the From field. "+1anonymous" is not acceptable for MOC. And thats why OCS was dropping this call, saying that the SIP Method is not acceptable here.
When we got rid of +1 from from field, problem got resolved.