Digit analysis / conversion on inbound only?

[mnealtx]

More snags with the night service transfer.

We have a standalone switch in a physically separate location. Both the local network and remote switch are the same prefix (781). Dialplan is 4 digit dialing at both locations.

Issue: List trace tac shows attendant console calls coming in as "78" instead of "0". There is an x-port station 78 that forwards to attd. Normal 4-digit station calls come in correctly. Dialplan at main location has 78 as a 2 digit extension.

Local users attempting to dial a full station number (781-xxxx) instead of the last 4 get routed to the operator, as well, since the switch intercepts at "78".

I know that it can be handled by user training, but have to ask the question: Is there any way to filter or change the "78" ONLY on the inbound trunk from location 2? I don't have access to location 2 at this time to check the programming of the standalone switch.

 

[4merAvaya]

Are they using UDP to dial between the 2 switches? You can create a new Route Pattern in the originating switch that captures the 781-xxxx and deletes 3 digits.

Kevin

 

[mnealtx]

There is no processor level connection between the two switch, I know that - the only connection is the tie trunk.

Where would I look in the local switch to see if we're using UDP?

Here's what is on the local (receiving) switch.

Dialplan:
58 length 4, aar
78 length 2, ext

ARS ana:
78158 goes to p58

route-pattern 58 sends to trunk 5 (to switch location 2, the originating end of the "78" calls).

I don't have any way to check programming at the other switch, it's about 30 miles away and we cannot have a remote connection ( dot-mil contract).