[quote=“batchen, post:6, topic:40075”]
why do you want to remove it from the log ?
I’ve got this one.
PBX2 is the wrong source for that extension. PBX2 is extensions 100-199, so the caller ID is picking up an incorrect caller ID setting from somewhere.
Now, back to the question. There are several places where the Caller ID can be set. There is a module called SetCallerID() that can do it, plus the extension, outbound route, and trunk can all set (or modify) the outbound Caller ID.
In the outbound route, you can mark the route as an “Intracompany route” using the check box (right by the “Emergency route” checkbox). This reduces the number of places that update the Caller ID.
Note that this can be a good thing or a bad thing. I had a route mislableled as an IC route once and all of the calls when out from “510”. Not a valid Caller ID for the real world.
Something in your configuration is setting the Caller ID fields. Without either a lot more log information or more insight into your server config, there are just too many places that can cause this problem.