Vol.1 Lab 1.6 Voice Translation Rules

I am stuck on a particular task in this lab.   I cannot complete the task "Callers should be able to reach the PSTN number 4423221415555 by dialing 7, then any three digits followed by 5555".  As a side note, I believe there is an extra 2 in the PSTN number in the task portion of this lab. 

Based on the workbook configuration shown for the translation rule, it shows the following:

voice translation-rule 2

rule 1 /^7...(5555))/ /900442321411/

The translated number includes 900 in front but the Verification for this task says that translated number should be 442321415555 without 900.

Here is my 'test' of this rule

r3-br2#test voice translation-rule 2 71485555


Matched with rule 1

Original number: 71485555      Translated number: 900442321415555

Original number type: none      Translated number type: none

Original number plan: none      Translated number plan: none

...and Br2Ph2 goes to fast busy.  I don't know if Br2Ph1 should also be able to call successfully but it goes to fast busy as well.

 

Calls fail whether my translation-rule 2 uses /900442321411/ or /442321411/

Here is my config.

 

dial-peer voice 7 pots

 translation-profile outgoing TO_PSTN

 destination-pattern 7...T

 port 0/0/0:15 <-- my lab E1 PRI 

 

 

voice translation-rule 2

 rule 1 /^7...(5555)/ /442321411/  <-- also attempt to use /900442321411/ and calls fail

!

voice translation-profile TO_PSTN

 translate called 2

 


Calling 442321415555 directly from Br2Ph2 works fine as well as dialing 123 or 999 from either Br2Ph1 or Br2Ph2.







On a separate note, the Verification for the first task (dial 123 to reach 999) shows dialing 123 translates to 911 instead of 999.

 

