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

2017-06-07 Thread George Joseph
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 > Contact:sip:p65549t000m112562c59100@10.196.0.111:5089;+g.3gpp.a

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

2017-06-07 Thread bala murugan
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 Contact Header , if it is presented without brack

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

2017-06-07 Thread bala murugan
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

2017-06-07 Thread George Joseph
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 > > [Bala] I can see section 20.