remove the 9 to dial out

Unanswered Question
Jan 29th, 2009

What can be done so that we can eliminate the 9 to dial out in PBX mode.  Have had deals lost because you can not remove like old TDM's.  You can do it via cli in CME, but not the UC500. Why?

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Marcos Hernandez Thu, 01/29/2009 - 13:18

You can also do this on the UC500 via CLI, but the problem is that this setting is incompatible with CCA. Our recommendation is that you use Key System.

If key system is not an option, you may try the following:

- Remove the leading 9 from all your dial peers.

- Leave the "secondary dialtone" command under "telephony-service" so CCA doesn't present you with any errors.

The problem with the above is overlapping dialing, meaning there is chance for collisions and incorrect call routing.



7bridgesol Fri, 01/30/2009 - 10:26

I will give it a try.  Key System is not an option and they do not want this 9.

JOHN NIKOLATOS Thu, 05/21/2009 - 06:47

I know this post is a little old but I wanted to explain what Marcos said earlier another way...  For people who are new to this stuff.

You can edit the dial-peers to remove the 9 like below..  but if you have internal extensions lets say 201, 202, and 203 and you try to call Connecticut which is area code 203, your phone will not be able to call connecticut at a 203 number because the ip phone at INTERNAL extension 203 and its dial peer will match before you can finish dilaing the number and the ip phone will ring...  So you have to be careful and know what the internal extensions are vs. the phone numbers you are dialing..  somewhere it is going to get messy.

(EXAMPLE) - Just change the destination-pattern on ALL dial-peers to REMOVE the leading 9.

dial-peer voice 57 pots
trunkgroup ALL_FXO
corlist outgoing call-local
description **CCA*North American*7-Digit Local**
translation-profile outgoing OUTGOING_TRANSLATION_PROFILE
preference 5
destination-pattern 9[2-9]......
forward-digits all
  no sip-register

dial-peer voice 57 pots
trunkgroup ALL_FXO
corlist outgoing call-local
description **CCA*North American*7-Digit Local**
translation-profile outgoing OUTGOING_TRANSLATION_PROFILE
preference 5
destination-pattern [2-9]......
forward-digits all
  no sip-register

Damian Halloran Mon, 05/25/2009 - 23:19


Is it possible to remove the need to use a prefix on just one outbound line - for example a fax line? I've experimented with this from CLI but keep failing.

All users are happy to use a prefix for their extensions but were hoping not to have to use it for the fax machine.


Damian Halloran.

Marcos Hernandez Tue, 05/26/2009 - 06:04


If this line will be dedicated to faxes only, and other IP phones do not need to access it for outbound calls, then you can use the recently released CCA 2.0 and configure this trunk for Key-system mode, while keeping the other trunks in PBX mode. CCA 2.0 allows for mixed deployments.. You can also use the new Telephony Setup Wizard to expedite the configuration.

This would be one way to avoid having to jump on the CLI.

More info about the new CCA 2.0, on:


Marcos Hernandez
Technical Marketing Engineer
Cisco Systems, Inc.

Damian Halloran Tue, 05/26/2009 - 07:06

Hi Marcos,

Thanks for the quick reply.

Unfortunately after installing CCA 2.0 I've tried going into Configure -> Telephony -> Voice but it fails at the point where it is "Reading User parameters" and I get a java.lang.NullPointerException error dialog box.

Any suggestions on how to resolve this?


Damian Halloran B Comp CCNA

Capital IT Pty Ltd

Marcos Hernandez Wed, 06/03/2009 - 09:01

This is a sign of out of band changes made through the CLI. You would have to normalize (factory default) your configuration. I recommend you do that using CCA 2.0.


Audy Bautista Wed, 02/03/2010 - 11:47

I just removed the first digit from all the outgoing dial peers, and still needed to dial the first digit to call out.  I then did the following, and seems to dial out fine.  Is there any impact to leaving it this way?


voice translation-rule 1112
  rule 1 /^1/ //

voice translation-profile OUTGOING_TRANSLATION_PROFILE
translate called 1112

I then configured this, but I didn't remove OUTGOING_TRANSLATION_PROFILE from any of the dial peers:

voice translation-rule 1112
no rule 1 /^1/ //

Iverach13 Fri, 07/29/2011 - 11:12

I know this is a bit old, but its the only topic I've been able to find on the subject. I am in a similar situation as the original poster is.

I've done what has been posted here to the letter, but it actually makes it even worse. Instead of removing the "9" requirement, it causes the system to still require the 9, but cuts off the last digit in the phone number. So 123-456-7890 would wind up trying to dial 912-345-6789. If I try to dial without the 9, I get the usual error message saying no such extension exists after 4 digits. There are no conflicting extensions that will be causing any problems with this.

I am using 10 digit dialing as opposed to 7, on a UC560. I will also be needing to implement it on a 540 and a 320.

