<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
<div><br>
</div>
<div>Sorry. With (a) we would use existing SOPs to add Jabber after the dummy hardware phone was added. </div>
<div><br>
</div>
<div>The quick add assumes a DN has been assigned to the user and in the user screens a primary extension has been selected. Our SOP takes care of this. </div>
<div><br>
</div>
<div>My Hope is to use As much of the existing sop as possible. </div>
<div><br>
</div>
<div>But, as you suggest, I could have option (d) create a CSF for the user and follow the SOP using quick add for the remaining three Jabber devices. </div>
<div><br>
</div>
<div>Disadvantage would be the manual creation of the CSF and configuring of many parameters. I could do a super copy. </div>
<div><br>
</div>
<div>But an option nonetheless. </div>
<div><br>
</div>
<div><br>
</div>
<br>
<div dir="ltr">Sent from my iPhone</div>
<div dir="ltr"><br>
<blockquote type="cite">On Jul 1, 2020, at 3:59 PM, Anthony Holloway <avholloway+cisco-voip@gmail.com> wrote:<br>
<br>
</blockquote>
</div>
<blockquote type="cite">
<div dir="ltr">
<p></p>
<div style="background-color:#FFEB9C; width:100%; border-style: solid; border-color:#9C6500; border-width:1pt; padding:2pt; font-size:10pt; line-height:12pt; font-family:'Calibri'; color:Black; text-align: left;">
<span style="font-weight:bold;">CAUTION:</span> 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@uoguelph.ca</div>
<br>
<p></p>
<div dir="ltr">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?</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Wed, Jul 1, 2020 at 1:07 PM Lelio Fulgenzi <<a href="mailto:lelio@uoguelph.ca">lelio@uoguelph.ca</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Hello all. Looking for feedback and opinions and caveats. <br>
<br>
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.
<br>
<br>
Our SOPs include using Quick Add feature. (Thanks a million time Brian Meade for the pointer).
<br>
<br>
My choices so far, to address Jabber for new those without phones:<br>
<br>
(a) Create a fake hardware phone first. This has many benefits, namely, all SOPs remain the same. Hardware phone would be deleted afterwards.
<br>
<br>
(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.
<br>
<br>
(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.
<br>
<br>
I’m leaning towards (b), since it gives me the best of both worlds. <br>
<br>
Thoughts? <br>
<br>
Lelio<br>
<br>
Sent from my iPhone<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="https://puck.nether.net/mailman/listinfo/cisco-voip" rel="noreferrer" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><br>
</blockquote>
</div>
</div>
</blockquote>
</body>
</html>