[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cisco-voip
Subject:    Re: [cisco-voip] remove old phone models from choices
From:       lelio () uoguelph ! ca
Date:       2007-12-27 16:22:51
Message-ID: 20071227112251.kulk7coecgo40ggw () webmail ! uoguelph ! ca
[Download RAW message or body]

I haven't read up, but the provisioning tool was reasonably priced  
when it wasn't "unified". Now that it is unified, I guess it can do so  
much more that you have to pay a higher licence fee b/c of it.

With over 7500 phones and who knows how many switches, our fee was  
quite prohibitive.

Quoting Wes Sisk <wsisk@cisco.com>:

>       Hi Folks,  the CUPM team offered up a bit more insight:
>
> 1. "Does anyone know of a way to remove phone models from being a
> choice
> as a phone to add to the system?"
>
> This can be accomplished in CUPM by either adding a new customized
> subscriber role, or modifying an exhibiting subscriber role, to limit
> the selectable phone models. This can be done via the "Subscriber
> Role"
> management feature that can be accessed by an CUPM admin user under
> Advanced Setup->Policies->Subscriber Role. Select/create the
> subscriber
> in the appropriate domain and edit its orderable products to limit
> selection to only the phone models desired.
>
> 2. "The lack of support for AD integrated callmanagers kills it for
> me..."
>
> CUPM supports AD integrated Call Managers for CCM versions 5.x and
> greater. When adding an AD integrated CCM to CUPM using the
> CallProcessor wizard for v5.x+, you have the option of selecting
> "LDAP
> Directory Integration" to be one of : "Synchronization" or
> "Synchronization and Authentication".
>
> 3. "7 digit price tag"
>
> CUPM offers variable pricing based on the deployment size of the
> network
> to provisioned. Our product managers, John Freeman, or Tony Gerbic,
> can
> work with you to go over the pricing models based on the
> needs.
>
> /Wes
>
> lelio@uoguelph.ca wrote:
>
>   Quoting Bill Simon <bills@psu.edu>:
>
>   Anybody got any good alternatives to CUPM ... we really need a
> product like this but so far haven't had any success with CUPM in
> test and this rumored price tag isn't going to help the situation
> either.lelio@uoguelph.ca wrote:
>
>   I think the 7 digit price tag has something to do with it.
> ;)Quoting "Frazee, Timothy" <Timothy_Frazee@adp.com>:
>
>   That's what I figured. And that's fine. I don't hear much about the
> Provisioning Manager, is it a weak product or just not much talk about
> it?From: Wes Sisk [mailto:wsisk@cisco.com] Sent: Wednesday, December
> 26, 2007 12:22 PM To: Frazee, Timothy Cc: cisco-voip@puck.nether.net
> Subject: Re: [cisco-voip] remove old phone models from choicesI am
> not aware of anything in the native admin interface to remove
> devices.  Other choices: 1. create a template device and just copy
> it. this is available in CCMAdmin 2. have BAT profiles built for std
> phone configs then just BAT insert phone.  Even thought you may only
> insert 1 phone it forces that phone to use known template 3. use AXL
> to write your own admin interface 4. Cisco Unified Provisioning
> Manager - i'm not clear on the specifics in that product/WesFrazee,
> Timothy wrote:Group,Does anyone know of a way to remove phone models
> from being a choice as a phone to add to the system?Let's say that I
> never, ever intend on adding 7910s to a system. Is there somewhere I
> can config/tweak to prevent that from showing up as an option. Not a
> security thing, more like if I only intend on having 3 model of phone
> ever on a system I don't have to look at 30 plus when adding a phone.
>
>
>   _______________________________________________ cisco-voip mailing
> list cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip






[prev in list] [next in list] [prev in thread] [next in thread]