[OpenSIPS-Devel] [ opensips-Bugs-3502752 ] Internally generated requests are not RFC3261 compliant
SourceForge.net
noreply at sourceforge.net
Wed Mar 14 14:30:22 CET 2012
Bugs item #3502752, was opened at 2012-03-12 09:53
Message generated for change (Comment added) made by vladut-paiu
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=3502752&group_id=232389
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: trunk
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Dynamic Packet (dpacket)
>Assigned to: Vladut-Stefan Paiu (vladut-paiu)
Summary: Internally generated requests are not RFC3261 compliant
Initial Comment:
It seems internally generated requests via function "tmb.t_request_within()" do not contain Max-Forwards header and there therefor not RFC3261 compliant. This can be manifested by many internally generated requests, an easy one to test is with dispatcher ping.
Steps to reproduce:
1) Configure dispatcher module to use OPTIONS probes, with OpenSIPS#2 box in dispatcher list
2) On OpenSIPS#2, call "sipmsg_validate("sh")" early in route block before handeling OPTIONS
3) Watch as the sipmsg_validate fails, debug output attached
Suggested fix:
Patch tmb.t_request_within to include maxforwards header.
----------------------------------------------------------------------
>Comment By: Vladut-Stefan Paiu (vladut-paiu)
Date: 2012-03-14 06:30
Message:
Hello,
Thanks for reporting this.
The issue has been fixed and committed on the trunk and 1.7 branches.
Regards,
Vlad
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=3502752&group_id=232389
More information about the Devel
mailing list