This file is often located in a roaming profile and the ip of the executing terminalserver isn't fix , if there are multiple servers. in the moment we use a workaround - a batch who is looking for the server ip - then replace xxx.xxx.xxx.xxx in the file with the real ip and launch the the assistant. but that is quick and dirty , because he user user is able to initiate more then one session and new trouble
.The IP dependent entries are listet below.
"3CX Assistant CRM Integration.ini"
[Microsoft Outlook Plug-in]
ChannelUri=tcp://xxx.xxx.xxx.xxx:2200
[Microsoft Outlook Add-in]
ChannelUri=tcp://xxx.xxx.xxx.xxx:4824
[3CX Assistant CRM Integration]
ChannelUri=tcp://xxx.xxx.xxx.xxx:2201
... but it's cool to use the TSable Assistant
