I think you may find people are a bit put off when you make a post, bump it from lack of response hours later and then again the next day. This tends to result in people ignoring your posts. Have a little patience when you ask for help. Also, you have articulated in your request in a fairly confusing manner which probably makes it hard for people to understand. Lastly, don’t mess with extensions.conf, it will get overwritten - anything you do should be done in a file like extensions_custom.conf.
If you are looking at looking up your callerid from a source other than those provided in the cidlookup module, you are probably best to send your incoming trunk to it’s own context, lookup the source there, and from there send it on its way to from-pstn.
Philippe Lindheimer - FreePBX Project Lead
http//freepbx.org - IRC #freepbx
I tried adding the following line in extensions_custom.conf but it didn’t make any difference because the line is not read or maybe because incoming calls are set in extensions.conf.
To see the flow of how things work review the [from-pstn] context in extensnsions.conf. that is where calls normally go first. You will see that it calls other contexts for processing, most importantly it calls one ending in -custom which will not exist unless you create it.
You should only edit and/or create files that end in _custom.conf As the others will be replaced or updatd at different times. extensions.conf is touched every upgrade, extensions_additional.conf is touched every time there is a change and is automaticly generated by freepbx.
As Philippe stated you are probably best creating a new context and then you need to change flow of the incoming to go to your new context first. Have your custom context when done go to from-pstn (see right about from-pstn for a working example).
Yes when you start it is confusing. FreePBX still has to follow all the rules of asterisk so understanding how asterisk works help a lot.