locked
Problem in ACK via header RRS feed

  • General discussion

  • Hey All,

    I saw another problem today with the ACK sent from Mobicents Servlet application. I created an INVITE to the
    OCS and it responded with a 200 OK. Then I used  response.createAck
    ().send() and when it is received on the OCS side, ACK has been
    rejected saying the log pasted below. Is there a buffer of =150 symbols being parsed on the Via header ..

    Because the problem could be as OCS adds ms-received-cid and it says 'unexpected attribute  received-cid' ...

    Might be a parsing problem ???? Answers pls ..

    OCS log:
    +++++++
    Direction: incoming
    Peer: 199.30.18.97:2424
    Message-Type: request
    Start-Line: ACK sip:r... @ocsinterop.com;opaque=user:epid:olOhb_1rBF-
    aRLnsBJFpbwAA;gruu SIP/2.0
    From: "user 1"
    <sip:user1@server>;tag=67964634_512e1bef_189364280949115
    To: <sip:r... @ocsinterop.com>;tag=92dccb5d7e
    CSeq: 1 ACK
    Call-ID: 0a75603666cb8e02565816b06a9c2... @199.30.18.97
    Via: SIP/2.0/TCP
    199.30.18.97:5080;branch=z9hG4bKc93d78e75ad31474869b460fbc6c5b77;appname=512e1bef;app_id=189364280949115;ms-
    received-port=2424;ms-received-cid=1EC00
    Max-Forwards: 70
    Route: <sip:zngdy2ys.ocsinterop.com;transport=tcp;opaque=state:T;lr>
    Content-Length: 0
    Message-Body: –
    $$end_record

    TL_INFO(TF_COMPONENT) [0]0FB4.1628::07/22/2009-11:51:56.956.0000044a
    (SIPStack,CSIPRequest::ExtractIncomingRouteUri:SIPRequest.cpp(6281))
    ( 0000000006485D00 ) Matched route header with received address
    TL_INFO(TF_COMPONENT) [0]0FB4.1628::07/22/2009-11:51:56.956.0000044b
    (SIPStack,CSIPRequest::ExtractIncomingRouteUri:SIPRequest.cpp(6356))
    ( 0000000006485D00 ) Exit - extracted this proxy as first route entry
    TL_ERROR(TF_COMPONENT) [0]0FB4.1628::07/22/2009-11:51:56.956.0000044c
    (SIPStack,CSIPRequest::ProcessVia:SIPRequest.cpp(652))
    ( 0000000006485D00 ) Exit - the via header contains unexpected
    received-cid attribute. Returned 0xC3E93F04
    (SIPPROXY_E_REQUEST_NO_CORRECT_VIA)
    TL_ERROR(TF_COMPONENT) [0]0FB4.1628::07/22/2009-11:51:56.956.0000044d
    (SIPStack,CSIPRequest::ValidateInboundHeaders:SIPRequest.cpp(1448))
    ( 0000000006485D00 ) Exit - failed to ProcessVia(). Returned 0xC3E93F04
    (SIPPROXY_E_REQUEST_NO_CORRECT_VIA)
    TL_WARN(TF_DIAG) [0]0FB4.1628::07/22/2009-11:51:56.956.0000044e
    (SIPStack,SIPAdminLog::TraceDiagRecord:SIPAdminLog.cpp(142))$
    $begin_record
    LogType: diagnostic
    Severity: warning
    Text: Routing error occurred; check Result-Code field for more
    information
    Result-Code: 0xc3e93f04 SIPPROXY_E_REQUEST_NO_CORRECT_VIA
    SIP-Start-Line: ACK
    sip:r... @ocsinterop.com;opaque=user:epid:olOhb_1rBF-aRLnsBJFpbwAA;gruu
    SIP/2.0
    SIP-Call-ID: 0a75603666cb8e02565816b06a9c2... @199.30.18.97
    SIP-CSeq: 1 ACK
    Peer: 199.30.18.97:2424
    $$end_record
    Wednesday, July 22, 2009 3:17 PM