Motivating for Enterprise IPv6 Adoption

Firstly, head over to Packet Pushers and read Ethan’s excellent blog post about The Reason Enterprises Aren’t Deploying IPv6.  This post made me start thinking about IPv6 adoption, especially in light of the things I talked about almost 8 months ago in front of a group of education IT professionals.  In his post, Ethan discusses the problem with IPv6 in the enterprise from the perspective of it being more trouble than it’s worth right now.  I agree with him that there are a lot of issues to overcome today for very little immediate gain.  Today’s IPv6 implementations are still relegated to a lab or to the IT department network where they can be contained and properly tested.  I’d wager that Hurricane Electric tunnels is the most common method of IPv6 support right now.  It’s still very much a “hobby kit” type of implementation where the nerd spends several hours pouring over documentation and expends energy typing furiously at a dimly lit console only to finish up and say, “Cool.  It works.”  No fanfare, no raise.  Just the satisfaction of a hard job well done.  So how do we change that?

In college, I studied Management Information Systems, which is a fancy way of spelling Database Administrator.  I promptly forgot all my DBA training, but the Introduction to Database class was a goldmine of information thanks to my wonderful professor, Dr. Traci Carte.  She once told me that there are basically two ways to motivate people in business: fear and greed.  The more time I spend in the business world, the more I see that she had a good point.  Those two emotions tend to be pretty strong and are great motivators for people that wouldn’t ordinarily be compelled to take action.

When it comes to IPv6, we’ve already tried to motivate through fear.  If you remember any of the headlines from earlier this year you’ll agree that the Chicken Little mentality of the IPv4 sky falling down on us was reaching a fever pitch quickly.  It even made the local nightly news, which of course made my mom call and wonder when her computer was going to blow up.  Unfortunately, fear didn’t work here.  Why not?  Because there wasn’t a consequence.  It’s like announcing that an asteroid is going to hit the earth tomorrow.  If we make to the end of the day and no big rock comes down in our front yard, we just go back to life as it was.  When ICANN depleted their IPv4 prefixes and the Internet just kept working the next day, the rank-and-file users went right back to watching cat videos on Youtube without a care in the world.  After all, how bad can this problem be if there are still cat videos?

I think it’s time we move to motivator #2 – greed.  Greed, for lack of a better word, is good.   And greed can work for you.  IPv6 isn’t a compelling case when you tell your boss that most everyone can still use the Internet with no issues.  The key is that “most everyone” statement.  As APNIC and ARIN begin to deplete their reserves of IPv4 prefixes, the cost to acquire them will start skyrocketing.  For those not willing to pay a king’s ransom for a /28, there has to be an alternative.  Based on my distaste for things like carrier-grade NAT or NAT64, I would hope that pure IPv6 prefixes would start to be handed out.  Assuming that NAT64 does end up getting used as a necessary evil for those newly-minted prefixes, are we to assume that it’s going to work all the time?  What happens when there are hiccups or outages?  Only pure IPv6 sites will be available.  Right now, that’s Facebook or Google.  Greed comes into play when you can convince your decision makers to implement IPv6 to reach those customers.  If your widget is the only one those IPv6-only users can find when they search http://ipv6.google.com then you are going to have a competitive advantage over everyone else.  This might be a wash up front when you think about the costs needed to plan and implement IPv6 versus the additional revenue from those IPv6 only users.  However, we aren’t going to slow down our ravenous consumption of IPv4 addresses any time soon.  As more and more customers come online with native IPv6 support, they’re going to be surfing an Internet where you don’t have a presence.  First-to-market has a whole new meaning here.

Another avenue of greed to appeal to is the ego of a company and its decision makers when it comes to IPv6 implementation.  The same kind of mentality that drives executives to drive fancy cars and wear expensive accessories can be manipulated to drive adoption of new protocols.  Comments like, “Wouldn’t you like to be known as the first CxO to make their website ready for IPv6 in this market?” or “I hear that <competitor> is working on an IPv6 implementation and I’d like to beat them to it.” work on the ego of people that love attention and want to be known as leaders in their industry.  Giving them another headline or accolade plays right into their desire for recognition and gets you the time and resources needed to plan your implementation of IPv6.

Tom’s Take

