Cisco VPN Broken

VPN not functioning for connecting to other hosts including the CUE? Disable IP cef

conf t
no ip cef

Default Interface Cisco Command

I can't even count the number of times I've tried to remove all the configs from an interface by doing a no interface command. The router or switch always replies with a snarky "Removal of physical interfaces is not permitted." I then copy all the commands for the interface, open up notepad, put a no in front of all the ones I don't want and then paste it back into the CLI.

A 10 second change has now taken 2 minutes and increased my frustration level unnecessarily.

 Default to the rescue. Just use this command to return the physical interface and any subinterfaces to their default (unconfigured) values. Note: if you only want to default a single subinterface, you can just do a no to remove it and then add it back in.  

default

default fa0/1



http://blog.ioshints.info/2007/06/default-interface-configuration-command.html
http://www.cisco.com/en/US/docs/ios/12_2t/inter/command/reference/irftdce.html#wp1081863

Cisco - CUE - Show Voicemail Email Notification Settings for a User from CLI

 show voicemail notification owner email

Cisco Config Archive and Replace

Sweet.

http://www.fryguy.net/2011/06/06/cisco-archive-and-configure/

http://www.cisco.com/en/US/docs/ios/12_3t/12_3t7/feature/guide/gtrollbk.html#wp1066709

Cisco Command Tricks - Monitoring Performance

Show the list of tasks running sorted by CPU usage and excluding any that are using 0%

sh proc cpu sorted | ex 0.00

Show spanning tree changes

show spanning-tree detail | inc ieee|occur|from|is exec

Show interface counter errors

sh interface counters errors 

sh int | i line|error

Show interface queue statuses and drops

sh int | in Input|line

Cisco - ISDN Plan Map

Apparently Cisco CME creates its own ISDN call plan rule set automagically. With some vendors, when you send across a number which begins with 011 and plan type international their switches freak out. You can override this treatment by applying an ISDN MAP to the serial interface of the PRI.

interface Serial0/2/0:23
isdn map address 011.* plan isdn type unknown

Reference:
http://www.cisco.com/en/US/docs/ios/dial/command/reference/dia_i2.html

isdn map

To override the default ISDN type and plan generated by the router with custom values, use the isdn map command in interface configuration mode. To revert to the default ISDN type and plan, use the no form of this command.

isdn map address {{address | reg-exp} plan plan type type | transparent}

no isdn map address {{address | reg-exp} plan plan type type | transparent}

Syntax Description

address	Specifies that the default ISDN type and plan will be overridden.
address	Address map, which can be to either the calling number or the called number. This argument specifies the address for which the ISDN type and plan will be overridden.
reg-exp	Regular expression for pattern matching. This argument specifies that the ISDN type and plan will be overridden for addresses that match the regular expression.
plan plan	ISDN numbering plan. Valid values for the plan argument are as follows: •any—Any type of dialed number. •data—X.121 data numbering plan. •ermes—European Radio Message System numbering plan. •isdn—E.164 ISDN/Telephony numbering plan. •national—Number called to reach a subscriber in the same country, but outside the local network. •private—Private numbering plan. •reserved—Reserved for extension. •telex—F.69 telex numbering plan. •unknown—Number of a type that is unknown by the network.
type type	ISDN number type. Valid values for the type argument are as follows: •abbreviated—Abbreviated representation of the complete number as supported by this network. •any—Any type of called number. •international—Number called to reach a subscriber in another country. •national—Number called to reach a subscriber in the same country, but outside the local network. •network—Administrative or service number specific to the serving network. •reserved—Reserved for extension. •subscriber—Number called to reach a subscriber in the same local network. •unknown—Number of a type that is unknown by the network.
transparent	Specifies that the ISDN type and plan values received in raw messages from the ISDN originating gateway will take priority over the ISDN type and plan values received in the H.225 SETUP messages.

Command Default

The default is the ISDN type and plan generated by the router.

