Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

SIP connection problem Call Manager - CME

We have a SIP connection between Cisco Call Manager v6 and CME through VPN

Everything was working fine until we had to restart our Netgear ProSafe VPN (it has a VPN connection to ASA)

Now I get these errors in SIP debug:

 

Jun 11 11:53:09.379: //-1/xxxxxxxxxxxx/SIP/Error/sip_tcp_sockerror_to_spi: Send
TCP Socket Error Msg to SPI , connid: 2, sock_fd: 1, errno = 260, reason_code: 0
Jun 11 11:53:09.379: //-1/xxxxxxxxxxxx/SIP/Error/ccsip_spi_process_event: No GCB
. Dropping SEND FAILURE event.
Jun 11 11:53:09.379: //-1/xxxxxxxxxxxx/SIP/Error/ccsip_spi_process_event: No GCB
. Dropping SEND FAILURE event.
Jun 11 11:53:09.379: //-1/xxxxxxxxxxxx/SIP/Error/ccsip_spi_process_event: No GCB
. Dropping SEND FAILURE event.
Jun 11 11:53:09.379: //-1/xxxxxxxxxxxx/SIP/Error/ccsip_spi_process_event: No GCB
. Dropping SEND FAILURE event.
Jun 11 11:53:09.379: //-1/xxxxxxxxxxxx/SIP/Error/ccsip_spi_process_event: No GCB
. Dropping SEND FAILURE event.
Jun 11 11:53:09.379: //-1/xxxxxxxxxxxx/SIP/Error/ccsip_spi_process_event: No GCB
. Dropping SEND FAILURE event.
Jun 11 11:53:09.379: //-1/xxxxxxxxxxxx/SIP/Error/ccsip_spi_process_event: No GCB
. Dropping SEND FAILURE event.
Jun 11 11:53:29.767: //-1/xxxxxxxxxxxx/SIP/Error/sip_tcp_sockerror_to_spi: Send
TCP Socket Error Msg to SPI , connid: 3, sock_fd: 2, errno = 260, reason_code: 0
Jun 11 11:53:29.767: //-1/xxxxxxxxxxxx/SIP/Error/ccsip_spi_process_event: No GCB
. Dropping SEND FAILURE event.
Jun 11 11:53:29.767: //-1/xxxxxxxxxxxx/SIP/Error/ccsip_spi_process_event: No GCB
. Dropping SEND FAILURE event.
Jun 11 11:53:29.767: //-1/xxxxxxxxxxxx/SIP/Error/ccsip_spi_process_event: No GCB

-----------------------

Jun 11 11:57:12.571: //-1/xxxxxxxxxxxx/SIP/Event/ccsip_call_subscribe_response:
Queued event from SIP SPI : SIPSPI_EV_CC_SUBSCRIBE_RESP
Jun 11 11:57:12.571: //-1/xxxxxxxxxxxx/SIP/Event/ccsip_api_initiate_subscription
_termination: Queued event from SIP SPI : SIPSPI_EV_SUBSCRIPTION_TERMINATED
Jun 11 11:57:12.571: //-1/xxxxxxxxxxxx/SIP/Event/ccsip_call_subscribe_response:
Queued event from SIP SPI : SIPSPI_EV_CC_SUBSCRIBE_RESP
Jun 11 11:57:12.571: //-1/xxxxxxxxxxxx/SIP/Event/ccsip_api_initiate_subscription
_termination: Queued event from SIP SPI : SIPSPI_EV_SUBSCRIPTION_TERMINATED
Jun 11 11:57:13.503: //28975/5C445E57A2BC/SIP/Event/Session-Timer/sipSTSLMain: E
vent: E_STSL_SESSION_REFRESH_REQ
Jun 11 11:57:13.503: //28975/5C445E57A2BC/SIP/Event/Session-Timer/sipSTSLMain: d
ir:2, method:102, resp_code:0, container:3366A070
Jun 11 11:57:13.503: //28975/5C445E57A2BC/SIP/Event/Session-Timer/sipSTSLPrintTD
Container: Peer-Event: E_STSL_PASS_ST_PARAMS, SE Value:1800, SE Refresher:none,
Min-SE Value:1800, flags:2001
Jun 11 11:57:13.503: //28975/5C445E57A2BC/SIP/Event/Session-Timer/sipSTSLMain: E
vent: E_STSL_SESSION_REFRESH_RESP
Jun 11 11:57:13.503: //28975/5C445E57A2BC/SIP/Event/Session-Timer/sipSTSLMain: d
ir:1, method:102, resp_code:100, container:33667260
Jun 11 11:57:13.503: //-1/xxxxxxxxxxxx/SIP/Event/sipSPIEventInfo: Queued event f
rom SIP SPI : SIPSPI_EV_CC_CALL_PROCEEDING
Jun 11 11:57:13.507: //-1/xxxxxxxxxxxx/SIP/Event/sipSPIEventInfo: Queued event f
rom SIP SPI : SIPSPI_EV_CC_CALL_ALERTING
Jun 11 11:57:13.511: //-1/xxxxxxxxxxxx/SIP/Error/ccsip_call_service_msg: ccb NUL
L, unable to update the callinfo ui parameters
Jun 11 11:57:13.511: //-1/xxxxxxxxxxxx/SIP/Event/sipSPIEventInfo: Queued event f
rom SIP SPI : SIPSPI_EV_CC_MEDIA_EVENT
Jun 11 11:57:13.511: //28975/5C445E57A2BC/SIP/Error/sipSPI_ipip_set_history_info
_header: Not SIP2SIP mode
Jun 11 11:57:13.511: //28975/5C445E57A2BC/SIP/Event/Session-Timer/sipSTSLMain: E
vent: E_STSL_SESSION_REFRESH_RESP
Jun 11 11:57:13.511: //28975/5C445E57A2BC/SIP/Event/Session-Timer/sipSTSLMain: d
ir:1, method:102, resp_code:180, container:336676D8
Jun 11 11:57:13.511: //28975/5C445E57A2BC/SIP/Event/sipSPICreateRpid: Received O
ctet3A=0x00 -> Setting ;screen=no ;privacy=off

 

----------------

 

Jun 11 11:57:51.451: //-1/xxxxxxxxxxxx/SIP/Info/sip_tcp_resend: Socket blocked r
equeue data
Jun 11 11:57:51.459: //-1/xxxxxxxxxxxx/SIP/Info/sip_tcp_resend: Socket blocked r
equeue data
Jun 11 11:57:51.467: //-1/xxxxxxxxxxxx/SIP/Info/sip_tcp_resend: Socket blocked r
equeue data
Jun 11 11:57:51.475: //-1/xxxxxxxxxxxx/SIP/Info/sip_tcp_resend: Socket blocked r
equeue data
Jun 11 11:57:51.483: //-1/xxxxxxxxxxxx/SIP/Info/sip_tcp_resend: Socket blocked r
equeue data
Jun 11 11:57:51.491: //-1/xxxxxxxxxxxx/SIP/Info/sip_tcp_resend: Socket blocked r
equeue data
Jun 11 11:57:51.499: //-1/xxxxxxxxxxxx/SIP/Info/sip_tcp_resend: Socket blocked r
equeue data

 

Can not find any possible solution, every suggestion would be appreciated

 

Thank you!

 

2 REPLIES
New Member

Just to add: I can telnet to

Just to add:

 

I can telnet to 5060 to both ends of the SIP trunk, to Call Manager and to the CME

Can you try disabling SIP

Can you try disabling SIP Inspection/SIP ALG on the Netgear side?  Can you try getting packet captures as well?

238
Views
0
Helpful
2
Replies
CreatePlease to create content