Please help. I have a Lucent Merlin Legend with a 100D card and am trying to configure a PRI circuit with AT&T. They can see the D Channel activity but the B Channels will not come active. I am using 5ess , SFR, etc. I think I have all of the config right on my end I have run through it a hundred times. The card is getting the clocking from the PRI sucessfully...... any thoughts? Thanks Ralph

Ralph,
Make sure you programmed B-channels right. Will be nice to have print out of your Programming. Ask AT&T to make sure they set up for Custom 5ESS not for N2 protocol. What is SFR? You probably mean ESF. If you are not familliar with Legend it is not a lite wolking at all.

Ditto, Legend/Magix doesn't play nice with NI2.

SFR might mean Super FRame. ISDN/PRI circuits need to be provisioned as ESF/B8ZS.

Yes you are right I did mean Extended Super Frame. It is 5ESS not N2 and I do have it set for B8Zs

I am a novice at this type of programming. I did download the manual and it is worse than reading VCR instructions

I have a good friend who is a CTI and we have both looked at it and are somewhat stumped.

I will pull all the info and post it tomorrow when I am back in the office. Thanks for your help

What is a CTI??

Sorry I meant he is a CTI integration specialist and works with Definity switches all the time.

The config is

Type PRI
Frame Format EFS
Supression B8zs
Signaling Common channel
Line Comp 1
Channel Unit Foreign Exchange
Net Service 5ess - 56/64 digtl
Inc Rtng route by dial plan
Number to Send Line tel Number
Switch type 5ess
The controller and internal loopback tests passed but the CSU loopback failed with the first line all 003 and the following lines all 004

Thanks

Ralph

I would change NET SERVICE to "NO SERVICE".

At least that's how I set all of mine up.

Also, are there errors on the Module?

How are your LINES setup?

I will make that change. There are erros on the module but no alarms

What line set up are you asking about? I have them assigned to a call group

on the net service the options included AT&T toll 5ess a couple of others and miscellaneous. I selected miscellaneous and call by call

"line set up" - Are they in a pool?

Also, if this is call by call, it would not do you any good to assign them to a calling group.

In reality, there are no " RINGING LINES" per se in a PRI. Therefore, assigning them to a calling group will gain you nothing.

Yes they are in a pool. I can change the call by call. That was the option that for the miscellaneous under net service there was not a No Service option.

I thought you had to assign the ports to a calling pool so the incoming calls are routed to extensions (Auto Attendant)

For Outgoing Routing go to Service > Misc > No Service
For Incoming Routing go to Service > Misc > Any Service.

Include in your posting set up for all your Options. Then we can help you.

Clear all Alarms in Maintanance. Reset and Restore T1 card.

Thanks I will give it a try.

double check the carrier to make sure they are 5ESS and custom protocol. Keep in mind that switch type and protocol type aren't the same. The carrier can set there switch type to 5ESS and NI2 protocol, which will not work. You need switch type of 5ESS and custom protocol. You can use NI2 if the switch type is DMS 100 or DMS 250, but the Legend has never seemed to like anything outside of 5ESS/Custom. I think it was purposeful built that way... :confused:

Thanks to all. I have the card configured now with no alarms and no errors. I am waiting to hear back from AT&T to make sure they are using the correct protocol

Thanks

Ralph

It looks like AT&T is using NI2 and the project manager said he was not familiar with AT&T custom. Does anyone have specs I can send him?

Thanks

Ralph

You don't need to send specs to the project manager, you need to work with somebody that's REALLY in the telecom business.

I seriously can't believe that the PM has never heard of custom protocol. This is your biggest barrier to success right now.

Oh sure, I can send you my PRI "cheat sheet" if you're concerned about programming mistakes but, in the end, it may not be much help. Perfect programming is no match for uneducated people that are involved in the implementation cycle (and I DON'T mean you...you always have us on your side to help if needed).

I hear you. This has been very frustrating AT&T isn't what it used to be

Blaming AT&T is silly .... neither you nor your CTI have the correct qualifications or training to program this .. and the 500 page manual is difficult to understand at best.

Bring in an experienced Legend tech and this thing will be working in a flash.... certainly within a couple of hours.

The legend, nor most phone systems, are not easy to learn and to try and cut your teeth on one, especially involving a PRI, is not the best way to get your system running properly.

My reference to AT&T has to do with a lack of support and service/numerous missed dates. This circuit was ordered on January 19th with a due date of February 15th. They only began trying to turn it up a couple of weeks ago, a full month after we moved into our new facility. Each of the technicians are telling me something different and when I asked about the AT&T custom protocol I was told they did not know what that was.

I am happy to admit that I am under qualified for this programming and have engaged an experienced legend tech to help in this final stretch. However it does appear that the programming I did is all correct.

Like you I do not like finger pointing, just disappointed in the service I have received.

Success!! thank you all for your help Once the AT&T protocol was set and 1 routing change everything worked fine.