This may seem a little like gamesmanship to some.  You may disagree with me boiling things down to simplistic terms.  You may even think I’m a bit crazy for thinking that someone can be manipulated into implementing new technology solely by appealing to their desire for money and recognition.  However, until a real business case materializes for IPv6, it won’t really get implemented.  And until it is more pervasive, real business cases won’t materialize.  A classic Catch-22 scenario.  Something has to give.  It’s time to draw a line in the sand.  Maybe I have to spend a little more time stroking egos or building a compelling business case instead of typing away on a keyboard or working in Visio.  If I can drive IPv6 implementation along by playing a few head games now and then, I think I can sleep well at night knowing I made the world a slightly better place one /48 at a time.

The Last Cable Tool You’ll Ever Need

We all have our own tools that we carry around in our toolkits when we need to get down and dirty with our hands.  Screwdrivers, wire cutters, wire strippers, crimping tools, knives, duct tape, and even velcro are common sights.  You can see what Tony Matke has in his bag and contrast it with the contents of Jeff Fry’s bag.  However, a co-worker of mine recently purchased a tool that I think might trump all of them:

The Gerber Cable Dawg

Say hello to the Gerber Cable Dawg.  This little jewel represents the high-end for cable crimpers/strippers/destroyers.  It was designed by Gerber to be used by U.S. military personnel in Forward Operating Bases (FOBs) for cabling projects.  It is constructed from high-grade steel while the handles are made from glass-filled nylon.  This means that while the length of the tool is 7.5 inches, the weight is a svelt 14 ounces.  As you might expect, it is a hardy little device with a veritable toolbox attached to it.

The Cable Dawg includes anything you might find yourself needing to work with cabling.  There is a wire cutter and Category 5 (CAT 5) cable stripper in the spring-loaded nose.  An RJ-45 crimper rests behind the pivot point along with a stripping block that can handle a lot of different gauges of wire.  The handles also contain a great number of additions.  One hand includes a set of driver bits for slotted and Phillips screws as well as a punch-down bit for terminating wires.  There is also a lanyard attachment if you don’t want to carry the tool in the included tactical pouch.

The other handle is the greatest part of the tool, in my opinion.  It contains the driver attachment for the above driver bits as well as a knife blade with a partially serrated edge and “jacket cutter” which is the little hook on the end that is capable of slicing a CAT 5 wire jacket or skinning the intern that may dare try to do their job incorrectly.  While driver handles and knife blades are fairly standard fare on a multitool, the genius in the Cable Dawg is that the knife/driver handle detaches from the tool itself to feel more like a screwdriver or pocket knife in your hand.  No longer do you have to fumble around with an overly-large multitool when all you need to do is drive a screw or slice a tomato.  Pop off the handle and go to town!

The Cable Dawg is available from Gerber’s Military Tool website here.  You can also scout around and find it on a variety of different military gear websites.  That might be a good idea, since this thing appears to be out of stock frequently.  That’s all the more impressive when you consider the retail price for the Cable Dawg clocks in at $300.  It does come with a lifetime warranty for the price, but if you can come close to wearing this puppy out you are a more vicious cabler than I can imagine.

Tom’s Take

I’m a Gerber fan.  I own three of their multitools and equally as many folding knives.  They are very high quality and have never let me down.  When my friend told me that he ordered a cable tool from Gerber, I couldn’t wait to see what they had done with it.  The Cable Dawg is a little on the pricy side for most IT personnel, but if you find yourself in need of a rugged tool that will take loads of punishment and keep crimping and stripping no matter what, this is worth the price, especially if you are in the military.  Besides, it’s better than a $600 hammer, right?

I’d like to say thanks to Scott Baird for loaning me his Cable Dawg for the purposes of writing this review and for a little testing.  I promise to return it to you…soon.

Network Field Day 2: Network Boogaloo

Guess who’s back?

I’m headed to yet another Tech Field Day event!  This time, I’ll be attending Network Field Day #2 in San Jose, CA on October 27th and 28th.  I read about the first Network Field Day last year and learned a lot about the vendors and presentations from the delegates.  Now, it’s up to me to provide that same kind of response for Net Field Day 2.  The delegate list this time around is quite awe-inspiring for a guy like me:

Kurt Bales Network Janitor @NetworkJanitor
Ethan Banks PACKETattack @ECBanks
Tony Bourke The Data Center Overlords @tbourke
Brandon Carroll BrandonCarroll GlobalConfig @BrandonCarroll
Greg Ferro EtherealMind PacketPushers @EtherealMind
Jeremy L. Gaddis Evil Routers @JLGaddis
Ivan Pepelnjak Cisco IOS Hints and Tricks @IOSHints
Mrs. Y. Packet Pushers @MrsYisWhy

