Professional Documents
Culture Documents
Confidentiality Level
Document Name
Tharwat khateeb
Al-
28 05 2008
7/23/2013
Page 1 of 16
Confidentiality Level
7/23/2013
Page 2 of 16
Confidentiality Level
Table of Contents
Chapter 2 (Converting the original tone file)...............................................................................5 2.1 Preparations:...................................................................................................................... 5 Before converting the announcements we have to make the following preparations...............5 1- checking the tone ID and this is to see whether it match the tone ID in the SCP side or not and from the other side to see whether it match the tone configuration in the MSX side as not any ID can be played Successfully, some times the tones can not be played due to a problem in the tone ID , the tone ID should be compatible with the configuration in the MSX3000 side the related configuration represented by the following tables:.........5 Chapter 3 (Final conversion)...................................................................................................... 10 The pervious file converting is representing the first step file converting, but the converted result still con not be loaded to UMG so still there is another conversion which is the second and the last conversion before loading. This time we will use the UMG8900 tone tool this tools is included in the LMT software of the UMG8900 so once we load the LMT of UMG8900 successfully this tool will be loaded with it...............................................................................10 Chapter 4 (Loading the tones).................................................................................................... 14
4.1 loading the tone in BAM ................................... Error: Reference source not found 4.2 loading the tones in the VPU board...................Error: Reference source not found
7/23/2013
Page 3 of 16
Confidentiality Level
Chapter 1 (Overview).
1.1 Dynamic tones description
This technical Paper will introduce the procedure for loading the Dynamic announcement in the MGW but before that I would like to clarify the dynamic announcement. The entire announcement will be loaded in the UMG including the basic announcements and dynamic announcements which could be combined together in the tonefile.arj and then load it to the BAM and from the BAM to the VPU boards. But after loading the tonefile.arj the customer will request loading new dynamic announcements which will be related to new IN services and so on, in this case we will not get the tonefile.arj and combined it with the new announcements each time because loading the tonefile.arj in the running UMG will require resting the VPU boards and this is not possible each time we will load tones so for the new dynamic tones we will load them separately. And after several time and when the dynamic tones exceed the MAX number that can be saved in the boards, the system will reject loading , at that time we will get the tonefile.arj and all loaded dynamic announcements , combined them together with one tonefile.arj and load them back to the boards. This will create a new space for new dynamic announcements in the future. This paper will focus on loading the dynamic tones.
1.2 Playing the Dynamic tone. Here I would like to introduce the how the will play the announcements. The dynamic announcements is mostly representing IN announcements so we load it in the UMG to support a certain IN services , the related communication between MSC and SCP will be based on the announcements ID, the SCP will send PA Play announcement message to MSX over CAP interface, the message will include the announcement ID. MSC will send the message to UMG over Mc interface asking the UMG to play that announcement. Based on the ID, UMG will search in the Dynamic tone list and play it , if UMG did not find it will search about it the tonefile.arj and play it, if did not find the Subscriber will not hear any announcement and UMG will respond to MSC with resources is not available
7/23/2013
Page 4 of 16
Confidentiality Level
2.1 Preparations:
Before converting the announcements we have to make the following preparations 1- checking the tone ID and this is to see whether it match the tone ID in the SCP side or not and from the other side to see whether it match the tone configuration in the MSX side as not any ID can be played Successfully, some times the tones can not be played due to a problem in the tone ID , the tone ID should be compatible with the configuration in the MSX3000 side the related configuration represented by the following tables:
I. Language Category Index Position you can query that table by LST LKINDPOS II. Language Category table you can query that table by LST LANKIND III. Language Kind change you van query that table by LST LKINDCHG.
These three tables will control the announcement ID, so the ID should match the configuration above, otherwise the tones will not be played successfully. For more details about these three tables configuration, you can refer to the configuration guide of MSX3000. 2- To confirm the tone content: most of the time the tones will be loaded in two languages English and Arabic or English and France and so on , so each tone has ID depending on the language so we have to confirm with the SCP side that the content of the tone is correct before load it. 3- To confirm whether the tone is new tone or will overwrite existing one , sometimes customer will modify the tone content depending on changing a certain services in this case they ask to load the tone with the same ID but different in the content, in this case it will overwrite the old one, we need to confirm that for the rolling back and testing issue.
Confidentiality Level
We are usually receiving the tone from the customer or the SCP side with xxxx.wav format (xxxx is representing the tone ID). We can not load that tone directly as UMG will not distinguish that format so we will convert it to another format which is the first step before loading to UMG. We will convert it to xxxx.snd format . for this issue we will use different converting tools ( these tools are not huawei tools) and one of these tools is called GOLDWAVE tools ( we can down load it from the web site :www.goldwave.com) 2.2.1The procedure for converting. To convert the tone from xxxx.wav to xxxx.snd as should follow the following steps 1- open the gold wave tool and select Batch conversion in file
2- set the destination setting as follows: - file type :Raw (*.snd;*,raw) - Attributes: A low,Mono - Rate: 8000
Then determine the destination folder and press begin. The converted tone will be saved in the destination folder. To test it using goldwave tools
7/23/2013
Page 6 of 16
Confidentiality Level
2.2.2
After the successful converting you should test the converted file and to confirm that the quality of the sound is matching the requirements To test it using gold wave tools In the row file format you should fill the following setting: Format : A-low Channels: Mono Sampling rate:8000
7/23/2013 Huawei secret. Do not Spread without permission Page 7 of 16
Confidentiality Level
Then press Ok
You will hear the tone , confirm that the voice is normal , if not so the will be a problem in the Raw file format setting.
7/23/2013
Page 8 of 16
Confidentiality Level
7/23/2013
Page 9 of 16
Confidentiality Level
The pervious file converting is representing the first step file converting, but the converted result still con not be loaded to UMG so still there is another conversion which is the second and the last conversion before loading. This time we will use the UMG8900 tone tool this tools is included in the LMT software of the UMG8900 so once we load the LMT of UMG8900 successfully this tool will be loaded with it. This sep will convert the file step is to convert xxx.snd format to the last format which will loaded in the VPU boards of UMG XXX.STF To open that tool, select programs/HUAWEI Local Maintenance Terminal/ UMG8900 VxxxRxxx/ UMG8900 Tone Tool.
7/23/2013
Page 10 of 16
Confidentiality Level
In the tone config item, you will select the following: Type: Base service tone / fixed announcement. Config item info: select the tone from its destination folder, and copy the announcement ID and past in the AnnID. Then click OK Confirm that the tone type is Single tone and A/MU type is A-low then click creat tone. brows for folder window will display to select the destination folder for the converting file,
7/23/2013
Page 11 of 16
Confidentiality Level
After selecting the destination folder the tool will start converting, the result will be shown in the window of result
7/23/2013
Page 12 of 16
Confidentiality Level
is
XXX.STF
file
for
example
7/23/2013
Page 13 of 16
Confidentiality Level
After successful FTP putting, you can test using LST TONEFILE This command will give you the all Tons in the BAM/Bin/tonepatch.
7/23/2013
Page 14 of 16
Confidentiality Level
Notes: (1) There are some FTP tools can be used for loading the tones in the BAM, in this tools we will configure the IP of OMU and the FTP user name and password then we can query the BAM folders, copy, remove and so on.
Then monitor the loading process. The tones should be loaded to all VPU boards. If some boards not loaded so you need to repeat executing the command for that dedicated board.
After loading successfully you need to check the status of the tones in the boards.
7/23/2013
Page 15 of 16
Confidentiality Level
Use the command CHK TONE:; Select the frame number and slot number and execute, the result will show you the all Tones loaded to that board, there will be three column EXIST in BAM , EXIST in BOARD and MATCH. The three column should be YES.
Then you need to check with the SCP side to test whether they can hear the announcements normally or not.
7/23/2013
Page 16 of 16