|
|
Table Of Contents
hold-alert (voice register global)
huntstop (ephone-dn and ephone-dn-template)
Cisco Unified CME Commands: H
Last Updated: June 19, 2006First Published: February 27, 2006
This chapter contains commands to configure and maintain Cisco Unified Communications Manager Express (formally known as Cisco Unified CallManager Express). The commands are presented in alphabetical order. Some commands required for configuring Cisco Unified Communications Manager Express (Cisco Unified CME) may be found in other Cisco IOS command references. Use the command reference master index or search online to find these commands.
headset auto-answer line
To enable auto-answer on the specified line when the headset key is engaged, use the headset auto-answer command in ephone configuration mode. To disable headset auto-answer for this line, use the no form of this command.
headset auto-answer line line-number
no headset auto-answer line line-number
Syntax Description
Defaults
Headset auto-answer is not enabled.
Command Modes
Ephone configuration
Command History
12.4(4)XC
Cisco Unified CME 4.0
This command was introduced.
12.4(9)T
Cisco Unified CME 4.0
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
Use this command to enable headset auto-answer on a particular line. A line, as used in this command, is not identical to a phone button. A line, as used in this command, represents the ability for a call connection on this phone, and the line numbers generally follow a top-to-bottom sequence starting with the number 1.
The following examples represent common situations pertaining to a button:line relationship:
•
button 1:1—A single ephone-dn is associated with a single ephone button. Counts as one line.
•
•
•
Examples
The following example shows how to enable headset auto-answer for line 1 (button 1) and line 4 (button 4), which has overlaid ephone-dns but counts as a single line in this context. In this example, four (1, 2, 3, and 4) buttons are defined for ephone 3.
ephone 3button 1:2 2:4 3:6 4o21,22,23,24,25headset auto-answer line 1headset auto-answer line 4The following example shows how to enable headset auto-answer for line 2 (button 2), which has overlaid ephone-dns, and line 3 (button 3), which is an overlay rollover line. In this example, three (1, 2, and 3) buttons are defined for ephone 17.
ephone 17button 1:2 2o21,22,23,24,25 3x2headset auto-answer line 2headset auto-answer line 3The following example shows how to enable headset auto-answer for line 2 (button 3) and line 3 (button 5). In this case, the button numbers do not match the line numbers because buttons 2 and 4 are not used.
ephone 25button 1:2 3:4 5:6headset auto-answer line 2headset auto-answer line 3hold-alert
To set a repeating audible alert notification when a call is on hold on a Cisco Unified IP phone, use the hold-alert command in ephone-dn or ephone-dn-template configuration mode. To disable this feature, use the no form of this command.
hold-alert timeout {idle | originator | shared}
no hold-alert timeout {idle | originator | shared}
Syntax Description
Command Default
Audible alert notification for on-hold calls is disabled. Only a visual indication is provided.
Command Modes
Ephone-dn configuration
Ephone-dn-template configurationCommand History
Usage Guidelines
Use the hold-alert command to set an audible alert notification on a Cisco Unified IP phone to remind the phone user that a call is on hold. The timeout argument specifies the time interval in seconds from the time the call is placed on hold to the time the on-hold audible alert is generated. The alert is repeated every timeout seconds.
When the idle keyword is enabled, a one-second burst of ringing on the phone is generated on the IP phone that placed the call in the hold state, but only if the phone is in the idle state. If the phone is in active use, no on-hold alert is generated.
When the originator keyword is enabled, a one-second burst of ringing is generated on the phone that placed the call in the hold state, but only if the phone is in the idle state. If the phone is in use on another call, an audible beep (call-waiting tone) is generated.
When the shared keyword is enabled, a one-second ring burst is generated for all the idle phones that share the extension with the on-hold call. Phones that are in use do not receive an audio beep (call-waiting tone) alert. Only the phone that placed the call on hold hears a call-waiting beep if it is busy.
If you use an ephone-dn template to apply a command to an ephone-dn and you also use the same command in ephone-dn configuration mode for the same ephone-dn, the value that you set in ephone-dn configuration mode has priority.
Examples
The following example sets audible alert notification to idle on extension 1111:
Router(config)# ephone-dn 1Router(config-ephone-dn)# number 1111Router(config-ephone-dn)# name phone1Router(config-ephone-dn)# hold-alert 100 idleThe following example uses an ephone-dn template to set audible alert notification for extension 1111 to only occur when the phone is idle:
Router(config)# ephone-dn-template 3Router(config-ephone-dn-template)# hold-alert 100 idleRouter(config-ephone-dn-template)# exitRouter(config)# ephone-dn 1Router(config-ephone-dn)# number 1111Router(config-ephone-dn)# name phone1Router(config-ephone-dn)# ephone-dn-template 3Related Commands
ephone-dn
Enters ephone-dn configuration mode.
ephone-dn-template
Enters ephone-dn-template configuration mode.
hold-alert (voice register global)
To set a repeating audible alert notification when a call is on hold on all supported SIP phones directly connected in Cisco Unified CME, use the command in voice register global configuration mode. To disable this feature, use the no form of this command.
hold-alert timeout
no hold-alert
Syntax Description
timeout
Interval after which an audible alert notification is repeated, in seconds. Range is from 15 to 300. There is no default.
Defaults
Audible alert notification for on-hold calls is disabled. Only a visual indication is provided.
Command Modes
Voice register global configuration
Command History
Usage Guidelines
Use this command to set an audible alert notification on all supported SIP phones in a Cisco Unified CME system to remind the phone user that a call is on hold. The alert is repeated after a specific interval as defined by the timeout argument.
Note
Examples
The following example shows how to set audible alert notification on SIP phones for on-hold calls:
Router(config)# voice register globalRouter(config-register-global)# mode cmeRouter(config-register-global)# hold-alert 30Related Commands
hops
To define the number of times that a call can proceed to the next ephone-dn in a peer or longest-idle ephone hunt group before the call proceeds to the final ephone-dn, use the hops command in ephone hunt configuration mode. To return to the default number of hops, use the no form of this command.
hops number
no hops number
Syntax Description
Command Default
The number of hops automatically adjusts to the number of ephone hunt group members.
Command Modes
Ephone-hunt configuration
Command Modes
Usage Guidelines
This command is valid only for peer and longest-idle ephone hunt groups in Cisco Unified CallManager Express systems.
This command is required when you are configuring the automatic logout feature for peer and longest-idle hunt groups.
Examples
The following example sets the number of hops to 6 for peer hunt group 3:
Router(config)# ephone-hunt 3 peerRouter(config-ephone-hunt)# hops 6Related Commands
hops (voice hunt-group)
To define the number of times that a call can hop to the next number in a peer hunt group before the call proceeds to the final number, use the hops command in voice hunt-group configuration mode. To return to the default number of hops, use the no form of this command.
hops number
no hops
Syntax Description
Defaults
The default is the number of directory-number arguments configured in the list command.
Command Modes
Voice hunt-group configuration
Command History
Usage Guidelines
This command is valid only for peer or longest-idle voice hunt groups in Cisco CallManager Express systems.
Examples
The following example shows how to set the number of hops to 6 for peer voice hunt group 1:
Router(config)# voice hunt-group 1 peerRouter(config-voice-hunt-group)# list 1000, 1001, 1002, 1003, 1004, 1005, 1006, 006, 1007, 1008, 1009Router(config-voice-hunt-group)# hops 6Related Commands
hunt-group logout
To enable separate handling of DND and HLog functionality for hunt-group agents and the display of the HLog soft key on phones, use the hunt-group logout command in telephony-service configuration mode. To return to the default, use the no form of this command.
hunt-group logout [DND | HLog]
no hunt-group logout [DND | HLog]
Syntax Description
Command Default
DND and HLog functionality is not separate and the HLog soft key will not be displayed on phones.
Command Modes
Telephony-service configuration
Command History
12.4(4)XC
Cisco Unified CME 4.0
This command was introduced.
12.4(9)T
Cisco Unified CME 4.0
This command was integrated into Cisco IOS Release 12.4(9)T.
Usage Guidelines
When Do Not Disturb (DND) functionality is activated, no calls are received at the phone, including ephone hunt group calls. DND is activated and canceled using the DND soft key or the DND feature access code (FAC).
When HLog functionality is activated, hunt-group agents are placed in not-ready status and hunt-group calls are blocked from the phone. Other calls that directly dial the phone's extension numbers are still received at the phone. HLog is activated and canceled using the HLog soft key or an HLog FAC.
If the auto logout command is used, the Automatic Agent Status Not-Ready feature is invoked for an ephone hunt group. This feature is triggered when an ephone-dn member does not answer a specified number of ephone hunt group calls. The following actions take place:
•
•
Note
Examples
The following example creates hunt group 3 with three agents (extensions 1001, 1002, and 1003). It specifies that after one unanswered call, an agent should be put into not-ready status but not into DND status.
Router(config)# telephony-serviceRouter(config-telephony)# hunt-group logout HLogRouter(config-telephony)# exitRouter(config)# ephone-hunt 3 peerRouter(config-ephone-hunt)# pilot 4200Router(config-ephone-hunt)# list 1001, 1002, 1003Router(config-ephone-hunt)# timeout 10Router(config-ephone-hunt)# auto logoutRouter(config-ephone-hunt)# final 4500Related Commands
auto logout
Enables the automatic change of an agent's ephone-dn to not-ready status after a specified number of hunt-group calls are not answered.
hunt-group report delay hours
To delay the automatic transfer of Cisco CallManager Express (Cisco CME) basic automatic call distribution (B-ACD) call statistics to a file, use the hunt-group report delay hours command in telephony-service configuration mode. To remove to the delay setting, use the no form of this command.
hunt-group report delay number hours
no hunt-group report delay number hours
Syntax Description
Defaults
No hunt-group report delay is configured.
Command Modes
Telephony-service configuration
Command History
12.3(11)XL
3.2.1
This command was introduced.
12.3(14)T
3.3
This command was integrated into Cisco IOS Release 12.3(14)T.
Usage Guidelines
This command is used for Cisco CME basic automatic call distribution (B-ACD) and auto-attendant (AA) service only.
The hunt-group report delay hours command is used as part of a statistics reporting configuration that allows Cisco CME B-ACD call statistics to be sent automatically to files using TFTP. For detailed information, see Cisco CME B-ACD and Tcl Call-Handling Applications.
Statistics are collected and stored (statistics collect command and hunt-group report url command) in specified intervals (hunt-group report every hours command). The default is for the statistics to be collected one hour after the specified interval. Because calls are counted when they end, some of the longer calls may not be counted. For example, if there is a call from 1:35 p.m. to 3:30 p.m., the interval is 1 hour, and there is no delay, TFTP will write the 1 p.m. to 2 p.m. statistics at 3 p.m. However, at 3 p.m., the 1:35 p.m. call is still active, so the call will not be counted at that time as occurring in the 1 p.m. to 2 p.m. time slot. When the call finishes at 3:30 p.m., it will be counted as occurring from 1 p.m. to 2 p.m. The show hunt-group command will report it, but TFTP will have already sent out its report. To include the 1:35 p.m. call, you could use the hunt-group report delay hours command to delay TFTP statistics reporting for an extra hour so the 1 p.m. to 2 p.m. report will be written at 4 p.m. instead of 3 p.m.
Examples
The following example shows a configuration in which statistics are reported for B-ACD calls that occur within three-hour time frames, but the collection of the statistic collection is extended for an extra hour to include calls that did not end within the three-hour time period:
Router(config)# telephony-serviceRouter(config-telephony)# hunt-group report every 3 hoursRouter(config-telephony)# hunt-group report delay 1 hoursThe following is an example of a report that the previous configuration might send to a file if the statistics collect command was entered at 18:20:
23:00:00 UTC Tue Dec 20 2004,,01, Tue 18:00 - 19:00, HuntGp, 02, 01, 00005, 00002, 0003, 0006, 000001, 000001, 0011,01, Tue 19:00 - 20:00, HuntGp, 02, 02, 00000, 00000, 0000, 0000, 000000, 000000, 0000,01, Tue 20:00 - 21:00, HuntGp, 02, 02, 00006, 00003, 0003, 0009, 000001, 000003, 0012,Statistics collection has to take place for at least three hours for the statistics to be written to a file. The following is a chronology of events:
•
•
•
•
•
Related Commands
hunt-group report every hours
To set the hourly interval at which Cisco CallManager Express (Cisco CME) basic automatic call distribution (B-ACD) call statistics are automatically transferred to a file, use the hunt-group report every hours command in telephony-service configuration mode. To remove the interval setting, use the no form of this command.
hunt-group report every number hours
no hunt-group report every number hours
Syntax Description
number
Number of hours after which auto-attendant (AA) call statistics are collected and reported. The range is from 1 to 84.
Defaults
No hourly interval is configured.
Command Modes
Telephony-service configuration
Command History
12.3(11)XL
3.2.1
This command was introduced.
12.3(14)T
3.3
This command was integrated into Cisco IOS Release 12.3(14)T.
Usage Guidelines
This command is used for Cisco CME basic automatic call distribution (B-ACD) and auto-attendant (AA) service only.
The hunt-group report every hours command is used as part of a statistics reporting configuration that allows Cisco CME B-ACD call statistics to be sent automatically to files by means of TFTP. For detailed information, see Cisco CME B-ACD and Tcl Call-Handling Applications.
Because calls are counted when they end, some of the longer calls may not be counted in the report. To delay the time in which statistics are collected and transferred you may configure a delay time with the hunt-group report delay hours command.
Examples
The following example sets the statistics collection to occur every three hours. There is no delay.
Router(config)# telephony-serviceRouter(config-telephony)# hunt-group report every 3 hoursThe following is an example of a report that the previous configuration might send to a file if the statistics collect command was entered at 18:20:
22:00:00 UTC Tue Dec 20 2005,,01, Tue 18:00 - 19:00, HuntGp, 02, 01, 00005, 00002, 0003, 0006, 000001, 000001, 0011,01, Tue 19:00 - 20:00, HuntGp, 02, 02, 00000, 00000, 0000, 0000, 000000, 000000, 0000,01, Tue 20:00 - 21:00, HuntGp, 02, 02, 00006, 00003, 0003, 0009, 000001, 000003, 0012,Statistics collection has to take place for at least three hours for the statistics to be written to a file. The following is a chronology of events:
•
•
•
•
If the previous example were configured for a delay of one hour using the hunt-group report delay 1 hours command, the statistics would be written one hour later at 23:00.
Related Commands
hunt-group report url
To set filename parameters and the URL path where Cisco Unified CME basic automatic call distribution (B-ACD) call statistics are to be sent using TFTP, use the hunt-group report url command in telephony-service configuration mode. To remove the report URL settings and stop statistics from being sent to files, use the no form of this command.
hunt-group report url [prefix tftp://ip-address/directory-name.../prefix | suffix from-number to to-number]
no hunt-group report url [prefix tftp://ip-address/directory-name.../prefix | suffix from-number to to-number]
Syntax Description
Command Default
No statistics are sent to files.
Command Modes
Telephony-service configuration
Command History
Usage Guidelines
Use this command for Cisco Unified CME basic automatic call distribution (B-ACD) and auto-attendant (AA) service only. For detailed information, see Cisco Unified CME B-ACD and Tcl Call-Handling Applications.
The hunt-group report url command is used with the hunt-group every hour command to collect statistics about ephone hunt groups that are part of Cisco Unified CME B-ACD services. Data is collected for all agents combined and for individual agents. The data includes statistics on the number of calls received, the amount of time the calls had to wait to be answered, the amount of time they spent on hold or in queue, and so forth.
The hunt-group report url command transfers these call statistics to files using TFTP for time periods set by the hunt-group every hours command. Each set of statistics for each time period is sent to a different file that is named using the arguments in the hunt-group report url command. For example, the first set of statistics may go to a file named test001, the second set to test002, and so forth.
Prior to using the hunt-group report url command, you must create files with matching prefixes and suffixes. For example, for the following configuration:
telephony-servicehunt-group report url prefix tftp://239.1.1.1/dirname/dirname/datahunt-group report url suffix 0 to 3you must have files named data0, data1, data2, and data3 at the designated directory location (tftp://239.1.1.1/dirname/dirname).
For the following configuration, you must have files named data00, data01, data02, ... data50:
telephony-servicehunt-group report url prefix tftp://239.1.1.1/dirname/dirname/datahunt-group report url suffix 0 to 50For the following configuration, you must have files named data000, data002, ... data200:
telephony-servicehunt-group report url prefix tftp://239.1.1.1/dirname/dirname/datahunt-group report url suffix 0 to 200The files must be must empty read-and-write files. The following is an example of the statistics sent to a file using TFTP:
23:00:00 UTC Wed Apr 23 2003,01, Wed 21:00 - 22:00, HuntGp, 02, 02, 00005, 00002, 0003, 0006, 000001, 000001, 0011,01, Wed 21:00 - 22:00, Agent, 8001, 00002, 000001, 000001, 00002, 000002, 000002,01, Wed 21:00 - 22:00, Agent, 8003, 00001, 000001, 000001, 00000, 000000, 000000,01, Wed 21:00 - 22:00, Queue, 00002, 00002, 00000, 00002, 00003, 00000, 00000, 00000, 00000,The order of the data fields corresponds to the order of the descriptions issued by the show hunt-group command. See the " Examples" section for explanations of the data fields. The Cisco CME B-ACD and Tcl Call-Handling Applications document discusses how hunt-group reports align with the show hunt-group command output. Once the statistics are in a file, they can be sent to an application, such as Microsoft Excel or Access, to be merged into a chart or graph for easier reading.
For the report mechanism to collect data, you must first issue the statistics collect command.
Examples
The following configuration uses TFTP to send AA call statistics to files named test00, test01, ... test90 located at tftp://239.1.1.1/dirname/dirname/test:
Router(config)# telephony-serviceRouter(config-telephony)# hunt-group report url prefix tftp://239.1.1.1/dirname/dirname/testRouter(config-telephony)# hunt-group report url suffix 0 to 90The following example displays the raw data output that was transferred to files in TFTP format after the hunt-group report every hours command was used. Table 9 through Table 11 describe what each number in the example represents. Table 9 explains the first line of data, Table 10 explains the second and third lines of data, and Table 11 explains the fourth line of data.
18:00:00 UTC Tue Apr 23 2003,,01, Tue 16:00 - 17:00, HuntGp, 06, 06, 00002, 00002, 00000, 0006, 0011, 000004, 000006, 0000, 00002, 000002, 000005,01, Tue 16:00 - 17:00, Agent, 8001, 00001, 000002, 000002, 00001, 000003, 000003, 00002, 000003, 000003, 00002, 000001, 000001,01, Tue 16:00 - 17:00, Agent, 8003, 00001, 000006, 000006, 00001, 000005, 000005, 00000, 000000, 000000, 00000, 000000, 000000,01, Tue 16:00 - 17:00, Queue, 00002, 00002, 00000, 00001, 00001, 00000, 00000, 00000, 00000,Table 9 explains the first line of TFTP-format statistics, which are the main statistics that present data for the hunt group as a whole.
Table 10 explains the next two lines of TFTP-format statistics in the example, which provide data for individual agents. Note that only the second line is presented in the table, but the third line follows the same format.
In the table, some statistics are marked with the following comments.
•
•
Table 11 explains the final line of data in the example, which is the data for the B-ACD queue.
Related Commands
huntstop (ephone-dn and ephone-dn-template)
To discontinue call hunting behavior for an extension (ephone-dn) or an extension channel, use the huntstop command in ephone-dn or ephone-dn-template configuration mode. To disable huntstop, use the no form of this command.
huntstop [channel]
no huntstop [channel]
Syntax Description
channel
(Optional) For dual-line ephone-dns, keeps incoming calls from hunting to the second channel if the first channel is busy or does not answer.
Command Default
Ephone-dn huntstop is enabled.
Channel huntstop is disabled.Command Modes
Ephone-dn configuration
Ephone-dn-template configurationCommand History
Usage Guidelines
When you use the huntstop command without the channel keyword, it affects call hunting behavior that relates to ephone-dns (lines or extensions). If the huntstop attribute is set, an incoming call does not roll over (hunt) to another ephone-dn if the called ephone-dn is busy or does not answer and a hunting strategy has been established that includes this ephone-dn. A huntstop allows you to prevent hunt-on-busy from redirecting a call from a busy phone into a dial-peer setup with a catch-all default destination. Use the no huntstop command to disable huntstop and allow hunting for ephone-dns.
Channel huntstop works in a similar way, but it affects call hunting behavior for the two channels of a single dual-line ephone-dn. If the huntstop channel command is used, incoming calls do not hunt to the second channel of an ephone-dn if the first channel is busy or does not answer. For example, an incoming call might search through the following ephone-dns and channels:
ephone-dn 10 (channel 1)
ephone-dn 10 (channel 2)ephone-dn 11 (channel 1)
ephone-dn 11 (channel 2)
ephone-dn 12 (channel 1)
ephone-dn 12 (channel 2)When the no huntstop channel command is used (the default), you might have a call ring for 30 seconds on ephone-dn 10 (channel 1) and then after 30 seconds move to ephone-dn 10 (channel 2). This is usually not the behavior that you desire. Also, it is often useful to reserve the second channel of a dual-line ephone-dn for call transfer, call waiting, or conferencing. The huntstop channel command tells the system that if the first channel is in use or does not answer, an incoming call should hunt forward to the next ephone-dn in the hunt sequence instead of to the next channel on the same ephone-dn.
If you use an ephone-dn template to apply a command to an ephone-dn and you also use the same command in ephone-dn configuration mode for the same ephone-dn, the value that you set in ephone-dn configuration mode has priority.
Examples
The following example shows how to disable huntstop for the destination dial peer with the extension 5001. The huntstop for the dial peer is set to OFF and prevents calls to extension 5001 from being rerouted to the on-net H.323 dial peer for the 5... destination when 5001 is busy (the three periods are used as wild cards).
ephone-dn 1number 5001no huntstopThe following example shows a typical configuration in which ephone-dn huntstop (default) is required:
ephone-dn 1number 5001ephone 4button 1:1mac-address 0030.94c3.8724dial-peer voice 5000 voipdestination-pattern 5...session target ipv4:192.168.17.225In the previous example, the huntstop attribute is set to ON by default and prevents calls to extension 5001 from being rerouted to the on-net H.323 dial peer for 5... when extension 5001 is busy.
The next example shows another instance in which huntstop is not desired and is explicitly disabled. In this example, ephone 4 is configured with two lines, each with the same extension number 5001. This is done in order to allow the second line to provide call-waiting notification for extension number 5001 when the first line is in use. Setting no huntstop on the first line (ephone-dn 1) allows incoming calls to hunt to the second line (ephone-dn 2) on ephone 4 when the ephone-dn 1 line is busy.
Ephone-dn 2 has call forwarding set to extension 6000, which corresponds to a locally attached answering machine connected to a foreign exchange station (FXS) voice port. In this example, the plain old telephone system (POTS) dial peer for extension 6000 also has the dial-peer huntstop attribute explicitly set to prevent further hunting.
ephone-dn 1number 5001no huntstoppreference 1call-forward noan 6000ephone-dn 2number 5001preference 2call-forward busy 6000call-forward noan 6000ephone 4button 1:1 2:2mac-address 0030.94c3.8724dial-peer voice 6000 potsdestination-pattern 6000huntstopport 1/0/0description answering-machineThe next example shows a dual-line ephone-dn configuration in which calls do not hunt to the second channel of any ephone-dn, but they do hunt through the channel 1 for each ephone-dn in the order 10, 11, 12.
ephone-dn 10 dual-linenumber 1001no huntstophuntstop channelephone-dn 11 dual-linenumber 1001no huntstophuntstop channelpreference 1ephone-dn 12 dual-linenumber 1001no huntstophuntstop channelpreference 2The next example uses an ephone-dn-template in a dual-line ephone-dn configuration to keep calls from hunting to the second channel of any ephone-dn. The calls do hunt through the first channels for each ephone-dn in the order 10, 11, 12.
ephone-dn-template 2huntstop channelephone-dn 10 dual-linenumber 1001no huntstopephone-dn-template 2ephone-dn 11 dual-linenumber 1001no huntstopephone-dn-template 2preference 1ephone-dn 12 dual-linenumber 1001no huntstopephone-dn-template 2preference 2Related Commands
huntstop (voice register dn)
To disable call hunting behavior for an extension on a SIP phone, use the huntstop command in voice register dn configuration mode. To return to the default, use the no form of this command.
huntstop
no huntstop
Syntax Description
This command has no arguments or keywords.
Defaults
Disabled
Command Modes
Voice register dn configuration
Command History
Usage Guidelines
If this command is enabled, an incoming call does not roll over (hunt) to another directory number if the called directory number is busy, or does not answer, and a hunting strategy has been established that includes this directory number. A huntstop allows you to prevent hunt-on-busy from redirecting a call from a busy phone into a dial-peer setup with a catch-all default destination. Use the no huntstop command to disable huntstop and allow hunting for directory numbers (default).
Note
Examples
The following example shows a typical configuration in which huntstop is required. The huntstop command is enabled and prevents calls to extension 5001 from being rerouted to the on-net H.323 dial peer for 5... when extension 5001 is busy (three periods are used as wild cards).
voice register dn 1number 5001huntstopvoice register pool 4button 1:1mac-address 0030.94c3.8724dial-peer voice 5000 voipdestination-pattern 5...session target ipv4:192.168.17.225The next example shows an example in which huntstop is not desired (default). In this example, directory number 4 is configured with two lines, each with the same extension number 5001. This is done to allow the second line to provide call-waiting notification for extension number 5001 when the first line is in use. Not enabling huntstop on the first line (directory number 1) allows incoming calls to hunt to the second line (directory number 2) on phone 4 when the directory number 1 line is busy.
directory number 2 has call forwarding set to extension 6000, which corresponds to a locally attached answering machine connected to a foreign exchange station (FXS) voice port. In this example, the plain old telephone system (POTS) dial peer for extension 6000 also has the dial-peer huntstop attribute explicitly set to prevent further hunting.
voice register dn 1number 5001preference 1call-forward noan 6000voice register dn 2number 5001preference 2call-forward busy 6000call-forward noan 6000voice register pool 4button 1:1 2:2mac-address 0030.94c3.8724dial-peer voice 6000 potsdestination-pattern 6000huntstopport 1/0/0description answering-machineRelated Commands
Posted: Thu Jul 12 14:51:00 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
