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

[Anthony Holloway]

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 | @UofGCCS on Instagram, Twitter and Facebook
>
>
>
> [image: University of Guelph Cornerstone with Improve Life tagline]
>
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200115/c708c14a/attachment.htm>