[cisco-voip] UCCx and Jabber - compatible or not?

Fri Oct 18 15:28:24 EDT 2019

Correct. If you have agents who want to  use Jabber and have a hardphone DO NOT put their agent DN on any other device. If you search the DN in CUCM you need to see that DN associated to only a single device

Matthew Loraditch
Sr. Network Engineer
p: 443.541.1518
w: www.heliontechnologies.com | e: MLoraditch at heliontechnologies.com
From: Lelio Fulgenzi <lelio at uoguelph.ca>
Sent: Friday, October 18, 2019 3:26 PM
To: Matthew Loraditch <MLoraditch at heliontechnologies.com>; voyp list, cisco-voip (cisco-voip at puck.nether.net) <cisco-voip at puck.nether.net>
Subject: RE: UCCx and Jabber - compatible or not?

Yes jabber in deskphone control mode is ok. Jabber is not operating as a softphone in that mode and breaks no UCCX “rules”

In this case, do I have to make sure not to program a DN on Jabber?

---
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
519-824-4120 Ext. 56354 | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>

www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

From: Matthew Loraditch <MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>>
Sent: Friday, October 18, 2019 3:24 PM
To: Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>; voyp list, cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>) <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: RE: UCCx and Jabber - compatible or not?

LOL

Yes Historically you were good with the hardphone and CIPC b/c you can use ext. mobility on both to get you extension and from a UCCX perspective said extension was only on one device in CUCM.

Yes jabber in deskphone control mode is ok. Jabber is not operating as a softphone in that mode and breaks no UCCX “rules”

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>
[Helion Technologies]<http://www.heliontechnologies.com/>
[Facebook]<https://facebook.com/heliontech>
[Twitter]<https://twitter.com/heliontech>
[LinkedIn]<https://www.linkedin.com/company/helion-technologies>
From: Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>
Sent: Friday, October 18, 2019 3:17 PM
To: Matthew Loraditch <MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>>; voyp list, cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>) <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: RE: UCCx and Jabber - compatible or not?

Oh yeah – I remember that session. It was great. But not as good as the session where I raised my hand and asked when they were gonna get rid of that final cable from the room kit to the touch 10. 😉

But, I digress.

So, historically, are you saying then, that one could have a hardphone with an agent extension and use CIPC with extension mobility and activate that same agent extension on CIPC and things would work and it was supported?

>From your last statement, “Jabber CTI control is kosher and has no bearing on this issue.” , are you implying I could install Jabber and modify the call settings to use the hard phone and it _would_ work?

---
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
519-824-4120 Ext. 56354 | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>

www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

From: Matthew Loraditch <MLoraditch at heliontechnologies.com<mailto:MLoraditch at heliontechnologies.com>>
Sent: Friday, October 18, 2019 3:07 PM
To: Lelio Fulgenzi <lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>>; voyp list, cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>) <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: RE: UCCx and Jabber - compatible or not?

The problem is workers who have a deskphone and also need to use a softphone occasionally or vice-versa.

An agent extension can only be programmed on one device in all of CUCM.

Previously the above situation could be handled by CIPC as extension mobility is supported.

Jabber does not and will not support extension mobility as a softphone.

UCCX says that supporting an agent extension on multiple devices is extremely difficult to fix

I can’t remember if you were in those sessions at Cisco Live with me or not but it was a fun little it’s not my problem scenario from the two BUs in some of the sessions asking how they were going to fix this.

Jabber CTI control is kosher and has no bearing on this issue.

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>
[Helion Technologies]<http://www.heliontechnologies.com/>
[Facebook]<https://facebook.com/heliontech>
[Twitter]<https://twitter.com/heliontech>
[LinkedIn]<https://www.linkedin.com/company/helion-technologies>
From: cisco-voip <cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>> On Behalf Of Lelio Fulgenzi
Sent: Friday, October 18, 2019 2:55 PM
To: voyp list, cisco-voip (cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>) <cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>>
Subject: [cisco-voip] UCCx and Jabber - compatible or not?

I’ve heard all the rumblings with UCCx and Jabber. But I’m hoping someone can explain to me what exactly the problem is. From what I understand, there is not an actual incompatibility with UCCx and Jabber, just with some deployment methods and some restrictions UCCx places on things.

So, in simplest terms, if you have a desktop agent, with Jabber (4Win) running and only one (agent) extension and no other device has that extension, things work.

I believe it’s when you try to do anything else other than this simple deployment that things go awry. Say, have both Jabber and a hard phone and log into your queue using a phone agent on the hard phone but want to use Jabber to answer. Or you want Jabber to control your hard phone. Etc.

Can I get some ideas as to whether this is true and where people have seen trouble? And what is actually supported?

Lelio

---
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
519-824-4120 Ext. 56354 | lelio at uoguelph.ca<mailto:lelio at uoguelph.ca>

www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook

[University of Guelph Cornerstone with Improve Life tagline]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20191018/7ca428c9/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 1297 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20191018/7ca428c9/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 6884 bytes
Desc: image002.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20191018/7ca428c9/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image003.png
Type: image/png
Size: 431 bytes
Desc: image003.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20191018/7ca428c9/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 561 bytes
Desc: image004.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20191018/7ca428c9/attachment-0003.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.png
Type: image/png
Size: 444 bytes
Desc: image005.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20191018/7ca428c9/attachment-0004.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image574680.png
Type: image/png
Size: 9409 bytes
Desc: image574680.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20191018/7ca428c9/attachment-0005.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image230121.png
Type: image/png
Size: 431 bytes
Desc: image230121.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20191018/7ca428c9/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image901354.png
Type: image/png
Size: 561 bytes
Desc: image901354.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20191018/7ca428c9/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image540439.png
Type: image/png
Size: 444 bytes
Desc: image540439.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20191018/7ca428c9/attachment-0008.png>