[cisco-voip] Remote UCCX users
Matthew Loraditch
MLoraditch at heliontechnologies.com
Tue Aug 25 17:35:30 EDT 2020
Until SU1 for 12.5 comes out, a UCCX extension is only allowed on one device.
You would need their extensions to only be on their Jabber CSFs and them run Jabber on their home devices and not have them on their desk phones. You can also technically use IP Communicator with Extension Mobility but it’s no longer supported and hasn’t been updated in a while so depending on your risk tolerance that may or may not be an option. We are still using IPC for remote workers.
Once 12.5 SU1 comes out you can FINALLY have a uccx extension on as many devices as you want.
Matthew Loraditch
Sr. Network Engineer
p: 443.541.1518
w: www.heliontechnologies.com | e: MLoraditch at heliontechnologies.com
From: cisco-voip <cisco-voip-bounces at puck.nether.net> On Behalf Of James Dust
Sent: Tuesday, August 25, 2020 5:29 PM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] Remote UCCX users
[EXTERNAL]
I have a number of users working remotely who are part of a queue on UCCX,
They are using jabber on their windows desktop (csf profile on cucm) and are connecting into our network via our VPN.
The users would normally just take calls on their desk phones in our office, but are working remotely due to COVID.
Thing is they are only able to receive calls when logged into their desk phone’s in the office (even though they are fielding the calls via jabber whilst working remotely)
Is there any way around this dependancy?
Consider the environment - Think before you print
The contents of this email are confidential to the intended recipient and may not be disclosed. Although it is believed that this email and any attachments are virus free, it is the responsibility of the recipient to confirm this.
You are advised that urgent, time-sensitive communications should not be sent by email. We hereby give you notice that a delivery receipt does not constitute acknowledgement or receipt by the intended recipient(s).
Details of Charles Stanley group companies and their regulators (where applicable), can be found at this URL http://www.charles-stanley.co.uk/contact-us/disclosure/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200825/c8027784/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image775273.png
Type: image/png
Size: 9409 bytes
Desc: image775273.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200825/c8027784/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image359821.png
Type: image/png
Size: 431 bytes
Desc: image359821.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200825/c8027784/attachment-0001.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image270949.png
Type: image/png
Size: 561 bytes
Desc: image270949.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200825/c8027784/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image112461.png
Type: image/png
Size: 444 bytes
Desc: image112461.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20200825/c8027784/attachment-0003.png>
More information about the cisco-voip
mailing list