5 New IP Phones from Cisco

babul's picture

Not sure why this information isn't on Cisco or MyCiscoCommunity's websites, but here's the scoop from VoipInsider...
http://blog.voipsupply.com/5-new-ip-phones-from-cisco
I like having more button options...  Having only 4 buttons on the 525G has been limiting.  I just ordered the SPA500S for my own 525G.

Share/Save
5
Average: 5 (1 vote)
Your rating: None

Comments

cbandit's picture

Physical design flaws

After looking at these phones a bit more, I'm shaking my head at some of the design choices.  I'm nitpicking, to be sure, but I still think they're valid criticisms from a usability and physical appearance standpoint.
 
The only phone out of the five whose line appearances line up with their respective buttons is the SPA501G, which is the 8-line-appearance phone without an LCD display (it uses a paper line-label insert).  Since it has no display, the phone has no soft keys, so the four soft-key buttons have been assigned to static functions.  I really don't have any particular complaints with the design of this phone, it seems straightforward.
 
However, the SPA502G, which is allegedly a two-line-appearance phone, has no line appearance buttons at all, and the SPA504G, SPA508G, and SPA509G all have somewhat wacky line appearance button layouts.  I'm imagining one can use the dirpad to bounce back and forth between the two lines, but I don't understand why Cisco didn't just slap two buttons on the phone next to the display.
 
The rest of the phones suffer from having the buttons offset from the physical appearances of the lines on the display, with no lines or grooves on the bezel leading from the buttons to their lines. I understand why it is the way that it is: the buttons are in the same place as they are on the SPA501G, which has no header or footer on its display, so on that phone, the buttons line up exactly with the lines.  By keeping the buttons in the same place, Cisco can use some of the same circuit boards between models to save on production costs.  But on those others, with the header and footer, the buttons no longer line up. But it's not like all the phones use the exact same bezel mold (look carefully, they're all different in at least one way), so I don't see why they didn't put grooves on the bezel for the SPA502G-SPA509, like they do on the Cisco 79xx series (and the Avaya 46xx series, for that matter). Note that the SPA525G has the same flaw.
 
What is up with the SPA509G, though? Did Cisco really slap four additional line appearance buttons below the softkeys in that bezel inset? It just looks awkward, and I wonder how awkward it is to use.
 
IMHO, to keep production costs and configuration complexity down, Cisco should have stuck with the SPA501G, SPA504G, and the SPA508G and skipped the SPA502G and the SPA509G completely.  The latter two are kind of odd men out, and I don't think that anyone who needs more than eight line appearances would have crowed too loudly about needing the SPA500S sidecar.  If anything, I would like to see a "SPA516G" that looks like SPA508G with a "page" button to switch between two virtual pages of eight buttons (a la the 7915/7916 sidecars).
 
Finally, I really would have liked to see a sidecar with an LCD display, in addition to the paper-label-insert SPA500S.

marchern's picture

Contact information

cbandit,
 
I would be interested to discuss with you the phone application and the general comments you had. If you could contact me at marchern@cisco.com, that would be great.
 
Thanks,
Marcos

isworks's picture

I've known about these for a couple of months....

I did some usability with them. They're pretty cool.

ttrentler's picture

Nice work Babul!

I would think that we should see a new version of IOS by 9/2 to support these new phones.  Also it looks like these Use SPCP rather than SCCP so they should work with a Uc500 but not with CME on an ISR Router (except as a third party SIP phone).

marchern's picture

New Phones

We haven't posted he announcement on the community because public availability will be turned on in a few weeks. Right now, the products were announced to our Disti only, which is standard procedure. More information to come.
 
Thanks,
 
Marcos Hernandez
Technical Marketing Engineer
Cisco Systems, Inc.

cbandit's picture

SPCP-only again?

Argh. Marcos, why does Cisco keep releasing SPCP phones that only work with the UC500, instead of making them SCCP so they can also register with ISRs running UCME, or even with a CCM cluster? It's so aggravating, because the only difference between SPCP and SCCP, as far as I know, is that SPCP phones make sure they're registering with a UC500 instead of an ISR.
 
Let me answer my own question: clearly, there's no technical reason these phones couldn't work with an ISR, so it's just another example of artificial market segmentation, designed to force ISR customers to pay for more expensive 7900 series phones that aren't even as feature-rich as these new phones!

ttrentler's picture

SPCP vs SCCP

