magic pri cut

[DaveThePhoneDoctorLV]

The KSU has the Avaya Merlin Magix name on it. They want to port their existing XO Communications PRI and DID over to Cox.

We don't have any Merlin Magix support here in town that I can refer to the customer.

What should I expect to have to perform for this customer prior to the cut and on the day of the cut.

I understand that I will need to provide COx with some information and then will I have to configure anything in the Magix?

Should I continue this thread here?

Thanks

 

[TouchToneTommy]

You're in the Merlin forum, and the Magix is a Merlin Magix, so you're in the right place.

Pull printouts of the configuration, preferably the "ALL" report, but at minimim the PRI, T1, ARS, Trunk General, System Setup, Dial Plan, and Extension Directory reports.

System has existing service, and is porting to the same service from a different CLEC. If they match everything, you should only have to pull the plug from the old and connect to the new.

Good luck!!

 

[DaveThePhoneDoctorLV]

I have worked on the Merlin key systems but not the Magix.

This system does not have a printer attached to it. How do I pull a report?

Yes, this is up and running and all services to all lines and extensions are current, VM, AA, DID etc..

 

[SYQUEST]

If you do some searching on the Merlin forum, there is a lot of stuff that has been posted about PRI ISDN for the Magix & Legend. Check the FAQs, etc. Not knowing the area that is serving your client, Cox may be using 5ESS switches for their customers (they do in California). That makes it easy for them to provision PRI for the Magix. The required protocol is AT&T CUSTOM! There are NO exceptions! You really should not have to change anything on the Magix, but it would be a good idea to print the configuration so you have a hard copy for reference and testing. Cox may also provision the DS1 via fiber, since they can't do it on COAX. Make sure you identify all the DID numbers the client has in the process of switching providers, and make a check list.

As far as printing the configuration, using SPM you can save it to a file, then print it from your computer.

....JIM....

 

[DaveThePhoneDoctorLV]

here is what cox is looking for, they sent this to me today:

Make, model & Software version of the PBX
 
PBX Trunk Selection Sequence - Ascending (Bottom Up), Descending (Top Down) choose 1.
 
Variant - NI2 or NI1?
 
How many digits are needed to be sent from the Cox Switch to the PBX?

 

[ritelcarlos]

NORTEL NATE

WHERE ARE YOU LOCATED ?

 

[DaveThePhoneDoctorLV]

Las Vegas

 

[DaveThePhoneDoctorLV]

One of the things this customer needs me to change at this time before the cut is the following:

They are a shared tenant facility. One of their new tenants who has a DID number wants the receptionists to answer their calls.

How can I program the attendant to cover this users calls. They want her to answer if they can not.

BTW this customer bought this shared tenant business about a month ago and the original owner did not have any documents for the new owner. I was referred to them for help.

I would like to start to train myself on the Magix, I am a fast learner.

 

[Dexman]

Avaya has documents for many AT&T/Lucent/Avaya systems available for free download on it's website.

Securing a copy of WinSPM (the remote administrative software for the Merlin Legend & Magix) is also worth doing. R9 is the final release.

Syquest mentioned in an earlier post that "AT&T Custom" is the protocol suited for the Magix.

If it ain't broke, I haven't fixed it yet.

 

[DaveThePhoneDoctorLV]

yes, thank you I found several documents at avaya. us the programming done via a set or opcon?

 

[Dexman]

The system can be programmed either via WinSPM or a 4424LD+ (or MLX-20L) telephone set if connected to the correct extension ports.

If it ain't broke, I haven't fixed it yet.

 

[ttech]

If Cox is only giving you the option of NI1 or NI2 as the protocol, give up now, it won't work ~ AT&T Custom only.

 

[DaveThePhoneDoctorLV]

Thank you. I will verify this with Cox.

 

[phonesaz]

I have used the DMS100 switch with either NI1 or NI2 - it seems with the newer switches that is all I can get. There is actually a reference to using that setting in the Legend networking guide. But..Nate... I have a ??? for you - I am struggling with an XO cut where they say 'you can't do PRI on a Magix' and I say 'guess again we do it all the time' but they can't find a specific client in their data base that uses PRI/Magix. If you know of one up and running provided by XO I would love to find a way to give that name to xo. I am in phoenix so they probably share tech support at some level. I own a company called UniTech if you could pass that on to XO or google me or something. My customer is really hurting and something for them to work from would be useful.

 

[SYQUEST]

For AT&T Custom Primary ISDN protocol, the "L" flags only apply to the NT DMS10/DMS100/DMS200/DMS250 & DMS500 switches. The WECO/LUCENT/AVAYA 5ESS switch does not have trunk group flags.

All the DMS switches have the same trunk group protocol support. So nothing has changed except the people programming the switches!! They (the LECs/CLECs) are the ones causing the problem or are just being too lazy!!

Diana,

You should contact NortelNate. In his OP he mentions that his client now has XO PRI and wants to change to Cox. See if you can connect with each other and compare notes or whatever to get the info you need for your client!

....JIM....