CID Lookup using Phonebook seems to be broken


Maybe I’m missing something, but I think CID lookup via phonebook is broken.

Here’s what I did:

  1. Install the “Phone Books” add-on,

  2. Under PBX/Tools/Phonebooks, create an “External” phonebook, and import some content from a CSV file

  3. For the purposes of testing, I made sure that there was a value in each of the “Main Phone Number”, “Mobile Phone Number”, and “Home Number” for each entry in the phone book

  4. I also made sure that the phone numbers, as written in the CSV file, were pure numbers (no spaces, parentheses, etc.) and were exactly in the number format as being notified in the SIP signalling in incoming calls (checked with sngrep). (The phone book import decided to impose some weird formatting of its own for some of the numbers, but not for the test number I was using.)

  5. Under Incoming Calls/CID Lookup, I create a lookup using “Phonebook” as the source method, pointing to the phone book I created above.

  6. For my (only) inbound route, I change “CID lookup” to point to the lookup that I created above.

  7. I make a test inbound call, and observe that the caller name associated with the incoming number is not being passed to the receiving phone (checked with sngrep). I can also see from the asterisk logs that the CIDLOOKUP function is being invoked, using the lookup that I created, but is returning “CID_NAME=” (i.e. CID_NAME is being set to the empty string).

The incoming caller ID of the test call is an exact match to a row in the phone book, matching all three phone number columns.

If, instead of using the Phone Books add-on, I create a CID Lookup that uses a MySQL table as the source, it works perfectly.

Maybe I’m doing something wrong; if I am, then I’d be grateful if someone could point out what. But I think it’s broken.

VitalPBX v3.1.1-2
Asterisk v18.5.1-1
Phone book v3.0.2-5

1 Like

Thanks for reporting it. We will run through tests in our labs to find a solution.

Did you find anything?

Thanks for your patience. We didn’t have time to go over this issue in the previous release. Nonetheless, you can rest assured that this will get addressed in the next version.

It looks like v3.1.3-1 has fixed it :slight_smile:


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.