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

[Anthony Holloway]

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> 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
> 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/b3f03118/attachment.htm>