I am humbled to be included in such good company.  The two Packet Pushers, Mr. MPLS himself, the man that beat IOU, the Aussie JNCIE/CCIE candiate, the walking security dictionary Brandon Carroll, and the Network Security Princess herself.  I think my invitation must have gotten confused with someone else’s.

Odds are good that if you are involved in networking at all you already follow all of these people on Twitter and read their blogs daily.  If not, stop what you are doing and follow them RIGHT NOW.  You won’t be sorry.  In fact, this is the first time I haven’t had to start following a Tech Field Day delegate on the list of attendees since I’ve been following these folks for quite a while.

Getting Inolved with Tech Field Day

Tech Field Day is always looking for amazing people to attend events and share in the wealth of knowledge.  There are lots of ways you can add your voice to the gestalt:

1.  Read the TFD FAQ and the Becoming a Field Day Delegate pages first and foremost.  Indicate your desire to become a delegate.  You can’t go if you don’t tell someone you want to be there.  Filling out the delegate form submits a lot of pertinent information to Tech Field Day that helps in the selection process.

2.  Realize that the selection process is voted upon by past delegates and has selection criteria.  In order to be the best possible delegate for a Tech Field Day, you have to be an open-minded blogger willing to listen to the presentations and think about them critically.  There’s no sense in bringing in delegates that will refuse to listen to a presentation from Brocade because all they’ve ever used is Arista and they won’t accept Brocade having good technology.  If you want to learn more about all the products and vendors out in the IT ecosystem, TFD is the place for you.

3.  Write about what you’ve learned.  One of the hardest things for me after Tech Field Day was consolidating what I had learned into a series of blog posts.  TFD is a fire hose of information, and there is little time to process it as it happens.  Copious notes are a must.  As is having the video feeds to look at later to remember what your notes meant.  But it is important to get those notes down and put them up for everyone else to see.  Because while your audience may have been watching the same video stream you were watching live, they may not have the same opinion of things.  Tech Field Day isn’t just about fun and good times.  Occasionally, the delegates must look at things with a critical eye and make sure they let everyone know where they stand.


Be sure to follow Tech Field Day on Twitter (@TechFieldDay) for information and updates about Network Field Day 2 as the date approaches.  There will also be streaming video of the presentations at the Tech Field Day website.  The videos will also be posted in their entirety shortly afterwards.  If you want to follow along on Twitter, you can use the hastags #TechFieldDay or #NFD2 to make comments or ask questions during the presentations.  I usually have a TweetDeck window open and will relay your questions along if no one else beats me to it.  I try to tag all my posts with the #TechFieldDay and #NFD2 hashtags, so if I’m overwhelming you with commentary feel free to filter that hashtag from your feed to keep me quiet.  In the past, I’ve tried to have an IRC channel open during the presentations to allow for real-time communications and feedback for those of you out there that prefer an alternative to Twitter.  Once I have the room setup I will post the details.

Tech Field Day Sponsor Disclaimer

Tech Field Day is made possible by the sponsors.  Each of the sponsors of the event is responsible for a portion of the travel and lodging costs.  In addition, some sponsors are responsible for providing funding for the gatherings that occur after the events are finished for the day.  However, the sponsors understand that their financing of Tech Field Day in no way guarantees them any consideration during the analysis and writing of reviews.  That independence allows the delegates to give honest and direct opinions of the technology and the companies that present it.

Blogging with the Packet Pushers

I’ve always believed that everyone has at least one good story in them.  People have anecdotes about funny times in college or goofy stories about their kids.  Tech-oriented people have even more stories that usually revolve around technology gone bad or interaction with non-technical people.  From the amount of studying and learning that tech-oriented people do, it is inevitable that knowledge is accumulated and waiting to be passed on.  The trick with all these stories and knowledge is finding someone to share it with.

Blogging is my preferred method of getting the thoughts out of my head.  Most of my friends an colleagues do the same.  Some of us have established blogs that have been going for a while now.  Others are just starting out.  However, there are even more of you out there with stories to tell and things to share without a blog.  Maybe you have no desire to keep up with the day-to-day drudgery of maintaining a blog.  Perhaps you don’t think you have enough in you to keep writing day after day.  You have even avoided creating a blog because you couldn’t think of a catchy title.  Let me tell you that I’ve got a deal for you that will eliminate all those issues for you.