Comments

  • Hi Mark,

     

    The issue is related to the fact that you are matching a new dial-peer with that destination-pattern. The PSTN only accepts calls to 442321415555, however with that dial-peer you are in fact sending out the 900, which is the access code 9, and international dialing code 00. You can modify your translation rule to remove the 900, or change the dial-peer configuration to ensure it matches a peer that will strip the leading 900.

     

    Hope this helps

  • Josh,

    The "Configuration" output for this lab shows the following:

    voice translation-rule 2

    rule 1 /^7...(5555)/ /900442321411/

    This is the solution, correct? I'm assuming everything in the Configuration is supposed to be the answer to this task. Am I wrong in assuming this?  Otherwise I don't see how the Configuration could line up with the Verification.  The verification show the test voice translation-rule 2 output without the 900 in front of the international number.

     

    Calls are still failing for me.  Here is all the relevant portion of my configuration for Lab 1.6.  Other tasks in this lab work fine.

     

     

    voice translation-rule 1

     rule 1 /123/ /999/

    !

    voice translation-rule 2

     rule 1 /^7...(5555)/ /900442321411/

    !

    voice translation-rule 3

     rule 1 /.*(3...)/ /1/

    !

    voice translation-rule 4

     rule 1 reject /^4567/

    !


    voice translation-profile 123-999

     translate called 1

    !

    voice translation-profile 3XXX

     translate called 3

    !         

    voice translation-profile REJECT

     translate called 4

    !

    voice translation-profile TO_PSTN

     translate called 2

    !


    dial-peer voice 1 pots

     incoming called-number .

     direct-inward-dial

     port 0/0/0:15

    !

    dial-peer voice 999 pots

     corlist outgoing PT-DEFAULT

     destination-pattern 999

     port 0/0/0:15

     forward-digits 3

    !

    dial-peer voice 900 pots

     corlist outgoing PT-DEFAULT

     destination-pattern 9[1-8].......$

     port 0/0/0:15

    !

    dial-peer voice 902 pots

     corlist outgoing PT-PREMIUM

     destination-pattern 900T

     port 0/0/0:15

     prefix 00

    !

    dial-peer voice 901 pots

     corlist outgoing PT-DEFAULT

     destination-pattern 90[1-9]T

     clid restrict

     port 0/0/0:15

     prefix 0


    !         

    dial-peer voice 123 pots

     translation-profile outgoing 123-999

     destination-pattern 123

     port 0/0/0:15

    !

    dial-peer voice 7 pots

     translation-profile outgoing TO_PSTN

     destination-pattern 7...T

     port 0/0/0:15

    !

    dial-peer voice 456 pots

     translation-profile outgoing REJECT

     destination-pattern 4567

     port 0/0/0:15








    If I change


    voice translation-rule 2

     rule 1 /^7...(5555)/ /900442321411/

    to

    voice translation-rule 2

     

     rule 1 /^7...(5555)/ /442321411/

    it still fails. 

     

     

    The voice test translates accordingly, so the digit manipulation is working as expected.  That's what has me so frustrated.  Dialing 442321415555 directly from Br2Ph2 works. Dialing 71485555 from Br2Ph2 goes to fast busy.

     

     

     

    r3-br2(config)#voice translation-rule 2

    r3-br2(cfg-translation-rule)#rule 1 /^7...(5555)/ /442321411/

    r3-br2(cfg-translation-rule)#^Z

    Nov 21 20:57:14.699: %SYS-5-CONFIG_I: Configured from console by consoleice translation

    r3-br2#test voice translation-rule 2 71485555

    Matched with rule 1

    Original number: 71485555       Translated number: 442321415555

    Original number type: none      Translated number type: none

    Original number plan: none      Translated number plan: none

     

    What is really odd is debug ccsip messages makes it seem as if I am only dialing 7 from the SIP phone.  However it does this with 999 or 123 as well (shows only the first digit in debug) but calls still complete..so I don't think this is related.

     

     

    Nov 21 20:58:57.971: //-1/xxxxxxxxxxxx/SIP/Msg/ccsipDisplayMsg:

    Sent: 

    SIP/2.0 404 Not Found

    Via: SIP/2.0/UDP 177.3.11.101:5060;branch=z9hG4bK84a27939

    From: "Br2Ph2" <sip:[email protected]>;tag=002290ba2c50003d83656223-86a02f42

    To: <sip:[email protected];user=phone>;tag=7CDF54-D38

    Date: Sat, 21 Nov 2009 20:58:46 GMT

    Call-ID: [email protected]

    CSeq: 101 INVITE

    Allow-Events: telephone-event

    Server: Cisco-SIPGateway/IOS-12.x

    Reason: Q.850;cause=1

    Content-Length: 0

     

     

  • Hi Mark,

     

    You're correct, the solution works for the verification of the rule, but not for reaching the PSTN phone, and my last response missed one detail. The PSTN actually does in fact need the 00 for the call to work. So the 9 should be stripped, however the 00 should in fact still be sent. Sorry for the confusion on that, and I'll ensure the solution is updated.

     

    Thanks!

     

     

  • Josh,  

    I was able to get both Br2Ph1 and Br2Ph2 to call the international PSTN number by modifying the translation-rule.  

    r3-br2(config)#voice translation-r 2

     

    r3-br2(cfg-translation-rule)#rule 1 /^7...(5555)/ /00442321411/

    I figured it was just an oversight.  It wouldn't make sense to have 9 present since we are in effect translating an 8 digit internal extension into a valid PSTN number.  I just looked at my PSTN router config and see translation rule 20 strips 00 for calls coming from BR2.  Initially I didn't want to "cheat" by looking at the PSTN router while I was troubleshooting BR2.  Had I looked sooner I would have caught it. 

    My brain is pretty much fried for the day [*-)] but I would like to know if it matters what my final translation rule looks like on BR2 for this task.  I don't want to leave it in a state that breaks upcoming labs.



    Thanks again for your help!


     

     

  • Hey Mark,

     

    Your rule will certainly work, and accomplishes the task just fine. As another method of troubleshooting, you could have also looked at your other dial-peers to notice that the peer pointing to International patterns prefixed the 00.

     

Sign In or Register to comment.