A few years back I was talking with my editor at O'Reilly Media about a book I'd like to write. The book would cover details of the SIP protocol, best practice, interop scenarios, and even a few implementation specifics - FreeSWITCH, Asterisk, OpenSIPS, Kamailio, etc. Basically your typical open source software book only this time it would be SIP protocol inward.
While my editor liked the idea (I think they have to tell you that) he said there wouldn't be much of a market for it. If I remember correctly his exact words were "Kris, that's a great idea but only 100 people in the world would buy it". Clearly you can't print a physical book through a major publisher with editors, technical reviewers, etc if only 100 people are going to buy it. I tabled the idea.
Several years later I find myself still regularly talking about SIP and going into many protocol and implementation specifics. Like my editor once told me it seems there aren't a lot of people in this area with either the interest or experience. I guess he was right. Still, SIP is confusing enough and widespread enough that something has to be done.
Over the past couple of months (off and on - I rarely work uninterrupted these days) I sat down and wrote. Stream of consciousness, without reference, writing. What I ended up with is a (currently) 21 page document I like to call "Everything you wish you didn't need to know about VoIP".
It's still an early draft but as we say in open source "release early, release often". It has typos. It may not always be factually correct. There are no headings, chapters, or spacing. I may not always use apostrophes correctly. Over time I will correct these mistakes and hopefully (with your help) address other topics of concern or questions my readers may have. I may even divide it into logical chapters at some point! Wow, that would be nice.
However, as the philosophers say a 100 mile journey begins with a single step. With that said, blog reader, I present to you "Everything you wish you didn't need to know about VoIP".
Let me know what you think (I have a comments section and easy to find e-mail address).
7 comments:
Thanks Kristian,
As someone who has crossed paths with you in an interop. I plan to read and read often. Keep the updates coming!
Tim
I'm very excited to read through this! Thank you for taking the time and putting forth the effort to make this available to the public :)
Very interesting reading ! Thank you for having the time to do that, looking forward for the next updates :)
-Raul
That would be a good idea. I always wish I knew more about SIP :)
There are not enough fake mustaches in your manifesto. Also, there is a disturbing lack of plot. When I sit down to read a book, I prefer to have a story. One time, I read a story about an evil groundhog with Torret's syndrome who ate nothing but carrots and learned how to fly. It was very uplifting. Groudhog are not RFC-2833 compatible and they do not function very well as SIP Proxies.
I have a question, Kris, as I read through your little book here:
If, as you say in another post, you "[think] the “secret sauce” to business grade voice over the internet was monitoring and management", then why is it that you think registering SIP connections to gateway providers is a Bad Thing?
It would seem to me that it's your Yellow Alarm on that particular trunk group to that gateway; is there something I'm missing?
This document definitively has been an interesting read. Keep up the good work.
Post a Comment