Never had to do one on a 384i, is it simply connecting to the mini DIN connector?

trying to troubleshoot PRI

I believe you have to configure a DCI port to capture the data stream. They can be attached to a phone OR a 3 DCI unit. Been a long time. What is the PRI doing?

well it turned out it was a 1 cabinet 704i.
it has a mini-din connector (CN4) that is designated for DIMU.

I hooked up to it but was unable to send any of the MAIL IN commands, the only thing that shows up is when the system writes to memory or when the backup failed to write to the "broken" floppy disk.

What happened was the system lost its programming.
Used a backup to restore that was about 2 years old.
since the restore incoming PRI calls are failing to route to their destinations via the DID tables. Thye just go to the overflow destination.

I tried building a nother trunk group , but with the same results.

I would check how many digits the Telco is sending. FWIW on the iseries you always used the overflow for routing.

Talked to Dennis today and got a bit of info. Since it is a 704i it has the mini-din connectors. If you connect to the top one and type SON it will start the two-way communication and you can type your MAIL commands.

" FWIW on the iseries you always used the overflow for routing."
for ring groups yeah, but for DIDs it the table assignments.

So doing the MAIL command I can see the proper 4 digits being sent. But the weird thing is the R ISDN:<<<<<<<<< message comes after it has already rang a few times. I am going ot have to trouble shoot that a bit further.
When the R ISDN:<<<<<<<<<<< does come through it appears OK

R ISDN : <<<<<<<<<<<<<<<<
2f 0b a1 04 01 01 00 USL(5,1),SETUP IND
08 02 19 8e 05 Callref:ORG(6542),SETUP
04 03 80 90 a2 Bearer capability
18 03 a9 83 81 Channel identification
1e 02 82 83 Progress indicator
6c 0c 21 83 38 31 37 36 Calling party number [5415555555]
+32 36 35 34 38 33
70 05 80 31 39 36 32 Called party number [1962]this is the last 4 of their fax and should go to the extension
ISDN_MESSAGE_PRE_OPERATION->7801H
CEVENT_ISDN_T_POINT->01H
[6AD1]EV:0000:7801-0000-0000:2188:0983
GET_FACILITY
[6AD1]IN:7801:3401-0000-0000:0000:0C24
[6AD2]IN:3401:0401-0000-0000:0000:08AA3401 (channel 1) ringing 0401(port 1)
[6AD5]IN:3401:7801-00B6-0000:0000:0C0D
GET_CHANNEL->81H
S ISDN : >>>>>>>>>>>>>>>>
7f a1 02 01 01 00 USL(5,1),PROCEEDING REQ
08 02 99 8e 02 Callref:DES(6542),CALL PROCEEDING
18 03 a9 83 81 Channel identification
S ISDN : >>>>>>>>>>>>>>>>
0f a1 01 01 01 00 USL(5,1),ALERTING REQ
08 02 99 8e 01 Callref:DES(6542),ALERTING
[6AD7]IN:3401:7801-0024-0000:0000:0C0D
[6AD7]IN:0401:3401-0024-0000:437F:4808
[6AD8]IN:3401:437F-FFFE-FFFE:0401:08B0I believe 437F is a Virtual port?? since, for reasons unknown to me Port 1 is call fwded immediatly to a virtual (but I can;t get the hex index of 7F to match up to Virt port 896
[6ADE]IN:437F:0402-0000-0000:0000:08D5437f is tha call coverage key?? : on 0402(port2)?
[6ADF]IN:437F:0403-0000-0000:0000:08D5
[6AE1]IN:437F:0404-0000-0000:0000:08D5
[6AE2]IN:437F:0405-0000-0000:0000:08D5
[6AE4]IN:437F:0406-0000-0000:0000:08D5

I don't see were it tries to make a match in the table though.

I am having the customer do a complete power down and restart to see if that makes a difference.

I assume you have the 1962 going to 1962. I am pretty sure you have to have the DID table set 1962 goes to 1962 or whatever the number of the ext is. I don't think it "lands" on the ext number like other phone systems do.

Actually there isn't a 1 to 1 translation. 1962 should be going to an extension like 504.

Check your software level. You have to run a minimum level to make PRI work correctly if memory serves. When that damn floppy fails sometimes you get a previous version. I want to say something like 4.11...but I could be wrong it's been a LONG time.