[cisco-voip] setting primary phone for Jabber users without a physical phone - licensing

Pawlowski, Adam ajp26 at buffalo.edu
Wed Jan 15 15:33:06 EST 2020 

The UI broke at some point and none of the proper localization fills in, so I guess get used to error.add .

It seems to use AXL or something similar in the background, and you can debug what the error is from the application log in RTMT, though half the time it’s a code and not useful.

Duplicate items will break it, as will things that are not valid for insert but are part of your universal templates, such as #DEPT# and someone has a department name with & in it.

As for the custom templates, they’re one of those once-a-year things I clean up with the database by assigning the phonetemplate record to the type, and then removing any of the phone templates that aren’t associated with anything.

I used to say they don’t hurt anything but if you invest in MigrationFX, it will leverage the phone button template as a selector to help you choose the correct migration. Unless you want it to clone SEPasdfghjkl-Invididual Template-8841-MFX all over, you’ll want these to be consistent.


From: Lelio Fulgenzi <lelio at uoguelph.ca>
Sent: Wednesday, January 15, 2020 3:28 PM
To: Pawlowski, Adam <ajp26 at buffalo.edu>; Anthony Holloway <avholloway+cisco-voip at gmail.com>
Cc: voyp list, cisco-voip (cisco-voip at puck.nether.net) <cisco-voip at puck.nether.net>
Subject: RE: [cisco-voip] setting primary phone for Jabber users without a physical phone - licensing


If you really want to hear where it falls short, check this out:


  *   Create jabber phone with tool.
  *   It creates phone with custom phone button template.
  *   I don’t like it, so I change it to our standard.
  *   I want to test things again, so I delete phone and try to create again.
  *   It doesn’t work. It fails with the most descriptive error ever: “Error.add”
  *   TAC couldn’t figure it out.

Turns out, if you delete a phone with a custom phone button template, it will delete the template (if not in use elsewhere?). But because I changed the template to our standard template, the custom template remained.

When I tried to create the phone again using the tool, it tried to recreate the custom template, but because it already existed, it failed. ERROR.ADD

Ugh. UI 101….. better error messages!


From: Pawlowski, Adam <ajp26 at buffalo.edu<mailto:ajp26 at buffalo.edu>>
Sent: Wednesday, January 15, 2020 3:03 PM
To: Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>; Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway+cisco-voip at gmail.com>>
Cc: voyp list, cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>) <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: RE: [cisco-voip] setting primary phone for Jabber users without a physical phone - licensing

Yes, it’s “almost” there, but falls short on those things you note.

But, it is at least consistent in what it does or doesn’t do, so you know what you have to fix or clean up.



From: Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>
Sent: Wednesday, January 15, 2020 3:00 PM
To: Pawlowski, Adam <ajp26 at buffalo.edu<mailto:ajp26 at buffalo.edu>>; Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway+cisco-voip at gmail.com>>
Cc: voyp list, cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>) <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: RE: [cisco-voip] setting primary phone for Jabber users without a physical phone - licensing

Ok. I’ll have to keep that in mind.

I found a few “oddities” as I mentioned.


  *   No way to specify phone button templates. It creates a custom one for each user.
  *   It enables mobility by default which allows people to set up remote destinations for the jabber. We want to avoid that at launch so we will have to disable manually after the fact.
  *   It doesn’t populate the ASCII display fields.
  *   It doesn’t allow for the sip security profile and uses the universal template. Something we’ll have to change after.

They went so far with this tool, but missed out on a few things. I wish I had know about it sooner.

Lelio


From: Pawlowski, Adam <ajp26 at buffalo.edu<mailto:ajp26 at buffalo.edu>>
Sent: Wednesday, January 15, 2020 2:54 PM
To: Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>; Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway+cisco-voip at gmail.com>>
Cc: voyp list, cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>) <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: RE: [cisco-voip] setting primary phone for Jabber users without a physical phone - licensing

Yes this works, just with the caveat about common phone profiles not working (again, at least for me, 11.5) though that’s not quick add’s fault.

Also, in my experience click the buttons, pressing enter has undesirable effects. I have been able to press “enter” when adding a new device and have had it double – insert which I didn’t think was possible.



From: Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>
Sent: Wednesday, January 15, 2020 2:42 PM
To: Pawlowski, Adam <ajp26 at buffalo.edu<mailto:ajp26 at buffalo.edu>>; Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway+cisco-voip at gmail.com>>
Cc: voyp list, cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>) <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: RE: [cisco-voip] setting primary phone for Jabber users without a physical phone - licensing

Sorry. I’m mixing scenarios.

I think I have the process of adding Jabber devices for users with an existing phone down pat. With some oddities that we’ll have to address.

I’m concerned with creating Jabber devices for users without an existing phone -or- DN.

That being said, I believe I have that figured out, but will need to test it out.


  *   Go to quick user/phone add
  *   Select user (that has already been imported)
  *   Go to extension section
  *   Add a new extension using the appropriate Line template
  *   Click save (likely)
  *   Go to manage devices and add the appropriate device

We’ll have to see how that works out.

Lelio



From: Pawlowski, Adam <ajp26 at buffalo.edu<mailto:ajp26 at buffalo.edu>>
Sent: Wednesday, January 15, 2020 10:50 AM
To: Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>; Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway+cisco-voip at gmail.com>>
Cc: voyp list, cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>) <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: RE: [cisco-voip] setting primary phone for Jabber users without a physical phone - licensing

I’m still a bit confused, unless you mean that with the quick add you’ve already set extensions for the user so that the templates will work, as you’ve already provisioned a phone?

We are sort of in the same boat. The sync will provision based on a mask if your LDAP data contains good numbers. You can also tell it to start assigning numbers from a pool on the same screen.  I have multiple exchanges I issue numbers from based on customer/location so this doesn’t do me any good pool-wise, and we don’t control the LDAP data so anything goes there.

You can configure the DN first, yes, as long as it is the primary extension it will appear in the quick add tool. I haven’t quite figured out where it stores the rest of the DNs you can add there or their order but the primary extension sure appears there.

I’m not sure if Prime Provisioning can assist with this task since it has some more capabilities, if it works for your installation.

From: Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>
Sent: Wednesday, January 15, 2020 10:33 AM
To: Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway+cisco-voip at gmail.com>>
Cc: Pawlowski, Adam <ajp26 at buffalo.edu<mailto:ajp26 at buffalo.edu>>; voyp list, cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>) <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: RE: [cisco-voip] setting primary phone for Jabber users without a physical phone - licensing

Yeah – I was looking at that. I’m not sure we can take that approach because we have so many already imported. And extensions are assigned by us, not the AD team. It’s weird.

I will look through.

Question: Is there a “pool” that CCM will grab an extension from to assign magically?

From: Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway+cisco-voip at gmail.com>>
Sent: Wednesday, January 15, 2020 10:28 AM
To: Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>
Cc: Pawlowski, Adam <ajp26 at buffalo.edu<mailto:ajp26 at buffalo.edu>>; voyp list, cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>) <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] setting primary phone for Jabber users without a physical phone - licensing

The way I use self-provisioning, is to allow CUCM to create the lines for me at user synchronization time.

System > LDAP > Dir > Enterprise Users* > Feature Group Template > Common Features* > User Profile > Common User* > Universal Line Template > Common Line* > All kinds of template settings
System > LDAP > Dir > Enterprise Users* > Apply Mask to synced telephone numbers to create a new line for inserted users > Checked
System > LDAP > Dir > Enterprise Users* > Apply Mask to synced telephone numbers to create a new line for inserted users  > Mask > XXXXXXXXXXXX**

*These are just the names of my objects, your names might be different.
**That's 12 Xs to accommodate a NANP +E164 number from LDAP

On Tue, Jan 14, 2020 at 9:54 PM Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:

I guess I’m missing the piece of how is an extension assigned then?

With an existing phone, the extension is assigned automatically.

I was gonna do some testing, but any pointers would help.

I mean, can I create the DN first? And configure DN with userID?

I’m still getting used to this process.
-sent from mobile device-

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<tel:519-824-4120;56354> | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>

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



On Jan 14, 2020, at 8:35 AM, Pawlowski, Adam <ajp26 at buffalo.edu<mailto:ajp26 at buffalo.edu>> wrote:
The quick user/phone add should work as generically for Jabber devices as anything else. Just that I’ve found that the common phone profile will not populate the correct “Cisco Support Field” for mobile and I have to go into those and key in the configuration file that customer should have.

It ended up being easier to insert via AXL to avoid having to fool with that.

Adam

From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> On Behalf Of Lelio Fulgenzi
Sent: Monday, January 13, 2020 1:13 PM
To: voyp list, cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>) <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: [cisco-voip] setting primary phone for Jabber users without a physical phone - licensing


I’m trying to setup an easy to replicate (troubleshoot/reconcile) system in place for our Jabber deployment.

We’ve decided to assign each Jabber device type to each user so there’s no end-user support issues when they want to use it on another device and/or move from one device type to another.

If I’m not mistaken, in this case, and, in any case where a primary phone is not set, more licenses are used then would need to be. The issue at hand here, is what happens when we deploy Jabber without a physical phone?

I’m already finding that the quick/add feature really only works when a phone is configured (although I have to work through that). So, I’m wondering, is it worthwhile to configure a “dummy” phone for Jabber users and set the primary phone for all Jabber clients to this dummy phone? Or should I ask them to pick the CSF jabber device as the primary phone for example?

What have others done?

Lelio

_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200115/a601b7a1/attachment.htm>

More information about the cisco-voip mailing list