[cisco-voip] Jabber Multiline is Here

Mon Apr 2 14:55:28 EDT 2018

Yea, this is the issue.  Almost all of my customers want agents to be able
to work from home if possible so forces us to go full Jabber for agents or
split desk phone and CIPC with extension mobility.  Desk phone and CIPC
seems to be the popular choice.

On Mon, Apr 2, 2018 at 2:51 PM, Ben Amick <bamick at humanarc.com> wrote:

> Gotcha, so the issue only exists because of partial teleworking. Outside
> of supervisors in my environment everyone is either 100% telework or 100%
> in office so it’s never been a problem for us, and everyone just uses CIPC
> anyways outside of a few legacy desk phone deploys.
>
>
>
> Ben Amick
>
> Unified Communications Analyst
>
>
>
> *From:* Matthew Loraditch <MLoraditch at heliontechnologies.com>
> *Sent:* Monday, April 2, 2018 2:48 PM
> *To:* Ben Amick <bamick at HumanArc.com>; Brian Meade <bmeade90 at vt.edu>;
> Lelio Fulgenzi <lelio at uoguelph.ca>
> *Cc:* Cisco VoIP Group <cisco-voip at puck.nether.net>
> *Subject:* RE: [cisco-voip] Jabber Multiline is Here
>
>
>
> *Security Notice:* This is an EXTERNAL email. Please exercise caution and
> DO NOT open attachments or click links from unknown or unexpected senders.
>
> I’m going to presume my answer is the same as Brian’s but our Call Center
> staff all have hard phones at the office, but when they work from home they
> need to use a softphone. Since UCCX requires agent extensions only exist on
> one device, they have to use EM and Jabber doesn’t support EM so we have to
> provision them with CIPC for at home usage.
>
>
>
>
>
>
>
>
>
> *Matthew Loraditch***
>
> *Sr. Network Engineer*
>
> p: *443.541.1518* <443.541.1518>
>
> w: *www.heliontechnologies.com* <http://www.heliontechnologies.com/>
>
>  |
>
> e: *MLoraditch at heliontechnologies.com* <MLoraditch at heliontechnologies.com>
>
> [image: Facebook] <https://facebook.com/heliontech>
>
> [image: Twitter] <https://twitter.com/heliontech>
>
> [image: LinkedIn] <https://www.linkedin.com/company/helion-technologies>
>
> *From:* cisco-voip <cisco-voip-bounces at puck.nether.net> *On Behalf Of *Ben
> Amick
> *Sent:* Monday, April 2, 2018 2:41 PM
> *To:* Brian Meade <bmeade90 at vt.edu>; Lelio Fulgenzi <lelio at uoguelph.ca>
> *Cc:* Cisco VoIP Group <cisco-voip at puck.nether.net>
> *Subject:* Re: [cisco-voip] Jabber Multiline is Here
>
>
>
> Brian,
>
> If you move to multiline on Jabber and decommission softphones/deskphones
> as a byproduct, what issue does that generate with UCCX?
>
>
>
> Being that Jabber tethers to your own controlled device without a specific
> CSF specified, what use case would extension mobility fulfill that jabber
> itself wouldn’t?
>
>
>
> Ben Amick
>
> Unified Communications Analyst
>
>
>
> *From:* cisco-voip <cisco-voip-bounces at puck.nether.net> *On Behalf Of *Brian
> Meade
> *Sent:* Monday, April 2, 2018 2:05 PM
> *To:* Lelio Fulgenzi <lelio at uoguelph.ca>
> *Cc:* Cisco VoIP Group <cisco-voip at puck.nether.net>
> *Subject:* Re: [cisco-voip] Jabber Multiline is Here
>
>
>
> *Security Notice:* This is an EXTERNAL email. Please exercise caution and
> DO NOT open attachments or click links from unknown or unexpected senders.
>
> Big holdup looks to be no multiline with MRA, still only single line
> there.
>
>
>
> The other big issue is no extension mobility support and UCCX is still
> enforcing their single device policy.  I've been having some discussions
> with the Jabber/UCCX teams around this.  Right now CIPC is EOL but I'm
> still having to do active deployments of it due to this issue as I'm sure
> many others are hitting.
>
>
>
> On Mon, Apr 2, 2018 at 1:43 PM, Lelio Fulgenzi <lelio at uoguelph.ca> wrote:
>
> Let’s hope voicemail works with multi lines. 😉
>
>
>
> ---
>
> *Lelio Fulgenzi, B.A.* | Senior Analyst
>
> Computing and Communications Services | University of Guelph
>
> Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON |
> N1G 2W1
> <https://maps.google.com/?q=50+Stone+Rd+E+%7C+Guelph,+ON+%7C+N1G+2W1&entry=gmail&source=g>
>
> 519-824-4120 Ext. 56354 <(519)%20824-4120> | lelio at uoguelph.ca
>
>
>
> www.uoguelph.ca/ccs | @UofGCCS on Instagram, Twitter and Facebook
>
>
>
> [image: University of Guelph Cornerstone with Improve Life tagline]
>
>
>
> *From:* cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] *On Behalf
> Of *Anthony Holloway
> *Sent:* Monday, April 2, 2018 10:44 AM
> *To:* Cisco VoIP Group <cisco-voip at puck.nether.net>
> *Subject:* [cisco-voip] Jabber Multiline is Here
>
>
>
> Just in case you missed it, Jabber multiline made it into 12.0.  You'll
> need to be on CUCM 11.5(1)SU4 and install a COP file to support it.
>
>
>
> Release Notes
>
> https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/
> Windows/12_0/RN/jabw_b_release-notes-for-cisco-jabber_12.html#reference_
> 6CABFFC6E6E2B025EA1C691A8744962A
>
>
>
> Configuration Guide
>
> https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/
> 12_0/cjab_b_feature-configuration-for-cisco-jabber-120/cjab_b_feature-
> configuration-for-cisco-jabber-120_chapter_011.html#reference_
> 08DB2E9280C0A8ABF98E1B329604E883
>
>
>
> Video Demo
>
> https://youtu.be/Cosfzf7XoBo
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
>
> *Disclaimer:* The information contained in this transmission and any
> attachments may contain privileged and confidential information including
> patient information protected by federal and state privacy laws. This
> transmission is sent for the sole use of the intended recipient. If you are
> not the intended recipient, please immediately (1) notify the sender via
> reply email; (2) do not open or read the message or any attachments; and
> (3) delete this message and any attachments. The review, dissemination,
> distribution, or duplication of this transmission by anyone other than the
> intended recipient is strictly prohibited.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/efebb5d5/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 431 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/efebb5d5/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 561 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/efebb5d5/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.png
Type: image/png
Size: 1297 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/efebb5d5/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 8404 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/efebb5d5/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 444 bytes
Desc: not available
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180402/efebb5d5/attachment-0004.png>