Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Call channel network and reply ports not updating after websocket reconnect #266

Open
MuneebAhmed568 opened this issue Aug 6, 2024 · 0 comments

Comments

@MuneebAhmed568
Copy link

MuneebAhmed568 commented Aug 6, 2024

Issue
I'm utilizing Sipjs for Webrtc Call with Freeswitch. Everything works well, but when there's a network issue, the user gets disconnected from the websocket. After reconnecting, the user re-registers to Freeswitch and re-establishes the call, which functions properly. However, I'm not receiving any events after that. Freeswitch continues to send events to the previous IP and port, rather than the new IP and port.
Sip_network_port & sip_reply_port remain same for the call channel and are not updated after reconnect

Before Network Error
3000,192.168.1.11,pi78clsipdicjhr950bt,sofia/internal/sip:[email protected];transport=wss;fs_nat=yes;fs_path=sip%3A3000%40192.168.50.29%3A58133%3Btransport%3Dwss,1722950851,192.168.50.29,58133,udp,debian,

After Reconnect and Register
3000,192.168.1.16,pi78clsipdicjhr950bt,sofia/internal/sip:[email protected];transport=wss;fs_nat=yes;fs_path=sip%3A3000%40192.168.50.47%3A58243%3Btransport%3Dwss,1722950963,192.168.50.47,58243,udp,debian,

BYE EVENT

tport.c:4621 tport_by_name() tport(0x7fe0e8054fd0): found 0x7fe0e808ce20 by name wss/192.168.50.29:58133
tport.c:3290 tport_tsend() tport_tsend(0x7fe0e808ce20) tpn = wss/192.168.50.29:58133
2024-08-06 18:19:04.255548 21.97% [DEBUG] switch_core_state_machine.c:932 (sofia/internal/[email protected]) State REPORTING
2024-08-06 18:19:04.255548 21.97% [DEBUG] switch_core_state_machine.c:168 sofia/internal/[email protected] Standard REPORTING, cause: NORMAL_CLEARING
tport_type_ws.c:310 tport_send_stream_ws() tport_ws_writevec: vec 0x7fe0e808d020 0x7fe0e80f8db0 547 (0)
tport.c:3625 tport_vsend() tport_vsend(0x7fe0e808ce20): 547 bytes of 547 to wss/192.168.50.29:58133
tport.c:3526 tport_send_msg() tport_vsend returned 547
send 547 bytes to wss/[192.168.50.29]:58133 at 18:19:04.272116:
------------------------------------------------------------------------
BYE sip:[email protected];transport=wss SIP/2.0
Via: SIP/2.0/WSS 192.168.1.16:7443;rport;branch=z9hG4bK924gHmgp1BKee
Max-Forwards: 70
From: "3007" <sip:[email protected]>;tag=m74tgKBr184Fp
To: <sip:[email protected];transport=wss>;tag=4tl1ip5qrk
Call-ID: 0b2117a9-ce99-123d-0e90-005056aed12b
CSeq: 86921327 BYE
User-Agent: FreeSWITCH
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY, PUBLISH, SUBSCRIBE
Supported: path, replaces
Reason: Q.850;cause=16;text="NORMAL_CLEARING"
Content-Length: 0

Expected Behaviour
I need to keep the ports the same before and after the reconnect and registration or update the ports within the FreeSWITCH channel. uuid_setvar doesn't work for the latter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant