Webrtc outbound call fail if inbound call receive on another sip sbc server

[nitinpo-Kore]

webrtc working and non working.zip
hi @davehorton ,

As we have checked webrtc on single sbc sip server it is working fine or call receive on same sbc server where webrtc agent is register then also it works fine , but if we have multiple sbc sip server for example: inbound call receive on sbc2 and user agent of webrtc is register on sbc1 then transferred webrtc call not get connected. i have attached the log for reference and shared the password in personal for these file.

[xquanluu]

Hi @davehorton could you please send me the zip credential?

[nitinpo-Kore]

@xquanluu shared with you in personal

[xquanluu]

Hi @nitinpo-Kore
https://github.com/jambonz/sbc-outbound/blob/main/lib/middleware.js#L223

From this line of code, sbc-outbound will forward the call to correct sbc outbound server IP address.

[xquanluu]

Hi @nitinpo-Kore
could you please help to run a testcase that cause the issue and collect pcap on feature server.
Log for feature server and sbc-outbound

[nitinpo-Kore]

shared access to you

[xquanluu]

Due to webrtc client is registered on different sbc 2, the sbc1 who received the inbound call will return 302 Moved Permanent response to feature server and the Contact header should contains the private IP address of the sbc 2.

However, wrong configuration on drachtio server that make tcp have public IP address for server.hostport.

xecStart=/usr/local/bin/drachtio --daemon
--contact sip:${LOCAL_IP}:5060;transport=udp --external-ip ${PUBLIC_IP}
--contact sips:${LOCAL_IP}:5061;transport=tls --external-ip ${PUBLIC_IP}
--contact sips:${LOCAL_IP}:8443;transport=wss --external-ip ${PUBLIC_IP}
--contact sip:${LOCAL_IP}:5060;transport=tcp \

For tcp protocol, we should use local IP only

[davehorton]

I would like to see the logs for the problem call. Are they in the above zip?

I'm not sure I agree with you @xquanluu . jambonz SBC should be able to listen for incoming sip over tcp from the internet, ideally