T1 and Merlin Legend

[zeromeg]

Had a point to point T1 between two systems. That got removed and a T1 for voice was ordered. I configured the board per the carrier but it didn't seem to work. They came out and were able to directly connect to the circuit and make test calls.

The board was working with the point to point so I'm thinking it is something in the old programming that is stuck in there causing this not to work.

I'm wondering what could be wrong? Is there a way to set the board related programming back to factory and start over or is there something else that I'm missing?

Thanks in advance.

 

[franke]

The only way to 'reset' the module is to reset the entire system back to factory defaults and start over. Barring that, we would need to know how the p to p was programmed (i.e. as a PRI, TIE lines, drop and insert, etc) and how it is now to be setup. If this is going to be a PRI, make sure that the C.O. is set as 'Custom' and not 'National'.

franke

 

[zeromeg]

Thanks for the response. Is it that there is programmed system wide that needs to be cleared? I could take the module and put it in another system.

The p to p was to connect this location to another. The other system was where the voice mail was located. Voice mail was added to this system and the two disconnected from oneanother.

They had a series of phone numbers that travelled over the p to p where the voice mail on the other system answered and directed the calls typically back over the p to p to extensions in the current location. Unanswered calls would go back to the voice mail.

The only programmed we tried to address was with the new circuit so there could be things that the previous folks configured that I don't know about including passwords for the 100D board.

Dunno if that is helpful enough for you to give further advice or not.

FYI - It seemed that after setting the circuit to PRI that it would not let me select "CUSTOM" over "NATIONAL". I believe there was one other setting that I could only set if I configured it as a T1 instead of a PRI.

 

[SYQUEST]

Hi zeromeg,

Both T1 & PRI in the Legend have specific parameters programmed per customer and system requirements. You need to print out the system config and compare the parameters with what was ordered from the telco or service provider inorder to determine what the problem is. You might also post it on the forum if you have more questions so we can see what you are talking about.

You might read older posts covering this same subject. It has been covered many times!

Hope this helps!

....JIM....

 

[zeromeg]

This is what I was given:

Line Coding/Framing: B8ZS/ESF

PRI - NI-2

4 digits being sent

 

[SYQUEST]

Hi zeromeg,

For PRI if your CO switch is a 5ESS the protocol needs to be AT&T CUSTOM, the Legend won't work on NI-2. If it is a DMS100 it is different, and I don't have the docs @ hand, but if you go back and check some of the older posts on this forum you will find the info. One of them has an Avaya PDF doc you can you can download that covers most of the specs!

Hope this helps!

....JIM....

 

[Pepperz]

NI-2 for DMS 100, 250, 500.

Pepperz@charter.net

 

[zeromeg]

Carrier is saying that they came out with test equpiment and hooked up to the module and couldn't get a carrier so they are saying that the issue is in layer 1 not layer 2. The module was being used up until the point it got connected to this new T-1. It was being used to connect via p-to-p to another location for attendant and voice mail.

Could they test the card in that fashion without previously having been busied out prior to them hooking up their equipment to the plugs on the face of the module?

Carrier is suggesting getting a new module. Can I try a 100INA board in a Merlin Legend to act as a 100D instead of getting a new module at this point? Or does someone have a suggestion as to what I should try?

Thanks!

 

[killbox]

I had this problem before myself. I had to put the card back to T1, and the next tier of that (All Tie) and remove all the trunks from there. Then I re-programmed it, busy, reset, and released the board.

Anyway, I set it to PRI, then go into PRI, add all your b-channel (Slot Number and channel (0201,0202, etc)). Then add your lines in under the b-channel page.

After that you need to set your switch type. See if they can send 5E instead of NI-2.

You don't need another board. THe programming is in the processor, not the board. You just need to adjust the programming.

KILLBOX

 

[zeromeg]

They reprovisioned the circuit as a straight T1. I revised the configuration to match what they provided and they can now see me and the circuit is up.

I now need to do the rest of the programming to configure the T1 to work with the system so I can do some test calls.

Is the procedure for a T1 to be used this way available somewhere. I've been searching and thought that it was provided previously in a post. I did get the PRI one previously but the provider switched it a to straight T1 instead of making the couple of tweaks we requested. I have never done a non-PRI setup.

 

[SYQUEST]

If you go to Avaya's website you can download the manuals. T1 is covered in the System Planning, Network, and the Installation practices and even has some examples and steps. You also need to know how your service provider is setting up the channels, ie loop-start, ground-start, or E/M, etc.

You need to get ALL the parameters for the T1 and the channels.... This way you can have a perfect match!

Hope this helps!

....JIM....

 

[zeromeg]

Still trying to get this going. I attempted to setup the channels as DID Wink as they suggested but after setting the channels to all DID I then try to assign the lines to the block but it won't take them.

There is a 800-DID board in the system current and 6 lines are in block one and two in block 2.

Is having those the problem? If so, what can I do? If not, what do I do?

100DCD is in slot 5 and shows 8217-8240 as the lines. The 800DID is in slot 6 and shows 8241-8248 as the lines.

Circuit is configured as a T1, ESF, B8ZS, Robbed Bit.

 

[SYQUEST]

Hi zeromeg,

Since the service provider changed the T1 configuration, what parameters did they assign?? DTMF, digit feed, number blocks? Are they two-way trunks?

If they are two-way, they should be E/M TIE and you can assign them to a pool by using SS/PP, slot and position (05/01 thru 05/24), not the logical port! If they are DID inward only you don't assign them to any pools.

