|
|
Table Of Contents
New Commands in Cisco SRS Telephony, Version 2.02
call-forward busy (cm-fallback)
call-forward noan (cm-fallback)
default-destination (cm-fallback)
dialplan-pattern (cm-fallback)
ip source-address (cm-fallback)
pattern direct (vm-integration)
pattern ext-to-ext busy (vm-integration)
pattern ext-to-ext no-answer (vm-integration)
pattern trunk-to-ext busy (vm-integration)
pattern trunk-to-ext no-answer (vm-integration)
show call-manager-fallback all
show call-manager-fallback dial-peer
show call-manager-fallback ephone-dn
show call-manager-fallback voice-port
timeouts interdigit (cm-fallback)
transfer-pattern (cm-fallback)
Command Reference
This chapter documents new and modified commands. All other commands used with the SRS Telephony feature are documented in the Cisco IOS Release 12.2 command reference publications.
•
call-forward busy (cm-fallback)
•
•
•
•
•
•
•
•
•
•
New Commands in Cisco SRS Telephony, Version 2.02
•
•
•
•
•
access-code (cm-fallback)
To configure trunk access codes for each type of line so that the Cisco IP phones can access the trunk lines only in Cisco CallManager fallback mode when the SRS Telephony feature is enabled, use the access-code command in CallManager fallback configuration mode. To remove the telephone access code configuration from the Cisco IP phones, use the no form of this command.
•
no access-code {fxo | e&m} [dial-string]
•
no access-code {bri | pri} [dial-string] [direct-inward-dial]
Syntax Description
Defaults
No default behavior or values.
Command Modes
CallManager fallback configuration
Command History
Usage Guidelines
The access-code command configures trunk access codes for each type of line—BRI, E&M, FXO, and PRI—so that the Cisco IP phones can access the trunk lines in Cisco CallManager fallback mode when the SRS Telephony feature is enabled, which provides system-wide access.
Note
The access-code command creates temporary POTS voice dial peers for all the selected types of voice ports, in Cisco CallManager fallback mode. Use this command only if your normal network dial-plan configuration prevents you from configuring permanent POTS voice dial peers to provide trunk access for use in the fallback mode. When the access-code command is used, ensure that all ports covered by the command have valid trunk connections. Selection between ports for outgoing calls is random.
The dial string is used to set up temporary dial peers for each specified line type. If there are multiple lines of the same type, a dial peer is set up for each line. The dial peers are active only in Cisco CallManager fallback mode when the SRS Telephony feature is enabled. The result of this configuration is that all Public Switched Telephone Network (PSTN) interfaces of the same type, for example, BRI are treated as equivalent, and any port may be selected to place the outgoing PSTN call. The direct-inward-dial keyword enables you to set DID access for PRI and BRI trunk lines.
Examples
The following example sets the access-code command for BRI 8:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# access-code bri 8 direct-inward-dialThe following example sets the access-code command for E&M 8:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# access-code e&m 8The following example sets the access-code command for FXO 9:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# access-code fxo 9The following example sets the access-code command for PRI 9:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# access-code pri 9 direct-inward-dialRelated Commands
call-manager-fallback
Enables SRS Telephony feature support and enters CallManager fallback configuration mode.
alias (cm-fallback)
Cisco CallManager fallback, use the alias command in call-manager-fallback configuration mode. To disable rerouting of unmatched call destination calls, use the no form of this command.
alias tag number-pattern to alternate-number [preference preference-value] [huntstop]
no alias tag number-pattern to alternate-number [preference preference-value] [huntstop]
Syntax Description
Defaults
No default behavior or values.
Command Modes
Call-manager-fallback configuration
Command History
Usage Guidelines
The alias command provides a mechanism for rerouting calls to telephone numbers that are unavailable during fallback. An alias is activated when extension numbers are registered that fall within the range of the command's alternate-number argument.
The alias command supports all port types.
You can use a to alternate-number value once only. You can not put the same to alternate-number value into multiple alias command statements.
Examples
In the following example, alias 1 is configured to route calls to extensions 6000 through 6099 to extension 5001 using a dial-peer with a preference value of 2. Extensions 6000 through 6099 are a subset of IP phones without fallback service. During fallback, calls to these extension are routed to 5001.
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# alias 1 60.. to 5001 preference 2Related Commands
call-forward busy (cm-fallback)
To configure call forwarding to another number when a Cisco IP phone is busy, use the call-forward busy command in CallManager fallback configuration mode. To disable call forwarding, use the no form of this command.
call-forward busy directory-number
no call-forward busy [directory-number]
Syntax Description
Defaults
No default behavior or values.
Command Modes
CallManager fallback configuration
Command History
Usage Guidelines
The call-forward busy command configures call forwarding to another number when a Cisco IP phone is busy. The call forwarding mechanism is applied globally to all phones that register during fallback.
Examples
The following example forwards calls to extension number 5005 when an incoming call reaches a busy IP phone extension number:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# call-forward busy 5005The following example forwards calls to any available extension number in the 50xx bank of extensions when an incoming call reaches a busy IP phone extension number:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# call-forward busy 50..
Note
Related Commands
call-forward noan (cm-fallback)
To configure call forwarding to another number when no answer is received from a Cisco IP phone, use the call-forward noan command in CallManager fallback configuration mode. To disable call forwarding, use the no form of this command.
call-forward noan directory-number timeout seconds
no call-forward noan [directory-number]
Syntax Description
Defaults
No default behavior or values.
Command Modes
CallManager fallback configuration
Command History
Usage Guidelines
The call-forward noan command configures call forwarding to another number when no answer is received from a Cisco IP phone. The call-forwarding mechanism is applied globally to all phones that register during fallback. The timeout keyword sets the waiting time before the call is forwarded to another phone. The time is set in seconds. The range is from 3 to 60000 seconds.
Examples
The following example shows how to set call forwarding of incoming calls to directory number 5005 when line 1, directory number 5001, does not answer. The timeout period before the call is forwarded to the directory number 5005 is set for 10 seconds:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# call-forward noan 5005 timeout 10The following example shows how to set call forwarding of incoming calls to an available extension in the 50xx bank of extensions when line 1, directory number 5001, does not answer. The timeout period before the call is forwarded to the directory number 5005 is set for 10 seconds:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# call-forward noan 50.. timeout 10
Note
Related Commands
call-manager-fallback
To enable SRS Telephony support and enter CallManager fallback configuration mode, use the call-manager-fallback command in global configuration mode. To disable SRS Telephony support, use the no form of this command.
call-manager-fallback
no call-manager-fallback
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values.
Command Modes
Global configuration
Command History
Examples
The following example shows how to enter CallManager fallback configuration mode:
Router(config)# call-manager-fallbackThe resulting router prompt is
Router(config-cm-fallback)#.Related Commands
cor (cm-fallback)
To configure a class of restriction (COR) on the dial peers associated with directory numbers, use the cor command in call-manager-fallback configuration mode. To disable COR associated with directory numbers, use the no form of this command.
cor {incoming | outgoing} cor-list-name {cor-list-number starting-number - ending-number | default}
no cor cor-list-name cor-list-number
Syntax Description
Defaults
No default behavior or values.
Command Modes
Call-manager-fallback configuration
Command History
Usage Guidelines
The cor command sets the dial-peer COR parameter for dial peers associated with the directory numbers created during Cisco CallManager fallback. A list-based mechanism is provided to assign COR to specific sets of directory numbers during Cisco CallManager fallback. The COR functionality provides the ability to deny certain call attempts on the basis of the incoming and outgoing class of restrictions provisioned on the dial peers. This functionality provides flexibility in network design, allows users to block calls (for example, calls to 900 numbers), and applies different restrictions to call attempts from different originators.
COR is used to specify which incoming dial peer can use which outgoing dial peer to make a call. Each dial peer can be provisioned with an incoming and an outgoing COR list.
A default COR is assigned to the directory numbers that do not match any COR list number or number range. The assigned COR is invoked for the dial peers automatically created for each directory number during Cisco CallManager fallback registration.
You can have up to 20 COR lists for each incoming and outgoing calls. A default COR is assigned to directory numbers that do not match any COR list numbers or number ranges. An assigned COR is invoked for the dial peers and created for each directory number automatically during CallManager fallback registration.
If a COR is applied on an incoming dial peer (for incoming calls) and it is a super set or equal to the COR applied to the outgoing dial peer (for outgoing calls), the call will go through. Voice ports determine whether a call is considered to be incoming or outgoing. If you hook up a phone to an FXS port on an Cisco SRST router and try to make a call from that phone, the call will considered to be an incoming call to the router and voice port. If you make a call to the FXS phone, then the call will be considered to be outgoing.
By default, an incoming call leg has the highest COR priority. The outgoing COR list has the lowest. If there is no COR configuration for incoming calls on a dial peer, then you can make a call from a phone attached to the dial peer, so that the call will go out of any dial peer regardless of the COR configuration on that dial peer.
Examples
The following example shows how to set the dial-peer COR parameter for incoming calls to Cisco IP phone dial peers and directory numbers created during Cisco CallManager fallback:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# cor incoming LockforPhoneC 1 5002 - 5010The following example shows how to set the dial-peer COR parameter for outgoing calls to the Cisco IP phone dial peers and directory numbers created during fallback:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# cor outgoing LockforPhoneC 1 5010 - 5020The following example shows how to set the dial-peer COR parameter for incoming calls to the Cisco IP phone dial peers and directory numbers in the default COR list:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# cor outgoing LockforPhoneC defaultThe following example shows how sub- and super-COR sets are created. First, a custom dial-peer COR is created with names declared under it:
Router(config)# dial-peer cor customRouter(config-dp-cor)# name 911Router(config-dp-cor)# name 1800Router(config-dp-cor)# name 1900Router(config-dp-cor)# name local_callIn the following configuration examples, COR lists are created and applied to the dial peer.
Router(config)# dial-peer cor list call911Router(config-dp-corlist)# member 911Router(config)# dial-peer cor list call1800Router(config-dp-corlist)# member 1800Router(config)# dial-peer cor list call1900Router(config-dp-corlist)# member 1900Router(config)# dial-peer cor list calllocalRouter(config-dp-corlist)# member local_callRouter(config)# dial-peer cor list engineeringRouter(config-dp-corlist)# member 911Router(config-dp-corlist)# member local_callRouter(config)# dial-peer cor list managerRouter(config-dp-corlist)# member 911Router(config-dp-corlist)# member 1800Router(config-dp-corlist)# member 1900Router(config-dp-corlist)# member local_callRouter(config)# dial-peer cor list hrRouter(config-dp-corlist)# member 911Router(config-dp-corlist)# member 1800Router(config-dp-corlist)# member local_callIn the example below five dial peers are configured for destination numbers 734...., 1800......., 1900......., 316...., and 911. A COR list is applied to each of the dial peers.
Router(config)# dial-peer voice 1 voipRouter(config-dial-peer)# destination pattern 734....Router(config-dial-peer)# session target ipv4:1.1.1.1Router(config-dial-peer)# cor outgoing calllocalRouter(config)# dial-peer voice 2 voipRouter(config-dial-peer)# destination pattern 1800.......Router(config-dial-peer)# session target ipv4:1.1.1.1Router(config-dial-peer)# cor outgoing call1800Router(config)# dial-peer voice 3 potsRouter(config-dial-peer)# destination pattern 1900.......Router(config-dial-peer)# port 1/0/0Router(config-dial-peer)# cor outgoing call1900Router(config)# dial-peer voice 4 potsRouter(config-dial-peer)# destination pattern 911Router(config-dial-peer)# port 1/0/1Router(config-dial-peer)# cor outgoing call911Router(config)# dial-peer voice 5 potsRouter(config-dial-peer)# destination pattern 316....Router(config-dial-peer)# port 1/1/0 ; No cor is applied.Finally, the COR list is applied to the individual phone numbers.
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# max-conferences 8Router(config-cm-fallback)# cor incoming engineering 1 1001 - 1001Router(config-cm-fallback)# cor incoming hr 2 1002 - 1002Router(config-cm-fallback)# cor incoming manager 3 1003 - 1008The example configuration allows for the following:
•
•
•
•
Related Commands
date-format (cm-fallback)
To set the date display format on all the Cisco IP phones attached to the router, use the date-format command in CallManager fallback configuration mode. To display the date in the default format, use the no form of this command.
date-format {mm-dd-yy | dd-mm-yy}
no date-format {mm-dd-yy | dd-mm-yy}
Syntax Description
mm-dd-yy
Sets to month, day, and year. Each slot needs a two-digit number. This format is the default setting.
dd-mm-yy
Sets to day, month, and year. Each slot needs a two-digit number.
Defaults
The default is mm-dd-yy.
Command Modes
CallManager fallback configuration
Command History
Examples
The following example sets the date format to date, month, and year for all affected Cisco IP phones:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# date-format dd-mm-yyRelated Commands
call-manager-fallback
Enables SRS Telephony feature support and enters CallManager fallback configuration mode.
debug ephone alarm
To set SkinnyStation alarm messages debugging for the Cisco IP phone, use the debug ephone alarm command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ephone alarm [mac-address mac-address]
no debug ephone alarm [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone alarm command shows all the SkinnyStation alarm messages sent by the Cisco IP phone. Under normal circumstances, this message is sent by the Cisco IP phone just before it registers, and has the severity level for the alarm set to "Informational" and contains the reason for the phone reboot or reregister. This type of message is entirely benign and does not indicate an error condition.
If the mac-address keyword is not used, the debug ephone alarm command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
Debugging can be enabled or disabled on any number of Cisco IP phones. The Cisco IP phones that have debugging enabled can be displayed by entering the show ephone command. Look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for any Cisco IP phone directory numbers associated with the Cisco IP phone.
Examples
The following example shows a SkinnyStation alarm message that is sent before the Cisco IP phone registers:
Router# debug ephone alarmphone keypad resetCM-closed-TCPCM-bad-stateRelated Commands
debug ephone detail
To set detail debugging for the Cisco IP phone, use the debug ephone detail command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ephone detail [mac-address mac-address]
no debug ephone detail [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone detail command output includes the error and state levels.
If the mac-address keyword is not used, the debug ephone detail command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
Debugging can be enabled or disabled on any number of Cisco IP phones. The Cisco IP phones that have debugging enabled can be displayed by entering the show ephone command. Look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for any Cisco IP phone directory numbers or virtual voice ports associated with the Cisco IP phone.
Examples
The following is sample output of detail debugging of the Cisco IP phone with MAC address 0030.94c3.8724. The sample is an excerpt of some of the activities that take place during call setup, connected state, active call, and the call getting disconnected:
Router# debug ephone detail mac-address 0030.94c3.8724Ephone detail debugging is enabled1d04h: ephone-1[1]:OFFHOOK..1d04h: Skinny Call State change for DN 1 SIEZE..1d04h: ephone-1[1]:SetCallState line 1 DN 1 TsOffHook..1d04h: ephone-1[1]:SetLineLamp 1 to ON..1d04h: ephone-1[1]:KeypadButtonMessage 5..1d04h: ephone-1[1]:KeypadButtonMessage 0..1d04h: ephone-1[1]:KeypadButtonMessage 0..1d04h: ephone-1[1]:KeypadButtonMessage 2..1d04h: ephone-1[1]:Store ReDial digit: 5002.SkinnyTryCall to 5002 instance 1..1d04h: ephone-1[1]:Store ReDial digit: 50021d04h: ephone-1[1]:SkinnyTryCall to 5002 instance 1..1d04h: Skinny Call State change for DN 1 ALERTING..1d04h: ephone-1[1]:SetCallState line 1 DN 1 TsRingOut..1d04h: ephone-1[1]:SetLineLamp 1 to ON1d04h: SetCallInfo calling dn 1 dn 1calling [5001] called [5002]..1d04h: ephone-1[1]: party1 calling1d04h: ephone-1[1]: party2..1d04h: SkinnyUpdateDnState by EFXS_RING_GENERATEfor DN 2 to state RINGING..1d04h: SkinnyGetCallState for DN 2 CONNECTED..1d04h: ephone-1[1]:SetLineLamp 3 to ON1d04h: ephone-1[1]:UpdateCallState DN 1 state 4 calleddn 2..1d04h: Skinny Call State change for DN 1 CONNECTED..1d04h: ephone-1[1]:OpenReceive DN 1 codec 4:G711Ulaw64k duration 10 ms bytes 80..1d04h: ephone-1[1]:OpenReceiveChannelAck 1.2.172.21 port=201801d04h: ephone-1[1]:Outgoing calling DN 1 Far-ephone-2 called DN 21d04h: SkinnyGetCallState for DN 1 CONNECTED..1d04h: ephone-1[1]:SetCallState line 3 DN 2 TsOnHook..1d04h: ephone-1[1]:SetLineLamp 3 to OFF..1d04h: ephone-1[1]:SetCallState line 1 DN 1 TsOnHook..1d04h: ephone-1[1]:Clean Up Speakerphone state1d04h: ephone-1[1]:SpeakerPhoneOnHook1d04h: ephone-1[1]:Clean up activeline 11d04h: ephone-1[1]:StopTone sent to ephone1d04h: ephone-1[1]:Clean Up phone offhook state1d04h: SkinnyGetCallState for DN 1 IDLE1d04h: called DN -1, calling DN -1 phone -11d04h: ephone-1[1]:SetLineLamp 1 to OFF1d04h: UnBinding ephone-1 from DN 11d04h: UnBinding called DN 2 from DN 11d04h: ephone-1[1]:ONHOOK1d04h: ephone-1[1]:SpeakerPhoneOnHook1d04h: ephone-1[1]:ONHOOK NO activeline...Related Commands
debug ephone error
To set error debugging for the Cisco IP phone, use the debug ephone error command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ephone error [mac-address mac-address]
no debug ephone error [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug phone error command cancels debugging at the detail and state level. This command is used to detect significant internal errors.
If the mac-address keyword is not used, the debug ephone error debug command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
Debugging can be enabled or disabled on any number of Cisco IP phones. The Cisco IP phones that have debugging enabled can be displayed by entering the show ephone command. Look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for any Cisco IP phone directory numbers or virtual voice ports associated with the Cisco IP phone.
Examples
The following is sample output of error debugging for the Cisco IP phone with MAC address 0030.94c3.8724:
Router# debug ephone error mac-address 0030.94c3.8724EPHONE error debugging is enabledsocket [2] send ERROR 11Skinny Socket [2] retry failureRelated Commands
debug ephone keepalive
To set keepalive debugging for the Cisco IP phone, use the debug ephone keepalive command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ephone keepalive [mac-address mac-address]
no debug ephone keepalive [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone keepalive command sets keepalive debugging.
If the mac-address keyword is not used, the debug ephone keepalive debug command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
Debugging can be enabled or disabled on any number of Cisco IP phones. The Cisco IP phones that have debugging enabled can be displayed by entering the show ephone command. Look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for any Cisco IP phone directory numbers or virtual voice ports associated with the Cisco IP phone.
Examples
The following is sample output of the keepalive status for the Cisco IP phone with MAC address 0030.94C3.E1A8:
Router# debug ephone keepalive mac-address 0030.94c3.E1A8EPHONE keepalive debugging is enabled for phone 0030.94C3.E1A81d05h: ephone-1 Set interface FastEthernet0/0 ETHERNET1d05h: ephone-1[1]:Keepalive socket[1] SEP003094C3E1A81d05h: ephone-1 Set interface FastEthernet0/0 ETHERNET1d05h: ephone-1[1]:Keepalive socket[1] SEP003094C3E1A81d05h: Skinny Checking for stale sockets1d05h: ephone-1 Set interface FastEthernet0/0 ETHERNET1d05h: ephone-1[1]:Keepalive socket[1] SEP003094C3E1A81d05h: ephone-1 Set interface FastEthernet0/0 ETHERNET1d05h: ephone-1[1]:Keepalive socket[1] SEP003094C3E1A81d05h: Skinny active socket list (3/96): 1 2 4Related Commands
debug ephone pak
To provide voice packet level debugging and to print the contents of one voice packet in every 1024 voice packets, use the debug ephone pak command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ephone pak [mac-address mac-address]
no debug ephone pak [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone pak command provides voice packet level debugging and prints the contents of one voice packet in every 1024 voice packets.
If the mac-address keyword is not used, the debug ephone pak debug command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
Debugging can be enabled or disabled on any number of Cisco IP phones. The Cisco IP phones that have debugging enabled can be displayed by entering the show ephone command. Look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for any Cisco IP phone directory numbers or virtual voice ports associated with the Cisco IP phone.
Examples
The following is sample output of packet debugging for the Cisco IP phone with MAC address 0030.94c3.8724:
Router# debug ephone pak mac-address 0030.94c3.8724EPHONE packet debugging is enabled01:29:14: ***ph_xmit_ephone DN 3 tx_pkts 5770 dest=10.2.1.1 orig len=32pakcopy=0 discards 27 ip_enctype 0 0 last discard: unsupported payload type01:29:14: to_skinny_duration 130210 offset -30 last -40 seq 0 adj 001:29:14: IP: 45B8 003C 0866 0000 3F11 3F90 2800 0001 0A02 010101:29:14: TTL 63 TOS B8 prec 501:29:14: UDP: 07D0 6266 0028 000001:29:14: sport 2000 dport 25190 length 40 checksum 001:29:14: RTP: 8012 16AF 9170 6409 0E9F 000101:29:14: is_rtp:1 is_frf11:0 vlen:0 delta_t:160 vofr1:0 vofr2:0scodec:11 rtp_bits:8012 rtp_codec:18 last_bad_payload 1901:29:14: vencap FAILED01:29:14: PROCESS SWITCH01:29:15: %SYS-5-CONFIG_I: Configured from console by console01:29:34: ***SkinnyPktIp DN 3 10.2.1.1 to 40.0.0.1 pkts 4880 FAST sw01:29:34: from_skinny_duration 15091001:29:34: nw 3BBC2A8 addr 3BBC2A4 mac 3BBC2A4 dg 3BBC2C4 dgs 2A01:29:34: MAC: 1841 080001:29:34: IP: 45B8 0046 682E 0000 3E11 E0BD 0A02 0101 2800 000101:29:34: TTL 62 TOS B8 prec 501:29:34: UDP: 6266 07D0 0032 000001:29:34: sport 25190 dport 2000 length 50 checksum 001:29:34: RTP: 8012 55FF 0057 8870 3AF4 C39401:29:34: RTP: rtp_bits 8012 seq 55FF ts 578870 ssrc 3AF4C39401:29:34: PAYLOAD:01:29:34: 1409 37C9 54DE 449C 3B42 0446 3AAB 182E01:29:34: 56BC 5184 58E5 56D3 13BE 44A7 B8C401:29:34:01:29:37: ***ph_xmit_ephone DN 3 tx_pkts 6790 dest=10.2.1.1 orig len=32pakcopy=0 discards 31 ip_enctype 0 0 last discard: unsupported payload type01:29:37: to_skinny_duration 153870 offset -150 last -40 seq 0 adj 001:29:37: IP: 45B8 003C 0875 0000 3F11 3F81 2800 0001 0A02 010101:29:37: TTL 63 TOS B8 prec 501:29:37: UDP: 07D0 6266 0028 000001:29:37: sport 2000 dport 25190 length 40 checksum 001:29:37: RTP: 8012 1AAF 9173 4769 0E9F 000101:29:37: is_rtp:1 is_frf11:0 vlen:0 delta_t:160 vofr1:0 vofr2:0Related Commands
debug ephone raw
To provide raw low-level protocol debugging display for all SCCP messages, use the debug ephone raw command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ephone raw [mac-address mac-address]
no debug ephone raw [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone raw command's debug display provides byte level display of Skinny TCP socket messages.
If the mac-address keyword is not used, the debug ephone raw debug command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
Debugging can be enabled or disabled on any number of Cisco IP phones. The Cisco IP phones that have debugging enabled can be displayed by entering the show ephone command. Look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for any Cisco IP phone directory numbers or virtual voice ports associated with the Cisco IP phone.
Examples
The following is sample output of raw protocol debugging for the Cisco IP phone with MAC address 0030.94c3.E1A8:
Router# debug ephone raw mac-address 0030.94c3.E1A8EPHONE raw protocol debugging is enabled for phone 0030.94C3.E1A81d05h: skinny socket received 4 bytes on socket [1]0 0 0 01d05h:1d05h: SkinnyMessageID = 01d05h: skinny send 4 bytes4 0 0 0 0 0 0 0 0 1 0 01d05h: socket [1] sent 12 bytes OK (incl hdr) for ephone-(1)1d06h: skinny socket received 4 bytes on socket [1]0 0 0 01d06h:1d06h: SkinnyMessageID = 01d06h: skinny send 4 bytes4 0 0 0 0 0 0 0 0 1 0 01d06h: socket [1] sent 12 bytes OK (incl hdr) for ephone-(1)Related Commands
debug ephone register
To set registration debugging for the Cisco IP phone, use the debug ephone register command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ephone register [mac-address mac-address]
no debug ephone register [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If the mac-address keyword is not used, the debug ephone register debug command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
Debugging can be enabled or disabled on any number of Cisco IP phones. The Cisco IP phones that have debugging enabled can be displayed by entering the show ephone command. Look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for any Cisco IP phone directory numbers or virtual voice ports associated with the Cisco IP phone.
Examples
The following is sample output of registration debugging for the Cisco IP phone with MAC address 0030.94c3.8724:
Router# debug ephone register mac-address 0030.94c3.8724Ephone registration debugging is enabled1d06h: New Skinny socket accepted [1] (2 active)1d06h: sin_family 2, sin_port 50778, in_addr 10.1.0.211d06h: skinny_add_socket 1 10.1.0.21 507781d06h: ephone-(1)[1] StationRegisterMessage (2/3/12) from 10.1.0.211d06h: ephone-(1)[1] Register StationIdentifier DeviceName SEP003094C3E1A81d06h: ephone-(1)[1] StationIdentifier Instance 1 deviceType 71d06h: ephone-1[-1]:stationIpAddr 10.1.0.211d06h: ephone-1[-1]:maxStreams 01d06h: ephone-(1) Allow any Skinny Server IP address 10.1.0.6..1d06h: ephone-1[1]:RegisterAck sent to ephone 1: keepalive period 30..Related Commands
debug ephone state
To set state debugging for the Cisco IP phone, use the debug ephone state command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ephone state [mac-address mac-address]
no debug ephone state [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
If the mac-address keyword is not used, the debug ephone state debug command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
Debugging can be enabled or disabled on any number of Cisco IP phones. The Cisco IP phones that have debugging enabled can be displayed by entering the show ephone command. Look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for any Cisco IP phone directory numbers or virtual voice ports associated with the Cisco IP phone.
Examples
The following is sample output of state debugging for the Cisco IP phone with MAC address 0030.94c3.E1A8:
Router# debug ephone state mac-address 0030.94c3.E1A8EPHONE state debugging is enabled for phone 0030.94C3.E1A81d06h: ephone-1[1]:OFFHOOK1d06h: ephone-1[1]:SIEZE on activeline 01d06h: ephone-1[1]:SetCallState line 1 DN 1 TsOffHook1d06h: ephone-1[1]:Skinny-to-Skinny call DN 1 to DN 2 instance 11d06h: ephone-1[1]:SetCallState line 1 DN 1 TsRingOut1d06h: ephone-1[1]:Call Info DN 1 line 1 ref 158 called 5002 calling 50011d06h: ephone-1[1]: Jane calling1d06h: ephone-1[1]: Jill1d06h: ephone-1[1]:SetCallState line 3 DN 2 TsRingIn1d06h: ephone-1[1]:Call Info DN 2 line 3 ref 159 called 5002 calling 50011d06h: ephone-1[1]: Jane calling1d06h: ephone-1[1]: Jill1d06h: ephone-1[1]:SetCallState line 3 DN 2 TsCallRemoteMultiline1d06h: ephone-1[1]:SetCallState line 1 DN 1 TsConnected1d06h: ephone-1[1]:OpenReceive DN 1 codec 4:G711Ulaw64k duration 10 ms bytes 801d06h: ephone-1[1]:OpenReceiveChannelAck 1.2.172.21 port=240101d06h: ephone-1[1]:StartMedia 1.2.172.22 port=246121d06h: DN 1 codec 4:G711Ulaw64k duration 10 ms bytes 801d06h: ephone-1[1]:CloseReceive1d06h: ephone-1[1]:StopMedia1d06h: ephone-1[1]:SetCallState line 3 DN 2 TsOnHook1d06h: ephone-1[1]:SetCallState line 1 DN 1 TsOnHook1d06h: ephone-1[1]:SpeakerPhoneOnHook1d06h: ephone-1[1]:ONHOOK1d06h: ephone-1[1]:SpeakerPhoneOnHook1d06h: SkinnyReportDnState DN 1 ONHOOKRelated Commands
debug ephone statistics
To set call statistics debugging for the Cisco IP phone, use the debug ephone statistics command in privileged EXEC mode. To disable debugging, use the no form of this command.
debug ephone statistics [mac-address mac-address]
no debug ephone statistics [mac-address mac-address]
Syntax Description
mac-address
(Optional) Defines the MAC address of the Cisco IP phone.
mac-address
(Optional) Specifies the MAC address of the Cisco IP phone.
Command Modes
Privileged EXEC
Command History
Usage Guidelines
The debug ephone statistics command provides a debug monitor display of the periodic messages from the Cisco IP phone to the router. These messages include transmit-and-receive packet counts and an estimate of drop packets. The call statistics can also be displayed for live calls using the show ephone command.
If the mac-address keyword is not used, the debug ephone statistics debug command debugs all Cisco IP phones that are registered to the router. You can remove debugging for the Cisco IP phones that you do not want to debug by using the mac-address keyword with the no form of this command.
Debugging can be enabled or disabled on any number of Cisco IP phones. The Cisco IP phones that have debugging enabled can be displayed by entering the show ephone command. Look at the debug field in the output. When debugging is enabled for a Cisco IP phone, the debug output is displayed for any Cisco IP phone directory numbers or virtual voice ports associated with the Cisco IP phone.
Examples
The following is sample output of statistics debugging for the Cisco IP phone with MAC address 0030.94C3.E1A8:
Router# debug ephone statistics mac-address 0030.94C3.E1A8EPHONE statistics debugging is enabled for phone 0030.94C3.E1A81d06h: Clear Call Stats for DN 1 call ref 1621d06h: Clear Call Stats for DN 1 call ref 1621d06h: Clear Call Stats for DN 1 call ref 1621d06h: Clear Call Stats for DN 2 call ref 1631d06h: ephone-1[1]:GetCallStats line 1 ref 162 DN 1: 50011d06h: ephone-1[1]:Call Stats for line 1 DN 1 5001 ref 1621d06h: ephone-1[1]:TX Pkts 0 bytes 0 RX Pkts 0 bytes 01d06h: ephone-1[1]:Pkts lost 4504384 jitter 0 latency 01d06h: ephone-1[1]:Src 0.0.0.0 0 Dst 0.0.0.0 0 bytes 80 vad 0 G711Ulaw64k1d06h: ephone-1[1]:GetCallStats line 1 ref 162 DN 1: 50011d06h: STATS: DN 1 Packets Sent 01d06h: STATS: DN 2 Packets Sent 01d06h: ephone-1[1]:Call Stats found DN -1 from Call Ref 1621d06h: ephone-1[1]:Call Stats for line 0 DN -1 5001 ref 1621d06h: ephone-1[1]:TX Pkts 275 bytes 25300 RX Pkts 275 bytes 253001d06h: ephone-1[1]:Pkts lost 0 jitter 0 latency 0Related Commands
default-destination (cm-fallback)
To assign a default destination number for incoming telephone calls on the SRS Telephony router, use the default-destination command in CallManager fallback configuration mode. To delete the default destination number on the SRS Telephony router, use the no form of this command.
default-destination phone-number
no default-destination phone-number
Syntax Description
Defaults
No default behavior or values.
Command Modes
CallManager fallback configuration
Command History
Usage Guidelines
The default-destination command assigns default destination numbers when a call arrives at an Foreign Exchange Office (FXO) port without called number information. A default directory number is required to route the call.
If a default destination number is set, calls arriving on an FXO port are routed to the default destination number that is provided. If a default destination number is not set, calls arriving on the FXO port receive a secondary dial tone. The caller must then enter the extension number.
Examples
The following example sets the default destination to 40802:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# default-destination 40802Related Commands
dialplan-pattern (cm-fallback)
To create a global prefix that can be used to expand the extension numbers of inbound and outbound calls into fully qualified E.164 numbers, use the dialplan-pattern command in call-manager-fallback configuration mode. To disable the dialplan-pattern command settings, use the no form of this command.
dialplan-pattern tag pattern extension-length extension-length [extension-pattern extension-pattern] [no-reg]
no dialplan-pattern tag [pattern extension-length extension-length extension-pattern extension-pattern] [no-reg]
Syntax Description
Defaults
No default behavior or values
Command Modes
Call-manager-fallback configuration
Command History
Usage Guidelines
The dialplan-pattern command builds additional dial peers. For example, if a hidden Plain Old Telephone System (POTS) dial peer is created, such as the following:
Router(config)# dial-peer voice 20001 potsRouter(config-dial-peer)# destination-pattern 1001Router(config-dial-peer)# voice-port 50/0/2and a dial- plan pattern is created, such as 40855510.., then an additional dial peer will be created that allows calls to both the 1001 and 4085551001 numbers. For example:
Router(config)# dial-peer voice 20002 potsRouter(config-dial-peer)# destination-pattern 4085551001Router(config-dial-peer)# voice-port 50/0/2Both dial peers can be seen with the show dial-peer command.
The dialplan-pattern command also creates a global prefix that can be used by inbound calls (calls to an IP phone in a Cisco SRST system) and outbound calls (calls made from an IP phone in a Cisco SRST system) to expand their extension numbers to fully qualified E.164 numbers.
For inbound calls (calls to an IP phone in a Cisco SRST system) where the calling party number matches the dial-plan pattern, the call is considered a local call and has a distinctive ring that identifies the call as internal. Any calling party number that does not match the dial-plan pattern is considered an external call and has a distinctive ring that is different from the internal ringing.
For outbound calls, the dialplan-pattern command converts the calling party's extension number to an E.164 calling party number. Outbound calls that do not use an E.164 number and go through a Primary Rate Interface (PRI) connection to the Public Switched Telephony Network (PSTN), may be rejected by the PRI link as the calling party identifier.
A dial-plan pattern is required to register the Cisco IP phone lines with a gatekeeper. Directory numbers for the Cisco IP phones must match the number the extension-length argument. For example, if the extension length is 3, then all extension must be three numbers in length. Otherwise, the extension number cannot be converted to a qualified E.164 number.
If there are multiple patterns, called-party numbers are checked in numeric order, starting with pattern 1, until a match is found or the until last pattern has been checked. The valid dial-plan pattern with the lowest tag is used as a prefix to all local Cisco IP phones.
When extension-pattern extension-length keyword and argument are used, the leading digits of an extension pattern are stripped and replaced with the corresponding leading digits of the dial-plan. For example, the following command maps all extension numbers 4xx to the PSTN number 40855501xx, so that extension 412 corresponds to 4085550112.
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# dialplan-pattern 1 4085550100 extension-length 3 extension-pattern 4..The number of extension-pattern argument characters must match the extension-length argument. For example, if the extension-length is three, then the extension-pattern can be 8.., 1.., 51., and so forth.
The no-reg keyword provides the option of not registering specific numbers to the gatekeeper so that those numbers can be used for other telephony services.
Examples
The following example shows how to create dial-plan pattern 1 for extension numbers 5000 to 5099 with a prefix of 408555. If an inbound calling party number (4085555044) matches dial-plan pattern 1, then the recipient phone will display an extension (5044) as the caller ID and use an internal ringing tone. If an outbound calling party extension number (5044) matches dial-plan pattern 1, then the calling party extension will be converted to an E.164 number (4085555044). The E.164 calling party number that will appear as the caller ID.
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# dialplan-pattern 1 40855550.. extension-length 4 extension-pattern 50..In the following example the dialplan-pattern command creates dial-plan pattern 1 for extensions 800 to 899 with the telephone prefix starting with 4085559. As each number in the extension pattern is declared with the number command, two POTs dial-peers are created. In the example, they are 801 (an internal office number) and 4085579001 (an external number).
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# dialplan-pattern 1 40855590.. extension-length 3 extension-pattern 8..In the following example shows a configuration for two Cisco SRST systems. Each is configured with the same dialplan pattern commands, but one system uses 50.. and the other uses 60.. for extension numbers. Calls from the "50.." system to the "60.." system, and vice versa, are treated as internal calls. Calls that go across a H.323 network and calls that go to a PSTN through an Integrated Service Digital Network (ISDN) interface on one of the configured Cisco SRST routers are represented as E.164.
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# dialplan-pattern 1 40855550.. extension-length 4 extension-pattern 50..Router(config-cm-fallback)# dialplan-pattern 2 51055560.. extension-length 4 extension-pattern 60..Related Commands
call-manager-fallback
Enables Cisco SRST support and enters call-manager-fallback configuration mode.
huntstop (cm-fallback)
To set the huntstop attribute for the dial peers associated with the Cisco IP phone dial peers created during CallManager fallback, use the huntstop command in CallManager fallback configuration mode. To disable huntstop, use the no form of this command.
huntstop
no huntstop
Syntax Description
This command has no arguments or keywords.
Defaults
Huntstop is enabled by default.
Command Modes
CallManager fallback configuration
Command History
Usage Guidelines
In CallManager fallback configuration mode, huntstop is enabled by default. This command may be used in conjunction with the alias command, which creates targeted call destinations. Huntstop must be disabled for the alias command to work properly.
In CallManager fallback configuration mode, the huntstop attribute by default is set uniformly to all Cisco IP phone lines (for example, to all or to none).
Note
Examples
The following example shows how to disable huntstop for all the Cisco IP phones:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# no huntstopRelated Commands
ip source-address (cm-fallback)
To enable a router to receive messages from Cisco IP phones through the specified IP addresses and ports, use the ip source-address command in CallManager fallback configuration mode. To disable the router from receiving messages from Cisco IP phones, use the no form of this command.
ip source-address ip-address [port port] [any-match | strict-match]
no ip source-address [ip-address port port] [any-match | strict-match]
Syntax Description
Defaults
Default port number: 2000
Default server address match: any-matchCommand Modes
CallManager fallback configuration
Command History
Usage Guidelines
The ip source-address command is a mandatory command, and the fallback subsystem does not start if the IP address is not provided. If the port number is not provided, the default value (2000) is used. The IP address is usually the IP address of the Ethernet port to which the phones are connected.
Use the any-match keyword to instruct the router to permit Cisco IP phone registration even when the IP server address used by the phone does not match the IP source address. This option can be used to allow registration of Cisco IP phones on different subnets with different default Dynamic Host Configuration Protocol (DHCP) routers or different TFTP server addresses.
Use the strict-match keyword to instruct the router to reject Cisco IP phone registration attempts if the IP server address used by the phone does not exactly match the source address. By dividing the Cisco IP phones into groups on different subnets and giving each group different DHCP default-router or TFTP server addresses, this option can be used to restrict the number of Cisco IP phones allowed to register.
The ip source-address command enables a router to receive messages from Cisco IP phones through the specified IP addresses and port. If the router receives a registration request from a Cisco IP phone, the router in return requests the phone configuration and dial-plan information from the Cisco IP phone. This data is stored locally in the memory of the router and is used to create voice port and dial-plan information. The voice port and dial-plan information is used to handle telephony calls to and from the Cisco IP phone if the Cisco CallManager is unreachable.
Examples
The following example shows how to set the IP source address and port:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# ip source-address 10.6.21.4 port 2002 strict-matchRelated Commands
call-manager-fallback
Enables SRS Telephony feature support and enters CallManager fallback configuration mode.
keepalive (cm-fallback)
To configure the time interval between successive keepalive messages from Cisco IP phones, use the keepalive command in CallManager fallback configuration mode. To restore the default interval, use the no form of this command.
keepalive seconds
no keepalive seconds
Syntax Description
seconds
Keepalive message transmission interval, in seconds. The valid range is from 10 to 65535 seconds. The default timeout value is 30.
Defaults
30 seconds
Command Modes
CallManager fallback configuration
Command History
Usage Guidelines
The keepalive command configures the time interval between successive keepalive messages from Cisco IP phones to the SRS Telephony router. If the router fails to receive three successive keepalive messages, it considers the Cisco IP phone to be out of service until the phone reregisters.
Note
Examples
The following example sets the keepalive timeout value to 60 seconds:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# keepalive 60Related Commands
call-manager-fallback
Enables SRS Telephony feature support and enters CallManager fallback configuration mode.
limit-dn (cm-fallback)
To specify the maximum number of lines available on each Cisco IP phone, use the limit-dn command in CallManager fallback configuration mode. To return to the default setting, use the no form of this command.
limit-dn {7910 | 7940 | 7960} max-lines
no limit-dn [7910 | 7940 | 7960]
Syntax Description
7910
Cisco IP Phone 7910.
7940
Cisco IP Phone 7940.
7960
Cisco IP Phone 7960.
max-lines
Maximum lines setting is from 1 to 34. The default is 34.
Defaults
Maximum number of lines: 34
Command Modes
CallManager fallback configuration
Command History
Usage Guidelines
The limit-dn command specifies the maximum number of lines (directory numbers) available for each Cisco IP phone type.
Note
The range of the maximum number of lines is from 1 to 34. The default number of lines is 34. If there is any active phone with a number greater than the specified limit, warning information is displayed for phone reset.
Examples
The following example shows how to set a directory number limit of two for the Cisco IP Phone 7910:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# limit-dn 7910 2Related Commands
call-manager-fallback
Enables SRS Telephony feature support and enters CallManager fallback configuration mode.
max-dn (cm-fallback)
To set the maximum number of directory numbers or virtual voice ports that can be supported by the router, use the max-dn command in CallManager fallback configuration mode. To return to the default number of directories or virtual voice ports, use the no form of this command.
max-dn max-directory-numbers
no max-dn
Syntax Description
max-directory-numbers
Maximum number of directory numbers or virtual voice ports supported by the router. The maximum number is platform-dependent. See the "Memory Requirements" section. The default is 0.
Defaults
0 directory numbers
Command Modes
CallManager fallback configuration
Command History
Usage Guidelines
The max-dn command limits the number of Cisco IP phone directory numbers or virtual voice ports available on the router.
Note
Examples
The following example sets the maximum number of directory numbers or virtual voice ports to 12:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# max-dn 12Related Commands
call-manager-fallback
Enables SRS Telephony feature support and enters CallManager fallback configuration mode.
max-ephones (cm-fallback)
To configure the maximum number of Cisco IP phones that can be supported by a router, use the max-ephones command in CallManager fallback configuration mode. To return to the default number of Cisco IP phones, use the no form of this command.
max-ephones max-phones
no max-ephones
Syntax Description
max-phones
Maximum number of Cisco IP phones supported by the router. The maximum number is platform-dependent. See the "Memory Requirements" section. The default is 0.
Defaults
0 Cisco IP phones
Command Modes
CallManager fallback configuration
Command History
Usage Guidelines
The max-ephones command limits the number of Cisco IP phones supported on the router.
Note
Examples
The following example sets the maximum number of Cisco IP phones for a Cisco router to 24:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# max-ephones 24Related Commands
call-manager-fallback
Enables SRS Telephony feature support and enters CallManager fallback configuration mode.
moh (cm-fallback)
To configure music on hold (MOH), use the moh command in CallManager fallback configuration mode. To disable music on hold, use the no form of this command.
moh filename
no moh filename
Syntax Description
Defaults
MOH is enabled by default.
Command Modes
CallManager fallback configuration
Command History
Usage Guidelines
The moh command allows you to specify the .au and .wav format music files that are played to callers who have been put on hold. MOH works only for G.711 calls and on-net Voice over IP (VoIP) and Public Switched Telephone Network (PSTN) calls. For all other calls, callers hear a periodic tone. For example, internal calls between Cisco IP phones do not get MOH, instead callers hear a tone.
Note
Examples
The following example enables MOH and specifies the music files:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# moh minuet.wavRouter(config-cm-fallback)# moh minuet.auRelated Commands
call-manager-fallback
Enables SRS Telephony feature support and enters CallManager fallback configuration mode.
pattern direct (vm-integration)
To configure the dual-tone multifrequency (DTMF) digit pattern forwarding necessary to activate the voice-mail system when the user presses the messages button on the phone, use the pattern direct command in voice-mail integration configuration mode. To disable DTMF digit pattern forwarding when the user presses the messages button on the phone, use the no form of this command.
pattern direct tag1 {CGN | CDN | FDN} [tag2 {CGN | CDN | FDN}]
[tag3 {CGN | CDN | FDN}] [last-tag]no pattern direct tag1 {CGN | CDN | FDN} [tag2 {CGN | CDN | FDN}]
[tag3 {CGN | CDN | FDN}] [last-tag]Syntax Description
Defaults
This feature is disabled by default.
Command Modes
Voice-mail integration configuration
Command History
Usage Guidelines
The pattern direct command is used to configure the sequence of DTMF digits passed to a voice-mail system attached to the Cisco IOS Telephony Service router through one or more voice ports. When a call is placed directly from a Cisco IP phone attached to the Cisco IOS Telephony Service router, the voice-mail system expects to receive a sequence of DTMF digits at the beginning of the call that identify the mailbox of the user calling the voice-mail system accompanied by a string of digits indicating that the caller is attempting to access the designated mailbox in order to retrieve messages.
Although it is unlikely that you will use multiple instances of the CGN, CDN, or FDN keyword in a single command line, it is permissible to do so.
Examples
The following example sets the DTMF pattern for a calling number ($CGN) for a direct call to the voice-mail system:
Router(config) vm-integrationRouter(config-vm-integration) pattern direct 2 CGN *Related Commands
pattern ext-to-ext busy (vm-integration)
To configure the dual-tone multifrequency (DTMF) digit pattern forwarding necessary to activate the voice-mail system once an internal extension attempts to connect to a busy extension and the call is forwarded to voice mail, use the pattern ext-to-ext busy command in voice-mail integration configuration mode. To disable DTMF digit pattern forwarding when an internal extension calls a busy extension and the call is forwarded to a voice-mail system, use the no form of this command.
pattern ext-to-ext busy tag1 {CGN | CDN | FDN} [tag2 {CGN | CDN | FDN}]
[tag3 {CGN | CDN | FDN}] [last-tag]no pattern ext-to-ext busy tag1 {CGN | CDN | FDN} [tag2 {CGN | CDN | FDN}]
[tag3 {CGN | CDN | FDN}] [last-tag]Syntax Description
Defaults
This feature is disabled by default.
Command Modes
Voice-mail integration configuration
Command History
Usage Guidelines
The pattern ext-to-ext busy command is used to configure the sequence of DTMF digits passed to a voice-mail system attached to the Cisco IOS Telephony Service router through one or more voice ports. When a call is routed to the voice-mail system by call forward on busy from a Cisco IP phone attached to the Cisco IOS Telephony Service router, the voice-mail system expects to receive a sequence of digits identifying the mailbox associated with the forwarding phone together with digits that identify the extension number of the calling IP phone.
Although it is unlikely that you will use multiple instances of the CGN, CDN, or FDN keyword in a single command line, it is permissible to do so.
Examples
The following example sets the DTMF pattern for a local call forwarded on busy to the voice-mail system:
Router(config) vm-integrationRouter(config-vm-integration) pattern ext-to-ext busy 7 FDN * CGN *Related Commands
pattern ext-to-ext no-answer (vm-integration)
To configure the dual-tone multifrequency (DTMF) digit pattern forwarding necessary to activate the voice-mail system once an internal extension fails to connect to an extension and the call is forwarded to voice mail, use the pattern ext-to-ext no-answer command in voice-mail integration configuration mode. To disable DTMF digit pattern forwarding, use the no form of this command.
pattern ext-to-ext no-answer tag1 {CGN | CDN | FDN} [tag2 {CGN | CDN | FDN}]
[tag3 {CGN | CDN | FDN}] [last-tag]no pattern ext-to-ext no-answer tag1 {CGN | CDN | FDN} [tag2 {CGN | CDN | FDN}]
[tag3 {CGN | CDN | FDN}] [last-tag]Syntax Description
Defaults
This feature is disabled by default.
Command Modes
Voice-mail integration configuration
Command History
Usage Guidelines
The pattern ext-to-ext no-answer command is used to configure the sequence of DTMF digits passed to a voice-mail system attached to the Cisco IOS Telephony Service router through one or more voice ports. When a call is routed to the voice-mail system by call forward on no-answer from an IP phone attached to the Cisco IOS Telephony Service router, the voice-mail system expects to receive a sequence of digits identifying the mailbox associated with the forwarding phone together with digits that identify the extension number of the calling IP phone.
Although it is unlikely that you will use multiple instances of the CGN, CDN, or FDN keyword in a single command line, it is permissible to do so.
Examples
The following example sets the DTMF pattern for a local call forwarded on no-answer to the voice-mail system:
Router(config) vm-integrationRouter(config-vm-integration) pattern ext-to-ext no-answer 5 FDN * CGN *Related Commands
pattern trunk-to-ext busy (vm-integration)
To configure the dual-tone multifrequency (DTMF) digit pattern forwarding necessary to activate the voice-mail system once an external trunk call reaches a busy extension and the call is forwarded to voice mail, use the pattern trunk-to-ext busy command in voice-mail integration configuration mode. To disable DTMF digit pattern forwarding when an external trunk call reaches a busy extension and the call is forwarded to a voice-mail system, use the no form of this command.
pattern trunk-to-ext busy tag1 {CGN | CDN | FDN} [tag2 {CGN | CDN | FDN}]
[tag3 {CGN | CDN | FDN}] [last-tag]no pattern trunk-to-ext busy tag1 {CGN | CDN | FDN} [tag2 {CGN | CDN | FDN}]
[tag3 {CGN | CDN | FDN}] [last-tag]Syntax Description
Defaults
This feature is disabled by default.
Command Modes
Voice-mail integration configuration
Command History
Usage Guidelines
The pattern trunk-to-ext busy command is used to configure the sequence of DTMF digits passed to a voice-mail system attached to the Cisco IOS Telephony Service router through one or more voice ports. When a call is routed to the voice-mail system by call forward on busy from an IP phone attached to the Cisco IOS Telephony Service router, the voice-mail system expects to receive a sequence of digits identifying the mailbox associated with the forwarding phone together with digits indicating that the call originated from a Public Switched Telephone Network (PSTN) or Voice over IP (VoIP) caller.
Although it is unlikely that you will use multiple instances of the CGN, CDN, or FDN keyword in a single command line, it is permissible to do so.
Examples
The following example sets the DTMF pattern for call forwarding when an external trunk call reaches a busy extension and the call is forwarded to the voice-mail system:
Router(config) vm-integrationRouter(config-vm-integration) pattern trunk-to-ext busy 6 FDN * CGN *Related Commands
pattern trunk-to-ext no-answer (vm-integration)
To configure the dual-tone multifrequency (DTMF) digit pattern forwarding necessary to activate the voice-mail system when an external trunk call reaches an unanswered extension and the call is forwarded to voice mail, use the pattern trunk-to-ext no-answer command in voice-mail integration configuration mode. To disable DTMF digit pattern forwarding when an external trunk call reaches another extension where the called party does not answer and the call is forwarded to a voice-mail system, use the no form of this command.
pattern trunk-to-ext no-answer tag1 {CGN | CDN | FDN} [tag2 {CGN | CDN | FDN}]
[tag3 {CGN | CDN | FDN}] [last-tag]no pattern trunk-to-ext no-answer tag1 {CGN | CDN | FDN} [tag2 {CGN | CDN | FDN}]
[tag3 {CGN | CDN | FDN}] [last-tag]Syntax Description
Defaults
This feature is disabled by default.
Command Modes
Voice-mail integration configuration
Command History
Usage Guidelines
The pattern trunk-to-ext no-answer command is used to configure the sequence of DTMF digits passed to a voice-mail system attached to the Cisco IOS Telephony Service router through one or more voice ports. When a call is routed to the voice-mail system by call forward on no-answer from an IP phone attached to the Cisco IOS Telephony Service router, the voice-mail system expects to receive a sequence of digits identifying the mailbox associated with the forwarding phone together with digits indicating that the call originated from a Public Switched Telephone Network (PSTN) or Voice over IP (VoIP) caller.
Although it is unlikely that you will use multiple instances of the CGN, CDN, or FDN keyword in a single command line, it is permissible to do so.
Examples
The following example sets the DTMF pattern for call forwarding when an external trunk call reaches an unanswered extension and the call is forwarded (FDN) to a voice-mail system:
Router(config) vm-integrationRouter(config-vm-integration) pattern trunk-to-ext no-answer 4 FDN * CGN *Related Commands
reset (cm-fallback)
To reset Cisco IP phones, use the reset command in CallManager fallback configuration mode.
reset {all seconds | mac-address mac-address}
Syntax Description
Defaults
No default behavior or values.
Command Modes
CallManager fallback configuration
Command History
Usage Guidelines
This command does not have a no form.
Examples
The following example resets all Cisco IP phones in eight-second intervals:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# reset all 8The following example resets the Cisco IP phone with MAC address CFBA.321B.96FA:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# reset mac-address CFBA.321B.96FARelated Commands
call-manager-fallback
Enables SRS Telephony feature support and enters CallManager fallback configuration mode.
show call-manager-fallback all
To display the detailed configuration of all Cisco IP phones, voice ports, and dial peers in your network while the Cisco CallManager fallback feature is active, use the show call-manager-fallback all command in EXEC mode.
show call-manager-fallback all
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show call-manager-fallback all command:
Router# show call-manager-fallback allCONFIG======ip source-address 10.0.0.1 port 2000max-ephones 10max-dn 10no huntstoptranslate called 1call-forward busy 5001call-forward noan 5001 timeout 8cor incoming allowall 1 5001-5010cor outgoing allow1800 2 5010-5020alias 2 3... to 5555keepalive 30voicemail 914085551000ephone-dn 1number 4444no huntstoptranslate called 1ephone-dn 2number 3333no huntstoptranslate called 1ephone-dn 3number 5555 secondary 3...no huntstoptranslate called 1ephone-dn 4no huntstoptranslate called 1...voice-port 50/0/1station-id number 4444timeout ringing 8translate called 1!voice-port 50/0/2station-id number 3333timeout ringing 8translate called 1!voice-port 50/0/3station-id number 5555timeout ringing 8translate called 1!voice-port 50/0/4timeout ringing 8translate called 1...dial-peer voice 20046 potsdestination-pattern 4444call-forward busy 5001call-forward noan 5001port 50/0/1dial-peer voice 20047 potsdestination-pattern 3333call-forward busy 5001call-forward noan 5001port 50/0/2dial-peer voice 20048 potsdestination-pattern 5555call-forward busy 5001call-forward noan 5001port 50/0/3dial-peer voice 20049 potspreference 9destination-pattern 3...call-forward busy 5001call-forward noan 5001port 50/0/3Table 3-2 provides an alphabetical listing of the command fields in the sample output.
Related Commands
show call-manager-fallback dial-peer
To display output for the dial peers while Cisco CallManager fallback mode is active, use the show call-manager-fallback dial-peer command in EXEC mode.
show call-manager-fallback dial-peer
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show call-manager-fallback dial-peer command:
Router# show call-manager-fallback dial-peerdial-peer voice 20046 potsdestination-pattern 4444call-forward busy 5001call-forward noan 5001port 50/0/1dial-peer voice 20047 potsdestination-pattern 3333call-forward busy 5001call-forward noan 5001port 50/0/2dial-peer voice 20048 potsdestination-pattern 5555call-forward busy 5001call-forward noan 5001port 50/0/3dial-peer voice 20049 potspreference 9destination-pattern 3...call-forward busy 5001call-forward noan 5001port 50/0/3Table 3-3 provides an alphabetical listing of the command fields in the sample output.
Related Commands
show call-manager-fallback ephone-dn
To display output for the Cisco IP phone directory numbers or virtual voice ports while Cisco CallManager fallback is active, use the show call-manager-fallback ephone-dn command in EXEC mode.
show call-manager-fallback ephone-dn
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show call-manager-fallback ephone-dn command:
Router# show call-manager-fallback ephone-dnephone-dn 1number 4444no huntstoptranslate called 1ephone-dn 2number 3333no huntstoptranslate called 1ephone-dn 3number 5555 secondary 3...no huntstoptranslate called 1ephone-dn 4no huntstoptranslate called 1Table 3-4 provides an alphabetical listing of the command fields in the sample output.
Table 3-4 show call-manager-fallback ephone-dn Field Descriptions
ephone-dn
Cisco IP phone directory number.
huntstop
Huntstop is set.
number
Cisco IP phone number.
Related Commands
show call-manager-fallback voice-port
To display output for the voice ports while Cisco CallManager is active, use the show call-manager-fallback voice-port command in EXEC mode.
show call-manager-fallback voice-port
Syntax Description
This command has no arguments or keywords.
Command Modes
EXEC
Command History
Examples
The following is sample output from the show call-manager-fallback voice-port command:
Router# show call-manager-fallback voice-portvoice-port 50/0/1station-id number 4444timeout ringing 8translate called 1!voice-port 50/0/2station-id number 3333timeout ringing 8translate called 1!voice-port 50/0/3station-id number 5555timeout ringing 8translate called 1!voice-port 50/0/4timeout ringing 8translate called 1!Table 3-5 describes the significant fields shown in the display.
Related Commands
show ephone
To display Cisco IP phone output, use the show ephone command in EXEC mode.
show ephone [mac-address | summary | registered | unregistered | 7910 | 7940 | 7960 | ringing | offhook | dn dn-tag | remote | telephone-number phone-number]
Syntax Description
Command Modes
EXEC
Command History
Usage Guidelines
The show ephone command displays statistical information for registered and unregistered Cisco IP phones. If a MAC address is not specified, all phones that can be identified by the Cisco SRS Telephony router are displayed. This command includes several keywords to enable you to get different types of output specific to your needs.
Examples
The following is sample output from the show ephone command:
Router# show ephoneephone-1 Mac:0003.E3E7.F627 TCP socket:[1] activeLine:1 REGISTEREDmediaActive:1 offhook:1 ringing:0 reset:0 reset_sent:0 debug:0IP:10.0.0.51 50570 Telecaster 7940 keepalive 49button 1: dn 1 number 3001 CONNECTEDActive Call on DN 1:3001 10.0.0.51 31808 to 10.2.159.100 22708Tx Pkts 452 bytes 41584 Rx Pkts 452 bytes 41584 Lost 0Jitter 0 Latency 0ephone-2 Mac:0030.94C3.E1A8 TCP socket:[2] activeLine:1 REGISTEREDmediaActive:1 offhook:1 ringing:0 reset:0 reset_sent:0 debug:0IP:1.2.159.100 50942 Telecaster 7960 keepalive 78button 1: dn 2 number 3002 CONNECTEDActive Call on DN 2:3002 10.2.159.100 22708 to 10.0.0.51 31808Tx Pkts 452 bytes 41584 Rx Pkts 452 bytes 41584 Lost 0Jitter 0 Latency 0ephone-3 Mac:0030.94C3.F946 TCP socket:[-1] activeLine:0 UNREGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 debug:0IP:10.2.1.2 52163 Telecaster 7960 keepalive 59ephone-4 Mac:0030.94C3.F43A TCP socket:[-1] activeLine:0 UNREGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 debug:0IP:10.2.1.1 51768 Telecaster 7960 keepalive 59The following is sample output from the show ephone mac-address command for the Cisco IP phone with the MAC address 0030.94c3.f43a:
Router# show ephone 0030.94c3.f43aephone-3 Mac:0030.94C3.F43A TCP socket:[3] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 debug:0IP:10.5.81.13 Telecaster 7960 keepalive 28button 1: dn 3 number 5003 IDLEbutton 2: dn 5 number 5005 IDLEbutton 3: dn 6 number 5006 IDLEspeed dial 1:3005speed dial 2:3006The following is sample output from the show ephone dn dn-tag command:
Router# show ephone dn 5Tag 5, Normal or Intercom dnephone 1, mac-address 0030.94C3.CAA2, line 2ephone 2, mac-address 0030.94c2.9919, line 3The following is sample output from the show ephone 7910 command:
Router# show ephone 7910ephone-5 Mac:0004.DD1E.56ED TCP socket:[1] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0IP:10.30.0.83 52234 Telecaster 7910 keepalive 270 max_line 2 dual-linebutton 1: dn 15 number 5000 IDLEbutton 2: dn 16 number 5500 IDLEThe following is sample output from the show ephone 7960 command:
Router# show ephone 7960ephone-11 Mac:0007.0EA6.2AA9 TCP socket:[13] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0IP:10.30.0.53 52548 Telecaster 7960 keepalive 272 max_line 6button 1: dn 16 number 9001 IDLEbutton 2: dn 17 number 9002 IDLEbutton 3: dn 18 number 9003 IDLEbutton 4: dn 26 number A5001 auto dial A5002 IDLEbutton 5: dn 31 number 1111 IDLEspeed dial 1:8001ephone-12 Mac:0002.B9EB.0CB1 TCP socket:[14] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 paging 0 debug:0IP:10.30.0.54 50387 Telecaster 7960 keepalive 272 max_line 6button 1: dn 20 number 9005 IDLEbutton 2: dn 21 number 9006 IDLEbutton 3: dn 22 number 9007 IDLEbutton 4: dn 23 number 9008 IDLEbutton 5: dn 30 number 1110 IDLEThe following is sample output from the show ephone registered command:
Router# show ephone registeredephone-1 Mac:0653.D6B4.C601 TCP socket:[4] activeLine:0 REGISTEREDephone-2 Mac:0653.D6B4.C602 TCP socket:[6] activeLine:0 REGISTEREDephone-3 Mac:0653.D6B4.C603 TCP socket:[2] activeLine:0 REGISTEREDephone-4 Mac:0653.D6B4.C604 TCP socket:[7] activeLine:0 REGISTEREDephone-5 Mac:0653.D6B4.C605 TCP socket:[9] activeLine:0 REGISTEREDephone-6 Mac:0653.D6B4.C608 TCP socket:[1] activeLine:0 REGISTEREDephone-7 Mac:0653.D6B4.C609 TCP socket:[8] activeLine:0 REGISTEREDephone-8 Mac:0653.D6B4.C614 TCP socket:[5] activeLine:0 REGISTEREDephone-9 Mac:0653.D6B4.C622 TCP socket:[11] activeLine:0 REGISTEREDephone-10 Mac:0653.D6B4.C623 TCP socket:[3] activeLine:0 REGISTEREDephone-11 Mac:0007.0EA6.2AA9 TCP socket:[13] activeLine:0 REGISTEREDephone-12 Mac:0002.B9EB.0CB1 TCP socket:[14] activeLine:0 REGISTEREDephone-13 Mac:0653.D6B4.C625 TCP socket:[10] activeLine:0 REGISTEREDephone-14 Mac:0653.D6B4.C624 TCP socket:[12] activeLine:0 REGISTEREDThe following is sample output from the show ephone telephone-number phone-number command:
Router# show ephone telephone-number 4085558001DP tag: 1, primaryTag 1, Normal or Intercom dnephone 1, mac-address 0030.94c3.CAA2, line 1Table 3-6 provides an alphabetic listing of the command fields in the sample output.
The following is a sample output from the show ephone summary command:
Router# show ephone summaryephone-1 Mac:0030.94C3.37CB TCP socket:[-1] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 debug:0IP:10.1.1.1 Telecaster 7910 keepalive 45 1:1sp1:5002 sp2:5003ephone-2 Mac:0030.94C3.F96A TCP socket:[-1] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 debug:0IP:10.1.1.2 Telecaster 7960 keepalive 45 1:2 2:3 3:4sp1:5004 sp2:5001ephone-3 Mac:0030.94C3.F946 TCP socket:[-1] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 debug:0IP:10.2.1.2 Telecaster 7960 keepalive 59ephone-4 Mac:0030.94C3.F43A TCP socket:[-1] activeLine:0 REGISTEREDmediaActive:0 offhook:0 ringing:0 reset:0 reset_sent:0 debug:0IP:10.2.1.1 Telecaster 7960 keepalive 59Table 3-7 provides an alphabetic listing of the command fields shown in the sample output.
Related Commands
show ephone-dn
To display a Cisco IP phone destination number, use the show ephone-dn command in EXEC mode.
show ephone-dn [tag | loopback | summary]
Syntax Description
Command Modes
EXEC
Command History
Examples
The following is sample output from the show ephone-dn tag command:
Router# show ephone-dn 750/0/7 INVALIDEFXS 50/0/7 Slot is 50, Sub-unit is 0, Port is 7Type of VoicePort is EFXSOperation State is UPAdministrative State is UPNo Interface Down FailureDescription is not setNoise Regeneration is enabledNon Linear Processing is enabledNon Linear Mute is disabledNon Linear Threshold is -21 dBMusic On Hold Threshold is Set to -38 dBmIn Gain is Set to 0 dBOut Attenuation is Set to 0 dBEcho Cancellation is enabledEcho Cancellation NLP mute is disabledEcho Cancellation NLP threshold is -21 dBEcho Cancel Coverage is set to 8 msPlayout-delay Mode is set to defaultPlayout-delay Nominal is set to 60 msPlayout-delay Maximum is set to 200 msPlayout-delay Minimum mode is set to default, value 4 msPlayout-delay Fax is set to 300 msConnection Mode is normalConnection Number is not setInitial Time Out is set to 10 sInterdigit Time Out is set to 10 sCall Disconnect Time Out is set to 60 sRinging Time Out is set to 8 sWait Release Time Out is set to 30 sCompanding Type is u-lawRegion Tone is set for USStation name None, Station number NoneCaller ID Info Follows:Standard BELLCOREVoice card specific Info Follows:Digit Duration Timing is set to 100 msThe following is sample output from the show ephone-dn summary command:
Router# show ephone-dn summaryPORT DN STATE CODEC VAD VTSP STATE VPM STATE======== ========== ======== === ===================== =========50/0/1 DOWN - - - EFXS_ONHOOK50/0/2 DOWN - - - EFXS_ONHOOK50/0/3 DOWN - - - EFXS_ONHOOK50/0/4 INVALID - - - EFXS_INIT50/0/5 INVALID - - - EFXS_INIT50/0/6 INVALID - - - EFXS_INITTable 3-8 provides an alphabetical listing of the command fields shown in the sample output.
Related Commands
time-format (cm-fallback)
To set the time display format on all Cisco IP phones attached to a router, use the time-format command in CallManager fallback configuration mode. To disable the time display format, use the no form of this command.
time-format {12 | 24}
no time-format {12 | 24}
Syntax Description
Defaults
12-hour format
Command Modes
CallManager fallback configuration
Command History
Usage Guidelines
The time-format command sets the time display format on all the Cisco IP phones attached to the router.
Examples
The following example shows the time format on the Cisco IP phones being set to the 24-hour format:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# time-format 24Related Commands
call-manager-fallback
Enables SRS Telephony feature support and enters CallManager fallback configuration mode.
timeouts interdigit (cm-fallback)
To configure the interdigit timeout value for all Cisco IP phones attached to a router, use the timeouts interdigit command in CallManager fallback configuration mode. To return the interdigit timeout value to its default, use the no form of this command.
timeouts interdigit seconds
no timeouts interdigit seconds
Syntax Description
seconds
Interdigit timeout duration, in seconds, for all Cisco IP phones. Valid entries are integers from 2 to 120. The default is 10.
Defaults
10 seconds
Command Modes
CallManager fallback configuration
Command History
Usage Guidelines
The timeouts interdigit command specifies how long, in seconds, the system waits after a caller enters the initial digit or a subsequent digit of the dialed string. The timeouts interdigit timer is activated when the caller enters a digit and is restarted each time the caller enters subsequent digits until the destination address is identified. If the configured timeout value is exceeded before the destination address is identified, a tone sounds and the call is terminated. The default is 10 seconds.
To disable the timeouts interdigit timer, set the seconds value to 0.
Examples
The following example sets the interdigit timeout value to 5 seconds for all Cisco IP phones:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# timeouts interdigit 5In this example, the 5 seconds refers to the elapsed time after which an incompletely dialed number times out. For example, if you dial nine digits (408555898) instead of the required ten digits (4085558984) you hear a busy tone after the 5 "timeout" seconds have elapsed.Related Commands
transfer-pattern (cm-fallback)
To allow Cisco IP phones to transfer telephone calls from callers outside the local IP network to another Cisco IP phone, use the transfer-pattern command in CallManager fallback configuration mode. To disable transfer of calls to other numbers, use the no form of this command.
transfer-pattern transfer-pattern
no transfer-pattern
Syntax Description
Defaults
This feature is enabled by default.
Command Modes
CallManager fallback configuration
Command History
Usage Guidelines
The transfer-pattern command allows you to transfer a call from a non-IP phone number to another CIsco IP phone on the same IP network using the specified transfer pattern. By default, all Cisco IP phone directory numbers or virtual voice ports are allowed as transfer targets.
Examples
The following example sets a transfer pattern:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# transfer-pattern 55540..A maximum of 32 transfer patterns can be entered. In this example, 55540.. (the two decimal points are used here as wildcards) permits transfers to any numbers in the range from 555-4000 to 555-4099.Related Commands
call-manager-fallback
Enables SRS Telephony feature support and enters CallManager fallback configuration mode.
translate (cm-fallback)
To apply a translation rule to modify the phone number dialed by any Cisco IP phone user while CallManager fallback is active, use the translate command in CallManager fallback configuration mode. To disable this feature, use the no form of this command.
translate {called | calling} translation-rule-tag
no translate {called | calling} translation-rule-tag
Syntax Description
Defaults
No default behavior or values.
Command Modes
CallManager fallback configuration
Command History
Usage Guidelines
The translate command allows you to apply a previously configured number-translation rule to modify the number dialed by a specific extension. Translation rules are a powerful general-purpose number-manipulation mechanism that performs operations such as automatically adding telephone area and prefix codes to dialed numbers.
Examples
The following example applies translation rule 20 to the inbound called number:
Router(config)# translation-rule 20Router(config-translate)# rule 0 1234 2345 abbreviatedRouter(config-translate)# exitRouter(config)# call-manager-fallbackRouter(config-cm-fallback) translate called 20Related Commands
vm-integration
To enter voice-mail integration configuration mode and enable voice-mail integration with dual tone multifrequency (DTMF) and analog voice-mail on systems connected to the Public Switched Telephone Network (PSTN) through the Foreign Exchange Office (FXO) or Foreign Exchange Service (FXS) ports, use the vm-integration command in global configuration mode. To disable voice-mail integration, use the no form of this command.
vm-integration
no vm-integration
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Usage Guidelines
The vm-integration command allows integration with DTMF and analog voice-mail systems. Typically, calls are forwarded to voice mail when the called number is busy or does not answer. To play personal greetings, a voice-mail system requires the number of the phone that does not answer, known as the redirected dialed number identification service (RDNIS). During fallback, a RDNIS must to be passed to voice-mail systems through the PSTN. If the trunks are FXS or FXO, the vm-integration command can facilitate the in-band passing of RDNIS information to a voice-mail system.
The vm-integration command does not support Primary Rate Interface (PRI) or Basic Rate Interface (BRI). If trunks are an Integrated Services Digital Network (ISDN), then it may be possible to pass the RDNIS as part of Q.931 signalling. Cisco SRST includes RDNIS in the Q.931 setup signalling by default. Note, however, that some carriers drop RDNIS, thus nullifying this solution
Examples
The following example shows how to enter voice-mail integration configuration mode:
Router(config) vm-integrationRouter(config-vm-integration)Related Commands
voicemail (cm-fallback)
To configure the telephone number that is speed-dialed when the messages button on a Cisco IP phone is pressed, use the voicemail command in CallManager fallback configuration mode. To disable the messages button, use the no form of this command.
voicemail phone-number
no voicemail
Syntax Description
Defaults
No phone number is configured, and the messages button is ineffective.
Command Modes
CallManager fallback configuration
Command History
Usage Guidelines
The voicemail command configures the telephone number that is speed-dialed when the messages button on a Cisco IP phone is pressed. The same voice-mail telephone number is configured for all Cisco IP phones connected to the router.
Examples
The following example specifies 4085551000 as the speed-dial number that is dialed to retrieve messages when the messages button is pressed:
Router(config)# call-manager-fallbackRouter(config-cm-fallback)# voicemail 914085551000The number 914085551000 is called when the Cisco IP phone messages button is pressed to retrieve messages.
Related Commands
call-manager-fallback
Enables SRS Telephony feature support and enters CallManager fallback configuration mode.
Posted: Thu Mar 24 09:52:41 PST 2005
All contents are Copyright © 1992--2005 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
