[Freeswitch-dev] Bug in SIP URI: ; received="XX.XX.XX.XX:XXXX" is not valid (SIP BNF)

Michael Jerris mike at jerris.com
Wed Nov 19 06:53:29 PST 2008

We can follow up on the bug on this, but brian and I were testing this  
last night, it seems to work fine in our code, but I want to make sure  
there are no devices that expect it the other way, so we can post the  
patch we worked up last night but it will need some level of interop  
with different devices to make sure we don't have a regression we have  
to find out how to address.


On Nov 19, 2008, at 9:44 AM, Iñaki Baz Castillo wrote:

> 2008/11/19 Anthony Minessale <anthony.minessale at gmail.com>:
>> lets get an interop going then.
>> can you open the issue in jira http://jira.freeswitch.org
> Hi, in my second mail in this thread I already open a bug report that
> is already being handled:
>   http://jira.freeswitch.org/browse/SFSIP-102
>> will the twinkle author cooperate?
> Well, I will contact him sure. Anyway, I can sure you that my report
> is 100% correct (I've long exprience with SIP BNF grammar since I've
> done my own SIP parser trying to be fully SIP compliant and totally
> strict).
>> The problem with being the most sip compliant
>> "whatever" is the key to interop is bending on both sides.
> Sure, but again I can sure you that, in this case, Twinkle is correct
> but FS is not (FS creates an invalid SIP URI).
> Thanks for all, hope you developers could solve this small issue so I
> can use Twinkle to try FS.
> Be sure that I will examinate, test and force FS SIP stack all I can
> and will report issues if they appear ;)

More information about the Freeswitch-dev mailing list