Prefixes using CallerID Lookup

Hello,

recently we created a contact list in one of our deployments and configured it under “CallerID Lookup Sources” to bring some more meaningful and consistent data to our agents for planned or expected numbers. The problem we’re facing is that for each of the numbers that match a record in the Contact List and receive the updated CallerID data, the prefix that was added by the inbound route is stripped and no longer present.

Is there a supported method or configuration for leveraging CID Prefix alongside CallerID Lookup Sources?

@lgaetz Any chance you might be able to shed some light on this behavior?

Consider using a dynamic route with a MySQL query or AGI call as the first step in the call. Read up and give it a go.

Dynamic Routes Module - PBX GUI - Sangoma Documentation (atlassian.net)

Dynamic Routes - Working Examples - PBX GUI - Sangoma Documentation (atlassian.net)

I use it in similar functions with great success.

Neat - and definitely something id like to try. But I would still like to understand the flow and why this is acting the way it is if someone knows much about it. :slight_smile:

1 Like