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.

Multiple extensions with same CID for internal calls

Discussion in '3CX Phone System - General' started by Frank D, Nov 14, 2016.

Thread Status:
Not open for further replies.
  1. Frank D

    Frank D New Member

    Joined:
    Oct 6, 2014
    Messages:
    215
    Likes Received:
    6
    Hi,

    we have several places, where we need multiple phones to send the same CID to other extensions. While this can easily be configured for external calls (edit extension details in 3cx "outgoing number), I looks to be quite difficult for internal calls, as those are not effected by the changes above.

    Provisioning multiple phones with the same extension, is no sustainable solution for us, because 3cx supports provisioning for one phone for each extension only. We need to roll-out changes to all our phones.

    Yealink W52p supports choosing an outgoing account, if you have several accounts on the phone. So here, we add the desired account (to be shown as CID) to the phone and choose this account for outgoing calls.

    But for T46G we have no solution. You can select a "default acccount" for outgiong calls via the Phones GUI or the arrow keys:
    https://xeloq.wordpress.com/2015/02/20/ ... arrow-key/
    But that change will be lost after restarting the phone. It will always select account 1 after restarting the phone. It is not saved in the local provisiong file, neither, when you enable the protection of user settings.

    Do you have a solution?

    One solution is to manually edit account 1 and account 2, swiching the account, so that the desired account is number 1. You could even just overwrite "account 1" this way the additional account would be used for provisioning only. This will cause some minor problems regarding possbile password and other account changes on the server, but is the best solution I have at this point. This requires user settings protect to be enabled, so the provisioning won't overwrite these settings.

    Any thoughts on this?
    Any other solutions?

    Best regards

    Frank
     
Thread Status:
Not open for further replies.