Installation and Upgrade

MGU utilizes RPM package manager for software and firmware installation and upgrade. There is only one RPM for the whole MGU installation and this RPM contains all software, and MSP and FPGA FW (firmware) images previously used.

The MGU RPM is named mgw-X.Y.Z-1.ppc.rpm or mgw-X.Y.Z.B-1.ppc.rpm. X.Y.Z is the FW version number, where X represents software generation, Y represents functional extension and Z represents fault correction. If B is present, it represents build number of version X.Y.Z.

MGU provides support for downloading the RPM from a software server using HTTP protocol. Installation is normally ordered by MX-ONE Service Node through O&M signalling port, but can be done through MGU upgrade command. Installation of the RPM could involve reboot of MGU; for example, if boot loader or Linux has been changed.

Upgrading the RPM with Linux rpm command is not recommended.

NOTE: After installing FW version 4.0.0 or newer, it will not be possible to downgrade the to an FW older than 4.0.0.

General

The software consists of the following parts:
  • Boot Loader.
  • Linux operating system and root file system stored on-board in local (NAND) flash file system.
  • Media Gateway applications. There are three server applications on MGU, each using SCTP protocol and a well-known port that an external MX-ONE Service Node may connect to and communicate with application through. These applications are named "Device Board Server" (eridbs), "Media Control Application" (erimca) and "Operation & Maintenance Application" (erioma) using SCTP ports 2816, 2818 and 2817, respectively.
  • Media Gateway commands. Not for normal usage. There are commands mainly for manufacturing and development purposes, but also a few possible to use for fault isolation. These are further documented in the mgw man-page (e.g. enter "man mgw" when logged in on MGU).

Boot Loader

The boot loader is the bootstrapping process that starts operating systems (Linux) on the MGU. It handles:
  • Basic initialization of the MGU board.
  • Chip Select setup.
  • SDRAM configuration.
  • Linux boot.

The boot loader have also a Programmable Built-In Self-Test (PBIST) support.

The bootloader also share configuration data with the OS (Linux) which resides on a NOR-flash memory.

The flash contains:
  • Boot configuration parameters.
  • Manufacturer data (MAC addresses, serial number etc).
  • Product information (ROF, index numbers and revision information).
  • Configuration data (IP-network and linux configuration data)
Printout sample from nor flash: 
DISP *ROF_num = ROF 137 6304/1
DISP *ROF_rev = R1A
DISP *ROF_ser = T01D896676
DISP *eth0_mac = 00:13:5E:F0:AD:C3 
DISP *eth1_mac = 00:13:5E:F0:AD:C2 
DISP *eth2_mac = 00:13:5E:F0:AD:F4 
DISP *eth3_mac = 00:13:5E:F0:AD:F5
DISP nfsroot = /mgu_root
DISP lilo_arg = root=/dev/mtdblock1 rw rootfstype=yaffs noatime 
DISP autoupdate = no
DISP eth0_ip = 10.105.68.57/24
DISP autoboot = yes 
DISP nfsboot = no
DISP phy0_mode = AUTO 
DISP lan_active = LAN0 
DISP lan_primary = LAN0
DISP eth2_ip = 10.105.68.58/24
DISP phy1_mode = AUTO 
DISP eth1_ip = 10.10.1.2/24
DISP def_route = 10.105.68.1 
DISP def_route1 = 10.10.1.1 
DISP eth3_ip = 10.10.1.3/24

Operating System and Root File System

The operating system and root file system is based on Wind River® Linux version 1.4.

Device Board Server

The Device Board Server (DBS) subsystem in MGU hosts the ISDN signaling and Device Board interface functions.

The message passing on Service Node (SN) interface is carried out using Stream Control Transmission Protocol (SCTP) on port 2816.

SCTP has many features but mainly message integrity and safe data delivery is currently in use.

The messages from the SN use configured multiple number identities (in the message header) to address the functions.

The ISDN and Device Board functions are described in other parts of this document.

Media Control Application

The Media Control Application (MCA) is a service on the MGU which main function is to provide control of media related functions for MX-ONE Service Node on SCTP port 2818. In short, these functions include:
  • Creating and managing VoIP (Voice media) and FoIP (T38).
  • Creating and managing secure VoIP streams, using SRTP/SRTCP.
  • Controlling auxiliary functions like DTMF signal detection and playing recorded voice announcements.
  • Quality of Service (RTCP/RTCP-XR, VLAN and Diffserv).

Operation & Maintenance Application

The Operation and Maintenance Application (OMA) is a service on MGU that provides an interface for MX-ONE Service Node on SCTP port 2817 for the following functions:
  • Selection of market and time zone.
  • Setting and retrieving run-time parameters.
  • Alarm configuration and reporting.
  • Inventory information (SW, FW and HW revisions).
  • Network configuration.
  • Installation & Upgrade of SW and FW.
  • Installation of Recorded Voice Announcements.
  • Selection of TDM synchronization source.
  • Common restart functions, such as MGU restart, reboot and shutdown.
Parent topic: MGU Software
↑