D-cahnnel fails to turn-up connecting Prologic to Tenor DX

[hummer3331973]

Hi all-

I'm trying to connect a Tenor DX back-to-back to an Avaya Prologix using the ffg settings (below) but I can't get the D channel to turn-up. Anything I'm missing here?

My Tenor DX's ISDN is set-up like this:

Protocol= PRI5ESS
D-channel= Channel 24
Orientation = Network/Master
T1, B8ZS, ESF
Channel group = 1-23

The client Avaya PBX has this settings:

                                DS1 CIRCUIT PACK

            Location: 01C07                           Name: Skype
            Bit Rate: 1.544                    Line Coding: b8zs
   Line Compensation: 1                       Framing Mode: esf
      Signaling Mode: isdn-pri
             Connect: pbx                        Interface: network
   TN-C7 Long Timers? n                   Country Protocol: 1
Interworking Message: PROGress            Protocol Version: b
Interface Companding: mulaw                            CRC? n
           Idle Code: 11111111
                              DCP/Analog Bearer Capability: 3.1kHz

      Slip Detection? n                 Near-end CSU Type: other


                                SIGNALING GROUP

 Group Number: 3              Group Type: isdn-pri
                    Associated Signaling? y          Max number of NCA TSC: 0
                       Primary D-Channel: 01C0724     Max number of CA TSC: 0
                                                   Trunk Group for NCA TSC:
       Trunk Group for Channel Selection: 10      X-Mobility/Wireless Type: NONE
          Supplementary Service Protocol: a


                               TRUNK GROUP

Group Number: 10                   Group Type: isdn          CDR Reports: y
  Group Name: Skype                       COR: 75       TN: 1        TAC: 175
   Direction: two-way        Outgoing Display? y         Carrier Medium: PRI/BRI
 Dial Access? n                Busy Threshold: 99        Night Service:
Queue Length: 0
Service Type: tie                   Auth Code? n            TestCall ITC: rest
                         Far End Test Line No:
TestCall BCC: 4
TRUNK PARAMETERS
         Codeset to Send Display: 6     Codeset to Send National IEs: 6
        Max Message Size to Send: 260   Charge Advice: none
  Supplementary Service Protocol: a     Digit Handling (in/out): enbloc/enbloc

            Trunk Hunt: cyclical
                                                   Digital Loss Group: 13
Calling Number - Delete:     Insert:                 Numbering Format: pub-unk
              Bit Rate: 19200        Synchronization: async    Duplex: full
 Disconnect Supervision - In? y  Out? n
 Answer Supervision Timeout: 0

                                 TRUNK GROUP
                                      Administered Members (min/max):   1/23
GROUP MEMBER ASSIGNMENTS                  Total Administered Members:  23

       Port    Code Sfx Name        Night           Sig Grp
 16: 01C0716  TN464  F                                3
 17: 01C0717  TN464  F                                3
 18: 01C0718  TN464  F                                3
 19: 01C0719  TN464  F                                3
 20: 01C0720  TN464  F                                3
 21: 01C0721  TN464  F                                3
 22: 01C0722  TN464  F                                3
 23: 01C0723  TN464  F                                3
 24:

I have set-up a Tenor DX on another PBXs (not Avaya) and they are working. This is just my first time to install to an Avaya. Layer 1 is "up" as seen from the mux, it's just the D channel that fails to sync. Any ideas?

 

[hummer3331973]

These are the errors, btw:

                        STATUS SIGNALING GROUP

        Group ID: 3                               Active NCA-TSC Count: 0
      Group Type: isdn-pri                         Active CA-TSC Count: 0
  Signaling Type: facility associated signaling
     Group State: out-of-service


                           Primary D-Channel


            Port: 01C0724        Level 3 State: out-of-service


                          Secondary D-Channel


            Port:                Level 3 State: no-link



                                 TEST RESULTS

Port        Maintenance Name  Alt. Name Test No. Result            Error Code

01C07       UDS1-BD                     138      PASS
01C07       UDS1-BD                     139      PASS
01C07       UDS1-BD                     140      FAIL
01C07       UDS1-BD                     141      PASS
01C07       UDS1-BD                     142      PASS
01C07       UDS1-BD                     143      PASS
01C07       UDS1-BD                     144      PASS
01C07       UDS1-BD                     145      PASS
01C07       UDS1-BD                     146      PASS
01C07       UDS1-BD                     1227     ABORT             1951
01C0701     ISDN-TRK          10/01     36       PASS
01C0701     ISDN-TRK          10/01     255      FAIL              8
01C0701     ISDN-TRK          10/01     256      ABORT             1116
01C0701     ISDN-TRK          10/01     257      ABORT             1116
01C0702     ISDN-TRK          10/02     36       PASS

 