Command Modes

Interface configuration

Command History

Release	Modification
12.0(6)T	This command was introduced.
12.3(7)T	The transparent keyword was added.

Usage Guidelines

The default ISDN type and plan can be overridden with custom values on a per-number basis or for numbers that match regular expression patterns.

If you use the isdn map command to configure custom values for the ISDN type and plan, these values take priority over any other ISDN type and plan values. The order of precedence for ISDN type and plan values is as follows, beginning with the highest precedence:

•Type and plan values configured with the isdn map command.

•Type and plan values from voice translation rules specified with the rule (voice translation-rule) command.

•Values received in the H.225 SETUP messages.

•Values received from the ISDN originating gateway in raw messages.

Configuring the isdn map command with the transparent keyword results in raw messages received from the ISDN originating gateway receiving priority over H.225 SETUP messages. When the isdn map command is configured with thetransparent keyword, the order of precedence for ISDN type and plan values is as follows:

•Type and plan values configured with the isdn map command.

•Type and plan values from voice translation rules specified with the rule (voice translation-rule) command.

•Values received from the ISDN originating gateway in raw messages.

•Values received in the H.225 SETUP messages.

Examples

The following example overrides any plan and type used for any ISDN calls with a called or calling number that exactly matches 123:

interface serial1:23

 isdn map address 123 plan isdn type unknown 

The following example overrides any plan and type used for ISDN calls with a called or calling number that begins with the numerals 12:

interface serial1:23

 isdn map address 12.* plan data type subscriber

The following example matches any number that ends with the number 7:

interface serial1:23

 isdn map address .*7 plan data type subscriber

The following example reverses the precedence of ISDN type and plan values received from the ISDN originating gateway and from the H.225 SETUP message:

interface serial1:23

 isdn map address transparent

Related Commands

Command	Description
rule (voice translation-rule)	Defines a translation rule.

Cisco NTP Setup

NTP Setup Misc Notes
NTP Server to Use: time-a.nist.gov - 129.6.15.28
Other NTP Servers

http://www.cisco.com/en/US/docs/ios/12_1/configfun/configuration/guide/fcd303.html#wp1001151



http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a00807ca437.shtml#configs

Cisco IP Communicator

Hitting / on the number pad on your keyboard translates into a # in Cisco IP communicator. If you spend a lot of time working with Cisco phone systems and CIPC, you know how much time this will save you. If not, this is pretty useless info.

Now if I can just find a way to create profile files/shortcuts so I don't need to keep reconfiguring CIPC for every customer/site.

PS, doesn't seem to work in eyeBeam/X-Lite.

Cisco Regex and CLI Filters Misc

Not a fully formed note/post yet. Just some notes and links.

http://www.cisco.com/en/US/docs/ios/12_0t/12_0t1/feature/guide/cliparse.html#wp5286
http://hackathology.blogspot.com/2007/04/cisco-ios-cli-regular-expressions-part.html

http://hackathology.blogspot.com/2007/02/basic-cisco-ios-router-management-to.html
http://www.handsomeplanet.com/archives/7

Cisco VPN PSK Decryption

Had a customer today who needed their Cisco IPSec VPN pre-shared key. The problem is we didn't keep that information for their VPN account (only for our own) and the password is stored encrypted on the ASA.

I can reset their PSK easily, but then the other computers that are already deployed with the existing PSK will need to be reconfigured.

The Group Name, IP and PSK are all stored in a profile file (.pcf) on computers that are already configured. The PSK is encrypted. However, the encryption used for the PSK is very easily crackable.

Here's How:
1) Locate the profile (.pcf) file for your connection entry. This should be located at C:\Program Files\Cisco Systems\VPN Client\Profiles\ENTRYNAME.pcf.
2) Open the profile with a text editor.
3) Look for the line that begins with enc_GroupPwd=
4) Grab the string of characters that follow the = sign.
5) Input the characters into the Encrypted User/Group Password: field on this website.
6) Hit decode. Use the retrieved password to setup the remaining machines.

