[asterisk-dev] Issue with Parsing Contact Header without Brackets and with additional HeaderParameters seperated with semicolon

[George Joseph]

On Tue, Jun 6, 2017 at 9:44 AM, bala murugan <fightwithme at gmail.com> wrote:
> Hi ,
>
> Can anyone tell me if there is a know bug raised and fixed when we handle or
> Parse Contact Header , if it is presented without brackets
>
> I get a INVITE with
> Contact:sip:p65549t0000000m112562c591000000 at 10.196.0.111:5089;+g.3gpp.accesstype="cellular";+sip.instance="<urn:gsma:imei:3561119000-996900-0>"
>
> currently this is getting parsed incorrectly based on the closed brackets
> and we end up storing the fullcontact with incomplete URI (metnioned below)
> and same is sent in the BYE REQURI.

RFC3261 isn't exactly clear on this.  Section 20.10 implies that the
brackets are optional if a display name isn't specified but the ABNF
specified down in section 25.1 implies that they are required always.

Are you using chan_sip or chan_pjsip?

>
> sip:p65549t0000000m112562c591000000 at 10.196.0.111:5089;+g.3gpp.accesstype="cellular";+sip.instance="<urn:gsma:imei:3561119000-996900-0
>
> Let me know if this is not fixed then will go ahead and raise a bug .
>
> thanks,
> Bala
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-dev mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-dev



-- 
George Joseph
Digium, Inc. | Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
Check us out at: www.digium.com & www.asterisk.org