Merlin Magix PRI Setup 1

[ph3189]

I am currently trying to install a PRI line on a Magix R2.1, but I am having trouble getting the D-Channel to work (PRI D-CHNL INOPERATIVE). The phone company setup the switch as DMS-100 and NI1 and we tried 5ESS as well, but it still doesn't work. The carrier comes up and we can get the line to work with a test set, so I think I have something wrong on the system.

I set the DS1 card for PRI ESF B8ZS and the switch type is currently set to 5ESS... Any ideas?

 

[gregarican]

As long as the DS1 agrees on the ESF and B8ZS then you have a baseline of service. But for the PRI functions to work (i.e. - D Channel signaling) you need to ensure the following items agree:

1) LinesTrunks-->PRI-->Switch Type = 5ESS (or whatever the last type telco set their end to)

2) LinesTrunks-->PRI-->B-ChannlGrp-->NetworkServ = 5ESS (or whatever the last type telco set their end to)

3) LinesTrunks-->PRI-->Protocol-->Timers = check with your telco carrier

4) LinesTrunks-->PRI-->Protocol-->TEI = check with your telco carrier

The first two items should be straight-forward, as if telco designates this circuit as being 5ESS then Merlin needs to look for this on the D and B Channels.

The last two items really aren't modified much as a rule from what I've run into. But nevertheless you still can verify what telco's end looks like.

 

[ph3189]

Thanks for the reply... Those are the settings I have, and the telco carrier set the switch to 5ESS and it still isn't working. Any other ideas?

 

[gregarican]

If you have verified the switch type, line coding, frame format, network service, etc. then I would suggest verifying that they are giving you a Terminal Equipment Identifier of 0. This is the default that Merlin looks for.

If this checks out then perhaps perform tests on the card itself through Merlin programming. You can perform Internal Loopback and Board Controller tests through Maintenance-->Slot-->Demand Test as long as the card is busied out.

Are there any other messages of note in the main System Error Logs (other than the D Channel failure)?

 

[ph3189]

