Inbound PRI trace Merlin Magix 1

[memphisribs]

How can I use the monitor fuction to see the incoming digits on a PRI? I can use trace to see the B channels but not the D channel information containing the incoming routing. To bad Avaya won't document the monitor feature. Thanks for any help.

40 years in the business and counting.

 

[elalich]

I used to work for a CLEC in the field performing D channel decodes. Your best bet is to find someone, be it a LEC tech or another vendor, and have them bridge a network analyzer into your ckt. They can print the trap and email it to you.

 

[Pepperz]

Seems like that is on a post on this forum somwhere.

Pepperzgm at gmail dotte comm

 

[telecomtekperson]

I am going to "skirt" around the actual name of the command cuz I promised I would never say it.

BUT, if you are using the 1 command that will trace the entire B channel group, that will show the incoming digits after you use the "PRI decoder" in monitor.

 

[Blueline]

Is there anything particular about installing AT&T PRI's on a Magix R4 ?

The 2 T's will have their own D-channels and trunk groups and will be used for LD, SDN and Megacom service via DNIS.

Is there anything in route patterns or special in the PRI setup other than the standard stuff ?

 

[Blueline]

Sorry about that. Too many windows open at the same time ;-)

 

[memphisribs]

Telecomtekperson, thanks for your input. Got the data I needed. Strangly enough the LEC was sending 5 digits when calls orginated from certain CO's, switch was expecting only 3. LEC corrected problem. Thanks again.

40 years in the business and counting.

 

[telecomtekperson]

I had the lec ASSURE me during 2 different coinference calls that they were sending 4 digits. The use of the trace, showed they were sending 0 (Zero).

I dont know why the monitor function is so gaurded by Avaya. As Business partners I feel we should have EVERY resource to fix a customer problem, and not have to pay Avaya $100/hr to help us with what we already are sure of.