We have 39 locations in 5 states. We are migrating one extension at a time from an old FreePBX15 server to a FreePBX17 server, both servers on prem at the same location.
Our branches connect back to our on-prem server. We specify in the extension for these branches their main telephone number for caller ID / E911, etc.
We have 35 AT&T Sip trunks on an IP Flex circuit. On that trunk(hooked to the 15 server only), we have our main telephone number specified for the outgoing caller ID for corporate / main location(so that’s what gets used by default for extensions at that locations that have no outgoing caller ID specified for their extension). When the remote locations dial out(the ones connected direclty to the 15 server), the caller ID on their extension is overwriting that and it works fine.
However, with our new FreePBX 17 server, it connects to our FreePBX15 server through a Pjsip trunk for both internal calling between locations and external calls. When remote phones on the new 17 server dial out, it goes over that trunk to the 15 server, then out on the AT&T Sip trunks on the flex circuit. No matter what I do, it’s overlaying the extension specified caller ID with the default one set for the main office on the AT&T Trunk.
I can provide some more specific details if needed, but I feel like I’m missing a setting I need to change on one of the trunks or outbound routes to get this to work properly. Thank you in advance for any suggestions you can provide.
Thank you for your suggestion. I guess the problem would we we would need a seperate trunk for each of the other 38 locations and I’m not sure there is a way to force specific extensions over a trunk without telling them they need to dial a prefix at the beginning of the number.(which isn’t going to fly for our company)
you would have two outbound routes, one with dial patterns for extension numbers, like xxxx that does not change the callerID, and one for 10 digit numbers like NXXXXXXXXX that forces the CID
In the past I’ve done this by storing the external CID number in a SIP header and then restoring it if needed on the far end, but @Eris’s 2 outbound route method should work better. Have one route marked intracompany to reach the local resources on the remote system, and another outbound route not marked intracompany for making external calls on the remote system, with appropriate dial rules for each.
I tried some of the suggestions listed here and none of them worked. The only way I was able to get this addressed was to completely remove the default CID from our trunk to our carrier, then specify the exact caller ID on every extension. Otherwise when coming from the 17 server, no matter what I would do, the CID on the trunk was overwriting it.