3G Core Network Configuration SeminarAgenda:
MGW MO Scripts template
-Procedure:
Following the MGW MO Scripts User guide and MGW HW configuration, select MO sub-files from MGW MO Scripts Template.
*
Modularity:
1 Central Processor Module (CPM)
4 M-MGw MODULEs
Different Subrack has different configuration. Please select the MGW HW Configuration from MGW B-module.
Signalling Standard Level:
System/Local Indication:
There are two kinds of MO script filename extended name:
*
File Name Description
include all Switch-module, Subracks and all Slots
03_CPP5_SW_Definition_SYS Lists all CPP5 loadmodules’ product No./Rev/Path
03_UPCF_SW_Definition_SYS Lists all UPCF loadmodules product No./Rev/Path
04_..._SW_Allocation_SYS Describes the way the loadmodules allocated on
each slots(GPB/SCB/SXB/MSB/ET-M4/ET-MFG/ET- C41/ET-MC1) in all subracks and loadmodules reliable-state
05_SW_Roles_Definition_SYS Lists the SW roles used by upgrade, LM match Board
06_..._SW_Roles_Allocation_SYS Allocates the SW roles to the all boards, SW will control Boards
07_..._ISL_and_Alarm_... Defines the Alarm, Inter-Subrack Links, Fans
08_..._ET_boards_definition_SYS Defines the ET-Boards MOs(ET-M4/ET-MFG/ET- C41/ET-MC1) in all subracks
09_TUB_Definition_SYS Defines the general characteristics of the TUBs
MO “Ch” VMGws Controller Handler(CH)Controller Handler GCPGCP CommandMeSCs.
VMGwsCh MO, VMGw pool. MGW16 Ch MOs
*
11_Media_Stream_Services_SYS Defined the services for device in pools in MSB
12_..._DevicePools_SYS Defined the device pools for the MSB devices
13_..._MSB_ Lock_SYS Locks the MSBs
14_…_MSB_Device_Group_Definition
15_…_MSB_Device_Set_Allocation_SYS
16_..._MSB_Unlock_SYS Unlocks the MSBs
20_..._UPCF_Media_Stream_Controllers_SYS
All HW&SW system configuration is finished.
*
Board Ports Interface Description
ET-MC1 8 E1PhysPathTerm E1-board
ET-MFG 1 GigaBitEthernet IP-board
24_..._MSPG_Groups_LOC Defines Multiplex Section Protection Group (MSPG)
Example: 2 Os155SpiTtp ports on ET-C41 boards could be defined as MSPG,
one ports should be Active; Another one should be Standby;
Muxmode 0 - standby
signalling and traffic on ET-MC1 and ET-C41 boards
28_..._VP_VC_ITU_LOC Defines ATM VP/VC for each ATM board(ET-M4)
29..._Atm_Cross_Connect_LOC Defines the ATM cross connections
30_NNISAAL_Profiles_LOC Defines NNISAAL profiles
Layer1(Physical):
VclTp (VCI)
Mtp3bAp (remote Access point code)
Mtp3bSls (SS7 signalling link set ,LS)
Mtp3bSr (MTP3b Signalling Route ,DEST)
Mtp3bSlItu (signalling link code ,SLC)
Mtp3bSlChina (signalling link code ,SLC)
*
Layer1(Physical):
DS0Bundle
Layer2:
Mtp2ProfileChina
Mtp2ProfileItu
Mtp3bSls (SS7 signalling link set,LS)
Mtp3bSr (MTP3b Signalling Route,DEST)
*
35_..._Sigtran_Signalling_LOC Defines signalling over IP
Defined IP Access Host GPB
IpAccessHostGpb (Ip Access Host used for signalling, executes on a GPB board )
IpInterface (IP address definition)
Defined SCTP(SCTP end point)
SCTP (SCTP is designed to transport signaling messages over IP networks)
Defined M3u Association
Mtp3bSpItu (OWN SP ITU ,same with broad band)
Mtp3bSpChina (OWN SP China ,same with broad band )
Mtp3bSrs (MTP3b Signalling point to other NODE,SP)
Mtp3bAp (remote Access point code)
M3uAssociation
*
39_.._AAL2_Signalling_LOC Defines the AAL2 signalling links
40_.._TdmGrp_Creation_LOC Defines the TDM termination groups on
ET-MC1 and ET-C41 boards
44_Tones_ITU_R4_LOC Defines the tones for the market
*
Interactive Messaging Messages, Structures and Files
A message is a spoken word or phrase, which can be played to a user. A message file is a stand alone file which provides data for the playing of a message. Message files are data files for basic messages (audio files) and configuration and algorithm files for variable messages.
The file names and the file paths of the associated message files are specified at message creation. The message files themselves are downloaded to the node separately by using FTP.
Basic Message - Each basic message has one associated message file, that is the data file containing the audio data.
Variable message – The contents of a Variable Message depend on input data from the IM system like date, time or phone number. This is defined in the associated configuration and algorithm files. There is a configuration and algorithm file associated to each variable message.
*
Configuration files (.map) in the package directory…
For M-MGw R3 and R4.0: /c/im_algorithms/algconfigfiles/
For M-MGw R4.1: /c/im_variable_messages/algconfigfiles/
For M-MGw R3 and R4.0: /c/im_algorithms/algsourcefiles/
For M-MGw R4.1: /c/im_variable_messages/algsourcefiles/
For M-MGw R3 and R4.0:
For M-MGw GMPv2.x
/p001000/phrases/ and /p001100/phrases/
For M-MGw GMPv3.0
/p001200/phrases/ and /p001300/phrases/
For M-MGw R4.1:
For M-MGw GMPv2.x
/p001000/im_basic_messages/phrases/ and /p001100/im_basic_messages/phrases/
For M-MGw GMPv3.0
/p001200/im_basic_messages/phrases/ and /p001300/im_basic_messages/phrases/
MGW Configuration R4
The IM Streamer is responsible for streaming the message towards the IM players (devices). There can be a master Streamer and a backup IM Streamer to provide redundant speech store. The basic messages are thus loaded on both IM Streamers and in case of failure of one of the IM Streamers the other one takes over. The IM Streamer runs on a GPB. Note that when an IM Streamer GPB is replaced, also the message files must be downloaded to the new GPB.
An IM Streamer must be created before the first basic message is created. The IM Streamer can then be associated to all basic messages, when they are created.
For M-MGw GMPv2.x, GPB 001000 is the active ImStreamer and 001100 is the standby.
For M-MGw GMPv3.0, GPB 001300 is the active ImStreamer and 001200 is the standby.
Interactive Message Streamer