[cisco-voip] remove old phone models from choices

Matthew Saskin matt at saskin.net
Wed Dec 26 14:43:09 EST 2007


The lack of support for AD integrated callmanagers kills it for me...

lelio at uoguelph.ca wrote:
> I think the 7 digit price tag has something to do with it. ;)
> 
> 
> 
> Quoting "Frazee, Timothy" <Timothy_Frazee at 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 at cisco.com]
>> Sent: Wednesday, December 26, 2007 12:22 PM
>> To: Frazee, Timothy
>> Cc: cisco-voip at puck.nether.net
>> Subject: Re: [cisco-voip] remove old phone models from choices
>>
>>
>>
>> I 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
>>
>> /Wes
>>
>> Frazee, 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.
>>
>>
>>
>> Timothy Frazee
>>
>> Network Solutions
>>
>> Automatic Data Processing, Inc.
>>
>> ________________________________
>>
>> This message and any attachments are intended only for the use of the
>> addressee and may contain information that is privileged and
>> confidential. If the reader of the message is not the intended recipient
>> or an authorized representative of the intended recipient, you are
>> hereby notified that any dissemination of this communication is strictly
>> prohibited. If you have received this communication in error, please
>> notify us immediately by e-mail and delete the message and any
>> attachments from your system.
>>
>>
>>
>>
>> ________________________________
>>
>>
>>
>>
>> _______________________________________________
>> cisco-voip mailing list
>> cisco-voip at puck.nether.net
>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>
>>
>> This message and any attachments are intended only for the use of   
>> the addressee and may contain information that is privileged and   
>> confidential. If the reader of the message is not the intended   
>> recipient or an authorized representative of the intended recipient,  
>>  you are hereby notified that any dissemination of this  
>> communication  is strictly prohibited. If you have received this  
>> communication in  error, please notify us immediately by e-mail and  
>> delete the message  and any attachments from your system.
>>
> 
> 
> 
> 
> 
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip



More information about the cisco-voip mailing list