Two incidentes are generated when one trunk goes out of service:
We've taken many actions at the PBX side:14/03/05 17:53:47 001030M|00/22/0/254|=4:3700=Unexpected event traited on term 3, protocol 21
14/03/05 17:53:47 001030M|00/22/0/254|=4:3701=Unexpected event traited, state 20, event 232
1. The MF R2 trunk group programming was verified and it is the same than the used in other sites with the same release 4400 R4.2h using the same carrier for these public trunks.
2. Synchrony is beeing given by public carrier. That was already verified using infocs command
3. PCM2 board and TY5 connectors were changed.
The public carrier also have taken actions:
1. They changed their interface board at their central office. And this is the last action that was taken but it did not correct the problem. After 3 days one channel appeared in HS state (verifying with the command trkstat)
Other information about this problem:
- To get back trunks to F (free) state it is necesary to reset every terminal using the command termstat n equipment.
- When I try to put in service the channel using inserv n equipment this doesn't work.
- If the public carrier resets their interface the problem continues (trunks remain in HS state).
Could somebody help me to know what is causing the problem. Thanks.
Roger.
