http://blog.roychowdhury.org/2005/12/29/developer-perspective-the-painful-evolution-of-sip/ Commentary on VoIP, SIP, IMS, Web 2.0 and Technology Tue, 06 Jan 2009 03:56:38 +0000 http://wordpress.org/?v=2.5.1 http://blog.roychowdhury.org/2005/12/29/developer-perspective-the-painful-evolution-of-sip/#comment-11 Anonymous Wed, 04 Jan 2006 05:01:00 +0000 http://iconverged.wordpress.com/2005/12/29/developer-perspective-the-painful-evolution-of-sip/#comment-11 Two of the most important things that I personally dislike about SIP and I am glad you mentioned both. 1) Why the heck have a text based protocol? Text based protocol in an embedded solution? Boy. 2) No architectural outlines. Two of the most important things that I personally dislike about SIP and I am glad you mentioned both. 1) Why the heck have a text based protocol? Text based protocol in an embedded solution? Boy. 2) No architectural outlines.

]]> http://blog.roychowdhury.org/2005/12/29/developer-perspective-the-painful-evolution-of-sip/#comment-10 Arjun Tue, 03 Jan 2006 16:59:00 +0000 http://iconverged.wordpress.com/2005/12/29/developer-perspective-the-painful-evolution-of-sip/#comment-10 I did mention Radvision - please check again :-) I did mention Radvision - please check again

]]> http://blog.roychowdhury.org/2005/12/29/developer-perspective-the-painful-evolution-of-sip/#comment-9 Anonymous Tue, 03 Jan 2006 10:31:00 +0000 http://iconverged.wordpress.com/2005/12/29/developer-perspective-the-painful-evolution-of-sip/#comment-9 I think you forgot to mention a major SIP stack vendor - this is RADVISION I think you forgot to mention a major SIP stack vendor - this is RADVISION

]]>