DCH and Maintenance Busy on PRI

[SYQUEST]

Just finished cutting over my first PRI ISDN. This was a SUPERTRUNK to PRI conversion. In testing the PRI I guess the Maintenance functions of the LEGEND are very limited and in some cases (maybe all) useless!

What is this test number for the PRI?
I assigned one and called it but it went to the default for unassigned numbers...

In the case of the DCH it shows a permanent busy mode??

Is this normal?

How do do you know if it is really inservice?
Very confusing when trying to understand what is working and what is not.

One very lacking feature is a busy status for channels, lines/trunks and stations. And I mean regular busy mode...

Thanks in advance for any helpful feedback or comments.

....JIM....

 

[telecomgear]

Your channels seem to be working since ya got to the attendant on your test call. I'm assuming you didnt program your incoming call routing. ya gotta program the incoming digits, strip digits if applicable, insert digits etc. Someone has posted the programming sequence on this forum for PRI and I assume it includes incoming digits. Just search for it here. Hope this helps.

 

[phonesrus]

Just ignore and remove the test line number, it is there for a loopback test. It is supposed to be a far end number that when called identifies the caller and call type (voice/Data) and then loops the call back.
The "D"ch will remain busy for as long as the trunk group is inservice and functional. It is essentially a "nailed up" data link from your switch to the CO switch thru which the call signaling messaging is passed. When it is Down, the trunk is down.
Generally speaking, when the red lamp on the PRI enabled board goes out, the "D" channel is up. The alarm log is the only other source unless you have a T-1 test set.

 

[SYQUEST]

From your explanation what I understand is that the DCH is inservice normal when the Legend says "maintenance busy:yes".

Well that sure follows the illogical Legend's illogic!

Is this test number actually suppose to work? And what would call it if it did work?

Oh, telecomgear, all incoming routing is by Dial Plan and no inserts or strips. This one is clean - no junk! The programming sheet reference was used as part of my preparation in setting up this PRI along with the Planning Document, etc. Unfortunately good examples and through explanations are lacking. You have to read betwen the lines sometimes. The Avaya documents that I reviewed give next to nothing about the test number which is probably typical on their part.

 

[phonesrus]

The "D" channel is actually a 64k active data channel, it passes setup, progress, and teardown messaging for every call in and out. This info is then converted to the CO switches SS7 interswitch signalgroup to connect calls to the endpoint, it is almost instanteous. There are timers to allow timeout for congestation on the network, but do not mess with them without assistance.
The test number is usually a piece of equipment at the carrier that receives the call, identifies it and then calls back with a loopback for test purposes. I usually use them when testing local and l/d calls on ISDN-BRI circuits to verify SPID's and connectivity using my test set.
If you want to learn more ISDN there are a couple of docs on the AVAYA support under the Definity group.
Definity/Communication Manager Networking
Definity ISDN/CEPT1 technical reference
plus numerous other docs if you google it.
You are right. Avaya docs since about 98/99 leave a lot to be desired. I have tons of paper docs and of course the CD's, did you ever try to make a post-it note stick to a cd in a particular place.
Avaya farmed out the doc production to a third party around that time, its gone downhill ever since.
MERRY CHRISTMAS!!

 

[merlinman]

In a time, long ago, and a land far away, I once received the complete Feature Reference for Merlin Legend Release 3.0, IN MICROSOFT WORD FORMAT.

It was GREAT! - We "TECH SUPPORT FOLKS" could put our post it notes (YELLOW HIGHLIGHTS) anywhere we wanted and we could share that info with the "Customer Support FOlks", and they would know things beyond the "normal" documentation, and all was good.

However, as phonesrus stated, they started farming it out, and that type of stuff went hasta' la' bye bye.

 

[SYQUEST]

Thanks to everyone for your responses.

I have known about the CCIS/CCS since it was first put into service in the late 1960s with the 4ESS and understand the basics there. But in relation to the Legend/Magix I wanted more specific information in how it uses and functions with ISDN PRI so when something goes wrong I can troubleshoot the problem better or at least know what to expect.

But with the Legend it has been the unexpected that keeps poping up.

I did find one AT&T document, TR41459, on ISDN. It is 452 pages long. So I have alot of reading to do. I suppose a protocol analyzer would be handy to have, but those are out of my budget! Maybe I could find an older T-Berd at a good price.

I guess the Monitor feature along with some utilities that are on the DOS SPM
disc I have might provide some information and understanding of the PRI once I figure out how to use them.

Anyway HO HO HO everyone!!!