As many of you know, I’ve been a regular contributor to the Packet Pushers Podcast.  Recently, Ethan and Greg have redesigned the site and started blogging more and more there.  They’ve also decided to open up the doors and invite some guest bloggers to write content for the site.  This is wonderful for those of you that are worried about blogging.  You don’t have to concern yourself with writing once a week.  Or month.  Or even year.  Just write whenever you feel the need to put something out there.  The Packet Pushers will make sure that everything is spelled correctly and put it up on the site.  You can be sure that your post will be seen by lots of visitors, as the Packet Pushers site gets hundreds every day and several thousand a month.  And you’ll get lots of feedback and comments for sure.

How do you get involved?  Send an email to packetpushers@gmail.com with the subject line “I Want To Blog With The Packet Pushers!”  You’ll get an account on the website for creating your post and the rest will take care of itself.  I look forward to see some of you writing on Packet Pushers and sharing all you’ve learned.  Remember, Too Much Blogging Would Never Be Enough.

365 Days of Blogging

My last real milestone to hit just came up.  This blog has now been around for one whole year.  I’m shocked to say the least.  I never believed that having a scratchpad for jotting down my ideas about troubleshooting would blossom into this.  Those of you that have followed me for a while know that I tend to flit around technologies from wireless to security to switching and back to posts about Apple computers from time to time (even though I don’t own one).  To see that I’ve been able to keep this going for as long as I have is either a testament to my stubbornness or the large amount of cruft floating around in my head.

My initial ideas about troubleshooting hit a writer’s block wall pretty quickly.  I started posting some things about my CCIE studies and the occasional voice-related article.  It took a couple of months before I started writing pieces based more on opinion than fact.  I was afraid at first.  I’m normally the kind of person that keeps my opinions to myself.  However, it was interesting to put my thoughts and ideas down on “paper” and see what people thought of them.  Opinion pieces don’t require paragraphs worth of console output or exhaustive testing.  Of course, they can also be wrong or inaccurate and subject to debate or correction.  Other bloggers have told me that opinion pieces aren’t for them due to the possibility of angering their audience or fear of rejection.  My advice is to give it a shot on something simple first.  Put your thoughts out there and see what the reaction looks like.  Remember the old adage, “If people agree with everything you’ve said, you aren’t doing your job.”

I find myself spending more time commenting on current events in long form now.  I do get a chance to discuss things on Packet Pushers from time to time, but when something really juicy comes up, I can’t resist adding my voice to the din.  Some of these articles are interesting, others not so much.  I tried my hand at adding some link aggregation pages every week or so but found that I didn’t really keep up with new things like I thought I would.  I really spend a lot more time out in the field doing rather than learning.  I’m not one for going over simple things that are well-documented elsewhere.  I tend to talk about the more esoteric configurations or things that you just can’t find anywhere else.  Those posts are as much for my benefit as anyone else’s.  If I know that I’ve run into a particular situation and I write about it, I know I can always find it here as opposed to sifting through Google for hours on end.  I just hope my readers can get some use out of it too.

I still blog about the CCIE a fair amount.  It feels a little different commenting on it from the other side of the line, but people seem to like reading about all things lab related.  There are a ton of great blogs out there that detail the process that lab candidates are going through and the little gems of knowledge that they unearth from time to time, whether it be revelations about Dynamic Trunking Protocol (DTP) or alias lists or even TCL scripts.  I should probably create a CCIE candidate blog list just so those of you out there that hunger for my CCIE-related material can get your fix from them as well.  My CCIE posts tend to be more on the commentary side and focused on the details in the process rather than the content.  I think it’s more of a way to talk about the things that I see are important to keep in mind besides the ability to remember OSPF LSA types on demand.  A “forest for the trees” approach, if you will.

Once again, I’d like to thank all my visitors and readers for your time.  I appreciate your feedback and comments about everything.  You help me be a better blogger with every post.  It helps me to know that the things I post can be useful.  Tanner Ezell and I discussed the idea that people should provide help and support because they can, not because they’re doing it for fame or recognition.  I like helping people solve problems.  It just so happens that the most efficient way for me to do it is by writing a blog.  The more you wonderful people read it, the more popular and well-known it becomes.  While I appreciate that, know that I’ll still be here plugging away and talking about things even if I’m on page 30 of a Google search.

Dial Plan Considerations

A Candlestick Phone (image courtesy of WIkipedia)

Dial Plans are probably one of the hardest parts of learning about voice.  I consider it to be just like subnetting for network enginee…rock stars.  There are volumes upon volumes of how to stage and arrange your dial plans to speed call routing and minimize memory usage on voice over IP (VoIP) equipment.  However, there are a couple of things that I’ve found over the course of my career in voice that I want to pass along that I’ve never really found written down anywhere.  Consider these some of the “street smarts” of VoIP.