stacy.thompson Wed, 05/19/2010 - 12:13

I know this is an old thread, but wondering how long a change like this takes so I can give our client an esimate for their request.

We have a UC560 and using CCA 2.2(4)....anyway to use it?

Or only CLI still ?



David Trad Wed, 05/19/2010 - 23:57

Hi Stacey,

I would have to say it would be quicker to do it via CLI, basically copy over all your Dial-peers to a txt file, remove the leading digit and then past them back (No more then 10 at a time) and bang it is over and done with :)

If CCA does allow the changes now i would still have to say it would be combersome and slow, you would be pointing and clicking quite a few times



stacy.thompson Thu, 05/20/2010 - 14:10

Agreed. Best to do CLI...

So the plot thickens:  We have this UC560 connected to a UC540 in Denver.  The Uc560 folks are in Colorado Springs and don't have to 10 digit dial, so they are on a 7 digit dial plan. I wrote the following (see below) to the client explaining some of the "gotchas" with removing their lead digit. He added the question "can a # be placed before the extension number to prevent this."  

My brain hurts...I don't know if I'd add a digit to dial peers or to the actual extenison numbers? I don't know if i even NEED to.  and what digit would I use? Since it's an internal extension without a 1 in front, then would it matter? I'm thinking we may just need to change that one user's 303 extension...except he's an owner...

  4 is used for intercom extensions, 6 is used to trsnfVM, .........

The answer is YES we can remove the lead digit 8 to call outbound. We do not have to change the internal extensions. BUT this can cause issues when with the overall dial plan in yours and Denver’s systems. Anyone who forgets to add the 1 before they place a long distance call to Denver 303 will actually end up calling Renny at extension 303.  Can a # or number be placed before the extension number to prevent this.  Denver office extensions are 101,102, and so on. Denver can NEVER have an extension 130 because that would mean anyone in Springs calling a Denver number would always end up calling the Denver ext 130.

stacy.thompson Mon, 05/24/2010 - 10:37

Does anyone have any input?

I'm thinking that adding a "lead digit" to extensions means we'd be rebuilding the extensions entirely...there is no dial peer for me to adjust is there?

any ideas with translation rules or something on doing this?

I guess I need to know:

1) Is there actually a way to add a lead digit to extension to extension dialing (internal calls) ?

2) If so, how does that effect the mutli site deployment that we've configured special for simple ext to ext dialing ( no lead digit or site digit)?



David Trad Mon, 05/24/2010 - 16:02

Hi Stacy,

I don't have much input on this as I would like to be able to work shop something up to be certain.

I know you can put characters in front of an extension such as A100 instead of extension 100, but i am not sure how you would apply this into your scenario correctly, I am also not sure if you can apply the # character in front of the number so users dialing local extensions would need to press this and then dial the extension (Makes sense to look at doing something like this actually).

Sadly I do not have my lab system right now and wont know when I will get it back I would really like to help you with this but I would need to try and emulate something on a non production system, as my work colleagues get annoyed with me when I break our system all the time.

I will research it and see if i can come up with some ideas for you that may work.



Damian Halloran Mon, 05/24/2010 - 16:32

Hi Stacy,

Can I clarify what it is you want to achieve please? Is it that when a internal user dials #303 it gets routed differently to just 303? One is for an internal extension, and the other is for a long distance call?  Is that correct?

You can add leading characters to extensions as I've seen it in one of the innumerable CME docs.  I'm at work now so I'm unable to hunt it down but will do so tonight.

One other question I have is: Is the most logical and reasonable answer to give your client no, we can't add this to the extensions because of all of the reasons why it isn't a good idea.  Then work on an easier more manageable solution with your client. Just a thought.


Damian Halloran

amelling1 Tue, 05/25/2010 - 08:47

Has anyone found a solution to this problem that does not break CCA?

I would basically like to reverse the requirement, so that rather than requiring a certain number before outgoing calls, we would require a certain number ("0" or "#", preferrably) before internal calls (to extensions).

As an example, my extension is 234. It would be great if my coworker could dial "#234" to call me, or "234567890" to call "567890" with area code "234".


stacy.thompson Tue, 05/25/2010 - 08:53


     Andrew asked my question in a more concise manner.

My concern is this: how do you add a lead digit to extensions? Rebuilding the extensions or thru a dial peer?

If it's a rebuild on the actual extension (ephone-dn), then we'd be rebuilding the entire system again.  and it seems to me that I'd just create another lead digit/area code conflict if we do it thru the extension (ephone-dn)...   whatever lead digit we choose paired with the extension will probably be an area code somewhere.  If we can't do it via dial peers, then I don't think it's a good solution. 

I would like to tell our client we are unable to do this, but I want to be certain of that and WHY.  or at least that we can, but it will require a rebuild and take 8-10 hours or something along those lines.



This Discussion