Did an interesting test over the weekend. In our lab we put a call form one IP phone to another on hold to see how long the call would stay on hjold before there was some type of hold call reminder. Well come monday morning, the MOH is still playing and there is no indication that there was ever a notification back to the phone that placed the call on hold in the first place. There is a parameter somewhere for a retrieval when you put a call on park. There should be a similar one for placing a call on hold. Anyone know of such a parameter buried somewhere in the 3.3 code? There is such a parameter for analog phones hanging on a VG248, but that is a VG248 system parameter.
I did see that someone asked this question back in Jan 2003, but a lot has changed.
In Service Parameters there is a field called: Tone on Hold Timer. When I clicked on the "I" button for help here is what it says:
This parameter specifies the number of seconds between every two hold tones played when a call is put on hold. Its effect on MGCP-based devices differs from other devices: a) For MGCP-based devices, if this value is 0 or 200,000, it completely disables the hold tone on that device; Any other value will enable the hold tone on MGCP-based devices when the caller is put on hold. b) For all other (non-MGCP-based) devices, if this value is 0, the held device will play the hold tone only one time when the caller is put on hold; if value is 200,000, no hold tone will be palyed at all; Otherwise, the held device will play the hold tone every so many seconds (specified by this value) repeatedly. If the value is less than 5 seconds, the device will raise it to 5 seconds.
The tone on hold is the indeed the tone that the held party hears when there's no MOH.
There's currently no feature that allows calls that are placed on hold to revert to the party that placed them on hold via an audible ring. If the reminder is needed, then the only way to do it, is like Paul mentioned, to park the calls instead of putting them on hold. I'm sure the feature has been requested before, so your Cisco Account Team might have info on when it might be implemented.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...