- Avoid Placing Extensions in the “9XXX” range.  This one seems to be the most popular issue.  No matter if you’re using 3-digit or 4-digit extensions, consider anything beginning with a “9″ to be off limits.  There are actually a couple of reasons for this.  First and foremost, “9″ is generally used at the PSTN access code (or escape code) for most PBX-style equipment in the world.  It’s also used as the escape code for Centrex phone service.  If any of the extensions on your Cisco phone system start with a “9″, the system will get a bit confused.  The external route patterns on your CUCM/CUCME system all start with “9″ and have the “Provide Outside Dial Tone” box checked (at least they should).  If you have an extension that is 9640, for instance, CUCM will not play the pitch-changed PSTN dial tone until the number you are dialing explicitly matches a route pattern with the “Provide Outside Dial Tone” check box enabled.  In this example, if you are calling a long distance number, when you hit “9″, you won’t hear the higher-pitched tone.  You also won’t hear it if you follow with 1, 3, or 1.  Not until you dial the 5th digit of your long distance call that eliminates the above 9640 extension will the caller hear the PSTN dial tone.  While this doesn’t really affect the operation of the system, it really throws the users for a loop when they don’t hear that dial tone for accessing the PSTN.

The other crucial reason for avoiding extensions that start with “9″ is to cut down on the number of misdialed emergency numbers (911 or 999).  I’ve talked about emergency numbers before and taking them into account here is just as critical.  I’ve even had to change the PSTN escape code to something other than “9″ (like 8 or 7) in order to correct this emergency calling issue.  In those cases, I have to avoid putting extensions in the 9 range and the new code range to keep my PSTN dial tones and emergency calling behavior straight.

- The 1XXX range is your friend.  If you need a number range for your extensions or voice mail ports or other system directory numbers, anything starting with a “1″ is a great idea.  Why?  Well, since the very beginning of phone systems two numbers have always been reserved and not used to start phone numbers.  One of these is “0″.  Zero has always been used as a signal to the phone company operator, so no number in the North American Numbering Plan (NANP) starts with a zero.  The other number is “1″.  One is a more curious case.  It turns out that the original “candlestick” phones had a bad habit of sending a fast pulse when they went off-hook.  In order to prevent a ton of misdialed calls, the system was configured to ignore any numbers that started with a “1″.  Again, no numbers in the NANP start with a “1″.  We now use One to signal a long distance telephone call, but that is really the only time it’s used.  If you use the 1XXX range for all your voice mail ports or park slots or even extensions, you never really have to worry about it colliding with other parts of your dialing plan.  If you’re setting up a home CUCME system, like I’m trying to do once I can convince my wife, you can put your extensions in the 1XX range and not need to worry about using a PSTN access code.  I’ll probably write a little more about this once my experiment is up and running.

- Create a local 10-digit dial peer.  I’ve mentioned this in passing once before, but if you still live in one of those areas that hasn’t switched to 10-digit dialing for all local calls, you should probably program an explicit local dial peer.  For example, in central Oklahoma calls are still dialed with 7 digits locally.  However, there are destinations that are not long distance (prefixed with a 1) that use 10-digits.  If you program a standard 10-digit dial peer (9.[2-9]XX[2-9]XXXXXX), when you dial 7-digit local calls the system must wait for the interdigit timeout to expire before dialing the call.  This is because those 7 digits can match two different dial peers (7-digit and 10-digit) and the system doesn’t know which one to use until you let the digit timeout expire, which could be up to 15 seconds.  That time is an eternity to your users.

Instead, until the time when your state figures out 10-digit dialing is what all the cool kids are doing, you should do this little work around.  Configure your regular 7-digit and long distance dialing codes.  Rather than creating a 10-digit route pattern though, just create a route pattern with your 10-digit local area code.  In the above example for central Oklahoma (area code 405), that explicit dial peer would be 9.405[2-9]XXXXXX.  This way, any 10-digit calls will route immediately.  Most of your 7-digit calls should route immediately as well when they match the 9.[2-9]XXXXXX route pattern.  The only issue you might have is if your local NANP prefix (the [2-9]XX part) is the same as your area code.  Chances are slim in that case, so your local calls won’t wait for the interdigit time to expire.  Just be sure to have the 10-digit dial peer for all local calls ready to go on the day you get switched over.  Otherwise you are going to have some confused and angry users.

Tom’s Take

