My users get on their Unity mailbox lots of voice mail with a recording of busy tone. This seems to happen when a call from PSTN is forwarded to a Unity mailbox, Unity plays her/his greeting, and the caller decides not to leave a message and hangs up. Somehow the call hasn't ended, and the Unity hears the busy tone and duly records it, I think. The problem doesn't happen when the caller is another IP Phone.
When I have a call between an IP Phone and a PSTN phone, and the PSTN side hangs up the call, I hear on my handset busy tone for about 30 seconds before the call actualy ends...
Sounds like you have a supervisory disconnect issue. What is your voice interface to the PSTN? Is it fxo? Sounds like you need to make sure the fxo is going back on hook when the PSTN user is hanging up. There is 3 ways to accomplish this. Most Telcos do power denial. If you telco is not doing that then you can do supervisory disconnect tone or battery reversal.
Is this a dual switch integration with a PBX? Is there a gateway involved that might be somehow recording analog busy tone?
My experience has been that the TSP will react to a busy state on an IP line rather than record the signal; the only time I've seen Unity record busy tone is when a PBX or gateway is sending the actual analog tones to the Unity.
Since your PSTN connectivity is via ISDN-PRI you will need to verify that the network is providing the proper disconnect message. If you watch the D-Channel traffic you will see a disconnect message form the CO. The Gateway should return a disconnect acknowledge message and the CO should, in turn proceed with the call clearing process.
The Call Manager has some pretty sophisticated dubug tools but a network protocol analyser would be most beneficial. If you are using a router as a gateway turn on ISDN Debug Event to watch a trace. You should see the normal clearing process described above.
The problem you are experiencing is odd as there really is no supervisory disconnect in ISDN. This task is performed through D-Channel messaging and is therefore not subject to the normal CO programming issues.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.