So I got on the phone with my sources at Cisco regarding this exact question.  Why not have these phones work with Unified Communications Manager or even full blown Unified Communications Manager Express?  From the replies I got, my impression is this. . .
The Business Unit that handles SBCS is separate unit that has a bit of free reign regarding features on the Uc520 and the SPA500 series phones.  I think that the BU is feeling pressure to get new features out onto the UC500 and having to support these phones on Unified Communications Manager/Express would add to delay at this point in getting features to market.  They shared with me some of the features that are upcoming even beyond CCA2.1 going into Early Field Trial next week and I must say they are impressive.  
Unfortunately I can't share them yet due to my signed NDA with Cisco :(
I am going to start selling more SPA525Gs.  Lets just say the hardware is beefier and can do more than the 7900 series. We will be seeing more features on this model in the next few months.
Ted
 
 

cbandit's picture

"I think that the BU is

"I think that the BU is feeling pressure to get new features out onto the UC500 and having to support these phones on Unified Communications Manager/Express would add to delay at this point in getting features to market."
 
This might be true for UCM, but I don't see how it's true for UCME, since the main UC520 unit is essentially an 1861 ISR that runs UCME with some bits in the EEPROM that identify it as a UC520.

babul's picture

cbandit - I understand where

cbandit -
I understand where you are coming from.  I would agree with you expect on one point.
These phones while feature rich on paper and on a desk, they do not have the same firmware "finish" of the 7900 series phones.  I would guess that Cisco doesn't want ISR or CCM clients to think these phones are drop in ready like the 7900 series are at this point.  If so, I totally agree.
Their Linksys-dev roots still REALLY show and all the odd quirks/annoyances I'm sure will eventually work themselves out.  But for now, my entire office is on the 7900 series phones because they work and act like normal office workers expect a phone to work - without ANY quirks.  My coworkers always Ooo and Aaah over the 525G, but when they see how quirky it is for me, they don't want anything to do with it.
Best analogy I have comparing 500 and 7900 series phones is comparing "High-End" Linksys Routers vs Cisco ISRs.  Apples and Oranges.
With all of the new 500 series models I am hoping the market reach of these phones gets larger so Cisco will invest more into this series to get them to the same level as the tried and true 7900s.
My .02...

cbandit's picture

The top end of the 7900

The top end of the 7900 series is great (I have a 7965 on my desk right now), but the low end blows, and that's why I'm so irritated about the market segmentation.  While the 7906 and 7912 languish with a single line appearance and no duplex speakerphone, and the 7906, 7912, 7942, and 7962 all have no backlight, these new phones all have backlit displays, duplex speakerphones, and (with the exception of the SPA501G) multiple line appearances, all at an affordable price point.  Yet they're tied to the UC500, a platform that's nice enough, but it's a dead end for the largish small companies I'm trying to sell to (those near the magic 48-phone mark) who might want to add more endpoints, trunks, DSPs, or voicemail storage than the UC500 will allow.  With the ISR and UCME, I can avoid a forklift upgrade for these growing customers, or at least move their modules to a new router if they grow.  If I sell these people a UC500, they're just stuck with a forklift upgrade of the entire system, but if I sell them an ISR with UCME off the bat, they're stuck with some pretty mediocre phones unless they pay through the nose for 79x5es, which most of them won't do.

marchern's picture

Question for you

Cbandit, based on you experience, do you think that is the market segment that UC500 should be attacking? That is, 50+ users with room for growth?
 
Also, and this is more of a rethorical question, would more DSP/memory help? Would you stay on UC500 instead of ISR if we had such a product?
 
Thanks,
Marcos

cbandit's picture

Marcos

To be honest, I've always been confused about the whole point of SBCS, at least as far as having a distinct hardware lineup. I understand and endorse the goal to provide an affordable, easy-to-manage, easy-to-configure system that combines firewall, routing, switching, controller-based wireless, and IP telephony, but I really don't understand why this can't be accomplished with the ISR and UCME.  The beauty of the ISR 2800/3800 series is that they're so modular and configurable. You can start off with a small ISR/UCME and move big without throwing everything out, and if you really want to, you can even graduate to UCM and still use the ISR as an MGCP gateway and/or an SRST.  I just don't understand why Cisco developed a whole new dead-end hardware lineup for SBCS when it had the 2800 series to build on.  Modularity and upgradeability don't complicate things; they're two big strengths of many of Cisco's product lines, and the products without it are just disappointing.
 
If nothing else, then yes, it would be very helpful for me if the SBCS platform supported 50-100 users, and it would be nice if it did so in an expandable manner (incremental license counts, at least, say 64, 80, and 96 user levels).
 
Better yet, killing SPCP in favor of straight SCCP and letting UC500 and UCME on the ISR use the same phones would help me immensely. And, of course, allowing any of the IP phones to run SCCP against any of the call processing platforms (UC500, ISR/UCME, and UCM) would be ideal.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.