018727: Dec 10 17:49:39.692 CDT: //58462/90B32AF39953/SIP/Info/sipSPICheckResponseExt: INVITE response with no RSEQ - disable IS_REL1XX
018728: Dec 10 17:49:39.696 CDT: //58462/90B32AF39953/SIP/State/sipSPIChangeState: 0x4ACEAEF0 : State change from (STA TE_SENT_INVITE, SUBSTATE_NONE) to (STATE_RECD_PROCEEDING, SUBSTATE_PROCEEDING_PROCEEDING)
018729: Dec 10 17:49:39.884 CDT: //-1/xxxxxxxxxxxx/SIP/Info/ccsip_process_sipspi_queue_event: ccsip_spi_get_msg_type r eturned: 2 for event 1
018730: Dec 10 17:49:39.884 CDT: //-1/xxxxxxxxxxxx/SIP/Transport/sipTransportProcessNWNewConnMsg: context=0x4A00D318
400 Bad Request indicates that the initial invite sent from Cisco to Lync is not supported by Lync. We need to check the complete sip logs to know which field(header/sdp) in the Invite is not supported.
Also it seems Lync doesn't support Rel1xx response. You may try disabling it under SIP config n check the behavior.
If not working after disabling the rel1xx, please collect debug ccsip message n debug voice ccapi inout for a test call along with the running config.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...