Here is an example of the encrypted password:
enc_GroupPwd=B54080BC72B142E7F537A9A2080C940D4B953BA6AE47C952C42C60C4C0EF69D6D8FA1E3E76038450E27724D29D851301CE97DF962667FD7A

Links:
http://coreygilmore.com/projects/decrypt-cisco-vpn-password/

Cisco CLI - Show Command Section Filter and Other CLI Shortcuts

One of the most useful Cisco show filters ever is the new(ish) section filter. This lets you view information from the section you specify. For example, show run | section include ephone  12 will return all the config lines in the running config which pertain to your ephone 12. The section command (like all Cisco show command filters) is case sensitive and doesn't allow tab completions or etc - you need to type exactly what you're looking for (or at least the beginning of what you're looking for).Note that per one site: "Cisco considers a section to be a line with no leading blank and includes all lines following it until the start of the next section."

! awesome. Now I don't have to filter through the config looking for the ephone  12 config.
2821#sh run | s i ephone  12
ephone  12
 device-security-mode none
 description Ryan IP Communicator
 video
 mac-address 0023.AE7F.0000
 type CIPC
 button  1:2 2:10
2821#

When I first start working on a router, I'll usually grab a copy of the running config and throw it into a txt file. Then I search through it for whatever I want. Once I find the relevant pieces, I'll copy them over to a new text file and prep the changes I want to make. Then I'll apply the changes to the router.

! term len 0 sets the terminal length to no pauses so you can get the complete config at once.
Rtr#term len 0
Rtr#sh run
! now do a copy all to clipboard from putty and paste into a text document. 

Verifying the changes is where the section filter can really be helpful. Rather than getting a complete new copy of the config and sifting through it, just do a sh run | s i whatever I'm looking for

. On major changes, I will always save the starting configs and the ending configs and compare them with WinMerge. However, the section command works very well to make sure everything is going well as I make each change.
 

So overall, the section command filter is a great shortcut. However, if you are looking for data on an interface, you should use show run interface . This method will allow for tabbed completions, abbreviations and isn't case sensitive so it is faster and better for this type of work than the section filter. It won't work with the variety of items that the section command will though. 

! annoying because I had to type this all the way out and even capitalize it correctly
2821#sh run | s i interface GigabitEthernet0/0
interface GigabitEthernet0/0
 no ip address
 duplex auto
 speed auto
 bridge-group 1

! less annoying - just do sh run int and use tab completion or abbreviations like you normally would.
2821#sh run int gigabitEthernet 0/0
Building configuration...

Current configuration : 92 bytes
!
interface GigabitEthernet0/0
 no ip address
 duplex auto
 speed auto
 bridge-group 1
end

2821#

Show Section Command Filter Links
http://www.cisco.com/en/US/docs/ios/12_3t/12_3t2/feature/guide/gtshfltr.html
http://www.techexams.net/forums/ccna-ccent/37408-show-run-section.html
http://cciepursuit.wordpress.com/2007/07/17/must-use-command-filtering-output-with-the-section-command/
http://www.nil.com/C1256F0A00429755/html/EnhanceIOSUI/
Cisco Documentation:

Command Reference

This section documents new commands. All other commands used with this feature are documented in the Cisco IOS Release 12.3 T command reference publications.

•show section

show section

To filter the output of a show command to match a given expression as well as any lines associated with that expression, use the show command section command in privileged EXEC mode.

show command | section [include | exclude] regular-expression

Syntax Description

command	Any Cisco IOS show command.
include	(Optional) Includes only the lines that contain a particular regular expression. This is the default keyword when none is specified.
exclude	(Optional) Excludes any lines that contain a particular regular expression.
regular-expression	Any regular-expression (text string) found in show command output.

Command Modes

Privileged EXEC

Command History

Release	Modification
12.3(2)T	This command was introduced.

Usage Guidelines

In many cases, it is useful to filter the output of a show command to match a specific expression. Filtering provides some control over the type and amount of information displayed by the system. The show section command provides enhanced filtering capabilities by matching lines in the show command output containing specific expressions as well as matching any entries associated with those expressions. Filtering is especially useful, for example, when displaying large configuration files using the show running-configuration command or the show interfaces command.

If the include or exclude keyword is not specified, include is the default.

If there are no associated entries for an expression, then only the line matching the expression is displayed.

Examples

The following examples compare the filtering characteristics of the show running-config | include command with the show running-config | section command. The first example gathers just the lines from the configuration file with "interface" in them.

Router# show running-config | include interface

interface Ethernet0/0 
interface Ethernet1/0 
interface Serial2/0 
interface Serial3/0

The next example uses the show command section command to gather the lines in the configuration file with "interface" in them as well as any lines associated with those entries. In this example, interface configuration information is captured.

Router# show running-config | section include interface

interface Ethernet0/0 
 shutdown 
 no cdp enable

interface Ethernet1/0 
 shutdown 
 no cdp enable 
interface Serial2/0 
 shutdown 
 no cdp enable 
interface Serial3/0 
 shutdown 
 no cdp enable

Related Commands

Command	Description
show append	Redirects the output of any show command and adds it to the end of an existing file.
show exclude	Filters show command output so that it excludes lines that contain a particular regular expression.
show include	Filters show command output so that it displays only lines that contain a particular regular expression.
show redirect	Redirects the output of any show command to a specified file.

Information About the Show Command Section Filter

The Show Command Section Filter feature enhances the functionality of the Cisco IOS CLI by filtering show command output matching a regular expression (text string) as well as filtering output associated with that expression. Prior to this enhancement, the level of filtering offered by the show command was limited to the individual lines of the output.

In many cases, it is useful to filter the output of a show command to match a specific expression. Filtering provides some control over the type and amount of information displayed by the system. With section filtering, show command output not only displays the individual entries matching the expression in the command output but also displays the section of entries associated with that expression.

Filtering is especially useful, for example, when displaying a large configuration file. In this case, it is helpful to display sections of the configuration file without having to enter multiple commands to gather the related configuration information.

Show MAC Address Table

Cisco command:

show mac-address-table

Cisco CME - SIP Providers

Some SIP providers require that your PBX use a specific SOURCE port when communicating with their network. Voip Your Life (VYL Media) business setup authenticates via public IP address and requires that your PBX use port 5060 as a source and destination port when communicating with their network.

The problem is that by default, Cisco CME does not use a static source port; it uses a random unassigned source port. This resulted in outgoing calls not working. Their device was specifically responding with a 404 not found error (which is not very helpful). To get this to work properly, we had to configure the UC540 to use port 5060 for the source port.

conf t
sip-ua
  connection-reuse
end

Additional information from Cisco:

1. By default the source port for SIP messages that the UC500 sends is ephemeral or random which is per the spec. You can force this to always be UDP 5060 by looking at section 4.4.12 on guide below

https://www.myciscocommunity.com/docs/DOC-1560
If the provider requires that SIP traffic always be sourced from the UC520 using TCP or UDP port 5060, this can be changed at a system level as below:
sip-ua
  connection-reuse

2. Need "deb ccsip message" for this to check the reason for the error. One possibility is mentioned here:
https://www.myciscocommunity.com/docs/DOC-1520#Inbound_calls_from_SIP_Trunk_on_UC520_fail_when_configured_using_CCA_19_or_higher

Earlier posts on NexVortex:
https://www.myciscocommunity.com/message/5595#5595

Cisco CME Basic Call Debugs

WIP:

debug isdn q931 - see live calling / called numbers on PRI
debug voip ccapi inout - This is hard to read but you will see something on the screen if calls come in / out of the FX0 / POTS lines.
debug ccsip messages - debug sip messages
debug ccsip all - debug all sip traffic - CAREFUL
term mon - see debugs on the screen
u all - disable all debugging 

Cisco KATE

Working on a problem with Cisco SPA525G phones freezing and rebooting. Going through the debugs, I find a bunch of KATE messages. Weird. Some research shows that this is pretty poorly documented. Research also shows that Google sucks if you want to do a case sensitive search, which in this case I definitely do.

After some digging around, it looks like KATE stands for "Keyboard Alphanumeric Text Entry" and deals with Cisco localization settings and etc.

Error Messages:

2010-02-10 08:49:16 Local3.Debug 192.168.1.9 KATE_tftp {
2010-02-10 08:49:16 Local3.Debug 192.168.1.9 KATE_tftpInit {
2010-02-10 08:49:16 Local3.Debug 192.168.1.9 }<010>
2010-02-10 08:49:16 Local3.Debug 192.168.1.9 KATE: finished waiting on EVENT_INIT_CNF_PARSED
2010-02-10 08:49:16 Local3.Debug 192.168.1.9 kate Name: English_United_States/525G-kate.xml

I was only able to find 2 pages in Cisco that defined KATE directly. Both are release guides that mention this in passing.

3.3 No Keyboard Alphanumeric Text Entry Support
3.3.1 Asian Locales
There is currently no localised Keyboard Alphanumeric Text Entry (KATE) support for the following Asian locales:

Chinese (China)
Chinese (Hong Kong)
Chinese (Taiwan)
Japanese (Japan)
Korean (Korea Republic)

The default English (United States) KATE will be presented to the user instead.
3.3.2 Cisco Unified IP Phone 3951"
KATE is not internationalised on this device and therefore cannot be localised. KATE is only used for local administation purposes only.

Source

Another Mention of KATE in another context.

Cisco IOS Bundles

Cisco IOS Packaging

Cisco IOS Packaging consists of eight packages for Cisco routers and five packages for Cisco switches. (See Figure 6.)

Figure 6—Cisco IOS Packaging for Cisco Routers and Switches

Four packages are designed to satisfy requirements in four typical service categories:

• IP data

• Converged voice and data

• Security and VPN

• Enterprise protocols

Three additional premium packages offer new Cisco IOS Software feature combinations that address more complex network requirements. All features merge in the Advanced Enterprise Services package that integrates support for all routing protocols with Voice, Security, and VPN capabilities.

Feature inheritance is another powerful aspect of Cisco IOS Packaging. After a feature is introduced, it is included in the more comprehensive packages. The feature inheritance facilitates migration by clarifying the feature content of the different packages and how they relate to each another.

Cisco IOS Packaging also simplifies image naming. Each name is designed to effectively convey the high-level feature content of, and the inheritance characteristics for the new packages.

These categories summarize the new naming convention:

• Base—entry level image (IP Base, Enterprise Base)

• Services—addition of IP Telephony Service, MPLS, Voice over IP (VoIP), Voice over Frame Relay (VoFR), and ATM (SP Services, Enterprise Services)

• Advanced—addition of VPN, Cisco IOS Firewall, 3DES encryption, SSH, Cisco IOS IPsec and Intrusion Detection Systems (IDS) (Advanced Security, Advanced IP Services)

• Enterprise—addition of multi-protocols, including IBM, IPX, AppleTalk (Enterprise Base, Enterprise Services)

These packages are new:

• IP Base

• IP Voice

• Enterprise Base

• Advanced Security

• SP Services

• Advanced IP Services

• Enterprise Services

• Advanced Enterprise Services

http://www.cisco.com/warp/public/620/1.html

Alias for CLI Access to the CUE

!creating an alias to enable CLI access to the CUE module much more easily.

! alias exec

!do a sh ip int brief and look for the service-engine or integrated service-engine number to fill in the proper one. It is usually 0/0 though.

!alias exec cue service-module service-Engine <Service-engine location> session

Examples:

alias exec cue service-module service-Engine 0/0 session

alias exec cue service-module integrated-Service-Engine 0/0 session

rtr#conf t

rtr(config)#alias exec cue service-module service-Engine 0/0 session

rtr(config)#end

rtr#cu?

*cue="service-module service-Engine 0/0 session"

rtr#cue

Trying 10.1.10.1, 2194 ... Open

rtrcue#

Rebooting Cisco Phones

http://www.cisco.com/en/US/docs/voice_ip_comm/cucme/command/reference/cme_r1ht.html#wp1013890

Note that when resetting or restarting phones, the phone will not be rebooted immediately if it is currently in use. Instead, it will be rebooted once the phone call is over. Thus, resetting or restarting should both be safe to do during business hours as long as call traffic is not high at that point in time.

reset (ephone)

To perform a complete reboot of a single phone associated with a Cisco CallManager Express (Cisco CME) router, use the reset command in ephone configuration mode.

reset

Syntax Description

This command has no arguments or keywords.

Command Default

No reset is performed.

Command Modes

Ephone configuration (config-ephone)

Command History

Cisco IOS Release	Cisco Product	Modification
12.1(5)YD	Cisco ITS 1.0	This command was introduced
12.2(8)T	Cisco ITS 2.0	This command was integrated into Cisco IOS Release 12.2(8)T

Usage Guidelines

After you update information for one or more phones associated with a Cisco CME router, the phone or phones must be rebooted. There are two commands to reboot the phones: reset and restart. The reset command performs a "hard" reboot similar to a power-off-power-on sequence. It reboots the phone and contacts the Dynamic Host Configuration Protocol (DHCP) server and the TFTP server to update from their information as well. The restart command performs a "soft" reboot by simply rebooting the phone without contacting the DHCP and TFTP servers. The reset command takes significantly longer to process than the restart command when you are updating multiple phones, but it must be used after updating phone firmware, user locale, network locale, or URL parameters. For simple button, line, or speed-dial changes, you can use the restart command.

Use the reset (ephone) command to perform a complete reboot of an IP phone when you are in ephone configuration mode. This command has the same effect as a reset (telephony-service) command that is used to reset a single phone.

This command has a no form, but the no form has no effect.

Examples

The following example resets the SCCP phone with a phone-tag of 1:

Router(config)# ephone 1

Router(config-ephone)# reset

Related Commands

	Description
reset (telephony-service)	Performs a complete reboot of one or all phones associated with a Cisco CME router.
restart (ephone)	Performs a fast reboot of a single phone associated with a Cisco CME router.
restart (telephony-service)	Performs a fast reboot of one or all phones associated with a Cisco CME router.

reset (telephony-service)

To perform a complete reboot of one or all phones associated with a Cisco CallManager Express (Cisco CME) router, use the reset command in telephony-service configuration mode. To interrupt and cancel a sequential reset cycle, use the no form of the command with the sequence-all keyword.

reset {all [time-interval] | cancel | mac-address | sequence-all}

no reset {all [time-interval] | cancel | mac-address | sequence-all}

Syntax Description

all	Resets all Cisco IP phones served by the Cisco CME router. The router pauses for 15 seconds between the reset starts for each successive phone unless the time-interval argument is used to change that value.
time-interval	(Optional) Time interval, in seconds, between each phone reset. Range is from 0 to 60. Default is 15.
cancel	Interrupts a sequential reset cycle that was started with a reset sequence-all command.
mac-address	MAC address of a particular Cisco IP phone.
sequence-all	Resets all phones in strict one-at-a-time order by waiting for one phone to reregister before starting the reset for the next phone. The sequencing of resets prevents possible conflicts between phones trying to access TFTP services simultaneously. There is a reset timeout of 4 minutes, after which the router stops waiting for the currently registering phone to complete registration and starts to reset the next phone.

Command Default

No reset is performed.

Command Modes

Telephony-service configuration (config-telephony)

Command History

Cisco IOS Release	Cisco Product	Modification
12.1(5)YD	Cisco ITS 1.0	This command was introduced.
12.2(8)T	Cisco ITS 2.0	This command was integrated into Cisco IOS Release 12.2(8)T.
12.2(11)YT	Cisco ITS 2.1	The time-interval range maximum was increased from 15 to 60 and the default was changed from 0 to 15.
12.2(11)YT1	Cisco ITS 2.1	The cancel and sequence-all keywords were introduced.
12.2(15)T	Cisco ITS 2.1	This command was integrated into Cisco IOS Release 12.2(15)T.

Usage Guidelines

After you update information for one or more phones associated with a Cisco CME router, the phone or phones must be rebooted using either the reset command or the restart command. The reset command performs a "hard" reboot similar to a power-off-power-on sequence and contacts the Dynamic Host Configuration Protocol (DHCP) server and the TFTP server for updated information as well. The restart command performs a "soft" reboot by simply rebooting the phone without contacting the DHCP and TFTP servers. The reset command takes significantly longer to process than the restart command when you are updating multiple phones, but it must be used after you make changes to phone firmware, user locale, network locale, or URL parameters. For simple button, line, or speed-dial changes, you can use the restart command.

When you use the reset command, the default time interval of 15 seconds is recommended so that phone reset operations are staggered in order to avoid all phones attempting to access router system resources at the same time. A shorter interval may be used on systems with only a small number of phones or for cases where a simple reset of the phones is desired that does not result in the phones downloading updates to the phone firmware (using the router's TFTP service).

When you use the reset sequence-all command, the router waits for one phone to complete its reset and reregister before starting to reset the next phone. The delay provided by this command prevents multiple phones from attempting to access the TFTP server simultaneously and therefore failing to reset properly. Each reset operation can take several minutes when you use this command. There is a reset timeout of 4 minutes, after which the router stops waiting for the currently registering phone to complete registration and starts to reset the next phone.

If the router configuration is changed so that the eXtensible Markup Language (XML) configuration files for the phones are modified (changes are made to user locale, network locale, or phone firmware), then whenever you use the reset all or restart all command, the router automatically executes the reset sequence-all command instead. The reset sequence-all command resets phones one at a time in order to prevent multiple phones from trying to contact the TFTP server simultaneously. This one-at-a-time sequencing can take a long time if there are many phones. To avoid this automatic behavior, use the reset all time-interval or the restart all time-interval with an explicit argument that is not equal to the default 15-second time interval; for example, set a time interval of 14 seconds. If a reset sequence-all command has been started in error, use the reset cancel command to interrupt and cancel the sequence of resets.

The restart command allows the system to perform quick phone resets in which only the button template, line information, and speed-dial information is updated. See the documentation for the restart command for more information.

The no form of this command has an effect only when used with the all or sequence-all keyword, when it interrupts and cancels the sequential resetting of phones.

Examples

The following example resets all IP phones served by the Cisco CME router:

Router(config)# telephony-service

Router(config-telephony)# reset all

The following example resets the Cisco IP phone with the MAC address CFBA.321B.96FA:

Router(config)# telephony-service

Router(config-telephony)# reset CFBA.321B.96FA

The following example resets all IP phones in sequential, not-overlapping order:

Router(config)# telephony-service

Router(config-telephony)# reset sequence-all

Related Commands

	Description
reset (ephone)	Performs a complete reboot of a single phone associated with a Cisco CME router.
restart (ephone)	Performs a fast reboot of a single phone associated with a Cisco CME router.
restart (telephony-service)	Performs a fast reboot of one or all phones associated with a Cisco CME router.
telephony-service	Enters telephony-service configuration mode.