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.

3CX Bridged Phonebooks

Discussion in '3CX Phone System - General' started by Joris Van Dessel, Feb 20, 2018.

Thread Status:
Not open for further replies.
  1. Joris Van Dessel

    Joined:
    Feb 20, 2018
    Messages:
    2
    Likes Received:
    1
    Dear all,

    We have three 3CX instances running in 3 different locations.
    The three locations are bridged with each other.

    Location 1 has extension from 100 till 800 and prefix 3
    Location 2 has extension form 100 till 300 and prefix 2
    Location 3 has extension form 200 till 700 and prefix 1

    We were able to present the 3 phonebooks on a Yealink T42S IP Phone by changing the remote phonebook parameters of the XML template. On the Phone UI, Directory --> Remote Phone Book.

    Unfortunately the XML import does not show the prefixes in the phonebooks.
    Is there a way to have the prefix presented in the yealink_phonebook.xml?

    Any info is appreciated.

    Kind Regards,
    Joris
     
    Brad Allison likes this.
  2. saqqara16

    Joined:
    Jan 13, 2016
    Messages:
    46
    Likes Received:
    7
    The phone book can not add a prefix to the number.

    When you say prefix with 3 , 2 or 1 does this mean the extensions start with this number or the prefix you add to the extension when dialling to get to the correct office location.

    If your extensions are 3 digits at each location and cover the same range, then the only solution and I know it is a big job is to change the extensions to 4 digits at each site

    Location 1 - 1xxxx
    Location 2 - 2xxxx
    Location 3 - 3xxxx

    This way the phone book will have the correct numbers, and within outbound rules you will route calls with length on 4, and prefix to the correct location
     
  3. Joris Van Dessel

    Joined:
    Feb 20, 2018
    Messages:
    2
    Likes Received:
    1
    Damn ... we were hoping if there's another solution and/or workaround.
    Anyway thanks for your reply.
     
Thread Status:
Not open for further replies.