PRI Problems

[coladmin]

I am having a few issues with a new PRI that was instilled a few weeks ago. Anyone have any ideas on what could be causing these issues

1.) Call set up time seems longer than it should. Placing a call can take up to 5 seconds.
2.) Sometimes when a number is dialed there is a long pause and then I get a wave off tone. After hanging up and trying to place the call again it seems to go thru with no problem. I have watched the Lights on the DS1 board and when this happens the light does not turn yellow would lead me to believe that the call does not make it to the network
3.) The caller ID number that should up for our new circuit is no correct is shows up as a residential phone number

Thanks Coladmin

 

[Ghostin]

I have a cheat sheet for the PRI. I don't think I can post it anywhere here, but if you email me at ghostin @ myway.com I will send it to you.

If anyone knows how I can post a PDF file here, let me know.

The cheat sheet goes step by step and usually eliminates most problems that arise from programming.

 

[ScoTTeL]

If you are using DID, you need to set up your switch to outpulse the digit stream based on your dial plan.

It sounds like you have a few things wrong based on your other problems. I am assuming Ghostin has the same sheet i have. It is simple and will take care of most of your problems. You still need to setup your extensions to outpulse your DID's properly. Do you know how many digits your DID's are?

 

[fonetek]

check the line comp. maybe change it to a 2.
you can go to numbers to send and make it outpulse what you want. there are some limitations.
hope this helps

FRANK C
CONSOLIDATED TECHNOLOGIES
AVAYA GOLD BUSINESS PARTNER

 

[coladmin]

I tried the libne compensation setting and still the same issue. here is the PRI info report let me know if there is anyting incorrect. I beleive that I have fixed the called id issue by adding a single number to all lines in the number to send

COL madmin




PRI INFORMATION



Slot 1 Switch: DMS-100

System: By line

BchnlGrp #: Slot: TestTelNum: NtwkServ: Incoming Routing:
1 1 CallbyCall By Dial Plan

Channel ID: 23 22 21 20 19 18 17 16 15 14
13 12 11 10 9 8 7 6 5 4
3 2 1

Line PhoneNumber NumberToSend
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823

Network Selection Table

Entry Number: 0 1 2 3
Pattern to Match: 101**** 10***

Special Service Table

Entry Number: 0 1 2 3 4 5 6 7
Pattern to Match: 011 010 01 00 0 1
Operator: none none none none none none none none
Type of Number: N I I N N N N N
Digits to Delete: 0 0 0 0 0 0 0 0

Call-By-Call Service Table

Entry Number: 0 1 2 3 4
Pattern 0: 0
Pattern 1: 1
PRI INFORMATION


Pattern 2: 2
Pattern 3: 3
Pattern 4: 4
Pattern 5: 5
Pattern 6: 6
Pattern 7: 7
Pattern 8: 8
Pattern 9: 9
Call Type: VOICE BOTH BOTH BOTH BOTH
NtwkServ: No Service
DeleteDigits: 0 0 0 0 0

Entry Number: 5 6 7 8 9
Call Type: BOTH BOTH BOTH BOTH BOTH
NtwkServ:
DeleteDigits: 0 0 0 0 0

Dial Plan Routing Table

Entry Number: 0 1 2 3
NtwkServ: Any service
Expected Digits: 4 0 0 0
Pattern to Match:
Digits to Delete: 0 0 0 0
Digits to Add: 0

Entry Number: 4 5 6 7
NtwkServ:
Expected Digits: 0 0 0 0
Pattern to Match:
Digits to Delete: 0 0 0 0
Digits to Add:

Entry Number: 8 9 10 11
NtwkServ:
Expected Digits: 0 0 0 0
Pattern to Match:
Digits to Delete: 0 0 0 0
Digits to Add:

Entry Number: 12 13 14 15
NtwkServ:
Expected Digits: 0 0 0 0
Pattern to Match:
Digits to Delete: 0 0 0 0
Digits to Add:



----------------------------------- ANNOTATION -----------------------------------

 

[coladmin]

I tried the libne compensation setting and still the same issue. here is the PRI info report let me know if there is anyting incorrect. I beleive that I have fixed the called id issue by adding a single number to all lines in the number to send

COLadmin




PRI INFORMATION



Slot 1 Switch: DMS-100

System: By line

BchnlGrp #: Slot: TestTelNum: NtwkServ: Incoming Routing:
1 1 CallbyCall By Dial Plan

Channel ID: 23 22 21 20 19 18 17 16 15 14
13 12 11 10 9 8 7 6 5 4
3 2 1

Line PhoneNumber NumberToSend
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823

Network Selection Table

Entry Number: 0 1 2 3
Pattern to Match: 101**** 10***

Special Service Table

Entry Number: 0 1 2 3 4 5 6 7
Pattern to Match: 011 010 01 00 0 1
Operator: none none none none none none none none
Type of Number: N I I N N N N N
Digits to Delete: 0 0 0 0 0 0 0 0

Call-By-Call Service Table

Entry Number: 0 1 2 3 4
Pattern 0: 0
Pattern 1: 1
PRI INFORMATION


Pattern 2: 2
Pattern 3: 3
Pattern 4: 4
Pattern 5: 5
Pattern 6: 6
Pattern 7: 7
Pattern 8: 8
Pattern 9: 9
Call Type: VOICE BOTH BOTH BOTH BOTH
NtwkServ: No Service
DeleteDigits: 0 0 0 0 0

Entry Number: 5 6 7 8 9
Call Type: BOTH BOTH BOTH BOTH BOTH
NtwkServ:
DeleteDigits: 0 0 0 0 0

Dial Plan Routing Table

Entry Number: 0 1 2 3
NtwkServ: Any service
Expected Digits: 4 0 0 0
Pattern to Match:
Digits to Delete: 0 0 0 0
Digits to Add: 0

Entry Number: 4 5 6 7
NtwkServ:
Expected Digits: 0 0 0 0
Pattern to Match:
Digits to Delete: 0 0 0 0
Digits to Add:

Entry Number: 8 9 10 11
NtwkServ:
Expected Digits: 0 0 0 0
Pattern to Match:
Digits to Delete: 0 0 0 0
Digits to Add:

Entry Number: 12 13 14 15
NtwkServ:
Expected Digits: 0 0 0 0
Pattern to Match:
Digits to Delete: 0 0 0 0
Digits to Add:



----------------------------------- ANNOTATION -----------------------------------

 

[GoKings]

What release level is your Merlin? There was a problem with one of the early versions of R7 Legend with having the 1st trunk port in the switch be a PRI channel. It was resolved by doing a flash upgrade to the DS1 (depending on its vintage) and also to the R7 processor.

 

[TouchToneTommy]

I don't do much with PRI's so I don't have much insight for you. However, I just posted a cut-n-paste of a Word document from the Avaya support site to the FAQ's section here. Look under PRI Troubleshooting, and see if there is anything in there that helps.

 

[ttech]

I had BIG problems with the First CO port being a PRI on a legend I had installed years ago. I had the CO busyout the first channel until I got the flash upgrades done - Per avaya.

Don

 

[coladmin]

Thanks for the posts. I have a release 3.0 Merlin. I am going to see if the have the L1 flag set per FAW that Tommy posted. Thanks! I will post the results. Hopefully they are positive

 

[jinxs]

Another thing to check is the your 24th channel isn't in apool. Your 24th channel should be MA busy. You can check this by going into Maintaince--Port--lines/trunks---type in your trunk number(824)--Status. IF the 24th lines is in a pool, this will cause some strange and various issues. The calls would have problems every 24th outbound phone call made by the user.

 

[GoKings]

Just another FYI, PRI's do typically have a longer delay following dialing out b4 you get ringback than either standard T1's or LS/GS trunks so just accept that. I doubt this is causing any trouble, because it should not matter, but I always leave the call type for entry 0 in the call by call table set to BOTH instead of changing it VOICE. Another question, you are sure that the PRI is coming from a DMS-100? If it is a DMS-100, have you verified that the Service Provider set the CO protocol to NTNAPRI? What type of DS1 board are you using, 100D w/ external CSU, 100DCD, 100R? Just trying to rule out the CSU as trouble.

 

[coladmin]

I am sure that they are DMS-100 but I believe when we set it up the only option they had was DMS100 NI-1 is that the same as NTNAPRI??? Also I am using the 100DCD w/ integrated CSU

coladmin

 

[GoKings]

No, NI-1 is a national protocol and the Merlin needs a custom protocol. NTNAPRI can also be referred to as AT&T Custom for the CO protocol. Call the Svc Provider and ask them to make the change to either NTNAPRI, and if they don't understand reference it as AT&T Custom. This is likely going to be the culprit of your trouble, here.

 

[merlinman]

I agree with GoKings, LEGEND/MAGIX is CUSTOM, based on the Serving Central Office, NOT NATIONAL.

 

[coladmin]

thanks!!! I will see what thet say tomorrow

 

[coladmin]

ok I finally got them on the phone and we had to changeit to 5ESS and ATT custom and they seemed to solve the issue with the network. I am still have an every so often when I try to make a call I get a busy signal but the call never makes it to the network. any ideas on this one?

thanks again for all your help

 

[coladmin]

I just checked my permant error log and when the above happens there is this error is the log.

pool maintenance busy exceeds 50%

 

[GoKings]

Ok...They couldn't have changed it from a DMS-100 to 5-ESS in a matter off days. They could have made the change to the CO Protocol from NI-1 to AT&T Custom, though. I trust that this is still on a DMS-100, or was it clarified that this is on a 5-ESS instead of a DMS-100?

The error you are getting indicates that a lot of the b-channels are likely in maintenance busy, which typically happens to channels that have been out of svc for a while. Go to Maintenance>Port>Lines and Trunks and enter each line number (b-channel) on the PRI and check status. You can perform a busy -out and restore to see if that brings them back into svc.

 

[coladmin]

ok after much testing we found that it a was an issue with the cabling that was running from the demarc to the switch.

they were able to switch it from 5ESS on the fly...I was able to get with the right people I guess.


we will see what happens now.

thanks for everyones help!