dlgouse

I have an issue getting an ISDN pri active n a G3si V6. I've attempted all I know and it still won't activate the D channel. The only thing I can see different is that QSIG options in the system parameters on this system are all n. ISDN-PRI is stroked to y. Is it possible that my QSIG being all n is the problem? All the othe systems I deal with have at least basic call setup set to y. This one doesn't. Any guideance would be apprecited.

Blah

ISDN as a feature won't prevent the D-channel from coming up.. you would never have been able to program the trunk group if ISDN PRI were not "yes."

The question is loaded, because it depends on the phone company.. is it T1? E1?

You can do a display ds1 and see your programming.

we code our line b8zs.. , frame it esf, PROGREss, mulaw, ISDN-PRI, "connect:network"

You may want to ensure your interface IDs match the telco's.. along with the D channel#. And ask what they are using.

DS1 protocols
A = AT&T Custom
B= Ni2
C= AT&T Custom ENHANCED

When you busy and release the board, does the telco see anything? If not, they don't see you and the D channel won't come up regardless.

I hope this helps more than hinders..

PBXtech.info

 

Blah

9 times out of 10, it's the phone company. I am sorry, but tis true. Best to you.

fataldata

Our system uses PRI's and all of our QSIG options are stroked to 'n'. Our ds1's are setup exactly as Blah mentioned.

__________________
Systems In Use:
S8700 CM3.0 and S8710 CM3.1.1

jsena

TI ISDN-PRI Troubleshooting:
Unplug the PBX from the T1 cable.
Step 1: Make sure vendor can test to the smart jack. If they can't see it, it is a problem on their end.
Step 2: Connect a loopback jack to the T1 cable where you would normally connect the PBX. If they can't test to that, there is a problem with the wiring in your building (from Demarc to PBX).
Step 3: Remove the CSU from the back of the PBX. Get what settings the vendor is looking for. Most likely bit 8 zero sub (b8zs), extended superframe (ESF), national 2 (NI2) which is protocol version "b". These settings are all on the change ds1 xxxxx page as mentioned by blah and fataldata. Also put the CSU to integrated if you are using the Avaya 120Ax CSU. Set up the ds1 page and add a signalling group, putting the d channel as xx24, but don't add the trunk group yet.
Step 4: Once you do the programming, look at the front of the 464 card. There are 4 status lights. All 4 should be out.
Step 4a: Plug in the CSU (but not the T1 cable yet) -- it should light 2 (red) and 4 (red). If not, you either have a bad ds1 card or bad CSU.
Step 4b: Plug in the T1 cable -- it should light 3 (green). If not, your ds1 programming is not matching the vendor's.

Post what step you get stuck at.

dlgouse

I've had the telco loop through to the csu successfully and thay hav connected a test set to the end of the cable from the smart jack at the PBX end and were able to place test calls successfully. I'll have a person on site next week that can do the other tests suggested and watch the status lights. The DS1 was configured as described by all. I have many other PRI's working and I also suspect the Telco but as you know, you have to prove it to them. Thanks for the feed back. I'll let you aall know what happens next

PBXtech.info

 

Blah

Here's what will happen.

You won't change anything and it will all start magically working.. then the telco will say, "Well, we didn't change anything.. " but it will be working.. you just never know.

dlgouse

I ran through the tests as suggested. Telco can loop to the CSU. D channel still will not come up. Totally baffeled. Appreciate all the assistance.

jsena

suspect bad hardware, then. Also, just to clarify:
on the change ds1 page -- Protocol Version: b
on the change signalling group page -- Supplementary Service Protocol: a

if you have that Supplementary Service Protocol as "b" you will not have working d-channel. If the ds1 protocol is wrong the d channel would come up but the b-channels wouldn't.

Try a different 120Ax and/or a different TN464x. Did you check the lights on the front of the TN464?

dlgouse

120a3's. All tests good from the pbx side. I'm going to have someone put a loopback jack in the CSU tomorrow just to prove the equipment.

technician101

More than once I have had the pairs reversed by the telco, loopback testing will work but circuit will not come up. Make a reversing cable with one end 568B and the other 568B with blue (pins 4&5) and orange (pins 1&2) pairs reversed. You stated that you placed test calls, did you have to reverse your connections to your test unit?

dlgouse

And the saga continues. The only thought I have come up with at this point is the R6 software doesn't support the TN464's as ISDN-PRI. The telco can loop csu's clean but see nothing coming back from me. I just spent 6 more hours messing with this and am about up to my eyeballs in frustration. One other thing. A status of the signal group shows Level 3 state as manual-out-of-service. I've never seen this before and the maintenance manual is a bit obsucre on what to release. Again, any thoughts would be appreciated.

DUDE

dlgouse

Dude, do you have the settings for the data mod? I never have set one up for a signal group before. This system is a dinosaur that I inherated.

ahays

If your system has a TN778 PACCON board and "display system-parameters customer-options" has ISDN via PACCON" set to "y" then you don't need a data module and the D channel will be controlled by the PACCON card on the packet bus.

If these items do not exist then you will need a T765 Processor Interface to control the D Channel on the TDM bus and you will have to add a data module with a type of 'procr-intf' with a non-DID extension number. Assign the data module to a physical channel of the TN765 PI board (01 to 04).

Do a 'change communications-interface links' to add the information for the ISDN board. Use the same physical channel as assigned to the data module.
Enable = n
Est Conn = y
PI Ext = Data mod extension number created above
PROT = ISDN
Brd = DS1 circuit pack slot
Identification = Whatever

Do a 'change communications-interface processor-channels' and add an entry:
Appl = ISDN
Link = same as assigned to the data module
Channel = blank
Priority = h

Do a 'add or change signaling-group x.
Associated Signaling = y for Facility Associated Signaling (most likely scenerio)
n for Non-Facility Associated Signaling (another can of worms)
Primary D channel - DS1 circuit pack slot, port 24
Trunk Group = # or leave blank

Go back to the 'change communications-interface links' form and enable the link that you are using.

Give it a few minutes to sync up and then do a 'status signaling-group x'. You should see the primary as 'in-service'

__________________
Al Hays, ACE, MCSE, CCNA
Homepage: http://www.jeral.com/
Training: http://www.jeral.com/avaya-learning.html