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

Legend PRI - AT&T Custom vs. National

Status
Not open for further replies.

Pepperz

Programmer
Jan 31, 2002
1,279
US
I'm being told maybe rightly, maybe wrongly that the local SBC Switch a Lucent 5ESS will only be administered with National Protocol, not AT&T Custom. They are telling me that they "can't" (won't is more likely) send the AT&T Custom.
Will this work, and how well will it work?

Pepperz@charter.net
 
The Legend/Magix can not do NATIONAL protocol.

I'd be willing to bet they can make it work with CUSTOM protocol.

I'd try to find out if they have other PRI Customers with LEGEND/MAGIX.
 
MM, I think it's one of those tarriff things. They probably have to pay more if it's AT&T Custom, or something. That's my take on it.
Thanks

Pepperz@charter.net
 
It may be that issue. Perhaps the customer may want to look at another provider.
 
MerlinMan,

I was told by a tier 2 tech that these systems were designed in the late 80's early 90's and there was no national protocol back in the day. That is the reason why they can't accept a NI2 setting? Any truth in that?

 
What SBC end office is involved and are you dealing with the SBC Consultant/Vendor Sales Group?
Alot of times the regular BO doesn't know what is going on or doesn't know where to go to get the right info....

....JIM....
 
It's someone selling SBC - that's why I think it's a quirky scenario.

Pepperz@charter.net
 
The Merlin Legend Release 1 was designed back in the late 80's/early 90's. But by now, I would think that you are at least release 5, hopefully Release 7. The Release 7 was NOT designed in the early 90s, but the later 90's.
 
Here's what I since found out: There is a "custom" protocol they use , not necessarily AT&T Custom, just custom, and a National 2 protocol which can also be referred to as standard. Apparently the AT&T Custom is older, and there is a gentle push to standardize on the more recent protocol version, BUT they will (if they feel like it) switch protocols at the time of cutover to make things work.

Pepperz@charter.net
 
I would say try the one they want to start with and see if it works.

It would be great if we could get them to gives enough details about whatever one works that we could ask for it next time around.

Who knows, it may even help them sell that type of service as well.

 
MM that's the way we started - National 2 - didn't work, they were abel to change to custom - poof, it worked. Got to keep the bureaucrats out of the technical jobs.

Pepperz@charter.net
 
Hey watch it! I'm still doing technical stuff, and I was once one of those.....

Oh well...
 
Don't know about that?
You always seem to know what you're doing!

Pepperz@charter.net
 
The NI2 protocol works fine if you are using a DMS-100 switch setting. I just cut 2 over. I have never tried anything but custom on a 5ESS.
 
I have had vendors say they cannot configure "custom" as well. If you tell them to configure it NI1 (which is the same thing) instead of NI2, then they were able to place the order. Just an issue of the service provider not knowing that custom and NI1 were the same thing.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top