Hello,
On 6/6/13 2:57 PM, Victor V. Kustov wrote:
Hello!
Updated:
Cisco drop OK message:
*Jun 6 04:53:54.686: //-1/xxxxxxxxxxxx/SIP/Info/sipSPILocateInviteDialogCCB: Could not find matching transaction for this response, Dropping it *Jun 6 04:53:55.206: //-1/xxxxxxxxxxxx/SIP/Info/HandleUdpSocketReads: Msg enqueued for SPI with IP addr: 172.16.17.8:5060 *Jun 6 04:53:55.206: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_process_sipspi_queue_event: ccsip_spi_get_msg_type returned: 2 for event 1 *Jun 6 04:53:55.206: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportProcessNWNewConnMsg: context=0x00000000 *Jun 6 04:53:55.206: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_new_msg_preprocessor: Checking Invite Dialog *Jun 6 04:53:55.206: //-1/xxxxxxxxxxxx/SIP/Error/sipSPIMatchRespToReqTran: Failed Response check insippmh_get_resp_code *Jun 6 04:53:55.206: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg: Received: SIP/2.0 200 OK Via: SIP/2.0/UDP 172.16.16.3:5060;branch=z9hG4bK2E17EF Record-Route: sip:172.16.17.8;lr=on;did=1f9.8fb1
The 200ok from the sip trace you sent in the first email looks ok. To match the transaction, call-id, from-tag, cseq and branch parameter in via should be the same -- and I couldn't spot a difference, but you can check yourself. Maybe you can get somewhoe more debug from cisco about why is not matching...
Cheers, Daniel