[cisco-voip] Bulk Admin and Jabber

[Anthony Holloway]

What programming language did you write it in, and is the interface GUI or
CLI based?

On Mon, Sep 16, 2019 at 1:04 PM Pawlowski, Adam <ajp26 at buffalo.edu> wrote:

> Catching up on this one since this list stopped sending me daily digests
> but more like whenever it feels like it digests
>
>
>
> We use the Quick User/Phone Add here and I put that into the procedures
> for the technicians since it can enforce some level of consistency. It’s
> not perfect by any means but for Jabber at least there is usually not too
> much farting around that needs to be done after the client is setup.
>
>
>
> Two sore points for me on it are:
>
>
>
> 1)      It does not fill in the ASCII Display Name field when it adds
> line appearances. I have no idea why, but CTI applications like CER still
> use this so I have to go open each one and click on it to avoid dispatch
> getting calls from “_”.
>
> 2)      Product specific fields are still not available here. On desk
> sets that’s the wireless hookswitch control. On Jabber, that’s the Cisco
> Support Field. Unless something has changed recently, the BOT/TAB/TCT
> devices’ flavor of Cisco Support Field is NOT the same one as in the common
> phone profile.
>
> I haven’t experimented to see if this works now, but it did not when we
> set all this up for Jabber. Our base jabber-config turns off everything but
> IM so anyone can just pop  open the client, then we change profile on the
> client to turn on the features or for hunt/pickup etc. I still have to
> touch this by hand for BOT, TAB, and TCT.
>
>
>
> It is “quick” and it works for 98% of new additions, it’s useless for
> moving resources between people as it re-provisions everything, and when
> you’re building procedures for people so they can avoid hand made changes,
> it doesn’t quite get us there.
>
>
>
> That being said I wrote a script to use AXL to bulk insert clients. I read
> a CSV with a userID, the client type, and the profile. I verify the user ID
> is in the system, insert the device, and then stack it on the association
> list. It really wasn’t that hard and comes a … well a bulk import tool I
> can hand off to the team. You can write product-specific configurations
> back with AXL, you just want to look at an example of how it is mashed
> together, and make sure you don’t break it. IIRC it’s a block of XML that
> comes out of the database, and I think this is one of those fields that
> when you set it back through AXL it gets written back exactly as you send
> it, so it is easy to clear settings.
>
>
>
> Best of luck
>
>
>
> Adam Pawlowski
>
> SUNYAB
> _______________________________________________
> 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/20190916/eef82ce9/attachment.htm>