EVT799 unreferenced error code

[padmin]

The last several days, our MICS has been having intermittent dial-out errors. In the System Test log the following has been showing up:

EVT799-xxxx00S7 (with xxxx being actual "line" #)

I haven't been able to find any reference to the error code of "00".

System is configured with ISDN PRI, destination code is 9 for dialing out route 001, route 001 is PRI-A.

 

[padmin]

oh yeah, the problem, is that a user will dial a number (or use speed dial), once the dialed number is completed, the phoneset returns to the on-hook state.

 

[JP1525]

I am having the same problem on a 5.0 Mics. First thing in the morning the customer makes calls and they all go right back to time and date after the last digit is dialed. If I use my cell phone an make call the main # on the PRI it rings and goes to AA. From that point on 99% of the calls go out fine for the rest of the day, but this does happen every morning. I have swapped out the 5.0 SW, the T-1 Card, the service cartridge. I have also swapped out the whole cabinet and reprogrammed from scratch. Is this a 5.0 issue?

 

[padmin]

JP1525, are you in Qwest territory?

 

[JP1525]

Yes this is in Qwest Territory

 

[padmin]

I wonder if Qwest started sending B-channel messaging down their PRIs last week?

 

[padmin]

Just got off the phone w/Qwest & they recently turned up B-Channel messages on their 5E switch our PRI is coming out of. So, I had them switch it off, and we'll see.

 

[JP1525]

My next step is to try 6.1 SW, would this be worth the expense? The PRI has worked fine for 5 months, then about a month ago the customer had the problem of dialing a number and having it go back to the time and date.

 

[Roldan]

Here is what I found on that Event code, seems as though padmin figured out the problem but I hope this helps anyway

799: ISDN_CP_Error P7 'B' Trace TestLog
799: | CAUSE:
799: | A call processing error has occured on an ISDN line.
799: | ENVIRONMENT:
799: | The first parameter identifies the location (line number
799: | or loop number). The second parameter is an error code,
799: | defined as follows:
799: | 1: Can't acquire the B-channel from the B-channel Arbitrator.
799: | This indicates an internal software error.
799: | 2: There is no free line available for the call (internal error).
799: | 3: A non B-channel call has been attempted. Such calls are
799: | not supported in this version of software.
799: | 4: Failed to instantiate on the chain (internal error).
799: | 5: Activation procedure failed (internal error).
799: | 6: Index conversion failed (internal error).
799: | 7: Unexpected digits on Manual Answer line. Possible
799: | Network / Norstar configuration mis-match.
799: | 8: Can't seize CO line on a BRI (internal error at the
799: | driver or card level).
799: | HUMAN ACTION:
799: | None.


Louie Roldan

http://www.4vertex.com

 

[JP1525]

Will 6.1 support B-Channel messaging? Or should I go with the 7.0?

 

[oldward]

Was there ever any resolution to this? I have several systems around Phoenix doing the same thing, worst time is early morning. Error log shows call trying to go out on line 17, 14, 13, but not on line 23 as it should because system has no traffic on it other than the RAD that I am dialed into. Also problem clears immediately after dialing in on main number and getting CCR. Qwest swears they haven't changed anything but a lot of my switches started acting up about a month ago.

 

[JP1525]

Yes, Qwest did remove B-channel Signalling from the T-1 and we have not had a problem since.

 

[oldward]

Thanks, I'll go back after the Bell Boys

 

[padmin]

We've not had a problem since Qwest removed the B-Channel messaging either.


(I'm not sure how to credit another thread for pointing out problems with B-channel messaging, but kudos to this thread thread799-758038 )