One-X Comm - SIP Shared Control

[underwoj]

Hi - It's me again

So - I have my One-X Communicator on my laptop configured/registered to our SBCE via TLS 5061 (I believe Shared Control requires a TLS connection). When I hop on my Citrix client (which is on our internal network) and try and connect to the Session Manager (via TLS 5061) - I get 'Login Error - The telephone you are trying to share control of is currently OOS or does not support this feature'.

What am I doing wrong.

If I try and login to the Citrix One-X using 'My Computer' - it does register to the ASM. Is there an issue doing a shared control if one client is connected to my SBC and other is connect to ASM (on-network)?

thanks!

 

[underwoj]

Just an FYI - this all works if both clients (One-X in Citrix and One-X on laptop) are both connected via SIP/Session Manager...just not if one is connected to our SBC and other is connected via ASM.

 

[kyle555]

I came across a support article that says its unsupported

 

[gwebster]

“Shared control” (i.e. Deskphone Mode) allows SIP One-X C to control a SIP 96xx/J100. Not control another instance of One-X C.

 

[underwoj]

say it ain't so! - but it's in their deployment guide for VDI Agent (Agent for Desktop). ugh

 

[underwoj]

oh...so maybe this will work with Agent for Desktop?? ...just not One-X Comm.

 

[kyle555]

I'd say ask your BP or ATAC. Nothing explicitly mentions it being supported. All I saw was a support article saying on one-x that it was definitely not supported.

If something's been done to change it, I'd expect it to be in Equinox.

If the PC and the phone are shared control, then why would one need to go thru an SBC? I suppose a fair answer for that is "my thinclients phone home to some mothership that isn't on the same network my PBX or IP phones are on"

Regardless, you wouldn't want to pay for anything agent related if your use case is UC since you were starting with one-x communicator in the first place.

I think it'd be cool if the SBC were smart enough to take only 1 advanced session license per hard+soft phone provided the softphone were in shared control. And maybe that's the right answer. If you can afford to run the thinclients on the desks through the SBC, why not the phones too? The solution I saw just mentioned that 1XC shared control required both endpoints register to the same place - they didn't say they both had to be remote workers or both on SM. I believe an 'advanced' SBC session lets you do any combination of things. I can't tell if that means it would be 1 license for a shared control softphone + hardphone, that would be nice if it were the case.

I did see this in the R8 Overview doc:

Shared Control port
In Remote Worker deployments where endpoints are configured in the shared control mode,
enable shared control port on the internal interface of Avaya SBCE towards Avaya Aura®
 network.
This port could be any unused TLS port on the internal interface of Avaya SBCE, for example, port
5063 . This port must be enabled on the internal firewall between Avaya SBCE and the Avaya
Aura®  network