[4merAvaya]

Failing Test 140 says that you're out-of-frame.

Kevin

 

[LoopbackJack]

It looks like your DX is set to be the master. You could try to change your interface setting to be user on the Avaya TG setting. Or see if the DX has peer-slave settings you can match up to the Avaya. Remeber one side is the master or network. The other side is the slave or user.

 

[lopes1211]

You also have the potocol as 5ESS on the DX and NI2 on the Avaya. You'll need to fix one of those.

-CL

 

[hummer3331973]

Thanks all for the reply.

The DX can either have "Master/Slave" or "User/Slave". I have already tried those settings but with no effect.

lopes1121- how do know that Avaya is using "NI2"? Is this due to protocol version = "b"? Will try to change my DX and will see how it goes.

What's causing "out-of-frame" error in Avaya? Is this a circuit pack problem?

 

[lopes1211]

right.
a = att custom
b = ni2
c = dms100

-CL

 

[dufus2506]

Framing errors can be caused by bad timing sources. Make sure that both systems have a similar timing source (say a T1 from an outside provider) or have the distant end system time off of the T1 you're installing.

Carpe dialem! (Seize the line!)

 

[hummer3331973]

Lopez1211- have set my DX to NI2 but with the same results, even after re-setting the board and D-channel.

Where can I check which clock is my Avaya DS1 board using? Sorry I'm not quite familiar with it. The DX is using the T1 as its clock source.

 

[vaoldschl]

display synchronization port-network x (1 in your case from the looks)

 

[hummer3331973]

This Avaya PBX only accepts "disp sync". Here's the screen shot. 01c07 is the T1 I'm trying to turn-up while 01A04 is the AT&T PRI.

                          SYNCHRONIZATION PLAN

               SYNCHRONIZATION SOURCE (circuit pack location)

                    Stratum: 4

                    Primary: 01A04      Secondary: 01C07

                CIRCUIT PACKS AVAILABLE FOR SYNCHRONIZATION
Location  Type  Name             Slip      Location  Type  Name             Slip
01C09     DS1                    y
01C10     DS1                    n
01A04     DS1                    n
01B10     DS1                    y
01A06     DS1   Cisco IP GW      n
01C06     DS1   TNTNTN767E       n
01A08     DS1   E1               n
01C07     DS1   Skype            n

NOTE: DS1 and BRI TRUNK sources result in stratum 4, type II synchronization

 

[LoopbackJack]

Another thought... Since this is a line side connection with no CSU I'm assuming, are you using a cross over T1 cable?

RJ-45#1 RJ-45#2
orange/white 1 4
orange 2 5

blue 4 1
blue/white 5 2

pins 3,7,8 not used

 

[hummer3331973]

Yes, a cross-over cable was the default cable with the DX. Although isn't it that Layer 1 won't turn-up if I'm using an incorrect cable?

I'm not sure what this means, but when I changed the signaling from ISDN to robbed-bit on the Avaya PBX, I was able to put all the 24 channels in service.

I think I can live with robbed-bit, but I'm not sure why the initial ISDN setting is not working? Any ideas?

 

[hummer3331973]

Here's my new, working TG setting, btw. I'm still curious on why I can't turn-up the D-channel when using ISDN..

                               TRUNK GROUP

Group Number: 10                   Group Type: tie           CDR Reports: y
  Group Name: Skype                       COR: 75       TN: 1        TAC: 175
   Direction: two-way        Outgoing Display? y Trunk Signaling Type:
 Dial Access? n                Busy Threshold: 99        Night Service:
Queue Length: 0                                   Incoming Destination:
   Comm Type: voice                 Auth Code? n
                                  Trunk Flash? n

TRUNK PARAMETERS
   Trunk Type (in/out): immed/immed      Incoming Rotary Timeout(sec):
    Outgoing Dial Type: tone                       Incoming Dial Type: tone
                                              Disconnect Timing(msec):
       Digit Treatment:                                        Digits:
                                                    Sig Bit Inversion: none
     Analog Loss Group: 9                          Digital Loss Group: 13
    Incoming Dial Tone? y

 Disconnect Supervision - In? y  Out? n
 Answer Supervision Timeout: 0             Receive Answer Supervision? y