Voice Translation Rule is a key part in the Voice Gateways which helps you to translate the Calling Number, Called Number and the Plan type customized for your customers / partners while sending or recieving calls in the gateway. This document helps you to create the Voice Translation Rules for configuring the Calling and Called Dial patterns and plans specific for National and International dialing plans. There are examples given for changing the Number type and plan and Rejecting calls. Example 1 This example replaces the first occurrence of the number "123" with "456". voice translation−rule 1 rule 1 /123/ /456/ These are test voice translation−rule examples: router#test voice translation−rule 1 123 Matched with rule 1 Original number: 123 Translated number: 456 router#test voice translation−rule 1 1234 Matched with rule 1 Original number: 1234 Translated number: 4564 router#test voice translation−rule 1 6123 Matched with rule 1 Original number: 6123 Translated number: 6456 router#test voice translation−rule 1 6123123 Matched with rule 1 Original number: 6123123 Translated number: 6456123 Original number type: none Translated number type: none Original number plan: none Translated number plan: none In this example, the rule matches the first occurrence of the number that contains the pattern "123" anywhere in the number. Specifically, you can use the start and end of number indicators. The Example 2 and Example 3 sections show this. Example 2 This example shows how to replace any occurrence of "123" at the start of a number with "456". voice translation−rule 1 rule 1 /^123/ /456/ These are test voice translation−rule examples. router#test voice translation−rule 1 123 Matched with rule 1 Original number: 123 Translated number: 456 router#test voice translation−rule 1 1234 Matched with rule 1 Original number: 1234 Translated number: 4564 router#test voice translation−rule 1 6123 6123 Didn't match with any of rules Example 3 If you want only the match of an exact number, specify both the start and end number indicators: voice translation−rule 1 rule 1 /^123$/ /456/ router#test voice translation−rule 1 123 Matched with rule 1 Original number: 123 Translated number: 456 router#test voice translation−rule 1 1234 1234 Didn't match with any of rules router#test voice translation−rule 1 6123 6123 Didn't match with any of rules Example 4 This example replaces all numbers with "5554000". voice translation−rule 2 rule 1 /.*/ /5554000/ router#test voice translation−rule 2 123 Matched with rule 1 Original number: 123 Translated number: 5554000 router#test voice translation−rule 2 86573 Matched with rule 1 Original number: 86573 Translated number: 5554000 router#test voice translation−rule 2 "" Matched with rule 1 Original number: Translated number: 5554000 Example 5 This example replaces any number that starts with a combination of zeros (0, 00, and so forth) with "909". voice translation−rule 5 rule 1 /^0+/ /909/ router#test voice translation−rule 5 0123456 Matched with rule 1 Original number: 0123456 Translated number: 909123456 router#test voice translation−rule 5 00123456 Matched with rule 1 Original number: 00123456 Translated number: 909123456 NUMBER TYPE AND PLAN TRANSLATION Example 1 In this example, if a number starts with "4" and the type is "national", the rule adds "90" as a prefix. If the type is "international", the rule adds "900" as the prefix. voice translation−rule 7 rule 1 /^4/ /904/ type national national rule 2 /^4/ /9004/ type international international router#test voice translation−rule 7 493456567 type national Matched with rule 1 Original number: 493456567 Translated number: 90493456567 Original number type: national Translated number type: national Original number plan: none Translated number plan: none router#test voice translation−rule 7 493456567 type international Matched with rule 2 Original number: 493456567 Translated number: 900493456567 Original number type: international Translated number type: international Original number plan: none Translated number plan: none This is useful when telephone companies (Telcos) remove access codes on national and international numbers. You can add the correct prefix with the number type as a basis. Example 2 This example changes the number type and plan. voice translation−rule 8 rule 1 /^2\(...$\)/ /01779345\1/ type unknown national plan unknown isdn This rule matches any four−digit number that starts with "2". The rule removes the "2", adds the number "01779345" as a prefix, and sets the plan to "isdn" and the type to "national". router#test voice translation−rule 8 2001 type unknown plan unknown Matched with rule 1 Original number: 2001 Translated number: 01779345001 Original number type: unknown Translated number type: national Original number plan: unknown Translated number plan: isdn Reject Calls Use the reject keyword to reject calls that match. This example rejects all calls that start with "234". rule 1 reject /^234/ router#test voice translation−rule 10 1234 1234 Didn't match with any of rules router#test voice translation−rule 10 2345 blocked on rule 1 Thanks. ... View more

