The rfc also describes why:<br><br>SIP provides a mechanism to represent common header field names in an<br> abbreviated form. This may be useful when messages would otherwise<br> become too large to be carried on the transport available to it<br>
(exceeding the maximum transmission unit (MTU) when using UDP, for<br> example). These compact forms are defined in Section 20. A compact<br> form MAY be substituted for the longer form of a header field name at<br>
any time without changing the semantics of the message. A header<br> field name MAY appear in both long and short forms within the same<br> message. Implementations MUST accept both the long and short forms<br> of each header name.<br>
<br><br><div class="gmail_quote">On Tue, Nov 18, 2008 at 11:52 AM, Iņaki Baz Castillo <span dir="ltr"><<a href="mailto:ibc@aliax.net">ibc@aliax.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
2008/11/18 Saurabh Aggarwal <<a href="mailto:saurabh_aggarwal@hotmail.com">saurabh_aggarwal@hotmail.com</a>>:<br>
> enabling compact headers - what is that?<br>
<br>
SIP allows compact headers names for a few heades:<br>
<br>
From = f<br>
To = t<br>
Via = v<br>
...<br>
<br>
<br>
--<br>
<font color="#888888">Iņaki Baz Castillo<br>
<<a href="mailto:ibc@aliax.net">ibc@aliax.net</a>><br>
_______________________________________________<br>
Freeswitch-users mailing list<br>
<a href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</font></blockquote></div><br>