Author Topic: Is this WDE/SIP EndPoint valid/supported?  (Read 97 times)

Offline PFCCWA

  • Hero Member
  • *****
  • Posts: 634
  • Karma: -7
Is this WDE/SIP EndPoint valid/supported?
« on: September 21, 2022, 10:04:38 PM »
I am working on a WDE/SIP endpoint deployment and wondered if this was a supported solution as below.

- WDE and sip endpoint in same workstation (but sip endpoint installed as a standalone application).
- WDE communicates with SIP Endpoint via https (securely) using default port /tls via certificate negotiation.

we have virtualised and non virtualised users in our platform and i wondered if we can just use the same application object for both. The virtualised users connect to the standalone sip endpoint (via https port 8000) so thought a locally installed WDE would just connect the same way as it uses the same application object and use the same certs/tls as the virtualised users.

i know we can install sip endpoint as a plugin (when WDE is already installed) but was trying to figure if both can co-exist- and if so what i need to take into account to make it work.


Offline hsujdik

  • Hero Member
  • *****
  • Posts: 501
  • Karma: 23
Re: Is this WDE/SIP EndPoint valid/supported?
« Reply #1 on: September 22, 2022, 06:32:15 AM »
You could have another "role" that has "Workspace Desktop Edition" permission "Can Use SIP Endpoint". Associate a new Access Group to that Role (eg. SIPPluginAccessGroup) and associate users that should use SIP Plugin to that access group

Then, when those users log into WDE, it will launch WDE SIP Endpoint plugin. The other users open the Standalone SIP Endpoint before opening WDE (since without that role, the WDE SIP Endpoint wouldn't be launched).

I believe it should work