Re: [cisco-voip] using the quick user/phone add - some artifacts

[Kent Roberts]

Opening a case… requesting things be fixed…….  Anyway where I was headed is…. 
I’ve been requesting a notepad section in CUCM since version 3.2, but I keep 
getting told thats not important…. (Almost made a couple of releases but got 
scrapped at last minute from what my AS team said)   I would think it would be 
a nice to have area, for tech notes, new DID imports, T1 or well now MPLS/Metro 
ethernet SIP circuit id’s and issues that might have been related.   Yah, it 
might be silly, but wouldn’t it be nice to have all that info in one spot with 
the rest of your CUCM configuration? I mean Lucent. (Pre-Avaya days) had 
that…. But I guess I am the only one seeing the good idea here…….  Anyone else? 
  I mean if this is a really silly idea, let me know, and I will drop it, but 
still think its a good idea…..  ?




> On Nov 27, 2019, at 1:25 PM, Pawlowski, Adam  wrote:
> 
> I haven't found a solution for that in the UCM  yet, I'm hoping it is fixed 
> better in 12.5 .
> 
> It may be one of those things that we have to get a case open for and then 
> get a defect going on, but, this takes up time.
> 
> The generic error is awful to deal with as well. & in the department name 
> breaking a template, something being too long that you've keyed in but no 
> explanation. I found the best one the other day so far. If you interact with 
> the dialog boxes that come up for a new phone/DN, and use the keyboard to 
> submit it, it double submits. The phone gives you an "Error" but then it is 
> added. When I did it with a DN, it actually inserted the DN twice (same 
> pattern and partition) so I have no idea what happened there.
> 
> Regarding the Universal templates, they have a lot of blank space and are 
> annoying to use that's for sure.  I've only seen it add the custom template 
> for Jabber for whatever reason but for the phones it will use the Universal 
> from the template.
> 
> More or less some day I'd like to get some better process going to review the 
> devices in the UCM and tweak and touch these things up. I have a lot of that 
> working in Ruby anyways for spot checks and work. Easy enough to grab the 
> device and make sure the displayname and asciidisplayname values are the same 
> and write it back. I have no time for cool things like this but the ultimate 
> goal is to allow the technicians to use the template without straying too far 
> or worrying about minutae, that we can pick up over night. We'd also look for 
> user name changes and re-write caller IDs and display names. This if course 
> means if the directory source says your name is Ronald then we are going to 
> put that there. Trivial enough with programming though to dip into another 
> field somewhere for a preferred name but I'm getting way off course now.
> 
> Adam
> 
> From: cisco-voip  <mailto:cisco-voip-boun...@puck.nether.net>> on behalf of Lelio Fulgenzi 
> mailto:le...@uoguelph.ca>>
> Sent: Monday, November 25, 2019 2:11 PM
> To: voyp list, cisco-voip (cisco-voip@puck.nether.net 
> <mailto:cisco-voip@puck.nether.net>)
> Subject: [cisco-voip] using the quick user/phone add - some artifacts
>  
>  
> So, tried out the quick user/phone add. I like it, although I had and am 
> still having some issues. (See notes below for first problem I had, with 
> solution)
>  
> The issue/concern I’m having now is that the process does the following:
>  
> Creates a custom phone button template with device name in the name of 
> template and uses that instead of the device type phone button template used 
> when creating manually.
> It uses the “Universal device template – model independent security profile” 
> instead of the device type security profile when creating manually.
> The process automatically enables mobility for the user and associates their 
> userID to the mobility ID.
> ASCII Display (Caller ID) is not filled in like the other field.
>  
> Has anyone found a way around any of these issues?
>  
> I checked the universal device template and there’s not options that I can 
> see to pick different phone button template.
>  
> I tried creating a copy of the default universal phone button template and 
> that is available in the drop down of the universal device template, but with 
> the same results.
>  
> This will mean a lot of going back to change things to match our current SOPs.
>  
>  
>  
>  
>  
>  
> Original Issue. Fixed.
>  
> For some historical archiving, I ran into the following problem: After 
> deleting a phone I created using the tool, I was not able to (re)create it 
> again. It gave me an ominous “error.add” pop-up.
>  
> Turns out, what I had done, was notice that the create process created a

Re: [cisco-voip] using the quick user/phone add - some artifacts

[Pawlowski, Adam]

I haven't found a solution for that in the UCM  yet, I'm hoping it is fixed 
better in 12.5 .


It may be one of those things that we have to get a case open for and then get 
a defect going on, but, this takes up time.


