MST trace from old Definity G3V6

[wmainc]

Old system, I know....
Customer has two locations tied together with a PRI. The testing that was done was:

Call from 713-459-XXXX into switch 1 at 512-430-XXXX and then dial 6101 to go across PRI to switch 2.

Switch 2 is not getting, or recognizing, 6101. Switch 2 uses 3 digit extensions. In the trunk group, it is set up to take 4 digit numbers starting with a 6, and delete the first digit. So, 6101 should be reduced to 101 and ring to 101. It's not happening. Here is the MST trace from the test call:

MESSAGE SEQUENCE TRACE DATA

Number Date/Time Type Message

1 07/19/17
14:01:31.375 60 00 00 3E 17 08 02 00 AA 05 04 03 80 90 A2 18 03
A9 83 81 28 0F 44 45 4E 4E 45 4E 42 45 52 47 2C
4D 49 43 48 6C 0C 21 80 [highlight #FCE94F]37 31 33 34 35 39 3X 3X
3X 3X[/highlight] 70 03 80 30 31
2 14:01:31.375 62 00 00 3E 17 08 02 80 AA 02 18 03 A9 83 81
3 14:01:31.375 62 00 00 3E 17 08 02 80 AA 01
4 14:01:39.075 62 00 00 3E 17 08 02 80 AA 07 1E 02 81 82
5 14:01:39.175 60 00 00 3E 17 08 02 00 AA 0F
6 14:01:44.825 62 00 00 3E 17 08 02 80 AA 45 08 02 81 90
7 14:01:44.925 60 00 00 3E 17 08 02 00 AA 4D
8 14:01:44.925 62 00 00 3E 17 08 02 80 AA 5A

I can see the calling number (last 4 x'd out). I can't see 6101 anywhere and can't remember where the called number would be located. The last 4 digits? That would be 3001. I tried deleting 30 and inserting 1 to force calls to 101, but that still didn't work.
Any help decoding the digits being sent by the first PBX would be appreciated.

 

[AvayaTier3]

I can decode for you.. What are you tracing?

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[wmainc]

Trying to figure out why calls coming across this "tie" PRI from one Definity to another are not being directed to the correct extension. This is the trace from the D-Channel of the PRI in PBX 2 capturing the test call.
The caller called into PBX 1 from the outside to the remote access number. Once in, he dialed 6101 which is directed across this PRI to PBX 2. I would have expected to see 6101 somewhere in the trace, but I don't.

 

[AvayaTier3]

You are looking at raw data. A raw d-channel setup message is much larger than what you have pasted here.
status mst and paste to show number of messages, % of wrap, etc.

A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[wmainc]

I set up MST to capture d-channel data on that particular PRI. I enabled mst and had the tech make one test call. After the call completed, I did a "list mst" and all that showed up on the screen was what I pasted above. I cleared the mst and had him do another test call. The same information (no more no less) showed up when I listed mst the second time. I'm actually just trying to help out another tech on this and I don't have dialup access right now.

 

[wmainc]

Well, finally got an answer from the PRI provider. They weren't actually sending any called number information, so no digits for the PBX to use to route calls. I knew there should have been more data following the calling number.