IPOSES 11.1.2.4 with J-Series phones using TLS thru an SBC - 46xxspecials 1

[telfire]

On a system with J-Series all using TLS and 3rd Party SSL thru an SBC, is it possible to manipulate a 46xxspecials.txt to tell Workplace to use TCP along with the obvious dialing rules? The customer has to deploy dozens of Workplace TCP with dialing rules on the local LAN and doesn't want to do every one of them manually. Is there another way to deploy a bunch setup as TCP with certain dialing rules?

 

[derfloh]

You can filter for the device type within 46xxspecials.txt

acw - Avaya Communicator for Windows
acm - Avaya Communicator for Mac
aci - Avaya Communicator for iPhone/iPad
aca - Avaya Communicator for Android.

Nevertheless I would use TCP for Workplace as well, so that you can easily use Workplace remotely if needed.

 

[telfire]

@derfloh - Where/How in the 46xxspecials, or even in the 46xxsettings, does it tell specifically for Equinox Settings to use TCP instead of TLS. I do see the IP and FQDN for the TLS on SIPAUTO and STIMULUS, but not specifically for Equinox/Workplace.

 

[derfloh]

Open 46xxspecials.txt. You will see something like
IF $MODEL SEQ ACW GOTO Equinox

Then you will have an Equinox Section starting with ## Equinox

There you can place what you need.

 

[telfire]

I get that part, but what line do I add to the specials that tells the IPO that WORKPLACE only uses TCP whereas everything else uses TLS?

 

[derfloh]

You should have somthing like this in your 46xxsettings.txt

SET SIP_CONTROLLER_LIST 192.168.42.1:5061;transport=tls

In your 46xxspecials.txt within the Workplace section (acm/acw/aci/aca) place this then:

SET SIP_CONTROLLER_LIST 192.168.42.1:5060;transport=tcp

The last entry the endpoint gets (46xxspecials is loaded after 46xxsettings) will be used.