Thanks Justin

But I get no change using this. Here's the setup:

Routers and Handsets are in no partition, so Translations should apply to all incoming calls.

I set it up as follows:

Translation Pattern: 7XXXXXXXXX

Calling party Transform Mask 07XXXXXXXXX

Rory

Rory,

The translation pattern must be blank or match your extension range as this only looks at the Called number - I also suggest you use prefix digits and not a mask.

Even once you put the Translation pattern in place it will never be used because your extension numbers will always be more specfic and CM will route to those and not the pattern - this is why you must use partions and CSS to force the issue.

Justin

Thanks Justin,

We already translate the Called Party number from the BT 6 digit presentation to 4 successfully for incoming calls, but we want tho translate the Calling Party also on incoming calls. This only seems possible on CM for modifying the outgoing CLI , which is why I was attempting to do it at the Voice port on the router using the Translation Rule. But the router just hangs after 2 rules are entered and outgoing calls placed.

The Translation Rule on the router will not accept a wildcard, so you have to say someing like (maybe not quite right, I'm now out of the office):

Translation-Rule 1

Rule 0 7.% 07 any unknown

and apply to the voice port.

This works for mobiles but then to cover the rest of the UK you need to add the prefixes for 01 and 02.

Rory

Justin,

All sorted thanks. Transforms of course are based on the called party number, but allow you to change/prefix the calling party as you recommended. So just added the prefix to the existing called party transform and all works.

Regards

Rory

Hi Justin,

This works great!

We had the same problem with a skinny gateway(c6k).

But this solution only works for national numbers, if the CLI is international there should be an extra prefix (here in Holland!) So I want another translation for international numbers...

Could that be possible?

thanx :-)

Sascha