Hows things? Hope all is well with you :) If you are using SCCP (I'm guessing here);
Transfer and Conference are two features that use Hookflash. You will probably need to tweak these settings;
Analog phones use hookflash to access a second dial tone to initiate some of the SCCP phone features listed in Table 2, such as transfer and conference. Hookflash is an on-hook condition of short duration that is usually generated when a phone user presses the Flash button on a phone. The duration of an on-hook condition generated by a Flash button varies for different phone makes and models. Cisco voice gateways measure the duration of detected on-hook conditions to determine whether they should be interpreted as hookflash or not. The duration of a detected on-hook condition is interpreted by Cisco IOS software as follows:
An on-hook condition that lasts for a time period that falls inside the hookflash duration range is considered a hookflash.
An on-hook condition that lasts for a shorter period than the lower limit of the range is ignored.
An on-hook condition that lasts for a longer period than the higher limit of the range is considered a disconnect.
The hookflash duration range for FXS ports is defined as follows:
The lower limit of the range is set in software at 150 ms, although there is also a hardware-imposed lower limit that is typically about 20 ms, depending on platform type. An on-hook condition that lasts for a shorter time than this hardware-imposed lower limit is not reported to the Cisco IOS software.
The upper limit of the range is set in software at 1000 ms by default, although this value can be changed using the timing hookflash-input command in voice-port configuration mode on the voice gateway. The upper limit can be set to any value from 50 to 1550 ms.
The following examples demonstrate the use of the timing hookflash-input command to modify the upper limit of the hookflash duration range for FXS ports:
If the timing hookflash-input command is set to X, a value greater than 150, then any on-hook duration between 150 and X is interpreted as a hookflash. For example, if X is 1550, the hookflash duration range is 150 to 1550 ms. An on-hook signal that lasts for 1250 ms is interpreted as a hookflash, but an on-hook signal of 55 ms is ignored.
If the timing hookflash-input command is set to X, a value less than 150, then any on-hook duration between Y, the hardware lower limit, and X is interpreted as a hookflash. For example, if X is 65, the hookflash duration range is Y to 65 ms (assume Y is 20 ms). An on-hook signal that lasts for 1250 ms is interpreted as a disconnect, but an on-hook signal of 55 ms is interpreted as a hookflash. An on-hook signal of less than Y is ignored.
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...