Thanks Marco,

i tried the below rule. it added the zero fine but for some reason now it is omiting the the last digit of the number (see 015804).  i have attached the debug file.

#rule 1 /\(^.........\)/ /0\1/

Debug log:

015798: //-1/F06AE196BBF4/RXRULE/regxrule_match: No match; number=803 rule precedence=6
015799: //-1/F06AE196BBF4/RXRULE/regxrule_match: No match; number=803 rule precedence=7
015800: //-1/F06AE196BBF4/RXRULE/sed_subst: Successful substitution; pattern=803 matchPattern=803 replacePattern=0286229803 replaced pattern=0286229803
015801: //-1/F06AE196BBF4/RXRULE/regxrule_subst_num_type: Match Type = none, Replace Type = none Input Type = unknown
015802: //-1/F06AE196BBF4/RXRULE/regxrule_subst_num_plan: Match Plan = none, Replace Plan = none Input Plan = unknown
015803: //-1/F06AE196BBF4/RXRULE/regxrule_profile_translate_internal: xlt_number=0286229803 xlt_type=unknown xlt_plan=unknown
015804: //-1/F06AE196BBF4/RXRULE/regxrule_profile_translate_internal: number=043317797 type=unknown plan=unknown numbertype=called
015805: //-1/F06AE196BBF4/RXRULE/regxrule_profile_match_internal: Matched with rule 1 in ruleset 1112
015806: //-1/F06AE196BBF4/RXRULE/regxrule_profile_match_internal: Matched with rule 1 in ruleset 1112
015807: //-1/F06AE196BBF4/RXRULE/sed_subst: Successful substitution; pattern=043317797 matchPattern=(^.........) replacePattern=0\1 replaced pattern=0043317797
015808: //-1/F06AE196BBF4/RXRULE/regxrule_subst_num_type: Match Type = none, Replace Type = none Input Type = unknown
015809: //-1/F06AE196BBF4/RXRULE/regxrule_subst_num_plan: Match Plan = none, Replace Plan = none Input Plan = unknown

thanks in advance for your help.

Hi John,

As per the following Debugs:

015807: //-1/F06AE196BBF4/RXRULE/sed_subst: Successful substitution; pattern=043317797 matchPattern=(^.........) replacePattern=0\1 replaced pattern=0043317797

It has matched the number correctly, however if my eyes are not playing up on me (Those dots are hard to see on this screen) you are missing one dot.

Add another dot in this section "(^.........)" and see if that helps. you should have 11 Numbers where as in the above you have 10, so you are loosing the one at the end cause the 10 digits starts from the first Zero. The system will auto strip the leading Zero due to the other rules if you have correct translation rules in place.

Cheers,

David.

Hey David, how are you doing mate?

i tried the 10 dots before it didn't work either.  because if you look at line 000463 for some reason  when i am dialing the missed call it is changing the number to 043317797 instead of 0433177970. => don't know why it is omiting the the 0 at the end of the number.

see also attached debug file.

000459: //-1/557E405B80F9/RXRULE/sed_subst: Successful substitution; pattern=803 matchPattern=803 replacePattern=0286229803 replaced pattern=0286229803
000460: //-1/557E405B80F9/RXRULE/regxrule_subst_num_type: Match Type = none, Replace Type = none Input Type = unknown
000461: //-1/557E405B80F9/RXRULE/regxrule_subst_num_plan: Match Plan = none, Replace Plan = none Input Plan = unknown
000462: //-1/557E405B80F9/RXRULE/regxrule_profile_translate_internal: xlt_number=0286229803 xlt_type=unknown xlt_plan=unknown
000463: //-1/557E405B80F9/RXRULE/regxrule_profile_translate_internal: number=043317797 type=unknown plan=unknown numbertype=called
000464: //-1/557E405B80F9/RXRULE/regxrule_match: more digits needed; number=043317797 rule precedence=1
000465: //-1/557E405B80F9/RXRULE/regxrule_rule_match: partial match found, partial_match 1
000466: //-1/557E405B80F9/RXRULE/regxrule_profile_match_internal: partial match found with rule 1 ruleset 1112
000467: //-1/557E405B80F9/RXRULE/regxrule_profile_translate_internal: partial match found
000468: //-1/557E405B80F9/RXRULE/regxrule_profile_translate_internal: number= type=unknown plan=unknown numbertype=redirect-target
000469: //-1/557E405B80F9/RXRULE/regxrule_get_RegXrule: Invalid translation ruleset tag=0

