[asterisk-dev] Possible bug – missing mandatory field Max-Forwards
me at anatoli.ws
Fri Feb 20 15:35:45 CST 2015
The proposed config option fixes the problem. I've sent feedback mentioning this in the issue tracker.
From: asterisk-dev-bounces at lists.digium.com [mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Mark Michelson
Sent: Friday, February 20, 2015 14:02
To: Asterisk Developers Mailing List
Subject: Re: [asterisk-dev] Possible bug – missing mandatory field Max-Forwards
Thanks for pointing this out.
I have commented on the issue with instructions with what I think is going wrong here.
On Thu, Feb 19, 2015 at 6:33 PM, Anatoli <me at anatoli.ws> wrote:
I was evaluating the latest Asterisk (13.2.0) with the latest PJSIP (2.3) and found a critical problem (critical if some of the endpoints enforce compliance with the SIP RFC).
I had a discussion on pjsip mailing list about this (http://lists.pjsip.org/pipermail/pjsip_lists.pjsip.org/2015-February/018120.html) where the consensus was that there is a bug in res_pjsip code that manages SIP headers. The problem consists in that first the code in res_pjsip.c removes Max-Forwards header from the request generated by PJSIP library, but it doesn't add it later, so Asterisk sends INVITE, ACK, BYE, etc. messages without this mandatory header and RFC enforcing clients reject these messages.
I've also submitted a bug report in the Asterisk issue tracker: https://issues.asterisk.org/jira/browse/ASTERISK-24807. It has a patch for a workaround, but it's not the correct way of addressing the problem (it patches pjsip library when the problem is inside res_pjsip adapter).
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the asterisk-dev