06-16-2014 06:35 AM - edited 03-16-2019 11:07 PM
Using function in Call Manager 8.6.2 to auto register Cisco IP Communicator clients on start up. Function works as design but I would like to update template which is used when devices are added to Call Manager. Can anyone tell me which template I need to update to pre-configure standard DN settings
thanks, Simon
Solved! Go to Solution.
06-23-2014 09:06 AM
Hi Simon
As you’ve found, Auto-Registration is pretty limited.
You can assign a Phone Button template to the device, and the device will receive a number from the pool of DNs you configure. It will go in a particular Device Pool, also as configured in Device Defaults.
That generally leaves you with a phone that doesn’t have appropriate services such as EM, doesn’t have proper CSSs assigned to the line or device, and doesn’t have other appropriate, standard settings.
It’s also considered a security risk as any phone or device can add itself to your system and get some sort of service. The phones you add probably don’t get the service you want them to, and the phones you didn’t add… well…
It is possible to configure them with a limited configuration and (for example) a CSS that just PLARs to your helpdesk. Your help desk can then properly configure the phone.
Alternately you could have them auto-add, and run a periodic process that converts the auto-reg phones into properly configured logged-out phones.
It sounds to me like you just need a better provisioning process, but in general auto-reg isn’t the answer, at least not entirely. It just isn’t flexible enough… pretty much all my clients have it turned off.
Aaron
06-19-2014 09:30 AM
Does this help answer your question?!
06-19-2014 01:53 PM
thanks Corey for your reply.
I have located above in Call Manager under Device > Device Settings > device defaults but was confused by heading Phone Template. I was hoping to use the template to define both directory and device setting for all devices created using auto registration. I now believe that this heading is labelled incorrectly and should read "Phone Button Template" instead of "Phone Template"
thanks again , Simon
06-20-2014 07:40 AM
06-23-2014 04:41 AM
yes that's right
06-23-2014 09:06 AM
Hi Simon
As you’ve found, Auto-Registration is pretty limited.
You can assign a Phone Button template to the device, and the device will receive a number from the pool of DNs you configure. It will go in a particular Device Pool, also as configured in Device Defaults.
That generally leaves you with a phone that doesn’t have appropriate services such as EM, doesn’t have proper CSSs assigned to the line or device, and doesn’t have other appropriate, standard settings.
It’s also considered a security risk as any phone or device can add itself to your system and get some sort of service. The phones you add probably don’t get the service you want them to, and the phones you didn’t add… well…
It is possible to configure them with a limited configuration and (for example) a CSS that just PLARs to your helpdesk. Your help desk can then properly configure the phone.
Alternately you could have them auto-add, and run a periodic process that converts the auto-reg phones into properly configured logged-out phones.
It sounds to me like you just need a better provisioning process, but in general auto-reg isn’t the answer, at least not entirely. It just isn’t flexible enough… pretty much all my clients have it turned off.
Aaron
06-24-2014 09:09 AM
great stuff , thanks Arron for the clarification on this - much appreciated
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide