Cisco CUBE cannot sent SIP message on the B-Leg. Error on SIPTransport

[Alexey Y]

Hello Dear Community,

I'm currently debugging an issue on a Cisco CUBE on which I see that the SIP request that is being constructed (after SIP manipulations) cannot be sent from the B-LEG.

Viewing the flow of the operations and comparing it to a different SBC I spot only one difference that has to do with the "local_addr" value which is not present. Here's the lines from the SIP Transport service:

*Jan 13 14:49:15.051: //94443171/605EABBB9AAB/SIP/Transport/sipSPITransportSendMessage: msg=0x7FD04CCD8968, addr=10.0.0.11, port=5060, sentBy_port=0, local_addr=, is_req=1, transport=2, switch=0, callBack=0x55B6CF4FEF60
*Jan 13 14:49:15.052: //94443171/605EABBB9AAB/SIP/Transport/sipSPITransportSendMessage: Cannot proceed to send msg-0x7FD04CCD8968 immediately. Msg in send context-0x7FD04B6DD048
*Jan 13 14:49:15.052: //94443171/605EABBB9AAB/SIP/Transport/sipSPITransportSendMessage: Enqueued msg-0x7FD04CCD8968 into transport pending Q tcb:0x0

On a different SBC the same call flow works flawlessly, and the "local_addr=" IS being populated with the correct address of the SBC. then the SIP Transport sends the message out of B-Leg.

Does any one happen to know what might cause this param not being populated?

P.S - all configurations related to dial-peers, sip-profiles, pattern matching are the same.

[Vaijanath Sonvane]

Hi @Alexey Y,

• Are both SBC running same software version?
• Is the binding interface configured correctly on the non working SBC?
• Is the SIP profile configured correctly on non working SBC?

Please post the configuration and working and non working logs. 

[Alexey Y]

Hi @Vaijanath Sonvane ,
Sorry for the delayed reply but I was able to resolve this issue.

[Roger Kallberg]

For the benefit of the community it would be nice if you could share what you did to solve your issue so that others can learn from it.