[cisco-voip] Siemens 100K vs Cisco 7.5K

Fri May 14 19:48:55 EDT 2010

CME as SRST.. but be careful you might find users intentionally breaking the wan link in order to get additional features provided by cme.

Dennis Heim
Network Voice Engineer
CDW  Advanced Technology Services
11711 N. Meridian Street, Suite 225
Carmel, IN  46032

317.569.4255 Office
317.569.4201 Fax
317.694.6070 Cell
dennis.heim at cdw.com
www.berbee.com

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Nate VanMaren
Sent: Friday, May 14, 2010 4:28 PM
To: Bill; 'Jason Aarons (US)'; 'Bill Woodcock'
Cc: 'cisco-voip at puck-nether.net'
Subject: Re: [cisco-voip] Siemens 100K vs Cisco 7.5K

What is SRST if Cisco is a centralized call processing.  Also what about clustering over the WAN, that Cisco has tried to increasingly support in the last few years.  Probably a recognition that it's bad to have phones not work when there is a connectivity problem to the central site.

What would be more ideal is a system that doesn't lose significant functionality or any functionality when there is a WAN problem.

-----Original Message-----
From: Bill [mailto:bill at hitechconnection.net]
Sent: Friday, May 14, 2010 2:23 PM
To: Nate VanMaren; 'Jason Aarons (US)'; 'Bill Woodcock'
Cc: 'cisco-voip at puck-nether.net'
Subject: RE: [cisco-voip] Siemens 100K vs Cisco 7.5K

" But Cisco leaves a lot to be desired in management and distributed call processing"

Cisco is centralized call processing so I can only hope that it does leave a lot to be desired for a distributed environment. 

-----Original Message-----
From: Nate VanMaren [mailto:VanMarenNP at ldschurch.org]
Sent: Friday, May 14, 2010 3:22 PM
To: Bill; 'Jason Aarons (US)'; 'Bill Woodcock'
Cc: 'cisco-voip at puck-nether.net'
Subject: RE: [cisco-voip] Siemens 100K vs Cisco 7.5K

Maybe ease of use and their distributed architecture?

PS.
I've never configured or used a shoretel phone.  But Cisco leaves a lot to be desired in management and distributed call processing, SRST, MOH from remote sites, are a bunch of hacks.

SRSV looks very promising, but hopes are usually broken when you try and make it all work.

-Nate

-----Original Message-----
From: Bill [mailto:bill at hitechconnection.net]
Sent: Friday, May 14, 2010 2:18 PM
To: Nate VanMaren; 'Jason Aarons (US)'; 'Bill Woodcock'
Cc: 'cisco-voip at puck-nether.net'
Subject: RE: [cisco-voip] Siemens 100K vs Cisco 7.5K

How in the world do you figure Shoretel is ahead of Cisco in the voice market? 

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Nate VanMaren
Sent: Friday, May 14, 2010 3:07 PM
To: Jason Aarons (US); Bill Woodcock
Cc: cisco-voip at puck-nether.net
Subject: Re: [cisco-voip] Siemens 100K vs Cisco 7.5K

Shoretel?

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Jason Aarons (US)
Sent: Friday, May 14, 2010 12:51 PM
To: Bill Woodcock
Cc: cisco-voip at puck-nether.net
Subject: Re: [cisco-voip] Siemens 100K vs Cisco 7.5K

Who is ahead of Cisco in the voice market? I recall in 2000, SCCP solved a gap as SIP had/has it's interoperability issues and was better than H323v1 !

-----Original Message-----
From: cisco-voip-bounces at puck.nether.net
[mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Bill Woodcock
Sent: Friday, May 14, 2010 12:39 PM
To: Andrius Kislas
Cc: cisco-voip at puck-nether.net
Subject: Re: [cisco-voip] Siemens 100K vs Cisco 7.5K

      On Fri, 14 May 2010, Andrius Kislas wrote:
    > maybe someone knows a reason why Cisco has a 7500 IP phones limitation
    > on one server while Siemens HiPath8000 states they can handle 100.000 IP
    > phones per server? Even more interesting is that Cisco uses lightweight
    > SCCP while Siemens uses SIP. Both companies use the same industry
    > standard servers so what might be the reason for such big difference?

Cisco has been hamstrung by their acquisition of Selsius.  Selsius was an early acquisition, that pre-dated the final ratification of SIP, so wasn't standards-based.  By dint of their early acquisition, they wound up having disproportionate political power within Cisco's decision-making processes.  
So they've always pushed their proprietary (and very early) "Skinny" 
protocol, squashing SIP development within Cisco whenever possible, taking revenue credit for phones sold, even if the phones were for use in SIP installations, making it impossible to buy phones pre-loaded with SIP images, etc., etc., etc.

So, Cisco wound up behind where they should be in the voice market, no matter how hard the hardware and SIP guys worked.

                                -Bill

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

-----------------------------------------
Disclaimer: 

This e-mail communication and any attachments may contain confidential and privileged information and is for use by the designated addressee(s) named above only.  If you are not the intended addressee, you are hereby notified that you have received this communication in error and that any use or reproduction of this email or its contents is strictly prohibited and may be unlawful.  If you have received this communication in error, please notify us immediately by replying to this message and deleting it from your computer. Thank you.

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

 NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

 NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip