Skip to content

Conversation

@slyoldfox
Copy link
Contributor

This could be the case if you're sending dialog.ringing(Some(headers, None))

This could be the case if you're sending dialog.ringing(Some(headers, None))
…iented transports (TCP), Content-Length MUST be specified.

Removed Header::MaxForwards from response because this is a request only header.
@shenjinti shenjinti merged commit 306a71e into restsend:main Oct 5, 2025
2 checks passed
@shenjinti
Copy link
Contributor

Thanks

@slyoldfox
Copy link
Contributor Author

Some context on this. I'm using flexisip (an intercom) which only manages TCP transport decently.

I was trying the registration sample and sending SIP MESSAGE to rsipstack through the flexisip. It seemed like the messages were arriving and that the OK reply were being sent correctly.

However the communication would stop after a few MESSAGE calls being received.

It seemed like flexisip was not get really getting the 200 OK replies at all (or at least ignoring them), because the Content-Length was not set. Because the stream is TCP. The spec requires the boundaries for the Content to be defined. If there is no body, it should be 0 and the header should always be sent so that the boundaries can be calculated.

FedorKiselev76 pushed a commit to FedorKiselev76/rsipstack that referenced this pull request Dec 28, 2025
Always send Content-Length, even if body is None
yeoleobun pushed a commit to yeoleobun/rsipstack that referenced this pull request Dec 29, 2025
fix(tts): fix test in tts track
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

Successfully merging this pull request may close these issues.

2 participants