8/4/2019 Translator Tracking
1/19
Translator Tracking
How to relate SDM trace andTranslator data
8/4/2019 Translator Tracking
2/19
The translator has four main parts.They are listed as per the sequencethey are hit:
Pre-Analysis
Result
Analysis
Translator
8/4/2019 Translator Tracking
3/19
Step 1 after you have got the SDMtrace
Search for call origin in the SDM trace.
Info: translator max loop 515/04/2011 12:42:57 | STATION_L |
/vob/mds_hlr_hlt/src/translator/service/Src/gdmiInterface.cc:1904 |Label:: |
Info: Enter translator : need swap false, translator counter 015/04/2011 12:42:57 | STATION_L |
/vob/mds_hlr_hlt/src/translator/service/Src/hytrap0.c:1667 | Label:: |Info: call origin: 5, numbering phase: 3, numbering plan: 1,
numbering typ: 115/04/2011 12:42:57 | STATION_L |
/vob/mds_hlr_hlt/src/translator/service/Src/hytrap0.c:522 | Label:: |
Info: number of digits to analyse: 12,15/04/2011 12:42:57 | STATION_L |
/vob/mds_hlr_hlt/src/translator/service/Src/hytrap0.c:524 | Label:: |Info: translate num: 53114477855506890000d007
8/4/2019 Translator Tracking
4/19
Step 2
The pre-analysis id is thus obtained as5311
Search the id on Pre-analysis in Translator,
enlist it and double click on it to queryresult
Click on query result and go to thecorresponding result id.
Check on SDM trace by following downafter call origin if you can see the rightresult id.
8/4/2019 Translator Tracking
5/19
8/4/2019 Translator Tracking
6/19
8/4/2019 Translator Tracking
7/19
Step 3: checking on SDM trace
15/04/2011 12:42:57 | STATION_L |/vob/mds_hlr_hlt/src/translator/service/Src/hytrap0.c:951 | Label:: |
Info: analysis digit 1,current block 81,new block 0, result 354
15/04/2011 12:42:57 | STATION_L |/vob/mds_hlr_hlt/src/translator/service/Src/hytrap0.c:593 | Label:: |
Info: result num 354, type 1
8/4/2019 Translator Tracking
8/19
8/4/2019 Translator Tracking
9/19
Step 4:
For this case the result type isLOOPANA which means that thisresult type is not the final result andneed to be analyzed more.
From the result click on target
translator to go to the correspondingtranslator id.
8/4/2019 Translator Tracking
10/19
8/4/2019 Translator Tracking
11/19
In our case it is 10.
Of the dialing codes linked with thetranslator id, the best match will be
hit. To confirm this see on SDM trace if
the next result id is as corresponding
to the right dialing code. In our case, best match is 447785 so
result id should be 1006
8/4/2019 Translator Tracking
12/19
SDM trace shows:15/04/2011 12:42:57 | STATION_L |
/vob/mds_hlr_hlt/src/translator/service/Src/hytrap0.c:951 | Label:: |
Info: analysis digit 5,current block 159,new block 185, result 1006
15/04/2011 12:42:57 | STATION_L |/vob/mds_hlr_hlt/src/translator/service/Src/hytrap0.c:894 | Label:: |
Info: analysis 0x5 @ 10 loop
So best match has been done rightly.
If not done, errors are likely to comewhile running your test case.
8/4/2019 Translator Tracking
13/19
8/4/2019 Translator Tracking
14/19
query result again!
You will get either to the finaltranslation or a new result id if thiswas not the final result.
In this case it leads us to the finalentity translation as seen in the nextscreenshot.
8/4/2019 Translator Tracking
15/19
8/4/2019 Translator Tracking
16/19
Thus you can track for any Entity
number, any calling/called number orany FTN by starting from call originand tracking it using translator.
If any error occurs likeUnexpectedDataValue or
UnknownSubscriber, do check withtranslator that the correct translationis being done.
8/4/2019 Translator Tracking
17/19
Some important points:
When checking the translation of a shortcode used for a certain action, it is requiredto see if the correct action code is linked
with it in the final translation stage.
E.g. 121 is used for NGVM_RESPRN. If itsfinal result does not have NGVM_RESPRN in
nActionCodeList, the error ofUnexpectedDataValue will come whenrunning the test case!
8/4/2019 Translator Tracking
18/19
8/4/2019 Translator Tracking
19/19
Top Related