Abnormal ISDN drop

[marshyrob]

Hello

Ive searched this forum and Google to try and gain a better understanding of this event i have seen in "disp events"

1166 Abnormal ISDN drop D2=CV

There seems to be people on here with the same issue but there never seemed to be a resolution. Does anyone have any idea what causes this. We are experiencing calls being dropped after a "whisper" announcement or mid way through a conversation, its quite random so i cant trace the station as we have 200 of them and they can be at anyone of them at any time!

Not sure if this error is related but is seems to indicate so? the telco's say that the ISDN 30's are fine. Also no other errors in alarms or errors.

Can anyone shed any light on this.

Thanks

Rob

 

[marshyrob]

Anyone have any idea about this? Im really struggling to find a resolution to this as Avaya's site is useless!!

Thanks

Rob

 

[definityandcmuk]

We have this denial event but our event log shows 1166 as "unassigned number"

I have checked the manual and this also shows event 1166 as unassigned number.

See page 195 on the attached maintenance doc

http://support.avaya.com/elmodocs2/comm_mgr/r3_1/pdfs/maintenance/03_300430_2_1.pdf

 

[marshyrob]

Hi definityandcmuk

Yes ive checked that document before and i have seen the same. Seems silly that this is not recognised as lots of people seem to get it. Im not sure if its related to the disconnects that we are getting but it would be nice to know.

In Event Data 1 and Event Data 2 there are some numbers, but in the manual it says they should be in hex. But the numbers/letters are not. For example i have:

1166 Abnormal ISDN drop D2=CV Event Data 1 = 545 Event data 2 = 1F

Any idea how to interpret these?

Cheers

Rob

 

[wildcard100001]

Have you checked the DS1(s) and see if it/they are taking any hits...?

list meas ds1 log xxxxx (ds1 board location)

You should see all zeros... if you don't start trouble shooting it...

Another thing you could do...
On the reports of dropped calls... if you have a CDR package, correlate the time of the dropped call with the CDR records... check the trunk record and see if it is on a particular circuit.

Thanks,

Wildcard

 

[mikeydidit]

http://www.avayatest.com/

The above site has a list of events that may help. The site is free to use.

"You don't stop playing because you get old. You get old because you stopped playing."

 

[marshyrob]

Thanks wildcard100001 & mikeydidit

Wildcard100001, i have checked the DS1's and they are all at zero's so no issues there, we dont have a CDR facility so i cant do the comparison that you suggest, although we do use CMS but i cant seem to find a report that will display calls dropped. Can you suggest anything else?

mikeydidit
Thanks Mikeydidnt, ive been to that site before and it was ok but it still doesnt really help. A good source for the future though!

Regards

Rob

 

[qz01gs]

Can you not set up an MST trace and have a trigger button set up on a couple of stations? and get Avaya or your BP to investigate it further.

What version of software are you running.?

 

[marshyrob]

Hi gz01gs

we are running:

Software Load - R011i.01.1.060.5
Mem Config - G3siV11

We did think of setting up a few stations with a trunk id button to get some inof of at least what trunk it was coming in on. Maybe we will go that route.

Not sure what a MST trace is as im new to this, i know how to do a trace on vector or VDN etc.

Regards

Rob

 

[qz01gs]

AN MST trace is much more detailed than a simple trace on a vector etc.

You can set it up so that certain stations can trigger the trace, i.e. when they get a call drop mid conversion for example. That trace can then be analysed by Avaya /BP.


Do all your VDN's have whispher announcements?

 

[marshyrob]

Hi gz01gs

That sounds a good idea!

Can you give any guidence or point me in the right direction in setting up the MST Trace?

The VDN's that seem to be dropping calls do have whispers, yes, and it seems to have started to happen when these were introduced, but i cant see why?

Rob

 

[wildcard100001]

marshyrob,

Just a thought...The only other thing that I can think of is the issue could be happening on another PSTN network span in route to your trunk group. Your good to the NIU, the NIU is good to the carrier switch, but an issue is occurring further in the PSTN cloud on some other network span or on another carrier network. If you happen to get ANI on the callers (date and time as well), capture them and report them to the carrier and see if they can trace the call and perhaps they can figure it out...

I would also make a lot of test calls to see if I could experience it myself... though you may route on a different span than the one potentially affected.

I've had that PBX software load before, I never had issues like that. But I have experienced the situation and it was a network related issue.

