Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

CTI Yealink T38

Discussion in '3CX Phone System - General' started by nplummer, Oct 16, 2014.

Thread Status:
Not open for further replies.
  1. nplummer

    Joined:
    May 14, 2010
    Messages:
    22
    Likes Received:
    0
    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?

    We are wondering if there are any other settings that we should change in the 3CX system to enable the CTI to work. We have other installations using different Yealink phones and the CTI is working properly.

    We do have the 3CX Phone For Windows set to use CTI. The computers running the 3CX Phone For Windows are running Windows 7 and are on the same local network as the phones. Many of the computers are plugged into the one port switch on the back of the phones.

    Thank You,
    Nepal
     
  2. nplummer

    Joined:
    May 14, 2010
    Messages:
    22
    Likes Received:
    0
    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
     
Thread Status:
Not open for further replies.