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

Kristian Kielhofner kkielhofner at star2star.com
Fri Nov 21 08:17:06 PST 2008

On 11/19/08, Michael Collins <mcollins at fcnetwork.com> wrote:
> I've been watching FS (and Asterisk) for the past 3 years and if there's
>  anything I've learned it's that SIP is a fickle friend. Saying that
>  something is "the most SIP compliant" device/endpoint/gadget isn't
>  exactly a bragging point. If every piece of SIP equipment out there
>  tried to adhere to the absolute letter of every SIP-related RFC then
>  nothing would work! (Yes, that's an exaggeration, but not a big one.)
>  Anyway, we're all stuck with SIP because no one could come up with
>  anything better *and* get enough telecom players to use it widely. So
>  instead we're all stuck with a grossly imperfect protocol that has its
>  strengths and weaknesses. The FS devs have chosen a wise course: make
>  their SIP implementation use the good stuff in SIP while trying to
>  minimize the stupid things that SIP allows and/or requires.
>  End of rant, thanks for listening.
>  -MC

Basic tenet for any RFC:

"Be strict in what you send and liberal in what you accept."

Kristian Kielhofner

More information about the Freeswitch-dev mailing list