Many of the folks here have suffered the Cisco/<insert_proprietary_hardware_vendor_here> lock-in and gotten burned by it. These days it makes less and less business sense to stick with proprietary platforms and protocols because you end up running the planned obsolescence hamster wheel.  With ANY proprietary platform everything is all good for the first two or three years until whatever company you bought the original platform from decides to release a software upgrade and then mandates that anyone on the old software release is going to pay double for any new licensing for users or features they may need to purchase. If you're paying a software maintenance agreement ($$) then you can do the upgrade any time you want without cost but those that aren't doing software maintenance get the major shaft.

This is why I like the business models for HP ProCurve and Adtran equipment. HP ProCurve equipment has a lifetime warranty with free software upgrades for the life of the product and Adtran generally has a 10 year warranty with free software upgrades for the life of the product. Polycom phones only come with a year warranty but have free software downloads for the life of their products.

All three of those vendors (Polycom, Adtran, and HP ProCurve) as far as I can tell strive to stick to standards defined by the IETF and as a result can fully interoperate with any platform that adheres to those standards.

My advice for those stuck with Cisco phones in a production environment is either to, for the time being, use Asterisk and chan_sccp or stick with CallManager. SIP Cisco phones really aren't good for use outside a Cisco CallManager environment. If you wish to contribute software development resources to further the interoperability of Cisco phones with sipXecs then no one is stopping you.

Also a bit off topic, for those that aren't aware, Cisco CallManager was not originally a Cisco product. It was conceived by Selsius Systems in 1997 and bought by Cisco in 1998. The original phones were very plain: http://imgs.inkfrog.com/pix/DREDD2010/vip.jpg
http://pictures.kyozou.com/pictures/_9/8540/8539412.jpg


Nathan Nieblas wrote:

It’s unfortunate that the Cisco bashing alone and not the lack of support or focus makes me want to stop using this product. In all honesty, it really doesn’t even come close to Callmanager and Unity Connection as a replacement and I actually wanted to see it get there at one point. I guess I will just replace my Cisco’s with Polycom’s before asking for any more help.

 

Regards

 

 

Nathan Nieblas

SACA Technologies, Inc.

 

From: sipx-users-boun...@list.sipfoundry.org [mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Michael Scheidell
Sent: Friday, April 23, 2010 6:16 AM
To: sipx-users@list.sipfoundry.org
Subject: Re: [sipx-users] Cisco and sipX 4.2

 

On 4/23/10 6:22 AM, Picher, Michael wrote:

“Cisco follows IETF standards for SIP”

 

That right there is funny!  Hahahaha  Good one Nathan!

they hired the same group from Microsoft that worked on the  standards for their mail server and clients.

--
Michael Scheidell, CTO
Phone: 561-999-5000, x 1259
> | SECNAP Network Security Corporation

·         Certified SNORT Integrator

·         2008-9 Hot Company Award Winner, World Executive Alliance

·         Five-Star Partner Program 2009, VARBusiness

·         Best Anti-Spam Product 2008, Network Products Guide

·         King of Spam Filters, SC Magazine 2008

 


This email has been scanned and certified safe by SpammerTrap®.
For Information please see http://www.secnap.com/products/spammertrap/


 


_______________________________________________ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/



_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to