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

Here you go george , i have raised a issue in Jira see below 1. Asterisk 2. ASTERISK-27045 Issue with Parsing Contact Header without Brackets and with additional

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

Bala, are you going to open an issue? On Thu, Jun 8, 2017 at 7:02 AM, George Joseph wrote: > > > Here's the ABNF: >>> >>> Contact= ("Contact" / "m" ) HCOLON >>>( STAR / (contact-param *(COMMA contact-param))) >>> contact-param = (name-addr /

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

Here's the ABNF: >> >> Contact= ("Contact" / "m" ) HCOLON >>( STAR / (contact-param *(COMMA contact-param))) >> contact-param = (name-addr / addr-spec) *(SEMI contact-params) >> name-addr = [ display-name ] LAQUOT addr-spec RAQUOT >> addr-spec = SIP-URI /

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

Bala wrote: Contact:sip:p65549t000m112562c59100@10.196.0.111:5089 ;+g.3gpp.accesstype="cellular";+sip.instance="" 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

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

On Wed, Jun 7, 2017 at 5:04 PM, bala murugan wrote: > 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 > >

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

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 [Bala] I can see section 20.10 mentioned as optional , but in ABNF section 25.1 i couldnt

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

Thanks George , I am using chan_sip On Jun 7, 2017 5:19 PM, "George Joseph" wrote: > On Tue, Jun 6, 2017 at 9:44 AM, bala murugan > wrote: > > Hi , > > > > Can anyone tell me if there is a know bug raised and fixed when we > handle or > > Parse

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

On Tue, Jun 6, 2017 at 9:44 AM, bala murugan 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 >

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

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:p65549t000m112562c59100@10.196.0.111:5089 ;+g.3gpp.accesstype="cellular";+sip.instance="" currently this is