- Joined
- Oct 16, 2013
- Messages
- 21
- Reaction score
- 0
We have two buttons programmed on our Yealink T38 operator station to easily set the phone to away or available. We have been using this setup for several years up to 3cx version 12. We have recently upgraded to v15.5 and the same configuration using the same XML files are really slow to execute. In V12, the button press to completion was about 2 seconds. With V15.5, it can take almost 10 seconds. Doesn't sound like much, but we frequently get incoming calls that will interrupt the execution which defeats the purpose of having the ability to quickly set the status to away. Here is the setup.
Key Type Value
DSS9 XML Browser https://<3cx-IP>:5001/provisioning/xxxxxxxxxxx/away.xml
away.xml file
<?xml version="1.0" encoding="UTF-8"?>
<YealinkIPPhoneExecute Beep="yes">
<ExecuteItem URI="Led:MEMO10_GREEN=off"/>
<ExecuteItem URI="Led:MEMO9_GREEN=on"/>
<ExecuteItem URI="Dial:*31" interrupetCall="no"/>
</YealinkIPPhoneExecute>
Key Type Value
DSS9 XML Browser https://<3cx-IP>:5001/provisioning/xxxxxxxxxxx/away.xml
away.xml file
<?xml version="1.0" encoding="UTF-8"?>
<YealinkIPPhoneExecute Beep="yes">
<ExecuteItem URI="Led:MEMO10_GREEN=off"/>
<ExecuteItem URI="Led:MEMO9_GREEN=on"/>
<ExecuteItem URI="Dial:*31" interrupetCall="no"/>
</YealinkIPPhoneExecute>