I have a client with MICS, 4.1, PRI and a NAM. Today they could not make or recieve calls. I cheked the network alarms and it had Alarm 73 and event code 799-0001oes7. Does anybody know what these are refering to. I saw another post hear that asked the same question, but there was no answer as to what the alarm meant.
Alarm 73 states "No DN is available to the new ISDN-S loop terminal.
Action - A DN may be made available by changing the DN type from portable to ISDN. If no portable DN can be changed, a DN can only be available by unplugging an S-loop terminal.
Thanks for the reply zsmilesss. This system has been working for 6 years and this is the first time that i have seen this alarm. Could you tell me what a DN can only be available by unplugging an S-loop terminal is refering to. How do I go about fixing this.
thanks
Alarm code: 73
Reset:
No
Description:
Timing has been lost on T1 or BRI. CSU is freerunning.
Event code: 799
Reset:
No
Description:
Indicates a call processing error has occurred on an ISDN line. The event number is followed by a number representing the line or loop number, a code for the type of error.
EVT799-XXXX YYS7 In this example, the error has occurred on line XXXX and the error is YY. Error code Meaning
01 Internal software error. Cannot acquire the B-channel from the B-channel arbitrator.
02 Internal software error. There is no free line available for the call.
03 A call that is not on the B-channel has been attempted. These kind of calls are part of EKTS service, which is not supported by this version of the software. Check with your service provider to make sure your package does not include EKTS service.
04 Internal software error. Failed to instantiate on the chain.
05 Internal software error. Activation procedure failed.
06 Internal software error. Index conversion failed.
07 Unexpected digits on a Manual answer moded line. Configuration of the ICS and the network connection may not match.
08 Internal software error. Cannot seize central office (CO) lin on a BRI connection.
09 Cannot get vterm (virtual terminal) from the Vterm Server.
0A Central office did not respond to the SPID intialization
0B Central office has rejected the SPID. Verify your SPID information programmed under Hardware and with your ISDN provider.
0C Internal software error. Already instantiated on the chain.
0E B Channel lockup. Line idle but set will lock line. Per ITAS ref ITAS Ticket 89230. This site was at 4.0 WI 5.05. They experienced dropped calls on the PRI. The system test log showed this event 799 00010ES7. All PRI calls in progress were dropped. Ugrading to 4.1 WI 6.04 corrected.
Action:
Contact your local support group.
Note: