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

Tue Jan 21 13:44:17 EST 2020

Oh jeez, and now I think I spotted my syntax error: I forgot to mention the
table name in the select statement.  Grrr.

I'll give it a shot a little later, but this syntax should work then:

admin:run sql insert into device (pkid, name, col1, col2, colN...) select
newid(), concat(name, " - copy"), col1, col2, colN... from device where
name = 'the name you want to copy'

On Tue, Jan 21, 2020 at 11:37 AM Tucci, Ben via cisco-voip <
cisco-voip at puck.nether.net> wrote:

> I was able to do a simplified version of that on a smaller table – we had
> to build an app internally for this due to CSCuz76525
> <https://bst.cloudapps.cisco.com/bugsearch/bug/CSCuz76525> (which has
> happened a few times to us). The AXL side requires that you send it all of
> the devices to add which isn’t ideal if we have many users trying to make
> changes. So we just call this insert from a separate web app for our admin
> users.
>
>
>
> It’s a mix of data sources so it’s possible the syntax error is something
> in the quotes used or something else. I’m leaving the IDs in but they would
> need to be made specific.
>
>
>
> insert into applicationuserdevicemap (pkid, fkdevice, fkapplicationuser,
> tkuserassociation) select newid(), pkid,
> 'b11187e9-ba5d-aeeb-5afa-1950b50f99e9', 1 from device where name =
> 'SEP204C9E6C71A0'
>
>
>
> Those IDs are also from a lab environment we set up, and I would be very
> careful with these changes as you can insert a record ccmadmin can’t
> display and cause quite a panic. This was run on 10.5.2.
>
>
>
>
>
> *From:* cisco-voip <cisco-voip-bounces at puck.nether.net> *On Behalf Of *Anthony
> Holloway
> *Sent:* Tuesday, January 21, 2020 12:05 PM
> *To:* Pawlowski, Adam <ajp26 at buffalo.edu>
> *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
>
>
>
> Disclaimer:  Please test in a lab thoroughly before playing cowboy/girl
> and just modifying the database willy-nilly.
>
>
>
> I was able to pull the SQL insert from CCMAdmin tomcat logs when adding a
> new template from the GUI, and then use the syntax to insert my own records
> at the CLI.  However, using the below structure to copy an existing record
> fails, with a syntax error, which is a real shame.
>
>
>
> admin:run sql insert into device (pkid, name, col1, col2, colN...) select
> newid(), concat(name, " - copy"), col1, col2, colN... where name = 'the
> name you want to copy'
>
>
>
> Where col1, col2, and colN are the required columns needed to properly
> insert a new record (again, taken from CCMAdmin traces upon inserting a new
> template via the GUI).
>
>
>
> The idea is to insert a new record, specifying all of the proper column
> names (e.g., pkid, name, fkdevicepool, etc.), while dynamically generating
> a new PKID, and appending " - copy" to the name of the record I want to
> copy.
>
>
>
> According to some documentation, that command syntax should work in
> Informix.  I tried a few other variations, but I can't figure it out.  Can
> anyone else figure it out?  Could be a useful construct for copying just
> about anything in the DB.
>
>
>
> On Tue, Jan 21, 2020 at 10:16 AM Pawlowski, Adam <ajp26 at buffalo.edu>
> wrote:
>
> They are in the database and you can pull them up as a phone if you nav to
> edit them with their record’s pkid as the key. I haven’t tried inserting
> one there but it’s in there.
>
>
>
> I bet it would work as well as any of that does otherwise.
>
>
>
>
>
>
>
>
>
> *From:* Lelio Fulgenzi <lelio at uoguelph.ca>
> *Sent:* Monday, January 20, 2020 1:58 PM
> *To:* Lelio Fulgenzi <lelio at uoguelph.ca>; Pawlowski, Adam <
> ajp26 at buffalo.edu>
> *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
>
>
>
>
>
> Ok, so I’m finding a few more issues with these templates. I have a case
> open for more details. But, I’m likely going to have to live with them.
>
>
>
> But what I don’t like? What I really don’t like?
>
>
>
> There’s no way to copy universal templates. ARGH.
>
>
>
> There’s not even a way to export them and then import them.
>
>
>
> Why?!?!
>
>
>
> </rant>
>
>
>
>
>
> *From:* cisco-voip <cisco-voip-bounces at puck.nether.net> *On Behalf Of *Lelio
> Fulgenzi
> *Sent:* Wednesday, January 15, 2020 8:56 PM
> *To:* Pawlowski, Adam <ajp26 at buffalo.edu>
> *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
>
>
>
> Sort of like how all the icons/graphics for ccmuser pages are broken for
> new phone types added with devpacks. Logs show nothing but errors. Opened
> up case, told it’s cosmetic.
>
>
>
>
>
> *-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 <519-824-4120;56354> | lelio at uoguelph.ca
>
>
>
> www.uoguelph.ca/ccs
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.uoguelph.ca_ccs&d=DwMFaQ&c=RyOedRvjc7OSsfc0bTI76Q&r=7N3S3VwV170meOMF2t3MxSPtfF4yZYjo-cGnk0FWjNE&m=aE1BH_PfX_QvNfpIqkJgT9XA7ThL-gMIMprmfS1LkO8&s=2KdznV740jNktbyeKcJbYV4T4Yb4pF_G56rNFdAJ3hY&e=> |
> @UofGCCS on Instagram, Twitter and Facebook
>
>
>
>
> On Jan 15, 2020, at 3:33 PM, Pawlowski, Adam <ajp26 at buffalo.edu> wrote:
>
> 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>
> *Sent:* Wednesday, January 15, 2020 3:03 PM
> *To:* Lelio Fulgenzi <lelio at uoguelph.ca>; 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
>
>
>
> 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>
> *Sent:* Wednesday, January 15, 2020 3:00 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
>
>
>
> 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>
> *Sent:* Wednesday, January 15, 2020 2:54 PM
> *To:* Lelio Fulgenzi <lelio at uoguelph.ca>; 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
>
>
>
> 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>
> *Sent:* Wednesday, January 15, 2020 2:42 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
>
>
>
> 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>
> *Sent:* Wednesday, January 15, 2020 10:50 AM
> *To:* Lelio Fulgenzi <lelio at uoguelph.ca>; 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
>
>
>
> 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>
> *Sent:* Wednesday, January 15, 2020 10:33 AM
> *To:* Anthony Holloway <avholloway+cisco-voip at gmail.com>
> *Cc:* Pawlowski, Adam <ajp26 at buffalo.edu>; 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
>
>
>
> 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>
> *Sent:* Wednesday, January 15, 2020 10:28 AM
> *To:* Lelio Fulgenzi <lelio at uoguelph.ca>
> *Cc:* Pawlowski, Adam <ajp26 at buffalo.edu>; 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
>
>
>
> 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> 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 <519-824-4120;56354> | lelio at uoguelph.ca
>
>
>
> www.uoguelph.ca/ccs
> <https://urldefense.proofpoint.com/v2/url?u=http-3A__www.uoguelph.ca_ccs&d=DwMFaQ&c=RyOedRvjc7OSsfc0bTI76Q&r=7N3S3VwV170meOMF2t3MxSPtfF4yZYjo-cGnk0FWjNE&m=aE1BH_PfX_QvNfpIqkJgT9XA7ThL-gMIMprmfS1LkO8&s=2KdznV740jNktbyeKcJbYV4T4Yb4pF_G56rNFdAJ3hY&e=> |
> @UofGCCS on Instagram, Twitter and Facebook
>
>
>
>
>
>
> On Jan 14, 2020, at 8:35 AM, Pawlowski, Adam <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> *On Behalf Of *Lelio
> Fulgenzi
> *Sent:* Monday, January 13, 2020 1:13 PM
> *To:* voyp list, cisco-voip (cisco-voip at puck.nether.net) <
> 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
> https://puck.nether.net/mailman/listinfo/cisco-voip
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_cisco-2Dvoip&d=DwMFaQ&c=RyOedRvjc7OSsfc0bTI76Q&r=7N3S3VwV170meOMF2t3MxSPtfF4yZYjo-cGnk0FWjNE&m=aE1BH_PfX_QvNfpIqkJgT9XA7ThL-gMIMprmfS1LkO8&s=KaWVkASPfjl2QnEdBe4e4cbfc4-_Xb7HgOSbP0z0FSk&e=>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
> <https://urldefense.proofpoint.com/v2/url?u=https-3A__puck.nether.net_mailman_listinfo_cisco-2Dvoip&d=DwMFaQ&c=RyOedRvjc7OSsfc0bTI76Q&r=7N3S3VwV170meOMF2t3MxSPtfF4yZYjo-cGnk0FWjNE&m=aE1BH_PfX_QvNfpIqkJgT9XA7ThL-gMIMprmfS1LkO8&s=KaWVkASPfjl2QnEdBe4e4cbfc4-_Xb7HgOSbP0z0FSk&e=>
>
> ------------------------------
> The information contained in this message may be privileged, confidential
> and protected from disclosure. If the reader of this message is not the
> intended recipient, or an employee or agent responsible for delivering this
> message to the intended recipient, you are hereby notified that any
> dissemination, distribution or copying of this communication is strictly
> prohibited. If you have received this communication in error, please notify
> your representative immediately and delete this message from your computer.
> Thank you.
> _______________________________________________
> cisco-voip mailing list
> 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/20200121/f69f0727/attachment.htm>