3300 Analog Trunks show releasing after dial tone is restored

[pmcilnay]

CX chasis- I have one CO line connected to the embedded trunk port on the CX. Using an analog station, I can use Individual Trunk Access to make a call out on the CO line. If I remove the CO line, and access it, I get Trunk Busy. This is expected. If I return the CO line to the port I still get Trunk Busy for up to 10 minutes. State of the line shows releasing. Mitel is escalating the issue since they were able to duplicate it in the lab. Anyone else run into this?

 

[pmcilnay]

Mitel's response-

Last Troubleshooting Note:

- LS trunks under normal conditions should be able to connect and disconnect to the CO based on calls and trunks that are connected to the CO, If you disconnect and connect back a trunk without making a call the caller should able to make a call after it's understood the trunk is in service again
- If the trunk gets disconnected physically from the controller and a user tries to call through the trunk, then the trunk is declared OOS and it will take time to recover based on internal tests that the controller makes to the trunk (recovery tests) this might take up to 10 min
- It is assumed that under normal conditions and if you use the trunk for emergency services (ie Fire Alarm) users won't use the trunk as it would be dedicated for that purpose

 

[kwbMitel]

I have observed similar time frames but it never concerned me. If I was testing an I wanted to restore service more quickly, I simply busy out the channel and return to service

**********************************************
What's most important is that you realise ... There is no spoon.

 

[pmcilnay]

I stumbled on this problem because the customer tried to make a test call while the fire alarm was being tested. It wouldn't have been an issue if the testing was done in the correct sequence.