[asterisk-bugs] [JIRA] (ASTERISK-27045) Issue with Parsing Contact Header without Brackets and with additional HeaderParameters seperated with semicolon

Joshua Colp (JIRA) noreply at issues.asterisk.org
Mon Dec 18 05:38:07 CST 2017


     [ https://issues.asterisk.org/jira/browse/ASTERISK-27045?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Joshua Colp updated ASTERISK-27045:
-----------------------------------

    Affects Version/s:     (was: 12.2.0)
                           (was: 11.3.0)
                       13.18.4

> Issue with Parsing Contact Header without Brackets and with additional HeaderParameters seperated with semicolon
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-27045
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27045
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/General, Resources/res_pjsip
>    Affects Versions: 13.18.4
>            Reporter: balamurugan
>              Labels: chan-sip-message-parsing
>
> 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.
> sip:p65549t0000000m112562c591000000 at 10.196.0.111:5089;+g.3gpp.accesstype="cellular";+sip.instance="<urn:gsma:imei:3561119000-996900-0



--
This message was sent by Atlassian JIRA
(v6.2#6252)



More information about the asterisk-bugs mailing list