[cisco-voip] Creating Jabber for non-existent phones

[Lelio Fulgenzi]

Yeah. More like 15-20 years worth of custom solutions, orphaned phones, unlinked phones and voicemail, different device CSS, various line CSS for long distance restrictions, and so on and so on.

I’d honestly have to end up making two dozen templates and then worry about the myriad of exceptions.

It would be horrible.

Sent from my iPhone

On Jul 1, 2020, at 6:09 PM, Anthony Holloway <avholloway+cisco-voip at gmail.com> wrote:



CAUTION: This email originated from outside of the University of Guelph. Do not click links or open attachments unless you recognize the sender and know the content is safe. If in doubt, forward suspicious emails to IThelp at uoguelph.ca


Yeah, I have done a bulk assignment on 2,000 users once, and it was a data collection/juggling nightmare for me.  BATing in CSF is a cakewalk if you start with good data.  However, getting that good data on a brownfield that's 10 years old with a lot garbage in it is painful to say the least.

On Wed, Jul 1, 2020 at 3:38 PM Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:

We may consider adding Jabber for any new phone requested. Not sure. There are disadvantages to adding a feature that someone hasn’t asked for.

As far as bulk load assignment, it would require significant reconciling and fixing of existing configurations. Not all our devices are associated with a user. Not all voicemails are. Not all phones match directory entries. Not all phones are unique 1:1 primary extensions.


Sent from my iPhone

On Jul 1, 2020, at 4:11 PM, Matthew Loraditch <MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>> wrote:



CAUTION: This email originated from outside of the University of Guelph. Do not click links or open attachments unless you recognize the sender and know the content is safe. If in doubt, forward suspicious emails to IThelp at uoguelph.ca<mailto:IThelp at uoguelph.ca>

I would add, why not just bulk add jabber for everyone who is licensed for it and then include in your normal onboarding? Does someone care if it’s configured and not used?


Matthew Loraditch​
Sr. Network Engineer
p: 443.541.1518<tel:443.541.1518>
w: www.heliontechnologies.com<http://www.heliontechnologies.com/>        |      e: MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>
<http://www.heliontechnologies.com/>
<image370352.png>
<https://facebook.com/heliontech>
<image284035.png>
<https://twitter.com/heliontech>
<image020357.png>
<https://www.linkedin.com/company/helion-technologies>
<image574419.png>
From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> On Behalf Of Anthony Holloway
Sent: Wednesday, July 1, 2020 4:00 PM
To: Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>
Cc: cisco-voip voyp list <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: Re: [cisco-voip] Creating Jabber for non-existent phones

[EXTERNAL]

Forgive my ignorance here, since I do not do day 2 ops work often (thus quick add's set backs are not top of mind), I mostly focus on new deployments, which typically involve BAT, so what is the trouble/uniqueness in Jabber CSF devices versus a physical phone?  Also, how come Option A doesn't mention the Jabber piece?  Is that implied that you would come back around and add Jabber afterwards, like you would do in option B, post DN add?

On Wed, Jul 1, 2020 at 1:07 PM Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>> wrote:

Hello all. Looking for feedback and opinions and caveats.

Right now, we’re deploying Jabber only to those with phones/DNs. But, we need to start deploying Jabber for those individuals without phones/DNs.

Our SOPs include using Quick Add feature. (Thanks a million time Brian Meade for the pointer).

My choices so far, to address Jabber for new those without phones:

(a) Create a fake hardware phone first. This has many benefits, namely, all SOPs remain the same. Hardware phone would be deleted afterwards.

(b) Use Directory Number admin page to create/update a DN first, then use Quick Add page to assign DN to user accordingly and then click manage devices and follow remaining SOP steps.

(c) create line templates and use those when creating new extensions under quick add. The issue with this is we have so many combinations, I’d need a lot of templates.

I’m leaning towards (b), since it gives me the best of both worlds.

Thoughts?

Lelio

Sent from my iPhone
_______________________________________________
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/20200701/c6a481fa/attachment.htm>