We've been using 4-digit station extensions and T1's to network 3 Merlin Legends successfully for more than 11 years. We're currently transitioning from these T1's [Legend-Ntwk] to AT&T's IPFlex BVoIP [5ESS]. The problem I'm having is with the adjustments to the Uniform Dial Plan (UDP) to route non-local extension calls through PRI channels (specifically for extensions in the range:1100-1199).
If I program an appropriate route, absorbing and adding the necessary digits to make a switch-to-switch call on the PRI (or even across the POTS lines), the switch generates a warble tone, an MLX display phone indicates the programmed line selection for the pool, but the 100D lights stay off and AT&T reports that no digits are coming from the switch to their Cisco 2811.
If I try to absorb NO digits and pad the number of digits in the UDP route, then I can successfully present the programmed digits to AT&T's router, but the Legend's dialed digits (e.g., 1120) are prepended to the dial string they see presented from the switch. Obviously, the switch and router are trying to act on these extensions (1100-1199) as long distance calling attempts. I've tried clearing the Special Services patterns in PRI programming to prevent a possible conflict and playing with the ARS tables, but without any success. All other extension patterns in the UDP are working (1200-1499) and as I indicated it's been working in a Legend-Network for 11 years. Thanks to anyone who can help, but what am I missing?
If I program an appropriate route, absorbing and adding the necessary digits to make a switch-to-switch call on the PRI (or even across the POTS lines), the switch generates a warble tone, an MLX display phone indicates the programmed line selection for the pool, but the 100D lights stay off and AT&T reports that no digits are coming from the switch to their Cisco 2811.
If I try to absorb NO digits and pad the number of digits in the UDP route, then I can successfully present the programmed digits to AT&T's router, but the Legend's dialed digits (e.g., 1120) are prepended to the dial string they see presented from the switch. Obviously, the switch and router are trying to act on these extensions (1100-1199) as long distance calling attempts. I've tried clearing the Special Services patterns in PRI programming to prevent a possible conflict and playing with the ARS tables, but without any success. All other extension patterns in the UDP are working (1200-1499) and as I indicated it's been working in a Legend-Network for 11 years. Thanks to anyone who can help, but what am I missing?