Summary:ASTERISK-21062: Pedantic should also be per extension directive
Reporter:Raul Dias (rsd)Labels:
Date Opened:2013-02-09 21:14:22.000-0600Date Closed:2013-02-10 15:02:24.000-0600
Versions: Frequency of
Environment:Androi SIP Clients. Tested with Ice Cream Sandwich (4.0) and JellyBean (4.1), probably GB (2.3) an JB (4.2) too.Attachments:
Description:The sip.conf global directive pedantic affects globally all SIP clients.
Android native SIP clients has a broken implementation.
It seems that it fails to set the From tag on the CANCEL.

With pedantic=yes, when a Android native SIP client HANGs UP, asterisk fails to detect it.
With pedantic=no everything works as expected.

As pedantic=no is not RFC complaint and some devices fails to work with it, it should be possible to have pedantic options in a extension config and not only globally.
Otherwise a mixed environment won't be possible in a few scenaries.
Comments:By: Michael L. Young (elguero) 2013-02-10 15:01:56.987-0600

Features requests are no longer submitted to or accepted through the issue tracker. Features requests are openly discussed on the mailing lists [1] and Asterisk IRC channels and made note of by Bug Marshals.

[1] http://www.asterisk.org/support/mailing-lists

If you would like to contribute a patch, it would be more then welcomed.  Also, new features have to be added against trunk.

By: Matt Jordan (mjordan) 2013-02-10 15:23:59.293-0600

As a follow up to Micheal's comment - this would be very difficult.

Many pedantic checks occur on messages before they are associated with a peer. As such, those pedantic checks would be broken if configured on a peer by peer basis. Given that all devices communicating using SIP should be encouraging compliance as much as possible and the difficulty involved in changing the granularity of this option, I don't really think this is something that would be worth pursuing, even as an improvement or new feature.