T38 CTI with 3CX

[nplummer]

We recently upgraded a large install of about 70 T38 phones with 3CX from version 11 to V12. The new 3CX Windows Phone is not activating CTI on the phones. We updated the phones to the most current 3CX supported firmware (38.70.0.221). When we try to use CTI the softphone does nothing and the phone also does nothing. However, if we change the "Trusted Action URI Server List" from "any" to the IP address of the desktop computer the phone will prompt for control, but if we reboot the phone or re-provision the phone it will no longer function and will not prompt for control. We have our provisioning file set for "any" under the "features.action_uri_limit_ip = " setting.

We have a couple of questions about this issue:

1. CTI will not function with “any” defined in the URL field.
2. Is there a timeout for the phone confirmation for control?
3. If the confirmation is missed will it come back?
4. Will the confirmation need to be done every time the phone is rebooted, re-provisioned, or firmware updates?

On a different note, is it possible to turn off the audible stutter tone when a new voicemail message is left?

Thank you in advance for your assistance.

Nepal Plummer
Fahillion Technologies

[Greysi]

Try first:

Web-Login T38 phone

Phone\Upgrade\"Reset to Factory"

[James_Yealink]

Hi Nplummer,

1. CTI will not function with “any” defined in the URL field.
- The any should work, can it work before your upgrading?
2. Is there a timeout for the phone confirmation for control?
-Yes, if you don't choose an option it will disappear after dozens of seconds.
3. If the confirmation is missed will it come back?
-Yes, if you don't choose OK, it will come back when you use CTI next time.
4. Will the confirmation need to be done every time the ph one is rebooted, re-provisioned, or firmware updates?
-You have to do a confirmation again after a reboot and firmware update. You


You can turn off the audible stutter.
Login into phone web interface, go to phone-> Tones, fill value "0" in the stuffer and message filed.

Regards,
James

[nplummer]

UPDATE WITH SOLUTION:

We had modified the standard 3CX provisioning template to include a customized admin password for the phones. This password included a non-alpha character. The older version of 3CX (v11) and the older firmware of the phone were OK with this password, but the newer versions must not like the non-alpha character. Once we changed the setting back to the default provisioning password template and re-provisioned the phone everything worked as it should.

Nepal

[James_Yealink]

nplummer, thanks for your share.

James