Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Germany Dialing Plan Problem

This is my first post so bear with me on this.

I am currently having a problem with my CallManager configuration.

We are running Cisco Unified CallManager 4.2 configured for a North American Dialing plan but we are using it as the CallManager for our Munich office in Germany.

We are experiencing problems with the amount of digits that the local Telco is pushing. Sometimes they push 11 and sometimes they push 12. Whenever I created a translation pattern for 11 digits it works, but when a 12th digit comes in the translation patter will only match and work for 11 digits.

Here is an example:

Here is some basic information:

089 7504 090 <~~ Main Number

089 7504 0901 <~~ Main Fax

When the user calls

089 7504 09015

The translation patter will find a match on the 11th digit (1) and will send the local Telco a stop signal.

Is there a way to work around this?

Thank you,


Re: Germany Dialing Plan Problem

Translation = always urgent priority. As soon as it finds a match, it will route it. Check out

-- -Mark Turpin
New Member

Re: Germany Dialing Plan Problem

While reading Cisco Unified Communications SRND (based on CUCM 6.x), I found a mistake or misunderstanding in Cisco document:

"It is possible to use route patterns instead of translation patterns to block calls within the line calling search space


The main difference between using a route pattern and a translation pattern to block calls is the end-user experience when trying to dial a blocked number, as follows:

• When using a translation pattern, the end users will be able to dial the entire number and only then will they hear a fast-busy tone.

• When using a route pattern, the end users will hear a fast-busy tone as soon as the number they are dialing can no longer match any allowed pattern. This behavior assumes an IP phone running SCCP, or an Type-B IP phone running SIP with no SIP dial rules configured in the phone."

Refer to:

In CUCM 6.x, translation pattern come along with implicit enabled Urgent Priority.

That makes sense...

New Member

Re: Germany Dialing Plan Problem


Did you find a way around this issue, i will be rolling a gateway out in Munich attached to a UCM cluster in the UK. i noticed the variable length numbers for fax, i thought it was a mis print, is this common in Germany ?

New Member

Re: Germany Dialing Plan Problem

Germany does not have a set digit plan like the States. They can vary depending on the Block bought from the Carrier.


Re: Germany Dialing Plan Problem

Do you have H323 gateways, the same issue is in Austria , Italy and Luxembourg

You need to create a Translation rule for them

089 7504 090 <~~ Main Number

089 7504 0901 <~~ Main Fax

rule 1 /^4090$/ /123/

rule 2 /^4090./ /4090./

Create a dummy DN for the main number so rule 1 will pick out the exact match 4090 and send it to the DN

Rule 2 is - may be needed, maybe not allows the other calls through without a translation, the idea is that it will wait until is check the translations first

The 4090 is dependant on the number of digits you receive from the Telco

New Member

Re: Germany Dialing Plan Problem

I just completed a CME deployment in Germany.

I had the same issue I believe.

I needed to enable overlap-receiving on each of my BRI channels:

isdn overlap-receiving


New Member

Re: Germany Dialing Plan Problem

For Germany I had to implement the isdn overlap-receiving T302 2500 timer, so my gateway have some extra time to receive all the digits

New Member

Re: Germany Dialing Plan Problem

Hi I found the best way was to convert to H323 and use translations it worked a treat.

voice translation-rule 1

rule 1 /^29921191$/ /1900/

rule 2 /^2992119\(.+\)/ /19\1/



voice translation-profile incoming

translate called 1



put the rule on the voice port incoming so it works in srst also

1900 is the ops and the other numbers are DDI and FAX. As you can see the ops number is less digits than the ddi.

hope this helps

dave white