OCS VOIP call gets dropped when caller ID is blocked


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 – (From Local Address: 1271 bytes:

05/01/2009|15:42:42.693 19C:958 INFO  :: SIP/2.0 488 Not Acceptable Here

Via: SIP/2.0/TLS;branch=z9hG4bK348BF8E1.9C327907F0A24A00;branched=TRUE;ms-internal-info=”cvrvQTOYB3PPrJyrA8PyG00ZaDTm0HeTKck0nEAgAA”

Via: SIP/2.0/TLS;branch=z9hG4bKb35a8c7f;received=;ms-received-port=52753;ms-received-cid=7E55B00

From: <sip:+1anonymous@contoso.com;user=phone>;epid=D879D48995;tag=c7e98f73c2

To: <sip:14083250000;phone-context=LocProf.contoso.com@contoso.com;user=phone>;epid=d3b7ada48f;tag=b26f9e40aa

Call-ID: 0546352d-011d-410b-9f80-ea5af6594146

CSeq: 37918 INVITE

Record-Route: <sip:Pool1.contoso.com:5061;transport=tls;ms-fe=BOS1FE02.contoso.com;opaque=state:F:Ci.R7e55800:Ieh.DOx_ldQyXFPaMlxTby7XcZtPI4-TcXqAeNynRKY7-a2rsHeTKcCGjeHwAA;lr;ms-route-sig=byiG0-l6h58Elb5oFW_pmBGtmCE_sHeTKcCGjeHwAA>;tag=35891F36E65216F9F7278C395DE32773

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″

Content-Length: 0



05/01/2009|15:42:42.693 19C:958 INFO  :: End of Sending Packet – (From Local Address: 1271 bytes


Everything in the above log was just fine except following line…

From: <sip:+1anonymous@contoso.com;user=phone>;epid=D879D48995;tag=c7e98f73c2

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.



Comments (7)

  1. Chicago medical billing says:

    wonderful key words thanks for sharing such nice blog.

  2. Send gift to Paksitan says:

    Thanks for sharing this information


  3. Great work done. says:

    I think this can go up http://www.bazee.pk

  4. rees says:

    Accessing your Gmail is easy and secure as Google only asks for your Gmail username & password
    http://stattutorials.com/www-gmail-com-postmaster-tools.html but will automatically detect if you are trying to login from an unknown location