Thanks! I believe the actual number of “Jabber only” telephony users will be quite small.
What we will likely see are those requests that ask to remove the hardware phone they have in lieu of Jabber. In that case, we’d add Jabber before removing the phone. If the frequency of Jabber only requests increase, I may consider option C. But B still looks good. Sent from my iPhone > On Jul 1, 2020, at 2:57 PM, Pawlowski, Adam <aj...@buffalo.edu> 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 > ith...@uoguelph.ca > > > B would be the way to go yes if you mean provision people for Jabber service > for telephony but they do not have a hardware phone. If they don't need phone > service at all and just IM then there are other ways. > > C is what we do here. I have line templates for > campus/local/national/international for each of our gateway locations, and a > couple for internal contact centers or similar that we grind through enough > that it is worth putting them in here. Anything more complicated does not > follow our SOP and gets pushed to someone with more hours on the system to > work through. This is combined with User Profile, which by default it setup > for a 1 line 5 button 8800 series device and is rarely changed. I built those > for 1 and 2 line 8800 and 7900 series (largely just common phone profile and > button template between them) which can be used when building something new > or when moving devices. In practice it doesn't usually get used as most > devices are either bog standard 1 line, or some mess of buttons and need > intervention. > > Adam > > > > > >> -----Original Message----- >> From: cisco-voip <cisco-voip-boun...@puck.nether.net> On Behalf Of Lelio >> Fulgenzi >> Sent: Wednesday, July 1, 2020 2:06 PM >> To: cisco-voip voyp list <cisco-voip@puck.nether.net> >> Subject: [cisco-voip] Creating Jabber for non-existent phones >> >> >> 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@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
