You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to get a web socket based client registered on sip server using Drachtio. My web socket client is based on latest SIP.js library.
While doing the registration, on node, I have observed that the registration call flow is correct (Register, 401 Unauthorized, Register and then 200 OK). I have also observed the same message sequence on client as well. However, despite that, the client is NOT changing the state to REGISTERED.
Based on the error logs of SIP.js, this is due to some issue in Contact Header received by SIP.js Client in 200 OK.
I then tried the same scenario with latest branch of FreeSWITCH server and this time the SIP.js client did successful registration (also changed the state to REGISTERED)
Here are the two contact headers:
Sent By Drachtio
Contact: sip:[email protected];transport=ws;expires=30
Sent By FreeSWITCH
Contact: sip:[email protected];transport=ws;expires=30
Analyzing the two strings, I think the problem is because of placement of '>' in the contact header value of drachtio. As you can see, the transport string ("transport=ws") is added after the main contact part by drachtio server where as it is part of contact string in FS.
Do you agree with this observation? or I am doing something wrong here?
Also, let me know if this can be fixed?
Thanks
The text was updated successfully, but these errors were encountered:
Hi,
I am trying to get a web socket based client registered on sip server using Drachtio. My web socket client is based on latest SIP.js library.
While doing the registration, on node, I have observed that the registration call flow is correct (Register, 401 Unauthorized, Register and then 200 OK). I have also observed the same message sequence on client as well. However, despite that, the client is NOT changing the state to REGISTERED.
Based on the error logs of SIP.js, this is due to some issue in Contact Header received by SIP.js Client in 200 OK.
I then tried the same scenario with latest branch of FreeSWITCH server and this time the SIP.js client did successful registration (also changed the state to REGISTERED)
Here are the two contact headers:
Sent By Drachtio
Contact: sip:[email protected];transport=ws;expires=30
Sent By FreeSWITCH
Contact: sip:[email protected];transport=ws;expires=30
Analyzing the two strings, I think the problem is because of placement of '>' in the contact header value of drachtio. As you can see, the transport string ("transport=ws") is added after the main contact part by drachtio server where as it is part of contact string in FS.
Do you agree with this observation? or I am doing something wrong here?
Also, let me know if this can be fixed?
Thanks
The text was updated successfully, but these errors were encountered: