Two CallerID formats, One Route

[sholinaty]

Hoping for some insights on this one.

I have two trunk providers that support some form of “passthrough” callerID.

One, we have our best luck sending NPANXXXXXX,
the other demands e.164 formatted calleriD

I want to use both of them as redundancy for outbound calls on the same dialing prefix (lets say *40)

is there a way to easily manipulate callerID on a Per-outbound-route, per-trunk basis?

I know I can manipulate the dialed number, but haven’t seen much for CallerID.

The goal here is to end up with a few hundred outbound routes (each with a unique dialing code), feeding the same 2-3 trunks

Any insights would be greatly appreciated, as always.

[Stewart1 (Stewart)]

Set up a predial hook that checks the trunk name and rewrites the caller ID if required

Hooking for fun and income

Despite the frequency with which it arises here in the forum, there is not yet a good resource for learning to use dialplan hooks in FreePBX. This will probably end up in the wiki at some point, but until that happens, here are the broad strokes for leveraging dialplan hooks in FreePBX 14. What is a dialplan hook? A dialplan hook refers to several pre-defined FreePBX contexts that exist solely for users to add their own Asterisk Macros to be run at specific locations in the call flow. They all …

[sholinaty]

damn… i was Really hoping i wasnt going to have to hand-build this.

Thank you my friend.