[Freeswitch-users] SIP Invite IP fragmentation issue

Jonas Gauffin jonas.gauffin at gmail.com
Tue Nov 18 03:05:18 PST 2008

The rfc also describes why:

SIP provides a mechanism to represent common header field names in an
   abbreviated form.  This may be useful when messages would otherwise
   become too large to be carried on the transport available to it
   (exceeding the maximum transmission unit (MTU) when using UDP, for
   example).  These compact forms are defined in Section 20.  A compact
   form MAY be substituted for the longer form of a header field name at
   any time without changing the semantics of the message.  A header
   field name MAY appear in both long and short forms within the same
   message.  Implementations MUST accept both the long and short forms
   of each header name.

On Tue, Nov 18, 2008 at 11:52 AM, Iñaki Baz Castillo <ibc at aliax.net> wrote:

> 2008/11/18 Saurabh Aggarwal <saurabh_aggarwal at hotmail.com>:
> > enabling compact headers - what is that?
> SIP allows compact headers names for a few heades:
>  From = f
>  To = t
>  Via = v
>  ...
> --
> Iñaki Baz Castillo
> <ibc at aliax.net>
> _______________________________________________
> Freeswitch-users mailing list
> Freeswitch-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20081118/9bca1d51/attachment-0002.html 

More information about the FreeSWITCH-users mailing list