So.. Broadvox assigned a trunk BTN as the primary number on another carrier, which the numbers will be porting soon-ish.
The intent is to set calls to forward on their current line to a DID on their new trunk.
Aside, the new DIDs ring in as expected on this new trunk, and will route to extensions properly, based on the inbound rules set for the DIDs. The BTN itself routes to an IVR.
The issue, though, is that when the call their current system, set to forward to one of these new DIDs.. the call routes to the IVR.. NOT the extension set on the DID.
I believe the PBX is seeing the caller's number.. and since it matches the BTN on the trunk, is triggering the inbound rule for the BTN.
Is there a method to correct this? Or.. would it be best to either wait for the port (would rather not) or have Broadvox assign a different BTN to the trunk? The alternative.. all forwarded calls will route to the IVR based on that inbound rule.. until the port.
The intent is to set calls to forward on their current line to a DID on their new trunk.
Aside, the new DIDs ring in as expected on this new trunk, and will route to extensions properly, based on the inbound rules set for the DIDs. The BTN itself routes to an IVR.
The issue, though, is that when the call their current system, set to forward to one of these new DIDs.. the call routes to the IVR.. NOT the extension set on the DID.
I believe the PBX is seeing the caller's number.. and since it matches the BTN on the trunk, is triggering the inbound rule for the BTN.
Is there a method to correct this? Or.. would it be best to either wait for the port (would rather not) or have Broadvox assign a different BTN to the trunk? The alternative.. all forwarded calls will route to the IVR based on that inbound rule.. until the port.
