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.

Importing contacts in Company Phonebook

Discussion in '3CX Phone System - General' started by Vali_3CX, Dec 14, 2017.

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

    Vali_3CX Well-Known Member
    Staff Member 3CX Support

    Dec 12, 2008
    Likes Received:
    Hi everybody
    In case you're a PBX administrator and you plan to import contacts in Company Phonebook:

    Be careful of WHAT you import! Do not import useless contacts!

    Today, during development, I connected my 3CX client to a PBX having an ~15000 contacts, from which only ~4000 were usable (!), all others being simply garbage. Sample of useless contacts:

    - contact having only first/last name, but no phones or eMails
    - contact having only phones but no first/last name
    - contact having only emails but no first/last name
    - contact having phone number specified as first/last name
    - contact having phones/emails but first/last name enclosed in quotes
    - contact having first/last name but garbage/invalid strings as phones/emails

    By filling the company phonebook with such useless contacts, you degrade performance not PBX's only, but clients' too by:
    - unnecessary extra network bandwidth required by all connected clients
    - unnecessary extra CPU required by PBX
    - slowing contact matching and filtering on both PBX/clients
    - wrong (or not at all) contact matching due to enclosing quotes in names
    - unnecessary risks due to garbage strings as emails/phone numbers

    As a PBX administrator, it's not a bad idea to review such bulk operations (and their scripts) before performing them, in order to make everybody's (yours, PBX's, clients', ours) life easier.

    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
    YiannisH_3CX likes this.
Thread Status:
Not open for further replies.