Thanks,

Wildcard

 

[marshyrob]

Thanks Wildcard

Ill try those options, seems to have calmed down now so thats a good thing. Must be related to the cloud as no one seems to have any real reason why calls start dropping all of a sudden!

Thanks for all your time, its appreciated.

Rob

 

[tr2653]

marshyrob,

Have you found any resolution to your ISDN dropping calls issue? I have recently accepted a new install, Avaya S8400 release 3.1.1 with 3 Point to point PRI T1s. I have one analog card (TN793cp) and several ISDN line Cards (TN556D) in the switch. The DS1 interface cards are TN464HP and we have 3 of those. What are the lights on the DS1 cards suppose to look like if everything is okay? Currently one of my has all steady lights while the other two have flasshing amber lights. My users have also been experiencing dropping of calls on external numbers.

I have contacted my commercial carrier and a D channel problem was found. However, the problems still remain. Avaya and the commercial carrier have been working together but now both are saying equipment and trunks are good.

How do you program the MST trace or trk-id button I heard about in this post?

I am also pulling my hair out any help is greatly appreciated. Thanks.

 

[gblucas]

I don't know if this has anything to do with it, but Avaya released the TN464HP HW01. It has an a problem with the 120A4 CSU. I had over 75 DS1 boards, and Avaya had to replace them all with HW02 cards. I had all kinds of errors on my T-1's and was not able to find a solution to it. This fixed my problem.

gblucas

 

[tr2653]

Thanks gblucas.

Do you know how to tell if the TN464HP HW01 already exists in the chassis. I know for sure we have the TN464HP but unsure of the HW01. I would think there is a revision number or something on the card? Do you recall how long ago your issue happened? I will look into it. Thanks so much.

 

[qz01gs]

do list config ds1

 

[tr2653]

Thanks qz01gs.

I will try the list config ds1.

Can you tell me how to program the MST trace or trk-id button?

Thanks again for everyone's help.

 

[gblucas]

Reply to tr2653...You should have your answer from qz01gs...My problem was about a year ago. It was a new office, new switch, CM3.0, and the BP was pointing to the distance that the T-1 ran from the dmarc to the phone room. I ran all kinds of tests on the cables, and lines from the carriers and was not able to find a solution. I was talking to the salesman at the BP, and he found a notice from Avaya that said that the boards had a problem. I changed the CSU from a 120A4 to a 120A3 and the problem went away. I had called Avaya 3 times, and they were unable to help me, until I brought up that issue, and they replaced every one of the cards. It did take some work, but it was all done and I never had any kind of problems again.

gblucas

 

[tr2653]

I was able to find some information out about the ds1 configuration today. Here is what I found:

TN464HP Vintage: HW02 FW018 CSUMOD: 120A4 (is this a problem?)

I was also able to complete a list trace station on a particular number and experienced the dropping of calls myself. Below is one of my findings which I am hoping might shed some light on decipering this problem:

13:20:12 idle station 6806 cid 0x16f
13:20:21 idle trunk-group 1 member 22 cid 0x175
13:20:47 Alert station 6806 cid 0x178
13:21:03 no answer station 6806 cid 0x178
13:21:03 coverage-path 4 point 1 cid 0x178
13:21:03 dial 86666# route:AAR
13:21:03 term trunk-group 99 cid 0x178
13:21:03 call-forwarding 86666#
13:21:03 route-pattern 99 preference 1 cid 0x178
13:21:03 seize trunk-group 99 member 6 cid 0x178
13:21:03 Calling Number & Name NO-CPNumber NO-CPName
13:21:03 Proceed trunk-group 99 member 6 cid 0x178
13:21:03 Alert trunk-group 99 member 6 cid 0x178
13:21:03 G711MU ssff ps:20 rn:1/1 ip address:8000 ip address:2932
13:21:03 xoip: faxT modemT tty:US ip address:2932 uid:0x50006
13:21:03 active trunk-group 99 member 6 cid 0x178
VOIP data from: ip address:2932
13:21:14 Jitter:5 5 5 5 5 5 5 5 5 5: Buff:13 WC:9 Avg:5
13:21:14 Pkloss:0 0 0 0 0 0 0 0 0 0: Oofo:0 WC:0 Avg:0
13:21:14 idle trunk-group 1 member 22 cid 0x178

At 13:21:14 I experienced a call dropping with the report of jitter and pkloss. Any ideas?