An outbound call to 0xxx would not hit this dial peer because the destination-pattern would not be matched. You would need a dial peer with destination-pattern 0xxx and then your translation should work.
Sorry, I was thinking about dialing 0xxx instead of the calling number being 0xxx. Try using a translation profile as described in the following link and enabling it on the dial-peer in the incoming direction such as:
I think that profile should work, but it will have to go on outgoing, since he wants to translate the calling number on his way out of the pots peer, towards the pstn switch.
If it does not work there, I think he could try applying it on the voice port and see what that does - I have found these things to be a little weird sometimes. Or, incoming on the voip peer. There are some debugs you can do:
debug voice translation
test voice translation-rule
It gets confusing because there was the old translation rule stuff, and now the new voice translation rule stuff - you have to remember which one you are using. Here is a link with some helpful info:
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.