locked
OCS Voice - calls failing from Cisco UCM to remote OC client RRS feed

  • Question

  •  

    MOC Client:  2.0.6362.76
    OCS Server:  KB952780 applied

    Overview:
    Cisco UCM 5.1.3 <--> Direct SIP Trunk <--> OCS Mediation Server

    All OC to OC calls work fine
    Calls from Cisco to internal OC user works
    Calls from internal OC user to Cisco works
    Calls from external OC user to Cisco works
    Calls from Cisco to external OC user fails

    Performed tracing on:

    Office Communicator -


    09/19/2008|08:46:17.824 E38:E3C INFO  :: Data Received - x.y.z.z:5061 (To Local Address: 192.168.101.100:49258) 602 bytes:



    09/19/2008|08:46:17.824 E38:E3C INFO  :: SIP/2.0 504 Server time-out



    ms-user-logon-data: RemoteUser



    From: "" <sip:15300;phone-context=DDAM@xyz.com;user=phone>;epid=1f5dac3e69;tag=4f3af1730e



    To: <sip:571203xxxx;phone-context=DDAM@xyz.com;user=phone>;epid=EE2AC5406B;tag=61a1b5e261



    Call-ID: 10e71410-ae30-4259-883b-9b8ee2d30356



    CSeq: 1 BYE



    Via: SIP/2.0/TLS 192.168.101.100:49258;received=x.y.z.z;ms-received-port=49258;ms-received-cid=5F7B00



    ms-diagnostics: 1015;reason="Cannot route from message source domain";source="lcs.us.didata.com";ErrorType="Error occured while processing Identity Header"



    Content-Length: 0



     



     



    09/19/2008|08:46:17.824 E38:E3C INFO  :: End of Data Received - 204.56.87.164:5061 (To Local Address: 192.168.101.100:49258) 602 bytes



    Mediation Server (no errors reported)
    AV Edge Server (no errors reported)
    Access Edge Server:


    TL_INFO(TF_PROTOCOL) [3]0784.027C::09/18/2008-21:34:56.140.0004d129 (SIPStack,SIPAdminLog::TraceProtocolRecord:1224.idx(122))$$begin_record



    Instance-Id: 003F1655



    Direction: outgoing;source="local";destination="external edge"



    Peer: x.y.z.z:49258



    Message-Type: response



    Start-Line: SIP/2.0 504 Server time-out



    From: "" <sip:15300;phone-context=DDAM@xyz.com;user=phone>;epid=1f5dac3e69;tag=8d50d4b917



    To: <sip:571203zzzz;phone-context=DDAM@xyz.com;user=phone>;epid=EE2AC5406B;tag=cdc02b86cf



    CSeq: 1 BYE



    Call-ID: fbd0a581-591b-4ae5-bfef-138cb0d437ed



    ms-user-logon-data: RemoteUser



    Via: SIP/2.0/TLS 192.168.101.100:49258;received=x.y.z.z;ms-received-port=49258;ms-received-cid=5F7B00



    ms-diagnostics: 1015;reason="Cannot route from message source domain";source="lcs.us.didata.com";ErrorType="Error occured while processing Identity Header"



    Content-Length: 0



    Message-Body:



    $$end_record

    So the only commonality here is this identity header error.  Has anyone seen this before?

    Monday, September 22, 2008 6:21 PM

All replies

  • In your mediation server properties, have you set the "a/v edge server" correctly / does it reflect the right servername and port of the A/V edge server that should be handling outbound calls?

     

    Regards,

    Matt

     

     

    Wednesday, September 24, 2008 3:31 AM
  • This is set to the A/V edge server internal name (internal interface ip dns name) and 5062.  The A/V edge server uses three ports internally, 443, 5062 and 3478 but I am assuming 5062 as it was the default entry when adding the server.

    Wednesday, September 24, 2008 12:00 PM