Ok. Hold on. Are you sure? I did mean userID. As a Cisco requirement. Not 
company standard.

I’m almost 100% positive I read in the deployment guide it needs to be the 
userID. And it was the Jabber deployment guide. Which, of course, I didn’t 
save. 😉

When asking about it, I was told, it was really the only way you could get a 
Jabber device to associate with a user after logon. How else would you?

I mean, there’s nothing else I think I’d really want to use, but, honestly, I 
believe(d) it’s a requirement.

Lelio


---
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]

From: Anthony Holloway <avholloway+cisco-v...@gmail.com>
Sent: Friday, September 13, 2019 12:40 PM
To: Lelio Fulgenzi <le...@uoguelph.ca>
Cc: Brian Meade <bmead...@vt.edu>; cisco-voip voyp list 
<cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] Bulk Admin and Jabber

"... when we know the device name for the softphones needs to be the userID"

Just to be clear, it does not.  That was an old CUPC requirement, and the new 
requirements are as follows:

CSF = could be whatever you want, e.g., banana (unless you have QM call 
recording, then it needs to be all caps CSFSOMETHING for QM)
TCT = must be all caps TCTSOMETHING
BOT =  must be all caps BOTSOMETHING
TAB = must be all caps TABSOMETHING

None of them however, need the User ID in the name.  Could be TCTBANANA for 
example.

Maybe that's not what you meant.  Maybe you meant, for your company's standard 
build, but I thought I'd address that, since other people might have read that 
it needed to be that way.

On Fri, Sep 13, 2019 at 10:25 AM Lelio Fulgenzi 
<le...@uoguelph.ca<mailto:le...@uoguelph.ca>> wrote:
This looks like an interesting option. I’ll have to see how much effort it 
takes to get the templates set up in order for us to use this.

I didn’t like the fact that it’s asking me to fill in the device name, when we 
know the device name for the softphones needs to be the userID. So this is a 
step that could lead to errors and extra effort.

I know this sounds like _I_ don’t want to do this stuff, but when you’re 
preparing instructions for a group of people with varying skill sets, the less 
work required the better.

At least we have some options.



---
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]

From: Brian Meade <bmead...@vt.edu<mailto:bmead...@vt.edu>>
Sent: Friday, September 13, 2019 11:02 AM
To: Lelio Fulgenzi <le...@uoguelph.ca<mailto:le...@uoguelph.ca>>
Cc: Anthony Holloway 
<avholloway+cisco-v...@gmail.com<mailto:avholloway%2bcisco-v...@gmail.com>>; 
cisco-voip voyp list 
<cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>>
Subject: Re: [cisco-voip] Bulk Admin and Jabber

Have you tried using the Quick/User Phone Add?  That works pretty well.  Just 
assign device/line templates to user profiles and adding a 
CSF/TCT/RDP/Deskphone/TAB/BOT device for a user takes all of a minute at most.

On Fri, Sep 13, 2019 at 10:42 AM Lelio Fulgenzi 
<le...@uoguelph.ca<mailto:le...@uoguelph.ca>> wrote:
I guess it’s a combo of built-in tools and tools people are familiar with.

I like the idea, but again, adding extra steps like that might not work. Now, 
that being said, I wonder if I can modify the order in which the columns are 
presented to the import tool? If they allow headers, that should be ok, right?

I might be stuck with looking for green columns for the first round. ☹

---
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]

From: Anthony Holloway 
<avholloway+cisco-v...@gmail.com<mailto:avholloway%2bcisco-v...@gmail.com>>
Sent: Friday, September 13, 2019 10:31 AM
To: Lelio Fulgenzi <le...@uoguelph.ca<mailto:le...@uoguelph.ca>>
Cc: cisco-voip voyp list 
<cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>>
Subject: Re: [cisco-voip] Bulk Admin and Jabber

"...I need to use the built-in tools..."

So, Excel + BAT is built-in, and Python + AXL is not?

I kid, I kid.  I get that there's a common familiarity with Excel and not one 
with Python.

I have a recommendation when working with BAT import files in Excel.  Insert a 
few input columns to the left of the actual data, and then drive your entire 
spreadsheet with formulas.  This will save you from having to constantly scroll 
left and right look for cells you need to fill in.  You will have to exclude 
them when you export/save as csv.  However, keeping the input columns together 
on the left should make this very easy.  You can duplicate the sheet and delete 
them, you can have two different files: XLSX and CSV, you can copy and paste 
into Notepad++ and CTRL+H replace tabs (\t) with commas (,).  There's a few 
options there.  Anyway, I find it much nicer to input the data this way.  I 
hope it helps you too.

Do this:

[image.png]

Not this:

[image.png]



On Thu, Sep 12, 2019 at 7:24 PM Lelio Fulgenzi 
<le...@uoguelph.ca<mailto:le...@uoguelph.ca>> wrote:

We really need to start to minimize the amount of custom scripts / programming 
that we use, not increase it.

It’s a bit of a long story.

So I need to use the built-in tools.

:(

We might just stick with super copy if bulk admin doesn’t work out.

Lelio
-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> | 
le...@uoguelph.ca<mailto:le...@uoguelph.ca>

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


On Sep 12, 2019, at 7:48 PM, Anthony Holloway 
<avholloway+cisco-v...@gmail.com<mailto:avholloway+cisco-v...@gmail.com>> wrote:
Why not roll your own build tool in Python?  You can ask questions here, as 
lots of us have Python and AXL experience, and then more people get to benefit 
from the collaboration.

Just think how cool it would be to build your very own Jarvis:

<image.png>

On Thu, Sep 12, 2019 at 5:22 PM Lelio Fulgenzi 
<le...@uoguelph.ca<mailto:le...@uoguelph.ca>> wrote:

It’s been a while since I’ve used Bulk Admin Tool.

Wondering how it might help with our Jabber deployment.

I’m thinking, since our requests will come in one at a time, the best approach 
would be to create a BAT file that has a line for each device type. We’ve 
decided to load all types so users can switch devices out/in as they wish.

Can you bulk load _without_ using a template?

What have others done with respect to Jabber bulk loads?

Lelio
-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> | 
le...@uoguelph.ca<mailto:le...@uoguelph.ca>

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

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

Reply via email to