Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Magix PRI fast busy

Status
Not open for further replies.

BTU789

Programmer
Jan 22, 2008
142
US
Hi all, I have a customer that has a merlin magix r4. The main number and a few DID's get a fast busy when called. I haven't actually heard this after about three dozen test calls but the customer and the provider say its happening. The provider actually emailed me the error description that he gets. By the way there are no errors at all in the error log.
Here is what the provider emailed me:

03109
Key Code Range: 03000 - 03999
Software Release: 5E10 and later
Protocol: Q.931
Error Analysis: yes
1. FORMAT
PER a/a bb:bb:bb Q.931 c d e CHAN-ID-INV
[TEI=f] CRV=g CRF=h KEY=3109
2. EXPLANATION OF VARIABLES
Refer to the 03(BASE) description for a full explanation of all variables shown in the format.
3. CAUSE
The switch received a Q.931 SETUP message from the customer premises equipment (CPE) on a primary rate interface (PRI) D-channel, but the message contained an invalid channel identification information element (IE).
4. EXTERNAL EVIDENCE
This PRI call setup attempt will fail. The switch will send a Q.931 RELEASE COMPLETE message to the CPE with a cause code value of 100 "invalid information element contents" in response to the Q.931 SETUP message. A level 3 message error count is pegged and reported in part 11 of the 24 hour plant report. Refer to OP:pLNT24-PT11 in the Output Messages manual for additional information.
5. CORRECTIVE ACTION
Determine why the PRI CPE is not populating the channel identification IE correctly.
6. REFERENCES
Other Manual(s):
235-600-750 Output Messages

Any info/ideas would be much appreciated.
Thanks,
Brian
 
Since you have no error alarm codes in the Magix, there may be a problem with certain B CHANNELs. Are you configured for a full Primary ISDN, which is 23B+D? So, in the Magix configuration there would be 23 BCH in the line pool. You want to verify what is in the Magix. Have you tried doing a power up reset? You might post a print of the configuration. How long has this been happening? Can you get the list of BCHs that have the failure from the LEC? That would be helpful in troubleshooting... The email info above does not have anything specific to the trunk group or its members. More info is needed.

....JIM....
 
Thanks for the response. I didn't print any of the system info because I stopped at this customer briefly in between other service calls. I'm scheduled to be there for a few hours on monday so I'll post the info you have suggested tomorrow. Thanks again!
Brian
 
Jim, here is the PRI info.
A PRI INFORMATION



A Slot 5 Switch: 5ESS

A Slot 13 Switch: 5ESS

A System: By line

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

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

A Line PhoneNumber NumberToSend
A 817 2126962500
A 818 2126962500
A 819 2126962500
A 820 2126962500
A 821 2126962500
A 822 2126962500
A 823 2126962500
A 824 2126962500
A 825 2126962500
A 826 2126962500
A 827 2126962500
A 828 2126962500
A 829 2126962500
A 830 2126962500
A 831 2126962500
A 832 2126962500
A 833 2126962500
A 834 2126962500
A 835 2126962500
A 836 2126962500
A 837 2126962500
A 838 2126962500
A 839 2126962500

A BchnlGrp #: Slot: TestTelNum: NtwkServ: Incoming Routing:
A 2 13 CallbyCall By Dial Plan

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

A Line PhoneNumber NumberToSend
A 841 2126962500
A 842 2126962500
A 843 2126962500
A 844 2126962500
A 845 2126962500
A 846 2126962500
A 847 2126962500
A 848 2126962500
A PRI INFORMATION


A 849 2126962500
A 850 2126962500
A 851 2126962500
A 852 2126962500
A 853 2126962500
A 854 2126962500
A 855 2126962500
A 856 2126962500
A 857 2126962500
A 858 2126962500
A 859 2126962500
A 860 2126962500
A 861 2126962500
A 862 2126962500
A 863 2126962500

A Network Selection Table

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

A Special Service Table

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

A Call-By-Call Service Table

A Entry Number: 0 1 2 3 4
A Pattern 0: 0
A Pattern 1: 1
A Pattern 2: 2
A Pattern 3: 3
A Pattern 4: 4
A Pattern 5: 5
A Pattern 6: 6
A Pattern 7: 7
A Pattern 8: 8
A Pattern 9: 9
A Call Type: BOTH BOTH BOTH BOTH BOTH
A NtwkServ: No Service
A DeleteDigits: 0 0 0 0 0

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

A Dial Plan Routing Table

A Entry Number: 0 1 2 3
A NtwkServ: Any service
A PRI INFORMATION


A Expected Digits: 0 4 0 0
A Pattern to Match: 0333
A Digits to Delete: 0 4 0 0
A Digits to Add: 1333

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

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

A Entry Number: 12 13 14 15
A NtwkServ:
A Expected Digits: 0 0 0 0
A Pattern to Match:
A Digits to Delete: 0 0 0 0
A Digits to Add:
Here is the Dial plan for lines/trunks.
DIAL PLAN FOR LINES/TRUNKS

A LINE # 1: 801 OUTSIDE LINE # 2: 802 OUTSIDE
A LINE # 3: 803 OUTSIDE LINE # 4: 804 OUTSIDE
A LINE # 5: 805 OUTSIDE LINE # 6: 806 OUTSIDE
A LINE # 7: 807 OUTSIDE LINE # 8: 808 OUTSIDE
A LINE # 9: 809 OUTSIDE LINE # 10: 810 OUTSIDE
A LINE # 11: 811 OUTSIDE LINE # 12: 812 OUTSIDE
A LINE # 13: 813 OUTSIDE LINE # 14: 814 OUTSIDE
A LINE # 15: 815 OUTSIDE LINE # 16: 816 OUTSIDE
A LINE # 17: 817 PRI-1 LINE # 18: 818 PRI-2
A LINE # 19: 819 PRI-3 LINE # 20: 820 PRI-4
A LINE # 21: 821 PRI-5 LINE # 22: 822 PRI-6
A LINE # 23: 823 PRI-7 LINE # 24: 824 PRI-8
A LINE # 25: 825 PRI-9 LINE # 26: 826 PRI-10
A LINE # 27: 827 PRI-11 LINE # 28: 828 PRI-12
A LINE # 29: 829 PRI-13 LINE # 30: 830 PRI-14
A LINE # 31: 831 PRI-15 LINE # 32: 832 PRI-16
A LINE # 33: 833 PRI-17 LINE # 34: 834 PRI-18
A LINE # 35: 835 PRI-19 LINE # 36: 836 PRI-20
A LINE # 37: 837 PRI-21 LINE # 38: 838 PRI-22
A LINE # 39: 839 PRI-23 LINE # 40: 840 OUTSIDE
A LINE # 41: 841 PRI-24 LINE # 42: 842 PRI-25
A LINE # 43: 843 PRI-26 LINE # 44: 844 PRI-27
A LINE # 45: 845 PRI-28 LINE # 46: 846 PRI-29
A LINE # 47: 847 PRI-30 LINE # 48: 848 PRI-31
A LINE # 49: 849 PRI-32 LINE # 50: 850 PRI-33
A LINE # 51: 851 PRI-34 LINE # 52: 852 PRI-35
A LINE # 53: 853 PRI-36 LINE # 54: 854 PRI-37
A LINE # 55: 855 PRI-38 LINE # 56: 856 PRI-39
A LINE # 57: 857 PRI-40 LINE # 58: 858 PRI-41
A LINE # 59: 859 PRI-42 LINE # 60: 860 PRI-43
A LINE # 61: 861 PRI-44 LINE # 62: 862 PRI-45
A LINE # 63: 863 PRI-46 LINE # 64: 864 OUTSIDE
I,m going on a conf call with the provider and the PRI switch tech now.
Thanks.
 
So, after the conf call where the provider kept denying it was a problem on their end, we decided to busyout the first trunk on the inbound PRI. I'm going back to the site at 2pm to see if the customer has had any more issues. At that point if there are no issues then the provider will send a tech with a t-bird to the site to test the circuit. I still think this is an issue with the circuit and I believe they are just trying to cover themselves. I'll update more later.
Brian
 
So, in case anyone is interested, a phone company tech came to the site with a t-bird and we tested inbound calls. Of course, we didn't receive a single fast busy. The phone tech said the issue may lie at the handoff from verizon to his company but on verizon's end.
But, for the heck of it I decided to swap the two PRI's to see if the board was actually the issue. I figured if the board is the problem then outbound calls would start having issues because the outbound PRI was now on the "questionable" board. This was last thursday and I haven't heard any reports of trouble with inbound or outbound calls.
Very strange. So, at this point I still don't know what was causing the issue.
The customer is happy so that's all that counts. I've been in contact with the provider and they still maintain that it was not their circuit.
Anyway, just wanted to give some sort of conclusion to this post.
Thanks,
Brian
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top