When we use SIP over low-bandwidth link, its very much necesasry to reduce the packet length, the usage of compact form is one of the simplest mechanism to reduce the message size. In addition we might need to use SIGCOMP to reduce the message size further but still convey the same information...
this could be applied in any network and also it is mandatory for every stack to support compact form for header representation... Regards, Nataraju A.B. -----Original Message----- From: [EMAIL PROTECTED] on behalf of Sarju Garg Sent: Fri 6/9/2006 2:24 AM To: 'SIP-implementors mailing list' Subject: [Sip-implementors] Query Regarding Compact Form in SIP Parameter Hi all, I wanted to know when should I use compact form of SIP parameters. Is there some specific network where this need to be used? Regards Sarju # 9810304396 ----- Original Message ----- From: "Frank Shearar" <[EMAIL PROTECTED]> To: "'SIP-implementors mailing list'" <[email protected]> Sent: Friday, June 09, 2006 11:46 AM Subject: Re: [Sip-implementors] Query Regarding SIP Tester > "Sarju Garg" <[EMAIL PROTECTED]> asks: >> >> I wanted to test my SIP UAS implementation againest some tester that >> generated almost all possible scenarios. > > I don't know about "all possible scenarios", but I found the SIP Foundry > Test Framework to be very useful (http://www.sipfoundry.org/sftf/). It > certainly allowed me to find a whole host of bugs. After that, pingtel run > a > server (http://interop.pingtel.com/) for interoperability testing. I've > not > had a chance to use it yet, but using it is near the top of my todo list. > > frank > > _______________________________________________ > Sip-implementors mailing list > [email protected] > https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors > _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors The information contained in this message may be confidential to Kodiak Networks, Inc. and its subsidiaries and protected from disclosure. If this message did not reach the intended recipient, or an employee or agent responsible for delivering it to the intended recipient, you are hereby informed that any distribution or copying of this communication is prohibited. If you have received this communication in error, please notify us immediately by replying to the sender of the message and then delete the message. Thank you. _______________________________________________ Sip-implementors mailing list [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
