Pingtel / SIPfoundry In Nortel’s Hands, I Guess Asterisk Was Too Hot!
August 28th, 2008
Why SIPfoundry was a better place for Nortel than Asterisk? Perhaps there might be reasons that you may have thought of. I have worked with SIPfoundry for a long time as well. Actually the SIP Softphone that I have worked on came from SIPFoundry. Now that Pingtel changed hands, a few times to end up in Nortels hand, I hope I continue to see the open source project prosper. SIPfoundry did provide for a niche that we worked on. The first open source conference server we worked on was from SIPfoundry.
I think you too should reaf what I read, The Hyperconnected Enterprise
by Tony Rybcynski from Nortel, on TMC Bloggers. Beelinebill told me about it.
Read the rest here:
Pingtel / SIPfoundry In Nortel’s Hands, I Guess Asterisk Was Too Hot!
Entry Filed under: Voice over IP
1 Comment Add your own
1. Duc Viet To Ho | August 29th, 2008 at 2:27 am
“Why SIPfoundry was a better place for Nortel than Asterisk?” Yes.. i am wondering about that a lot to and i am trying to figure out what is the best voip open-source solution.. But accquiring a company is not easy.. Tell me, if you are digium, will you share Asterisk with others? I dont think so
I just try Sipxecs for a while and my experience is still very limited. Yeap, i know that it has an api that support building a softphone and that is great but i dont need it though.. One of the most important features of Asterisk is manager interface and from any software, we can get any information of Asterisk.. I havent found it yet on Sipecs, if you know it is there, please let me know
I admit that sipxecs has promising features such as clustering, sip fully compliant.. Conference server with freeswitch is not ideal for me though.. As i can handle all i need about conference with asterisk.
Thanks
Your sincerely!
Duc Viet To Ho
Leave a Comment
Some HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>
Trackback this post | Subscribe to the comments via RSS Feed