At the end of a VoIP call, both ends hang up the phone or terminate the call. You would expect that all gateway ports involved with the end-to-end call would also disconnect. Sometimes this is not the case with FXO ports when using loop start signaling. There is a common problem known as the FXO disconnect problem.
The FXO port looks like a phone to the central office switch or PBX. The FXO interface closes the loop and the C.O. provides constant battery on the wire. Therefore, there is no disconnect supervision. Just as the switch expects a user to hang up the phone when the call is complete, it also expects the FXO port to hang up. There is no automated process in the router that tells the FXO to disconnect when a call is completed. This is why FXO ports can sometimes become hung up or continue to send ring tones after the call has already cleared. The FXO expects the C.O. switch or PBX to tell it when to hang up. If the local FXO initiated the call and sent it out of its FXO port, then it can supply local disconnect. If it's receiving a call on its FXO then it needs to have a disconnect signal from the PSTN or PBX. Now, there's always a work-around for everything. Here is a list of some of the methods Cisco uses to get around this problem.
These are the paths to get to each CCX logs through CLI. They may be helpful if you are having issues accessing RTMT or downloading logs through it.
If you want to download them you have to prefix "file get " and you can add one of the options (re...