The generic error is awful to deal with as well. & in the department name 
breaking a template, something being too long that you've keyed in but no 
explanation. I found the best one the other day so far. If you interact with 
the dialog boxes that come up for a new phone/DN, and use the keyboard to 
submit it, it double submits. The phone gives you an "Error" but then it is 
added. When I did it with a DN, it actually inserted the DN twice (same pattern 
and partition) so I have no idea what happened there.


Regarding the Universal templates, they have a lot of blank space and are 
annoying to use that's for sure.  I've only seen it add the custom template for 
Jabber for whatever reason but for the phones it will use the Universal from 
the template.


More or less some day I'd like to get some better process going to review the 
devices in the UCM and tweak and touch these things up. I have a lot of that 
working in Ruby anyways for spot checks and work. Easy enough to grab the 
device and make sure the displayname and asciidisplayname values are the same 
and write it back. I have no time for cool things like this but the ultimate 
goal is to allow the technicians to use the template without straying too far 
or worrying about minutae, that we can pick up over night. We'd also look for 
user name changes and re-write caller IDs and display names. This if course 
means if the directory source says your name is Ronald then we are going to put 
that there. Trivial enough with programming though to dip into another field 
somewhere for a preferred name but I'm getting way off course now.


Adam



From: cisco-voip  on behalf of Lelio 
Fulgenzi 
Sent: Monday, November 25, 2019 2:11 PM
To: voyp list, cisco-voip (cisco-voip@puck.nether.net)
Subject: [cisco-voip] using the quick user/phone add - some artifacts


So, tried out the quick user/phone add. I like it, although I had and am still 
having some issues. (See notes below for first problem I had, with solution)

The issue/concern I’m having now is that the process does the following:


  *   Creates a custom phone button template with device name in the name of 
template and uses that instead of the device type phone button template used 
when creating manually.
  *   It uses the “Universal device template – model independent security 
profile” instead of the device type security profile when creating manually.
  *   The process automatically enables mobility for the user and associates 
their userID to the mobility ID.
  *   ASCII Display (Caller ID) is not filled in like the other field.

Has anyone found a way around any of these issues?

I checked the universal device template and there’s not options that I can see 
to pick different phone button template.

I tried creating a copy of the default universal phone button template and that 
is available in the drop down of the universal device template, but with the 
same results.

This will mean a lot of going back to change things to match our current SOPs.






Original Issue. Fixed.

For some historical archiving, I ran into the following problem: After deleting 
a phone I created using the tool, I was not able to (re)create it again. It 
gave me an ominous “error.add” pop-up.

Turns out, what I had done, was notice that the create process created a custom 
phone button template, removed this and used the standard device phone button 
template and then delete the phone after some testing. This left the custom 
phone button template (with the userID in the name) in the system. Subsequent 
(re)creates tried to create that same custom phone button template and was 
failing. “error.add” was referring to the fact it couldn’t create the template 
since it already existed.

---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | le...@uoguelph.ca<mailto:le...@uoguelph.ca>

www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, 
Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[cisco-voip] using the quick user/phone add - some artifacts

[Lelio Fulgenzi]

So, tried out the quick user/phone add. I like it, although I had and am still 
having some issues. (See notes below for first problem I had, with solution)

The issue/concern I'm having now is that the process does the following:


  *   Creates a custom phone button template with device name in the name of 
template and uses that instead of the device type phone button template used 
when creating manually.
  *   It uses the "Universal device template - model independent security 
profile" instead of the device type security profile when creating manually.
  *   The process automatically enables mobility for the user and associates 
their userID to the mobility ID.
  *   ASCII Display (Caller ID) is not filled in like the other field.

Has anyone found a way around any of these issues?

I checked the universal device template and there's not options that I can see 
to pick different phone button template.

I tried creating a copy of the default universal phone button template and that 
is available in the drop down of the universal device template, but with the 
same results.

This will mean a lot of going back to change things to match our current SOPs.






Original Issue. Fixed.

For some historical archiving, I ran into the following problem: After deleting 
a phone I created using the tool, I was not able to (re)create it again. It 
gave me an ominous "error.add" pop-up.

Turns out, what I had done, was notice that the create process created a custom 
phone button template, removed this and used the standard device phone button 
template and then delete the phone after some testing. This left the custom 
phone button template (with the userID in the name) in the system. Subsequent 
(re)creates tried to create that same custom phone button template and was 
failing. "error.add" was referring to the fact it couldn't create the template 
since it already existed.

---
Lelio Fulgenzi, B.A. | Senior Analyst
Computing and Communications Services | University of Guelph
Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1
519-824-4120 Ext. 56354 | le...@uoguelph.ca

www.uoguelph.ca/ccs | @UofGCCS on Instagram, 
Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

<>___
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip