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 gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Merlin Magix - PRI - Pool Busy (4C03) 3

Status
Not open for further replies.

ROTGUT

IS-IT--Management
May 5, 2009
6
US
Hi, all. Hope you can help --- I am struggling with a Merlin Magix PRI.

I have a 100 DCD module connected to our PRI (8 channels active for voice, no data channels) and have configured per what I've read in the forum but I cannot receive or place calls.

Outbound gives fast busy and the error log shows 4C03 (POOL BUSY &/OR OOS). Inbound calls give busy signal and the error log fills with 7001 (PRI SVC AUDIT TIMEOUT), one for each of the 23 PRI channels.

I did notice that the port for the D-channel is in maintenance-busy and I cannot restore it (although I think that's normal since it is not an actual trunk).

The PRI is 5ESS (AT&T custom) and the provider confirms that configuration on their side. They say they are able to send the digits but get an ISDN error. I don't recall the error but it indicated that our switch was rejecting the call because it was not allowed (or something similar).

Relevant config info (PRI channels start at 825):

A T1/PRI/BRI Clock Synchronization:
A Primary Secondary Tertiary
A 8/1 Loop
A Slot # 0: CKE5 CPU
Serial Number Not Available
A Slot # 8: 100D/CSU/DSU-U
A Serial Number 051645203433

A GENERAL TRUNK INFORMATION
A QCC QCC Extern
A Trk SS/PP RemAccess Pool TlPrfx HldDisc Principal Prty Oper Switch
A 817 6/ 1 No Remote 890 Yes Long 4
A 818 6/ 2 No Remote 890 Yes Long 4
A 819 6/ 3 No Remote 890 Yes Long 4
A 820 6/ 4 No Remote 890 Yes Long 4
A 821 6/ 5 No Remote 890 Yes Long 4
A 822 6/ 6 No Remote 890 Yes Long 4
A 823 6/ 7 No Remote Yes Long 4
A 824 6/ 8 No Remote Yes Long 4
A 825 8/ 1 No Remote 891 Yes Long 4
A 826 8/ 2 No Remote 891 Yes Long 4
A 827 8/ 3 No Remote 891 Yes Long 4
A 828 8/ 4 No Remote 891 Yes Long 4
A 829 8/ 5 No Remote 891 Yes Long 4
A 830 8/ 6 No Remote 891 Yes Long 4
A 831 8/ 7 No Remote 891 Yes Long 4
A 832 8/ 8 No Remote 891 Yes Long 4
A 833 8/ 9 No Remote Yes Long 4
A 834 8/10 No Remote Yes Long 4
A 835 8/11 No Remote Yes Long 4
A 836 8/12 No Remote Yes Long 4
A 837 8/13 No Remote Yes Long 4
A 838 8/14 No Remote Yes Long 4
A 839 8/15 No Remote Yes Long 4
A 840 8/16 No Remote Yes Long 4
A 841 8/17 No Remote Yes Long 4
A 842 8/18 No Remote Yes Long 4
A 843 8/19 No Remote Yes Long 4
A 844 8/20 No Remote Yes Long 4
A 845 8/21 No Remote Yes Long 4
A 846 8/22 No Remote Yes Long 4
A 847 8/23 No Remote Yes Long 4
A 848 8/24 No Remote Yes Long 4

A DS1 SLOT ATTRIBUTES
A Slot Type Format Supp Signal LineComp
A 8 PRI ESF B8ZS DMI-MOS 1

A CSU/DSU ATTRIBUTES
A Slot 8
A CSU: Activated
A Assigned Channels:
A DSU: Deactivated
A Data Port 1
A Receive Clock: DTE
A Invert Transmit Clock: No
A Invert Receive Clock: No
A Invert Transmit Data: No
A Invert Receive Data: No
A Rate: 64 kbps
A Assigned Channels:
A Data Port 2
A Receive Clock: DTE
A Invert Transmit Clock: No
A Invert Receive Clock: No
A Invert Transmit Data: No
A Invert Receive Data: No
A Rate: 64 kbps
A Assigned Channels:

A PRI INFORMATION
A Slot 8 Switch: 5ESS
A System: By extension Base number: 2034021100
A BchnlGrp #: Slot: TestTelNum: NtwkServ: Incoming Routing:
A 1 8 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 825
A 826
A 827
A 828
A 829
A 830
A 831
A 832
A 833
A 834
A 835
A 836
A 837
A 838
A 839
A 840
A 841
A 842
A 843
A 844
A 845
A 846
A 847

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: I 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 A
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 Any service Any service
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: 4 5 6 7
A NetkServ:
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:
 
Ok you said you only have 8 voice channels, but you have 23 programmed and 23 lines. remove all but the first 8 b channels and all but the 8 lines that are in the 891 pool. then make sure your outgoing calls are routed to that pool.
Then clear all your alarms and do a board renumber. When the system comes up check for those maint busies, there should not be any, or you have other problems.
Good luck

43 years in the business and counting.
 
memphisribs, thank you so much for your assistance. I've worked with Cisco voice gateways and PRI's before --- it's amazing how little diagnostic information there is to go on with the Magix in comparison...

I removed the inactive channels and lines. When I configured the Magix, I did not include them but later did so based on the recommendation of a telco installer (who also could not get the PRI working). I should note that he eventually recommended I replace the 100 DCD --- I did that and have the exact same symptoms so I don't think this is a board issue.

Anyway, I previously set up a special ARS table entry for testing outbound calls over the PRI (see below). Only A/C 907 (Alaska) is included to avoid interrupting normal calling over Pool 890 (our POTS lines).

I then cleared all Alarms via Maintenance -> Slot -> 08 <Enter> -> Error Events -> Clear -> All -> Yes.

Finally, I completed a Board Renumber via System Programming -> Start -> System -> Board Renum -> Yes.

Checking under Maintenance -> Line/Trunk -> 825 <Enter> ->
Status...Next... I see lines 825 through 847 with "Maintenance Busy: no".

BUT...line 848 (sspp 0824) shows "Maintenance Busy: yes". I tried a port Restore and got "Restore Successfully Completed" but when I check status it is back to "Maintenance Busy: yes".


After the changes, I am getting the same behavior --- fast busy dialing 907-555-1212 with error 4C03 and inbound call attemps busy with error 7001 on ports 0801 through 0808.

NOTE: there are Permament and Transient Errors in the log so I don't know if I attempted to clear them in the proper way.


Here is the ARS table entry and PRI information.

TABLE 5: Area Code
01)907 02)--- 03)--- 04)--- 05)--- 06)--- 07)--- 08)--- 09)--- 10)---
11)--- 12)--- 13)--- 14)--- 15)--- 16)--- 17)--- 18)--- 19)--- 20)---
21)--- 22)--- 23)--- 24)--- 25)--- 26)--- 27)--- 28)--- 29)--- 30)---
31)--- 32)--- 33)--- 34)--- 35)--- 36)--- 37)--- 38)--- 39)--- 40)---
41)--- 42)--- 43)--- 44)--- 45)--- 46)--- 47)--- 48)--- 49)--- 50)---
51)--- 52)--- 53)--- 54)--- 55)--- 56)--- 57)--- 58)--- 59)--- 60)---
61)--- 62)--- 63)--- 64)--- 65)--- 66)--- 67)--- 68)--- 69)--- 70)---
71)--- 72)--- 73)--- 74)--- 75)--- 76)--- 77)--- 78)--- 79)--- 80)---
81)--- 82)--- 83)--- 84)--- 85)--- 86)--- 87)--- 88)--- 89)--- 90)---
91)--- 92)--- 93)--- 94)--- 95)--- 96)--- 97)--- 98)--- 99)--- 100)---

Pool Absorb Other Digits FRL Call type Start Pattern
1)891- 00 -------------------- 2 VOICE 00:00 A
2)891- 00 -------------------- 0 VOICE 00:00 A
3)---- -- -------------------- - ----- 00:00 A
4)---- -- -------------------- - ----- 00:00 A
5)---- -- -------------------- - ----- 00:00 A
6)---- -- -------------------- - ----- 00:00 A

Pool Absorb Other Digits FRL Call type Start Pattern
1)---- -- -------------------- - ----- 00:00 B
2)---- -- -------------------- - ----- 00:00 B
3)---- -- -------------------- - ----- 00:00 B
4)---- -- -------------------- - ----- 00:00 B
5)---- -- -------------------- - ----- 00:00 B
6)---- -- -------------------- - ----- 00:00 B


A PRI INFORMATION

A Slot 8 Switch: 5ESS

A System: By extension Base number: 2034021100

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

A Channel ID: 8 7 6 5 4 3 2 1

A Line PhoneNumber NumberToSend
A 825
A 826
A 827
A 828
A 829
A 830
A 831
A 832

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: I 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 Any service Any service Any service
A Expected Digits: 0 0 0 0
A Pattern to Match:
A Digits to Delete: 0 0 0 4
A Digits to Add:

A Entry Number: 4 5 6 7
A NtwkServ: Any service Any service Any service Any service
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: Any service Any service Any service Any service
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: Any service Any service Any service Any service
A Expected Digits: 0 0 0 0
A Pattern to Match:
A Digits to Delete: 0 0 0 0
A Digits to Add:


A ERROR LOG

A Last 99 System Errors:

A Message ss/pp Cnt First Last Code
A DID INTERDIGIT TIMEOUT 04/05 - - 07/06 21:00:31 0C02
A DID INTERDIGIT TIMEOUT 04/06 - - 07/06 21:00:31 0C02
A PRI SVC AUDIT TIMEOUT 08/01 - - 07/06 21:06:17 7001

A Permanent Errors:

A Message ss/pp Cnt First Last Code
A PRI SVC AUDIT TIMEOUT 00/00 071 05/21 23:41:18 06/23 11:08:30 7001
A PRI SVC AUDIT TIMEOUT 08/01 143 06/12 17:34:21 07/06 21:27:16 7001
A PRI SVC AUDIT TIMEOUT 08/02 138 06/12 17:34:21 07/06 21:27:16 7001
A PRI SVC AUDIT TIMEOUT 08/03 138 06/12 17:34:21 07/06 21:27:16 7001
A PRI SVC AUDIT TIMEOUT 08/04 138 06/12 17:34:21 07/06 21:27:16 7001
A PRI SVC AUDIT TIMEOUT 08/05 138 06/12 17:34:21 07/06 21:27:16 7001
A PRI SVC AUDIT TIMEOUT 08/06 139 06/12 17:34:21 07/06 21:27:16 7001
A PRI SVC AUDIT TIMEOUT 08/07 139 06/12 17:34:21 07/06 21:27:16 7001
A PRI SVC AUDIT TIMEOUT 08/08 139 06/12 17:34:21 07/06 21:27:16 7001
A PRI SVC AUDIT TIMEOUT 08/09 251 06/12 17:34:21 07/06 20:40:00 7001
A PRI SVC AUDIT TIMEOUT 08/10 251 06/12 17:34:21 07/06 20:40:01 7001
A PRI SVC AUDIT TIMEOUT 08/11 250 06/12 17:34:21 07/06 20:40:02 7001
A PRI SVC AUDIT TIMEOUT 08/12 250 06/12 17:34:21 07/06 20:40:03 7001
A PRI SVC AUDIT TIMEOUT 08/13 250 06/12 17:34:21 07/06 20:40:04 7001
A PRI SVC AUDIT TIMEOUT 08/14 250 06/12 17:34:21 07/06 20:40:05 7001
A PRI SVC AUDIT TIMEOUT 08/15 250 06/12 17:34:21 07/06 20:40:06 7001
A PRI SVC AUDIT TIMEOUT 08/16 250 06/12 17:34:21 07/06 20:40:07 7001
A PRI SVC AUDIT TIMEOUT 08/17 250 06/12 17:34:21 07/06 20:40:08 7001
A PRI SVC AUDIT TIMEOUT 08/18 250 06/12 17:34:21 07/06 20:40:09 7001
A PRI SVC AUDIT TIMEOUT 08/19 250 06/12 17:34:21 07/06 20:40:10 7001
A PRI SVC AUDIT TIMEOUT 08/20 250 06/12 17:34:21 07/06 20:40:11 7001
A PRI SVC AUDIT TIMEOUT 08/21 251 06/12 17:34:21 07/06 20:40:12 7001
A PRI SVC AUDIT TIMEOUT 08/22 251 06/12 17:34:21 07/06 20:40:13 7001
A PRI SVC AUDIT TIMEOUT 08/23 251 06/12 17:34:21 07/06 20:40:14 7001
A ABK EXTENSION BUSY 00/00 001 06/21 02:00:00 06/21 02:00:00 0404

A Transient Errors:

A Message ss/pp Cnt First Last Code
A NOT IN NORMAL OP MODE 05/00 092 05/01 22:01:55 07/06 21:34:29 7801
A BOARD RENUMBER 00/00 008 05/01 23:00:23 07/06 21:34:07 5802
A DS1 MISFRAME ALARM 08/00 001 06/18 15:00:16 06/18 15:00:16 6C09
A POWER UP COLD START 01/00 002 07/01 11:15:34 07/06 10:37:24 0016
A DID INTERDIGIT TIMEOUT 04/05 005 07/01 11:16:08 07/06 21:34:33 0C02
A DID INTERDIGIT TIMEOUT 04/06 005 07/01 11:16:08 07/06 21:34:33 0C02
A POOL BUSY &/OR OOS 00/03 012 07/02 01:48:11 07/06 21:38:35 4C03
A DID INTERDIGIT TIMEOUT 04/02 001 07/06 10:28:50 07/06 10:28:50 0C02
A DID INTERDIGIT TIMEOUT 04/01 001 07/06 10:29:17 07/06 10:29:17 0C02
A SOFTWARE COLD START 00/00 003 07/06 18:12:28 07/06 21:33:56 0003
A NOT IN STANDBY MODE 05/00 006 07/06 18:12:33 07/06 21:34:01 7806
 
Use the last 8 lines on the board (840-847) then the D Channel is 848. I know it shouldn't matter, but I have had partial PRI's that wouldn't come up when programmed with the first 8 channels, but when moved to the last 8 channels on the card it came right up. Worth a try. I doubt it's equipment related.
 
Make sure you change your B Channels to the last 8 on the module as well.
 
Well, I am not sure about using the LAST 8 Channels for the B Channels. I would first verify just where the Provider has put them.

On this PRI stuff, you can't guess, you have to know.

What do the errors look like?

How does the T1 itself look?

Has this EVER worked?



 
Telecommboy, I removed channels 1 - 8 and added channels 16 - 23, then removed lines 825 - 832 and added 840 - 847. Finally, I removed 825 - 832 from poll 891 and added 840 - 847.

After clearing errors and renumbering the boards, I got the same result.

Merlinman, this is a new PRI and has not yet been operational. The errors are 7001 (PRI SVC AUDIT TIMEOUT) on ss/pp 08/01 through 08/08 --- this did not change after changing the channels and lines per Telecommboy's recommendation --- and 4C03 (POOL BUSY &/OR OOS) for outbound attempts. I think channels 0801 - 0808 were in fact correct and agree with the provider's information. The T1 (converged PRI) has Carrier Detect and no Alarm --- it has been this way throughout all of the changes / troubleshooting so low-level signaling is good.

At this point all I can say is:

1) The Magix has incredibly disappointing error/event logging detail.

2) I'm VERY impressed by the response from the Tek-Tips community. Thank you all so much for helping out a total stranger. You're all good people.

Does Avaya offer pay-per-incident support? I'd like to make someone there sit through this tedious excercise out of spite... :)

P.S. My ARS table uses area code 907 so my first successful call can be to wish Sarah Palin well...LOL
 
For testing purposes, you can also assign the Pool Dial Out Code 891 to your extension, then dial it instead of 9 for your outbound call.

I have also set up partial PRI's where the carrier insisted that they were going to enable only the last X number of channels. But they were still sending IN calls on the first channels. So I simply enabled ALL 23 channels, and only put those last X channels in the pool.
 
Thanks, TouchToneTommy.

That would be similar to how I had things configured at the start tonight with all channels defined --- outbound could have failed with a channel number mismatch, but inbound should have worked based on the exmaple you site.

I'm at a loss for now....I'll pick up on it again tomorrow.

In the meantime, thanks for the help.

P.S. Remember Jenny / 867-5309? Sorry, that was Tommy Tutone not TouchToneTommy :)

Cheers.
 
Good luck tomorrow-

OT: We gave a customer's computer geek access to a Partner Messaging to configure Unified Messaging - "867-5309" is what he changed the system administrator's password to without telling anyone. Although we could have changed it back using the backdoor p/w, we made the customer confront the jerk about why he changed it!!
 
I would follow TTT's instruction about all 23 channels. If anything you won't have to add them later when the client wants more channels. Why only 8? Does SNET charge by the BCH for PRI?

Several things:
Make sure that the DCH is NOT in any pool or anyplace else. It could cause it to malfunction.

If all the DS1 conditions are proper, no Yellow, Red, or Blue alarms, then you probably have a Telco problem. What kind of testing did they do? Did they verify the DCH is INSERVICE IDLE? And what about the 8 BCHs are those INSERVICE IDLE?
In the 5ESS, the tester has to set the trunks INSERVICE, otherwise they won't stay up if in test mode. So what you need to do is, open a trouble ticket with repair service and request test assist. The tester or Customer Translations Group needs to UNBUSY the DCH TRUNK GROUP and the BCH TRUNK GROUP. Then do callthru testing both inward and outward to verify what is/is not working.

I have covered this material in previous posts along with many other members, since PRI is very popular on this forum. It would be a good idea if you took the time and read some of those for your own info, it could save you a lot of time in the future in addition to documentation on the Magix.

Next, what is your Dial Plan? How many digits are being sent for the stations? You did not mention what station format you are using. I did notice that you populated the Base Number field. The CID is very limited on the Legend/Magix, so you might want to tell us what you plan to do, and we can advise accordingly.

Let us know what your results are.

Hope this helps!

....JIM....
 
We're up and running!

I ended up putting just the lower 8 (active) B-Channels and associated lines in the B-Channel Group (1) and the same lines in the dial out Pool (891) --- but I am certain there is no harm to adding them all.

When I called in to bring up the circuit, they showed the D and B Channels IN SERVICE, IDLE.

HOWEVER, the person I worked with a week ago left the Cisco IAD (to which we connect for the PRI signal) configured for NI-2, something we tried as a last resort before deciding to replace the 100 DCD.

The guy I worked with today set it back to 5ESS and BINGO!!!

SO...replacing the module, cleaning out some of my test configs, and getting the switch on their side back to 5ESS did the trick.

In the end, I wish the resolution turned out to be more challenging given all of the support I received from the Tek-Tips community... :)

Sincere thanks to all for your help.
 
I am glad you are up and running! Alls well that ends well!

....JIM....
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top