-
Notifications
You must be signed in to change notification settings - Fork 83
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
sip/transp: Allow ACK w/o Max-Forwards header #1124
Conversation
src/sip/transp.c
Outdated
@@ -334,7 +334,10 @@ static void sip_recv(struct sip *sip, const struct sip_msg *msg, | |||
|
|||
if (msg->req) { | |||
if (!have_essential_fields(msg)){ | |||
(void)sip_reply(sip, msg, 400, "Bad Request"); | |||
if (!pl_strcmp(&msg->met, "ACK")) | |||
DEBUG_WARNING("Received bad ACK request\n"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
WARNING is perhaps a bit strict, perhaps INFO or DEBUG is better.
Remember what they said at IETF; Be conservative in what you send, be liberal in what you receive.
Perhaps also add some more info in the log message, for example
where is came from ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK, I'll try to improve the message. About being liberal, pjsip does accept ACK w/o Max-Forwards. It really does not cause any harm in ACK.
Max-Forwards is decremented by one for each SIP proxy, and for the ACK request this header is not really so useful. It should be fine to accept incoming ACK w/o Max-Forwards header... |
Alfred E. Heggestad writes:
It should be fine to accept incoming ACK w/o Max-Forwards header...
Done.
|
No description provided.