[cisco-voip] Jabber support for Extension Mobility - Any other Solutions out there

[Matthew Loraditch]

It is not on any roadmap I have seen and I saw a number at Cisco Live. We have the same issue and have to have our CCX employees use IPC when remote.

You can either solely use Jabber as a softphone (and only one jabber device type) and no  hard phone or you have to use IPC with EM and the Deskphone with EM.


Matthew G. Loraditch – CCNP-Voice, CCNA-R&S, CCDA
Network Engineer
Direct Voice: 443.541.1518

Facebook<https://www.facebook.com/heliontech?ref=hl> | Twitter<https://twitter.com/HelionTech> | LinkedIn<https://www.linkedin.com/company/helion-technologies?trk=top_nav_home> | G+<https://plus.google.com/+Heliontechnologies/posts>

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net] On Behalf Of Max Harmony
Sent: Tuesday, August 2, 2016 10:36 AM
To: Cisco VOIP <cisco-voip at puck.nether.net>
Subject: [cisco-voip] Jabber support for Extension Mobility - Any other Solutions out there

Hi All,

I have  remote UCCX agents that are using Jabber when they are remote, meanwhile in the office, they have shared 8945 IP Phones

Jabber is associated to UCCX End user

We would like to setup Extension Mobility so users can login when they are in the office, and at home login to Jabber

Problem:
1- Jabber does not support Extension Mobility
2- Cisco does not support multiple devices/not shared lines

Customer does not want to use IP communicator, so we are stuck with Jabber

Has anyone got feed back from the Cisco BU about this requirement, if Jabber is going to be the future does anyone know of a work around?


Appreciate your feedback

*******************************************



--
--
Grace Maximuangu

CloudPOP/InvictaCloud
www.cloudpop.com<http://www.cloudpop.com/>

 “Go beyond your limits, push yourself, be the best you can be.
Experience new cultures, broaden your horizons, stay connected.”


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20160802/40c34cde/attachment.html>