MDL Traces The MDL tracer gives a C++ object instantiated by the engine that contains a collection of TraceFile objects for the call. This MDL trace can give some details where the problem is related on the PGW 2200 and helps during the troubleshooting of call failures. This document helps you to collect the MDL Trace in PGW2200, also the display options available in the trace helps you to trace the call failures. Collect the PGW 2200 MDL Trace Use this procedure in order to collect an MDL trace via the MML command STA−SC−TRC (Start Trace). 1.Identify the Originating SS7 SigPath Number or the Originating TrunkGroup Number on which calls are placed. 2. Rotate the log: run script under /opt/CiscoMGC/bin/log_rotate.sh. 3.Start the MDL trace: mml>sta−sc−trc:<ss7sigPath name | orig trunkgroup number>:CONFIRM 4. Perform a test (make a call). 5.Stop the MDL trace: mml>stp−sc−trc:all 6. Identify the Call Id (C:) of the bad call. If this test call is made in a test environment, only one CALL_ID displays. Note: These files can contain tracings from many calls that are all mixed up together if the capture is taken on a production PGW. Each tracing record in the file has a specific record type and records information of a type that relates to that record. Each record has a Call ID that relates it to a specific call. 7. Convert the MDL trace into a readable format: a. Go to the /opt/CiscoMGC/var/trace directory. b. Run this command: get_trc.sh <trace file name> For example: /opt/CiscoMGC/var/trace mgcusr@mgc−bru−20%get_trc.sh _ss7path_20040116103221.btr get_trc.sh ca/sim/sp Trace File Utility Mistral Version 1.2 The ANALYSIS mdo file is: GENERIC_ANALYSIS.mdo Retrieving _ss7path_20040116103221.btr trace file Call ID's, please wait... Enter one of the following commands: S = Simprint in less F = Simprint with printing of sent and received Fields in less D = Display trc trace in less G = Display trc trace in less (Generated) C = Convert to trc trace file A = Display CA file in less N = Move to Next call ID P = Move to Previous call ID L = List call ID's in current file X = Set SP flags H = Print Help Q = Quit get_trc.sh Or just enter the ID of the call you want if you know it Use (N)ext and (P)revious to move between the call ID's _ss7path_20040116103221.btr contains 1 call(s) ==> Working on call 1 ID 23 H = Help [S/F/D/G/C/A/N/P/L/H/Q/id]? 8. Type Call Id at the prompt in order to jump to the MDL trace of the bad call. 9. Choose option C in order to convert the trace file. Note: The .btr files are binary trace files that are produced by the PGW tracer function. The main part of the file name is given in the VSC MML command sta−sc−trc. The PGW always adds a .btr extension to these files. By using the C option, the file is converted into a text format and the extension has .trc files that are text trace files. They contain detailed line by line trace information from the MDO code that is run in the simulation replay that produces the file. Therefore, they contain MDL traces. 10. The trace file is in /opt/CiscoMGC/var/trace. Collect the platform.log information under /opt/CiscoMGC/var/log. In some cases the TAC engineer can ask for other platform.log information related to the problem that is reported while the TAC case is handled. Thanks.. ... View more

MDL Traces The MDL tracer gives a C++ object instantiated by the engine that contains a collection of TraceFile objects for the call. This MDL trace can give some details where the problem is related on the PGW 2200 and helps during the troubleshooting of call failures. This document helps you to collect the MDL Trace in PGW2200, also the display options available in the trace helps you to trace the call failures. Collect the PGW 2200 MDL Trace Use this procedure in order to collect an MDL trace via the MML command STA−SC−TRC (Start Trace). 1.Identify the Originating SS7 SigPath Number or the Originating TrunkGroup Number on which calls are placed. 2. Rotate the log: run script under /opt/CiscoMGC/bin/log_rotate.sh. 3.Start the MDL trace: mml>sta−sc−trc:<ss7sigPath name | orig trunkgroup number>:CONFIRM 4. Perform a test (make a call). 5.Stop the MDL trace: mml>stp−sc−trc:all 6. Identify the Call Id (C:) of the bad call. If this test call is made in a test environment, only one CALL_ID displays. Note: These files can contain tracings from many calls that are all mixed up together if the capture is taken on a production PGW. Each tracing record in the file has a specific record type and records information of a type that relates to that record. Each record has a Call ID that relates it to a specific call. 7. Convert the MDL trace into a readable format: a. Go to the /opt/CiscoMGC/var/trace directory. b. Run this command: get_trc.sh <trace file name> For example: /opt/CiscoMGC/var/trace mgcusr@mgc−bru−20%get_trc.sh _ss7path_20040116103221.btr get_trc.sh ca/sim/sp Trace File Utility Mistral Version 1.2 The ANALYSIS mdo file is: GENERIC_ANALYSIS.mdo Retrieving _ss7path_20040116103221.btr trace file Call ID's, please wait... Enter one of the following commands: S = Simprint in less F = Simprint with printing of sent and received Fields in less D = Display trc trace in less G = Display trc trace in less (Generated) C = Convert to trc trace file A = Display CA file in less N = Move to Next call ID P = Move to Previous call ID L = List call ID's in current file X = Set SP flags H = Print Help Q = Quit get_trc.sh Or just enter the ID of the call you want if you know it Use (N)ext and (P)revious to move between the call ID's _ss7path_20040116103221.btr contains 1 call(s) ==> Working on call 1 ID 23 H = Help [S/F/D/G/C/A/N/P/L/H/Q/id]? 8. Type Call Id at the prompt in order to jump to the MDL trace of the bad call. 9. Choose option C in order to convert the trace file. Note: The .btr files are binary trace files that are produced by the PGW tracer function. The main part of the file name is given in the VSC MML command sta−sc−trc. The PGW always adds a .btr extension to these files. By using the C option, the file is converted into a text format and the extension has .trc files that are text trace files. They contain detailed line by line trace information from the MDO code that is run in the simulation replay that produces the file. Therefore, they contain MDL traces. 10. The trace file is in /opt/CiscoMGC/var/trace. Collect the platform.log information under /opt/CiscoMGC/var/log. In some cases the TAC engineer can ask for other platform.log information related to the problem that is reported while the TAC case is handled. Thanks.. ... View more