As a point of information, DID trunks and E/M TIE trunks on T1 have the same signalling bit pattern. They are either on or off, the AB bits are toggled together. Also called two state signalling.....

Hope this helps!

....JIM....

 

[zeromeg]

They are referring to it as a wink start t1. They told me to use this information: T1, ESF, B8ZS, Robbed Bit and to configure the lines as loop start with wink. They said that 4 digits were being sent and that they were porting onto the T1 the customer's main number and a set of numbers corresponding to 4 digit extensions 398-6300 to 6359.

Those numbers all relate to incoming calls. Currently they have an 800DID and they get 3 digits sent with a 6 added in front. I see lines from 8210 to 8248 configured in the system with 8201-8216 being POTS into 408 modules. 8217-8240 are noted on the 100DCD. 8241-8248 on the 800DCD board. Currently 8241-8246 are in DID block 1 and 8247 and 8248 are in block 2.

I have a straight cable from the T1 smart jack straight into the 100DCD. I set the type to T1, frame format to ESF, suppression B8ZS, signaling to robbed bit. I left line comp as 1. How do I know what Channel Unit should be set to?

I did a CSU loopback test and they saw it. I then set the T1 to All loop start. I didn't do anything else to configure the lines. Module shows errors with the Red light and Yellow lights on.

I told this to the provider and they suggested trying DID wink.

I then set all to DID and then attempted to put the lines using the numbers 8217, 8218, etc... into the blocks. The blocks are set to Wink. Remember I have DIDs already setup at this point. It didn't let me. FYI - module still showed errors with the Red light and Yellow lights on.

 

[zeromeg]

FYI - Checking the error log is see that those ports are showing "Stuck Ringing" error code 840C.

Also, I noted PRI errors. There isn't a PRI error.

Also, I inexpected the channels in setting it to T1 and then trying to switch from Loop Start to somethig else and it shows all as -L. I then selected "All Unequipped" and tried "All DID" and "All Tie" but that doesn't change. Trying to do a single channel just beeps.

 

[SYQUEST]

First of all the provider gave some wrong info, "to configure the lines as loop start with wink." -This is incorrect, loop-start IS NOT for DID and DOES NOT wink! You will need to configure the channels as T1-DID or T1-TIE, which ever is appropriate. The reason you are getting the 840C error code on the T1 module is because of the channel configuration. It shows 'stuck ringing' because the signalling bit pattern for loop-start is different for DID/EM, so the Legend thinks it is stuck with the ring bit on continuously.

Concerning the DID numbers and digits sent, since your existing is 3D with the Legend adding '6', I am assuming your dial plan has 4 DIGIT stations. There are a couple of ways to deal with the conversion. If you have the same provider, have them change the digit feed on the analogue DID trunk group to 4 DIGIT from 3 and delete the '6' digit added by the Legend to default. This would simplify testing and cutover. If not you can delete the added '6' when you cutover traffic to the T1, but you won't be able to place test calls because of the 'digits conflict' before cutover.

What do you mean by Channel Unit? Do you mean Channel Service Unit or CSU?

Remember you add the T1 channels/trunks by SS/PP, slot/port, not by dial plan assignments! So your T1 in slot 05 has channels 05/01 - 05/24 to be assigned as required. Now you may have some stuff left over from previous that needs to be defaulted or removed that may be causing the programming problem.

If you have not, do this: print out the Dial Plan, T1, PRI, and Trunk information. This way you can see what is there. This will make things easier to spot problems so you can fix them. If you want, you can post the printouts on TEK-TIPS, that way we can all see them. That goes for the error codes also.

On the 100DCD module the Yellow indicates channels in use or seized. The Red is an alarm condition. Does your CSU show an alarm from the Legend? You may be able to put a loop up in the CSU toward the Legend. This will tell you whether you have continunity between the two. Also check to see what leds are lit on the Telco's NIU at the demarc. You did mention that the provider tested OK with a loop....

Hope this helps!

If I missed anything let me know.

....JIM....

 

[zeromeg]

Thanks for taking the time to reply. I tried 8217 and also 0501 and neither would take. Something is keeping those lines stuck as Loop Start. I tried "All TIE" and just TIE and trying to select a single channel with no luck. They are still showing as -L. It lets me do the All TIE without telling me there was a problem but when I try just a single channel it beeps at me.

I'll print everything out to see what I can pick out that might be a problem. If I can't, I'll post it.

As for the last paragraph, doesn't the 100DCD have a CSU built in? The circuit is strictly voice.

We created a loopback straight from the smart jack and then also had the 100DCD do a loopback and the provider saw both properly. They have left the circuit up at this point since they saw layer one, I just haven't been able to configure it properly to test the next step.

 

[zeromeg]

In going through the reports I found some stuff on the PRI info that needed to be cleared out. It showed channels 1-21 in B Channel Group 80. It wouldn't let me remove the "Lines", would just beep. I was able to delete the channels and I cleared out the other settings.

 

[zeromeg]

Ok. I switched it back to PRI and then was able to remove the lines. I then switched it back to T1 and the channels were all unassigned. In restoring the slot all lights were then off. I was then able to make all "TIE". Still showing all lights off.

I set the trunks as two-way and the in/out as "Wink". The one thing I'm not sure of is if they should be Type1S, Type1C, Type5, etc... What does that mean? They are currently Type1S.

 

[merlinman]

1S is the most common, and usually what you should use.

If they work, don't worry, be happy!