TEI is set to 0 on both sides. I tried running the tests and it seems to be working ok, but I might be missing something. I am going to get a new card and try that. There are 2 other errors... INVALID SANITY RESPONSE and COMMAND BUFFER FULL. But the errors are not as consistent as the PRI D-CHNL INOPERATIVE error. Also, I tried running the PRISwTypTest and that Failed (I don't know if that means anything or not).

 

[gregarican]

As far as I know the PRI Switch Type Test is typically run when choosing Merlin private networking (i.e. - both ends are Merlin forming a private point to point link). I don't think it will do much in terms of testing a PSTN circuit.

If you are seeing Invalid Sanity Response (7804) error this indicates the internal sanity testing indeed didn't receive proper results. If the slot number coincides with the DS1 card you're working with, try resetting it. Since you've worked on the board awhile programming it I'd assume that the reset has been done.

The Command Buffer Full (000E) error is more indicative of processor board issues. Not being able to handle the amount of instructions being thrown to its memory resouces. This shouldn't happen too often. If it's consistently happening then perhaps the processor board is flaky. But I wouldn't think so.

The Invalid Sanity Response error is a little more crucial in my opinion. My gut reaction without being there is to try replacing the DS1 board. If you can swear up and down all of the provisioning settings match with telco and that the circuit tests good at the telco NIU then that's all I can think of.

Did you run the Board Controller and Internal Loopback tests? How did these go?

 

[ph3189]

Ok, I got a new board and I have the same problem. We even switched it back to DMS-100 to try that again. The SwitchType is now set to DMS-100 on the DS1 card.

Maybe the Channel Unit Selection is wrong... I have Foreign Exchange selected. Should it be Special Access?

Or maybe the B-Channel Group --> NetworkServ is set wrong because I have DMS-100 Local and then DMS-FX.

The telco carrier has a DMS-500 Switch that is now set to DMS-100 and Public (I didn't see an option for public so I chose DMS-FX)

 

[gregarican]

It sounds like you've tried to eliminate the Merlin end. I would really put the push on telco to verify what they are sending you. Changing all of the those settings back and forth I can't imagine that things are on the same page.

I know that the most recent circuit local telco brought in for me wasn't even handing off between carriers. It sat there with a blue alarm for two days until I convinced them to contact the other carrier along the way to ensure their part was provisioned.

The Channel Service Unit setting is intended for T1 facilities that emulate loop/ground start trunks. For PRI it shouldn't really matter. And Foreign Exchange is usually the default anyway.

Is the circuit going through another device between the telco NIU and the Merlin? If it's going through a drop and insert device or something like that you should have a crossover cable going between the middleman and the Merlin.

To me it still sounds like telco isn't giving you Common Channel Signaling in terms of what they say they're sending.

 

[franke]

ph3181, you are correct in your setting of 'Foreign Exchange'. What I did not see mentioned in your posts was your clock settings. Is your Primary Sync. clock set for local or loop (or not set at all)? You can verify this under maintenance > slot > clock. It should show you who is providing the sync. (it should be set for loop) it should also show you if the clock is activated (it should be).

franke

 

[gregarican]

Clock Synch! Good call. I forgot about that item. If this is the main PSTN link then it defintely should be set to Loop. I never paid attention to see if Merlin defaults to one or the other (Loop or Local). franke, do you know what it defaults to?

ph3181, please let us know what the final verdict is on this issue. I know I'm anxious to find out what the problem was!

 

[ph3189]

I set LinesTrunks-->PRI-->B-ChannlGrp-->NetworkServ = to DMS-100Local and DMS-Outwats and that brought the D-Channel up. Now I just need to figure out how to get the B-Channels all online. The first channel is up, but the rest are still down.

By the way... thanks for all of the help!

 

[gregarican]

The B-Channels should typically be an all-or-nothing 23-port situation (unless it's a frac PRI of course). Try resetting the DS1 module again and then checking the individual port statuses. Maybe these need to be reset too?

 

[ScoTTeL]

I posted to a similar question a while back. I have a sheet put out by avaya help for setup of PRI. It is the basic setup to get everything going. Any funky stuff you can modify later! Email me at EScottel@juno.com I will send it to you.

 

[ken07734]

I have some info on PRI w/ 5ess maybe it can help.





PRI INFORMATION



Slot 15 Switch: 5ESS

System: By line

BchnlGrp #: Slot: TestTelNum: NtwkServ: Incoming Routing:
1 15 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
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839

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 OP OP OP/P OP none none none
Type of Number: I 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: BOTH 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: No Service
Expected Digits: 4 0 0 0
Pattern to Match:
Digits to Delete: 0 0 0 0
Digits to Add:

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:

 

[Merlin101]

The PRI programming info shown above is incorrect, though it is close. You've replaced a module for nothing. The biggest problem you have is in the network settings. Check with Avaya Tech Support, or better yet, call their office and get a service order and a tech on site, and they can save you all the time and WAGS that have shown up so far...if you have the money to replace a DS1 board, it would be wise to contact somebody who is really technically proficient on the equipment.

 

[ken07734]

The info I posted is of an operational system, It was given to assist in programming as a guide not for the actual programming. It is for 5ESS and has experienced NO troubles in the past two years of operation. As posted I stated "maybe it can be of help"

 

[franke]

ken07734, although your example is 'mostly' correct, the entry you have at NtwkServ-"No Service" should actually be "Any Service". The switch basically stops looking for matches when it reaches a "No Service" entry. By placing it in '0', you will prevent any call processing. Although it's not imperative to have a "No Service" entry, it is usually a good practice to place it immediately after your last "Any Service" entry.

ph3189, if you are still having problems, you may want to verify that you T1 vendor is optioned for "Custom" and not "National". The Merlin and Merlin Magix systems do not recognize the "National" protocol. The protocol for the DMS100 and other Nortel switches is "NTNAPRI". It may also be necessary for them to set the field "L1 flags" in the "Trunk Sub-Group" table to "yes" when optioned as a DMS100. The protocol for the 5ESS and other similar switches is "AT&T Custom".

It is important that the protocals match as it affects how the 'D' and 'B' channels are brought up.