Hi John,

Ahh yes i didnt notice that.

Can you post your full Translation profiles and rules up please, i would like to put them in on the LAB system and try to simulate the problem, i would give you ones to work in but they can be somewhat specific to each box, and this part is quite touchy, you make a mistake it can cause problems with dialing.

Cheers,

David.

Don't get too hung up on that debug message - that is just telling you what the translation pattern matched on.  I'm pretty confidant Dave's original answer is the correct one and there are not enough dots in that rule.  An alternative way to do this is to use 'rule 1 /\(.+\)/ /0\1/'.  This matches on a string of one or more digits and prepends the zero.  It also means that if CLID has not been supplied, you don't get 'From 0' appearing on the phones.

A good way to help get these rules right is to use 'test voice translation-rule '.  That spits out the result of the rule processing on the command line - a bit quicker than making test calls.

Cheers,

Dave.

Mr. Harper :)

An alternative way to do this is to use 'rule 1 /\(.+\)/ /0\1/'.  This
matches on a string of one or more digits and prepends the zero.

Ahh you beat me too it Ninja Fingers :)

I was just testing that on the lab system, that was the next thing i was going to suggest, although i did come across a few problems but i think that was more related to some other dodge stuff i was doing to the config from previous testing

Cheers,

David.

Hi all,

i tried #rule 1 /\(.+\)/ /0\1/ same problem see debug file.

i have attached the running config, could you please check maybe there is a rule that is actually omiting the last digit which i am not aware off.

001528: //-1/FED57BB98148/RXRULE/regxrule_subst_num_type: Match Type = none, Replace Type = none Input Type = unknown
001529: //-1/FED57BB98148/RXRULE/regxrule_subst_num_plan: Match Plan = none, Replace Plan = none Input Plan = unknown
001530: //-1/FED57BB98148/RXRULE/regxrule_profile_translate_internal: xlt_number=0286229803 xlt_type=unknown xlt_plan=unknown
001531: //-1/FED57BB98148/RXRULE/regxrule_profile_translate_internal: number=043317797 type=unknown plan=unknown numbertype=called
001532: //-1/FED57BB98148/RXRULE/regxrule_profile_match_internal: Matched with rule 1 in ruleset 1112
001533: //-1/FED57BB98148/RXRULE/regxrule_profile_match_internal: Matched with rule 1 in ruleset 1112
001534: //-1/FED57BB98148/RXRULE/sed_subst: Successful substitution; pattern=043317797 matchPattern=(.+) replacePattern=0\1 replaced pattern=0043317797

cheers thanks.

Hi John,

See if this works:

rule 1 // /0\1/
rule 2 /\(^..........$\)/ /01\1/
rule 3 /\(^.*\)/ /0011\1/

rule 4 /\(.+\)/ /0\1/

I would like to see what happens.

Cheers,

David.

[EDIT]

I would like to see the debug output as well if possible...

Unless ofcourse Dave fixes up your issue via E-mail... And yes delete the config.txt file as well.

[EDIT-2]

It is matching it to this rule:

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

we can get it to match it to rule 1, this is normaly how i would do it, but it really is an each to his own thing, i just tested it on the lab system and it worked for me so i can verify that the above config on rule 1 will work.

David, i did added those rules. didn't work either.

see attached debug file.

Dave, i removed those files. i will email you tonight or tomorrow.

cheers thanks

John,

I forgot to tell you to remove ruleset 1112 (Temporarly) and then try it, no matter what it seems to go to that one as it is more of a specific rule then a generic one, which is not really what we want to do here, we want it to look at rule one and get the best match from there.

So try the following:

1. Apply Rule-1 with the following rule sets as illustrated above

2. Remove Rule-1112 but keep a backup of it and wri mem the config

At each stage please make sure you are doing "wri mem" (Force of habbit) just to make sure, it wont hurt to do so.

Oh i should add, before you make too many changes, please make a backup of your Running Config and save it somewhere, it pays to do this ;)

Cheers,

David.

For the benefit of the wider community, the problem in this case was that the translation rule was not being applied to the correct dial-peers that match on the incoming calls from the PSTN, so the translation rule was never being invoked.

Cheers,

Dave.