Google apps
Main menu

Post a Comment On: Not Just AstLinux Stuff

"Everything you wish you didn't need to know about VoIP"

7 Comments -

1 – 7 of 7
Blogger Unknown said...

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

June 14, 2012 at 7:10 PM

Blogger Unknown said...

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 :)

June 18, 2012 at 1:55 AM

Blogger Raul Fragoso said...

Very interesting reading ! Thank you for having the time to do that, looking forward for the next updates :)

-Raul

June 19, 2012 at 1:30 AM

Anonymous Nethawk said...

That would be a good idea. I always wish I knew more about SIP :)

June 21, 2012 at 6:57 AM

Blogger Damin said...

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.

June 25, 2012 at 11:12 AM

Anonymous Baylink said...

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?

July 18, 2012 at 2:50 PM

Anonymous Anonymous said...

This document definitively has been an interesting read. Keep up the good work.

February 7, 2013 at 7:50 AM

You can use some HTML tags, such as <b>, <i>, <a>

Comment moderation has been enabled. All comments must be approved by the blog author.

You will be asked to sign in after submitting your comment.
Please prove you're not a robot