D-Channel Protocol Identification on ATT G3R PBX 1

[jeanvaljean]

How do you identify the D-channel protocol in use for PRI trunk groups on the G3R.

I have both fas and nfas arrangements and can stat the trunks, list the trunks, etc. but I don't know how to identify the protocol in use for each trunk group.

We do have basic, what I call 'station-level' expertise so we are able to list trunk groups, sho and stat trunk groups, as well as basic station level telephone admin. But so far no one has been able to 'fish out' the d-channel protocols in use.

My own expertise is Cisco and Nortel. However, my organization has one large ATT (or Avaya) G3R with multiple PRI trunk groups and we need to identify the d-channel protocols currently in use for each trunk group.

In preparation for the change to Cisco I need to identify the d-channel protocol in use so as to match it in the upcoming Cisco setup.

Specifically: we need to know the commands look up the d-channel configuration for each trunk group.


any help would be truly appreciated.

thanks

24601

 

[jeanvaljean]

OK - if I've got this right, apparently the various d-channel protocols such as NI2, DMS, 5E, 4E, etc., are indexed as letters: a,b,c, etc.

So I need a "key", like, for example, protocol a = NI2, protocol b = DMS, protocol c = ess5, etc.??

Again, very grateful for any help with this.

thanks


24601

 

[AvayaTier3]

Command: list config ds1
Command: display ds1 xxxx cab car slot

Note: To confirm clear channel verify that the Line Coding fields are set
to b8zs for T1 facilities and hdb3 for E1 facilities.

1. A standard T1 will usually be set up for 2-way traffic, but not always. They
can be used for incoming and outgoing calls. They can be used for local or long
distance. They may be channelized/segmented!!!!! (Specific channels reserved for
different services.)

2. They can be set up as common-channel (To connect an Avaya PBX to another
Avaya PBX), or robbed bit.

o Common Channel means that you get 23 bearer channels (B-channels, which are
actual talk paths for voice calls), and the 24th channel is used for
D-channel-like signaling. This is a proprietary format used for PBX-to-PBX
only. The signaling is for things like call set-up information & name
information. But, unlike an ISDN-PRI T1, you do NOT need to set up a signaling
group to control the D-channel. You do, however, need to set up a separate
data trunk group and associated BX.25 translations for DCS.

o Robbed-Bit gives you 24 bearer channels. As the name indicates, bits are
robbed from each of the channels to carry the information normally carried on
the 24th channel. Instead of getting 23 64k voice channels, you get 24 56k
channels. If the customer plans to use any of their channels for data this is
usually not acceptable, and you should recommend they use common-channel.

3. They can be AMI-ZCS or B8ZS. We rarely see AMI any more. More than likely
they will be B8ZS (Bi-polar 8 zero code suppression). This is a higher quality
format. But you need to ask.

4. They can be D4 (SF) or ESF (Extended Super-Frame). Again, you will almost
always see ESF these days. But you need to ask.
* The following statements are great to use as a guideline, but these are not
absolute rules:
o A = Custom or NI1 National. This is typically used when your T1 comes out of
an AT&T 4ESS Central Office.
o B = NI2, and is typically used when your T1 comes out of a 5ESS Central Office
This is the only protocol capable of giving the customer NAME and number
Caller ID. You always prefer this protocol if the vendor can provide it!
ISO/ETSI QSIG. Also used for SBS signaling trunks.
o C = Nortel Custom. This is a new protocol, and is sometimes used when your T1
comes out of a Nortel DMS Central Office. RARE. ETSI public network.
o D = NI2 ECMA QSIG European Computer Manufacturer's Association (ECMA) QSIG
private network (supports only Name Identification and Additional Network
Feature Transit Counter (ANF-TC))

5. Line compensation refers to how far the smart-jack connection is from the PBX
We always WANT it to be a 1, which is up to 133 feet. However, if that is not
the case, this entry helps to compensate for longer distances. There is a chart
in our documentation. I have almost never used anything except a 1 in this
field, but you should know what the option is for. You need to FIRMLY request
that the vendor place the smartjack IN the equipment room! If it must be
extended, we want the vendor to do so!

6. Slip detection should be set to Y for T1s that are programmed as the primary
& secondary synchronization sources, and N for those that are not.

7. CSU will be "integrated" if you have the new integrated 120 CSUs, and "other"
if you have any other type of external CSU, such as a 3150 or 3160. Be aware
that if you have a 316X you will probably need a technician who knows how to
program them!

8. Synchronization should be set to clock off of long distance T1s whenever
possible, and local would be your second choice. The major exception to this is
if you are implementing a point-to-point T1. If you do a point-to-point the
satellite location should be set to clock off of the main switch, and the main
switch should be set to clock off of the long distance T1 whenever possible.
(Local T1 as the second choice at the main location.) You should always put a
primary and secondary in the synchronization if you have more than 1 T1.


A great teacher, does not provide answers, but methods to teach others "How and where to find the answers"

bsh

40 years Bell, AT&T, Lucent, Avaya
Tier 3 for 30 years and counting
[URL unfurl="true"]http://bshtele.com[/url]

 

[lopes1211]

A AT&T Custom
B National ISDN 2 (NI-2)
C Nortel Custom Nortel DMS (Lcl & LD)
D National ISDN 98 (NI-98)


-CL

 

[jeanvaljean]

Very grateful for both of the above posts. The problem is now officially nailed. Perfect information. Hopefully I can return the favor down the road. Great Holidays to you both.!!

24601