This is fine unless you use 0 to go to the operator, also what about local calls?
Local calls can start with 2 thru to 9 in the UK, if you have an internal extension 2342 and then set-up a route pattern to a local number 23422234 (without a 9) your going to have to wait for the inter-digit timeout before you call goes through to either the interal extension or the external local number, because CM has a match for both.
Thats why we always 9 (or whatever) to break out, if you've found a way to beat it I'd like to know how.
As for the original question, yes it can be done but I can't remember the link to the example Im afraid.
calling search space - incoming_SS, contains incoming_p
partition - internal_p
calling search space - DDI_SS, contains internal_p
gateway assigned to the incoming_SS
Translation pattern ! assigned to the partition incoming_p, modify incoming cli to 9xxxxxxxxxxx, search space of DDI_SS.
This way all incoming calls are sent through the translation pattern and a 9 is added infront of the 11 incoming digits (if BT are the provider change to 90xxxxxxxxxx) and then all incoming CLI has a 9 in front. The search space then passes the call to the internal_p which contains my extensions
I agree about the not using 9 put down, it's something dreamt up by non telephony people who do not understand the consequences.
If you are using ccm 3.2 then this works a lot better. On the translation pattern you have the option to prefix outgoing digits for the calling party transformation. This makes it so much easier to append what ever the access code is. Another thing is I usually just make the translation pattern 2xxx if my ext are in the 2000 range. If the ! is working for you go for it. Didn't know if you would be hitting the interdigit timeout or not have not tried it like that before.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.