If you are going to be a voice enginee…miracle worker, you are going to spend a lot of time learning about dial plans.  Before you know it, things will just be automatic and you’ll be able to churn them out without a second thought.  If you take my advice above into account as you’re learning about dial plans, you will have a much easier time when it comes to the strange corner cases you might run into like not hearing a PSTN dial tone or interdigit timeout issues for local calling.

Cisco Phone Cheat Codes

There are many things in this world that are hidden just beneath the surface that make our lives easier.  Whether it be the Secret Menu at In-n-Out Burger or the good old Konami Code, the good stuff that we need is often just out of reach unless you know the code.  This is also the case when dealing with Cisco phones.  There are three key combinations that will help you immensely when configuring these devices, provided you know what they are.

1.  Unlock Settings – *, *, #.  When you check the settings on a Cisco phone, you’ll notice that you can look at the values but you can’t change any of them.  Many of these values are set at the Cisco Unified Communications Manager (CUCM) level.  However, once common issue is the phone not being able to contact the CUCM server or the phone having the wrong address/TFTP server information from DHCP.  While there are a multitude of ways to correct these issues in the network, there is a quick method to unlock the phone to change the settings.

  • Go to the Settings page of the phone
  • While in the settings page, press *, *, # (star, star, pound) about 1/2 second apart
  • The phone will display “Settings Unlocked” and allow you to make changes

It’s that easy.  There won’t be a whole lot to do with the phone Telephony User Interface (TUI), but you can make quick changes to DHCP, IP address, or TFTP server address entries to verify the phone configuration is correct.  By the way, when putting in an IP address via TUI, the “*” key can be used to put a period in an IP address.  That should save you an extra keystroke or two.

2.  Hard Reset – *,*,#,*,*.  Sometimes, you just need to reboot.  There are a variety of things that can cause a phone to need to be reset.  Firmware updates, line changes, or even ring cadence necessitate reboots.  While you can trigger these from the CUCM GUI, there are also times that they may need to be done from the phone itself in the event of a communications issue.  Rebooting is also a handy method for beginning to troubleshoot issues.

But Tom?  Why not just pull the network cable from the back of the phone?  Won’t disconnecting the power reboot?

True, it will.  What if the phone is mounted to the wall?  Or if the phone is running from an external power supply?  Or positioned in such as way that only the keypad is visible?  Better to know a different way to reboot just in case.  Here’s where the reboot cheat code comes in handy.

  • Go to the settings page of the phone
  • Press *,*,#,*,* (star, star, pound, star, star) about 1/2 second apart
  • The phone will display “Resetting” and perform a hard reset

This sequence will cause the phone to reboot as if the power cable had been unplugged and force it to pull a new configuration from CUCM.  Once common issue I find when entering this code is the keypresses not registering with the phone.  Try it a couple of times until you develop a rhythm for entering it about 1/2 second apart.  Much more than that and the phone won’t think you’re entering the code.  Quicker than that and the keys might not all register.

3.  Factory Reset – “1,2,3,4,5,6,7,8,9,*,0,#”.  When all else fails, nuke the phone from orbit.  It’s the only way to be sure.  Some settings are so difficult to change that it’s not worth it.  Or you’ve got a buggy firmware that needs to be erased.  In those cases, there is a way to completely reset a phone back to the shipping configuration.  You’ll need access to unplug the power cable, as well as enough dexterity to press buttons on the front as you plug it back in.

  • Unplug the power from the phone.
  • As you plug it back it, press and hold the “#” key.  If performed correctly, the Headset, Mute, and Speaker buttons in the lower right corner will start to flash in sequence.
  • When those three buttons start flashing in sequence, enter the following code: 1,2,3,4,5,6,7,8,9,*,0,#.  You’ll notice that’s every button on the keypad in sequence from left to right, top to bottom.
  • Phone will display “Upgrading” and erase the configuration.

Don’t worry if you press a key twice on accident.  The phone will still accept the code.  However, you do need to be quick about things.  The phone will only accept the factory reset code for 60 seconds after the Headset, Mute, and Speaker buttons start flashing in sequence.

Tom’s Take

I find myself using these cheat codes all the time.  Whether I’m correcting a bad TFTP server entry or setting a static IP on a subnet, the ability to manipulate a phone without resorting to using CUCM all the time is very useful.  You can also use these codes to impress your friends with your intimate knowledge of the way Cisco phones work.  Just be careful with that reset code.  About every 1 out of 1,000 times it gives you 30 lives instead.