locked
OCS 2007 R2 RCC call established, but "parsing failure" RRS feed

  • Question

  • Hi,

    We have an issue with OCS R2 Enterprise (with latest updates) failing to recognise call establishment in a Remote Call Control setup.

    OCS front end server is connected to Broadworks UC-Connect and call origination from Communicator works, calling parties are connected fine, but the message about the successful call establishment is rejected and therefore Communicator never shows the correct call status.

     

    Here are the relevant log details:

     

    Incoming SIP message:

    TL_INFO(TF_PROTOCOL) [2]0E24.25D4::09/08/2011-16:03:00.210.025e783e (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(122))$$begin_record
    Instance-Id: 0016F255
    Direction: incoming
    Peer: yy.yy.yy.yy:59666
    Message-Type: request
    Start-Line: INFO sip:test1@ceondemand.com;opaque=user:epid:yPLeSVCLolCN6APLTdTq1QAA;gruu SIP/2.0
    From: <sip:csta@gateway.com>;tag=954797761-1315501500889
    To: "test1" <sip:test1@ceondemand.com>;tag=f15f02fa16;epid=2bcb25c6de
    CSeq: 620754143 INFO
    Call-ID: eb489bbeef0e49999b3e9bf4c79ece54
    Via: SIP/2.0/TLS yy.yy.yy.yy:5061;branch=z9hG4bKa8a9.46b0d801.0;i=3151
    Via: SIP/2.0/TCP xx.xx.xx.xx:5060;branch=z9hG4bKBroadWorks.8dag08-zz.zz.zz.zzV5060-0-620754143-954797761-1315501500889
    Route: <sip:pool.ourdomain.local:5061;ms-fe=poolserver1.ourdomain.local;opaque=state:T;lr;transport=tls>;tag=BE2789D931005B10BCBEFA6C2FBC46FD
    Contact: <sip:xx.xx.xx.xx:5060;transport=tcp>
    Max-Forwards: 9
    User-Agent: UC-Connect v. 2.0
    Content-Type: application/csta+xml
    Content-Length: 596
    Message-Body: <?xml version="1.0" encoding="UTF-8"?>
    < OriginatedEvent xmlns="http://www.ecma-international.org/standards/ecma-323/csta/ed3">
    < monitorCrossRefID>1006</monitorCrossRefID>
    < originatedConnection>
    <callID>localHost827393:1</callID>
    <deviceID>tel:+<THISISAPHONENUMBER></deviceID>
    < /originatedConnection>
    < callingDevice>
    <deviceIdentifier>tel:+<THISISAPHONENUMBER></deviceIdentifier>
    < /callingDevice>
    < calledDevice>
    <deviceIdentifier>tel:607937639;phone-context=dialstring</deviceIdentifier>
    < /calledDevice>
    < localConnectionInfo>connected</localConnectionInfo>
    < cause>normal</cause>
    < /OriginatedEvent>
    $$end_record

    Failure:

    TL_INFO(TF_PROTOCOL) [2]0E24.25D4::09/08/2011-16:03:00.210.025e7ad4 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(122))$$begin_record
    Instance-Id: 0016F256
    Direction: outgoing;source="local"
    Peer: yy.yy.yy.yy:59666
    Message-Type: response
    Start-Line: SIP/2.0 400 Missing correct Via header
    From: <sip:csta@gateway.com>;tag=954797761-1315501500889
    To: "test1" <sip:test1@ceondemand.com>;tag=f15f02fa16;epid=2bcb25c6de
    CSeq: 620754143 INFO
    Call-ID: eb489bbeef0e49999b3e9bf4c79ece54
    Via: SIP/2.0/TLS yy.yy.yy.yy:5061;branch=z9hG4bKa8a9.46b0d801.0;i=3151;received=yy.yy.yy.yy;ms-received-port=59666;ms-received-cid=4B200
    Via: SIP/2.0/TCP xx.xx.xx.xx:5060;branch=z9hG4bKBroadWorks.8dag08-zz.zz.zz.zzV5060-0-620754143-954797761-1315501500889
    ms-diagnostics: 1018;reason="Parsing failure";source="poolserver1.ourdomain.local"
    Content-Length: 0
    Message-Body: –
    $$end_record

    (real IPs have been masked)

     

    Do you have an idea what is wrong with the incoming message and why is OCS rejecting it? Or can you suggest any pointers for further debugging possibilties?

     

    BR,

    Andras

    Sunday, September 11, 2011 11:51 PM

Answers

  • TL_INFO(TF_PROTOCOL) [2]0E24.25D4::09/08/2011-16:03:00.210.025e7ad4 (SIPStack,SIPAdminLog::TraceProtocolRecord:SIPAdminLog.cpp(122))$$begin_record
    Instance-Id: 0016F256
    Direction: outgoing;source="local"
    Peer: yy.yy.yy.yy:59666
    Message-Type: response
    Start-Line: SIP/2.0 400 Missing correct Via header
    From: <sip:csta@gateway.com>;tag=954797761-1315501500889
    To: "test1" <sip:test1@ceondemand.com>;tag=f15f02fa16;epid=2bcb25c6de
    CSeq: 620754143 INFO
    Call-ID: eb489bbeef0e49999b3e9bf4c79ece54
    Via: SIP/2.0/TLS yy.yy.yy.yy:5061;branch=z9hG4bKa8a9.46b0d801.0;i=3151;received=yy.yy.yy.yy;ms-received-port=59666;ms-received-cid=4B200
    Via: SIP/2.0/TCP xx.xx.xx.xx:5060;branch=z9hG4bKBroadWorks.8dag08-zz.zz.zz.zzV5060-0-620754143-954797761-1315501500889
    ms-diagnostics: 1018;reason="Parsing failure";source="poolserver1.ourdomain.local"
    Content-Length: 0
    Message-Body: –

     

    In the logs we get  SIP/2.0 400 Missing correct Via header

    Make sure that the ip address which the RCC gateway is talking to the OCS servers is listed in the host authorization tab

    You will find host authorization tab when you right click on pool-->properties-->Front End server

    If you have a NAT device between the RCC gateway and Front End servers and the communication from the RCC gateway is hitting the FE servers with a NAT ip address, make sure you have that IP included in the host authorization tab and restart the FE services.

     

     

     

    • Proposed as answer by Sean_Xiao Monday, September 19, 2011 2:45 AM
    • Marked as answer by Sean_Xiao Tuesday, September 20, 2011 2:33 AM
    Thursday, September 15, 2011 4:59 AM