PBXtech.info - View Single Post

martinyoung · February 14th, 2006, 10:26 AM

Just in case you don't see my other message, I will repeat it here. The other answer posted here explained the denial event and a possible cause. The event data 2 entry of "0xf29" is the actual problem. The (f) shows where it happened and the (29) shows what happened.

0xf29 is a hex number that must be converted to decimal to find out what is going on. In Avaya document 03-300430 on page 130 is the location code table. Location code A to F mean the problem is at the far end of the circuit, the carrier equivalent of a blue alarm.

The hex value of 29 converts to a decimal value of 41 and this is mentioned in the cause code table on page 149. It is supposedly a temporary failure but since you can never call those four numbers, it is not temporary. The problem is at the far end, it is not you.

It is unlikely that one channel on a T1 will go bad unless the vendor has done something.

Possibilities are, unable to call that area code, area codes have split and those numbers are now in a different area code, the company you are calling has a problem on some numbers and they are unaware of it, the numbers you are calling are no longer in service, your vendor has a problem, etc.

Get with the vendor, the problem is in their ballpark or beyond.

One thing that might bring it closer to home is I notice you have to dial "99" to get out, this usually means Centrex. Check with your provider to make sure nothing has changed there, they might be inserting or deleting something to make it fail at the far end.

This is a longer answer than my other one because I have had a chance to sleep on it.

February 14th, 2006, 10:26 AM	#3 (permalink)
martinyoung Moderator Join Date: Dec 2005 Posts: 1,450	Re: Denial Event 1164 Just in case you don't see my other message, I will repeat it here. The other answer posted here explained the denial event and a possible cause. The event data 2 entry of "0xf29" is the actual problem. The (f) shows where it happened and the (29) shows what happened. 0xf29 is a hex number that must be converted to decimal to find out what is going on. In Avaya document 03-300430 on page 130 is the location code table. Location code A to F mean the problem is at the far end of the circuit, the carrier equivalent of a blue alarm. The hex value of 29 converts to a decimal value of 41 and this is mentioned in the cause code table on page 149. It is supposedly a temporary failure but since you can never call those four numbers, it is not temporary. The problem is at the far end, it is not you. It is unlikely that one channel on a T1 will go bad unless the vendor has done something. Possibilities are, unable to call that area code, area codes have split and those numbers are now in a different area code, the company you are calling has a problem on some numbers and they are unaware of it, the numbers you are calling are no longer in service, your vendor has a problem, etc. Get with the vendor, the problem is in their ballpark or beyond. One thing that might bring it closer to home is I notice you have to dial "99" to get out, this usually means Centrex. Check with your provider to make sure nothing has changed there, they might be inserting or deleting something to make it fail at the far end. This is a longer answer than my other one because I have had a chance to sleep on it. __________________ Marty Retired Avaya DSIC tech