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 Dialing on Yealink Phone - CID Formatting

Discussion in 'Windows' started by pcepbx, Apr 7, 2016.

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

    Joined:
    Apr 7, 2016
    Messages:
    20
    Likes Received:
    2
    Hello all--

    On our V14 SP3 PBX install, I've got 3cxPhone set to CTI control our Yealink T48s. On the server side, we've got an outbound rule for our Flowroute SIP trunk that prepends a "tech prefix"--a series of digits followed by an asterisk. This is used by Flowroute for IP based authentication.

    The challenge:
    After CTI dialing a phone number and pressing Call, the number on the 3cxPhone show the "prepended" phone number. This is a bit confusing for the user, but the real challenge is that the outbound call history on 3cxPhone shows this long string. Try to double click on this, and the call will fail since it's calling an invalid number. See attached for screencap of 3cxPhone call history (numbers obfuscated for security.)

    Is there a way to have the 3cxPhone show only the number dialed and not show the prepend?
     

    Attached Files:

  2. pcepbx

    Joined:
    Apr 7, 2016
    Messages:
    20
    Likes Received:
    2
    For what it's worth, this appears to only occur when dialing phone numbers that are not found in the 3cx contacts/directory. When the dialed number is found in the directory, it correctly lists the Name and phone number.
     
  3. NickD_3CX

    NickD_3CX Support Team
    Staff Member 3CX Support

    Joined:
    Jun 2, 2014
    Messages:
    1,380
    Likes Received:
    84
    Just thought I'd update this, I believe this is a known behavior which has been brought to the R&D departments attention.
     
  4. pcepbx

    Joined:
    Apr 7, 2016
    Messages:
    20
    Likes Received:
    2
    Thank you for the update!
     
Thread Status:
Not open for further replies.