In one PRI out another PRI? 2400

[DallasGooner]

I have a newly installed 24ptrb-a pri card in our 2400 that is connected to a ShoreTel phone system. I am able to pass calls all day long between the ShoreTel and the NEC 2400 but I can not send a call that comes from the shoretel on the 24ptrb-a (route 20) out the existing telco PRI connection (route 1). I can see that the card is getting the proper digits passed to it (9-xxx-xxx-xxxx) but all I get is a reorder tone. I have ARRC set to 1 for the 1<>20 route, 1<>31 and 20<>31. What else am I missing?

 

[NECPBX]

Stupid question but is the OPR set up properly
to go out correct rt in AFRS?

 

[DallasGooner]

I wish I could say with confidence yes but I can't. I think so, but not 100% sure. In the docs I have access to I can't find any good info on that command. I have it so the extensions on the NEC and out route 20 can call each other. Those out rt 20 can can get external via interaction by a user on the NEC so it makes me think I do. Just something is wrong in allowing tandem connections. Because they can not go into the NEC and out rt 1 on there own.

 

[NECPBX]

Do you have access to a MAT Connection?
If so:
Perform listup of afrs (lfrs)
See what OPR it is pointing to.
Perform listup of AOPR (LOPR)
Let me know!

 

[NECPBX]

I'm assuming other call are going out RT 1 in 2400

 

[NECPBX]

Also in ARRC I believe you will need:
20<>1 also.

 

[DallasGooner]

ARRC is good both ways.

Yes, all calls default out route 1 when they dial 9 first.

I did lfrs and lopr but not sure I know what I am looking for.

lopr
TDPTN OPR RA Order RA End Route SKIP PNL OVFT PRSC
0 1 0 0 1 1 0 0 0
0 2 0 0 1 0 0 0 0
0 3 0 0 2 0 0 0 0
0 15 0 0 1 1 0 0 0
0 17 0 0 15 2 0 0 0
0 20 0 0 20 0 0 0 0


lfrs for 0-999 for npc
Tenant Route Number Pattern Code OPR
1 20 8999 20
1 31 2 20
1 31 675 3
1 31 676 3
1 31 677 3
1 31 678 3
1 31 679 3
1 31 68 3
1 31 69 3
1 31 775 3
1 31 776 3
1 31 777 3
1 31 778 3
1 31 779 3
1 31 78 3
1 31 79 3
1 31 875 3
1 31 876 3
1 31 877 3
1 31 878 3
1 31 879 3
1 31 88 3
1 31 89 3
1 31 900 1
1 31 901 1
1 31 902 1
1 31 903 1
1 31 904 1
1 31 905 1
1 31 906 1
1 31 907 1
1 31 908 1
1 31 909 1
1 31 910 1
1 31 911 2
1 31 912 1
1 31 913 1
1 31 914 1
1 31 915 1
1 31 916 1
1 31 917 1
1 31 918 1
1 31 919 1
1 31 92 1
1 31 93 1
1 31 94 1
1 31 95 1
1 31 96 1
1 31 97 1
1 31 98 1
1 31 99 1

 

[CDRMAN]

On the outbound PRI see if there is anything in ACBC .The out bound carrier maybe looking for a TAG before letting the call go out,
If this is the case you will be SOL \I had a similar issue for years and NEC never figured it out, I ended up adding a NONPRI for this type of application