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
Originally created this issue over in the FSMRF repo, but after looking at the code, it seems like its actually a drachtio-server issue. Let me know which I should keep open.
We've begin leveraging TURN servers for our WebRTC connections, and it seems to have pushed us over some kind of limit on the size of the SDP that can be sent from Drachtio -> Freeswitch. We noticed because we began getting some SIP 400s sent back to us from Freeswitch. When the SDP is cut off in a particular spot that breaks parsing, then a 400 results. Usually it seems to work anyway though because what is getting cut off doesn't seem to matter. It seems the truncated INVITE always has a Content-Length of 8384. However, we were not able to find anything in code that would account for this ceiling. Also, when this happens, it seems to eventually put Drachtio into a bad state where it stops responding to requests.
In the drachtio logs, I see the 2 invites (a) one from wp#send which contains the full SDP (I've cut off some of it to save space) and (b) the Msg sent: log which is what is actually sent to FS. Also notice the 2 Content-Lengths are different.
@lylepratt can you give me a full drachtio log file showing the INVITE coming in and that going out? I can then use that example to craft my test case.
Originally created this issue over in the FSMRF repo, but after looking at the code, it seems like its actually a drachtio-server issue. Let me know which I should keep open.
Original issue:
drachtio/drachtio-fsmrf#66
We've begin leveraging TURN servers for our WebRTC connections, and it seems to have pushed us over some kind of limit on the size of the SDP that can be sent from Drachtio -> Freeswitch. We noticed because we began getting some SIP 400s sent back to us from Freeswitch. When the SDP is cut off in a particular spot that breaks parsing, then a 400 results. Usually it seems to work anyway though because what is getting cut off doesn't seem to matter. It seems the truncated INVITE always has a Content-Length of 8384. However, we were not able to find anything in code that would account for this ceiling. Also, when this happens, it seems to eventually put Drachtio into a bad state where it stops responding to requests.
In the drachtio logs, I see the 2 invites (a) one from
wp#send
which contains the full SDP (I've cut off some of it to save space) and (b) theMsg sent:
log which is what is actually sent to FS. Also notice the 2 Content-Lengths are different.Do you have any idea what could be causing this?
Correct invite
Cut off invite...notice the last line is cut
The text was updated successfully, but these errors were encountered: