Bug#355750: asterisk: Max-Forwards bug in SIP reply.

[Tzafrir Cohen]

Back on Tue, Mar 07, 2006 at 06:06:45PM +0100, Benoit Panizzon wrote:
> Package: asterisk
> Version: 1:1.2.1.dfsg-1bxlug0
> Severity: important
> 
> 
> Hi Asterisk Maintainer
> 
> Asterisk seams to reply all headers in sip replies, even headers not allowed:
> 
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP 157.161.x.x:5060;branch=z9hG4bK68613f0-22295;received=157.161.x.x
> From: <sip:157.161.10.10>;tag=847f7bac
> To: <sip:magma.woody.ch:5060>;tag=as49fc50f4
> Call-ID: 00000020450000680566137130619822118752831 at 157.161.x.x
> CSeq: 41580 OPTIONS
> User-Agent: Asterisk PBX
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY
> Max-Forwards: 70
> Contact: <sip:157.161.x.x>
> Accept: application/sdp
> Content-Length: 0
> 
> The Max-Forwards: is not allowed here and prevent interoperation with other PBX.
> 
> -Benoit-

Has this been tested with any later version of Asterisk? Is this a
bristuffed Asterisk? (bristuff patches chan_sip, though I don't believe
it should be relevant to this bug).

Any idea if the problem exists with upsteam 1.4 beta?

What is the other PBX you had a problem interoperting with?

[ System is Debian 3.1 ]

-- 
Tzafrir Cohen         sip:tzafrir at local.xorcom.com
icq#16849755          iax:tzafrir at local.xorcom.com
+972-50-7952406          jabber:tzafrir at jabber.org
tzafrir.cohen at xorcom.com     http://www.xorcom.com