[central2]
type = peer
context = from_central2
host = 181.168.xxx.xxx
dtmfmode = rfc2833
qualify=yes
canreinvite = no
insecure=port,invite
nat=yes
disallow = all
allow = alaw,ulaw
trunk=yes
When I tray to call from central2 to central1 from internal 100 (in central1) I have no problems
All other extensions from central1 can’t call with this error:
You cannot blindly call 104 on PBX A from 104 (or anything other extension on PBX A) from PBX B. When 104 from PBX B calls 104 on PBX A, PBX A is going to go “Oh 104 is attempting to send me a call, let me check their username/IP and auth them” expect since the IPs are going to be different and the auth isn’t going to work, you get no call.
When you connect multiple PBX systems together that have “overlapping” extensions, you need to make each PBX present calls so they don’t seem like they are coming from an extension that exists locally and the PBX rejects it due to it looking like a bad attempt.
You need to make the outgoing part for each of the PBX trunks present a unique “fromuser” so it doesn’t use the callers default “fromuser” (aka 104) but you also need to present the callers information via RPID or PAI so it can be seen in the CallerID.
You need to set the context on each trunk to something else besides “from-internal” so you can intercept it and deal with accepting the call then routing it back to the generated dialplan to call the extension.
Oh if you can’t make the needed changes on Central2, then you’re pretty much dead in the water. This can’t be a one sided fix. All PBXes involved need to be updated to deal with this.