Manual out of service?

[chevyman440]

Okay... my second question of the week. I have created a new signalling group. When I view the status I have

Group ID: 4
Type: facility associated signaling
Group State: out-of-service

Primary d-channel
link: Port: 01b1624 Level 3 State: manual-out-of-service



Do I need to somehow put this in service? I have a green light on my T1 link, but still down at both ends. Other side is a different phone system all together. Other side reports that no d-channel available on 24.

Getting there...hopefully.
-Matt

 

[mikeydidit]

You could try to "realease sig 4". It sounds like it may be busied out.


Mike Jones
LSUHSC

 

[chevyman440]

unfortunately I don't have that command... It's old V6 software on this switch...maybe that was a later command.

I'm wondering if I have a timing issue going on perhaps. It's weird!

thanks for the advice though,
-Matt

 

[mikeydidit]

I dont think it is a version problem. It could be a matter of your maintenance permissions with the password that you are using. You could try to reseat the circuit pack and see if that bring it to life for you.


Mike Jones
LSUHSC

 

[Simmy2106]

you could try release port 01b1624. unless the command you don't have is release.

 

[chevyman440]

Okay... that I can do... I reseated the tn464f card in the system. I am using the csu module attached to the back.

port maintenance name alt. name result err. code
01b1624 ISDN-LNK ABORT 1011

That is my result from release port 01b1624

Trying to release anything to do with that board gives me the error code 1011. Anyone know what that is?

The far end looks like it has connectivity, but no d-channel. Near end on the switch shows status lights 2 and 4 red on the card itself.

-Matt

 

[RTMCKEE]

ABORT 1011 is because the link was not busied first.
2 and 4 red usually mean you have not physical signal to the card. Check the connection to the T-1. Also what light do you have on the NIU. Sounds like your T-1 is bad.

RTMCKEE

CM 2.1.1
Prologix R9.05
Modular Messaging 1.1

 

[chevyman440]

okay... this could well be the case. Basically it is to attach an Asterisk phone system on to ours. My boss wants to evaluate it for a few special cases. I'm going out to a CSU 120 module. This essentially is wired with a crossover cable to the T1 interface in a server running Asterisk.

One other thing...this CSU module was found with the rest of the phone equipment I inherited years back. There is a possibility that it is no good. There is also the possibility that the TN464 card is no good as well although it was pulled from a working system.

I will put some effort in to verifying the T1's status. Maybe I will bypass the CSU and wire directly changing the type on the definity to OTHER for the csu. This is one way they suggested, but preferred the csu connection.

I was able to busy the card, then release it successfully now. Still have a down signaling group.

Thanks guys! I'll get it eventually.

-Matt

 

[RTMCKEE]

If you are going to use the 120 then you need integrated. Other is for external CSUs or a direct connect cable, (which you may need). Also you may what to look at how you have the DS1 set up, ie Network, PBX, etc... this tells the system which side the clock is coming from. There was a bad run of 120s I dont remember if they were 120a3, or a4s.

You should beable to build a hard loop cable and test the CSU DS1 board. (there are usually bunches of these around the NIU)

Finally I'd suggest doing a post in this forum on what the switch setup should be for connecting to an Astrisk, I know I just answered another question yesterday about routing tables to one. It looked like they had it connected and working. Here is the thread thread690-1033416

RTMCKEE

CM 2.1.1
Prologix R9.05
Modular Messaging 1.1

 

[orypecos]

You say "Other side reports that no d-channel available on 24"
Have you got the other end set up for 24 voice channels instead of 23 for Isdn?

 

[chevyman440]

RTMCKEE: It is actually a 120a2 CSU. My next step is going to be a direct wiring with a crossover cable just to test. This is my only space CSU presently and in an unknown condition. It is set for Network clock source on the Definity side. The other side is supposed to provide clock, but I will verify this in a few days. I'm out in Buffalo NY working out a terminal server installation the next two days...so it'll be next Monday before I can get to the system again.

I checked on that thread and I am pretty good on the configuration after receiving some help here. I've created the trunk, the signalling group, a route pattern, and fixed my aar table for UDP routing. It appears to route an extension as it should, but returns busy right away since the tie line is out of service.

orypecos: Yes I had it set for 23 channels (1-23) and also tried it with just the first four channels and 24 as the d-channel.

Thank you for your patience! I'm pretty sure I either have a bad CSU, or the clock source isn't right.

 

[orypecos]

Usually the t-1 will run with bad clocking, it will just have slips causing dropped calls and such.

 

[chevyman440]

Just to update everyone...checked over everything I can possibly imagine. Verified my Asterisk configs with the manufacturer of the T1 interface card.

I ditched the a120 csu in favor of a direct crossover cable..same results. Tried different switchtypes (national, old national 1)..different line encodings and framings, all with the exact same result. The line comes up, but no d-channel on the remote side.

The tn464 card in the carrier now has NO lights on it. I am unable to add all 23 channels in to my trunk group as I hit a licensing limit. Could I be unable to use this signalling group because of licensing? I can add almost all 23 ports to the trunk group. Could the tn464 card be out of comission?

I have maintenance with Avaya presently on the card. Should I loopback test the tn464 card?

After the snow storm last weekend this is just icing on my cake.
-Matt

 

[RTMCKEE]

A tg will run with only one member, you dont need all 23 members to be configured. Do you have another T-1 board you can swap to see if that is the issue? Definately sounds like you've done everything else.

I have called in cases to avaya to have boards replaced, and told them I swapped it with one I had on hand, and only needed a new board. If you dont have a spare, or can't take one down, maybe you can give that a go?

RTMCKEE

CM 2.1.1
Prologix R9.05
Modular Messaging 1.1