Magix DID issues with Monitor trace 2

[thrtnastrx]

My customer has a Magix with 2 PRI that have DID's working for 5 years. They recently added 1 more PRI which is working fine for outbound calls. The new PRI has 20 DID's associated with it but I can't get any of them to work. I have renumbered one extension to 2850 which is one of the DID's. When I call the number I am getting a telco recording. Telco assures me that the recording is just an alternative to fast busy and that there is nothing else they can do. Is there anything I need to to for the new PRI to accept DID's? I did a D-channel trace on the new PRI and see that when I call the 2850 or 2851 number some data appears but I don't know what it means. Here it is:

trace dchon 14
tracing of slot 14 is enabled
Ready
** 09/17/07 20:26:13 slot: 14 REC PRI msg 0005 SETUP ---------FIRST CALL TO 2850
24 08 02 00 57 05 04 03 80 90 A2 18 03 A9 83 81
6C 0C 21 83 38 31 38 36 31 32 34 39 32 30 70 05
80 32 38 35 30 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
** 09/17/07 20:26:13 slot: 14 SND PRI msg 005A RCOMP
09 08 02 80 57 5A 08 02 81 81 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
** 09/17/07 20:26:42 slot: 14 REC PRI msg 0005 SETUP ---------SECOND CALL TO 2851
24 08 02 00 58 05 04 03 80 90 A2 18 03 A9 83 81
6C 0C 21 83 38 31 38 36 31 32 34 39 32 30 70 05
80 32 38 35 31 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
** 09/17/07 20:26:42 slot: 14 SND PRI msg 005A RCOMP
09 08 02 80 58 5A 08 02 81 81 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
trace dchoff 14
tracing of slot 14 is disabled
Ready


Can anyone tell me what this is saying?

 

[dagwoodsystems]

The Avaya Monitor function is very powerful, and I really appreciate the fact that you have some familiarity with it. However, it doesn't make sense to kill a fly with a sledgehammer.

DID is simple. Some person somewhere dials a seven or ten digit number that points to the DID trunk. The telco reinterates or otherwise outpulses a predetermined number of digit to the responsive PBX, and the call is completed.

If the carrier is doing it's job, the VERY WORST thing that should happen is that the call completes to the Magix Operator. If that isn't happening, then all the tricky Magix Monitor function won't change that. The carrier is at fault.

Please post the telco recording or message...it may offer some insight as to what the true problem is.

Tim Alberstein

http://www.dagwoodsystems.com

 

[SYQUEST]

First of all, please post a print of your PRI config and list the DID number blocks the Telco is sending for each PRI and the number of digits sent for each, ie: 3 digit or 4 digit feed.

Next how do you have the DID parameters set? These parameters, eventhough they are listed for analogue DID trunks, are also used by the PRI to "control" the status of unassigned DID numbers in the Legend/Magix (invalid destination). In other words you can have the unassigned number sent to the Attendant Console or receive a "Fast Busy (120ipm)" when called.

Well in the case of PRI ISDN you won't get a "Fast Busy" because ISDN does not extend a call setup to a fast busy condition. The setup message on the DCH tells the CO switch the call can't be completed, so the CO switch sends the call to a non-completion recording! That is one of the reasons why you are getting a "Telco" recording when you call some of your DID numbers.

So one of the parameters may be hosed, causing the call not to complete to the assigned destination. You might try changing the option and send the calls to the Console and see what shows up on the display. That may provide some clues as to what is wrong. Other than my suggestion at the top, so more eyes can take a look see for anything obvious.

....JIM....

 

[glg01]

If your outbound is really working okay....then maybe the CO is sending you 7 digits on your new range of 20 DID's. I would try to setup a route for expecting 7 digits and delete 3 or 4 digits....can't tell if you have 4 digit extensions or not....you never really say. If the CO is sending 7 then your new DID's would start working. I doubt if it will be something this simple but you never know. I suspect some kind of protocol issue but you would think the CO could at least match your other two PRI's. If you haven't swapped the 100D/100DCD modules around to prove it out of your hardware you may want to try that as well. That would only take a few minutes just to be sure the new module is good. lg

 

[thrtnastrx]

Well I'm an idiot but I just started programming Magix systems again after 4 years or so. After doing a printout of the PRI I saw what was missing, the incoming call routing by dial plan. Thanks for all the help.

 

[dagwoodsystems]

You can't imagine how much I respect you for your honesty, thrtnastrx (I wish I knew your real name). Please don't ever define yourself as an idiot. Your response helped teach me something, and I've been doing Avaya systems for almost 19 years. Everyone here has something to contribute...even those that make mistakes.

Tim Alberstein

http://www.dagwoodsystems.com

 

[dagwoodsystems]

Also, I give cudos to SYQUEST (again), because I was absolutely sure that any call that telco terminated on a PRI trunk would [at minimum] be routed to the Magix console, regardless of the number of digits sent or a match to the Route-By-Dial-Plan table.

SYQUEST's third paragraph apparently tells the real story.

Tim Alberstein

http://www.dagwoodsystems.com