| TELECOMMUNICATION AND
INTERNETWORKING |
| Voice and Next-Generation
Networks |
|
 |
|
| |
| Media gateway simulator for functional
and traffic testing of a high capacity media gateway
controller |
| |
 |
| |
| The
client |
| The client
is a Next Generation Class 5/4 Switch vendor. |
| |
| The
challenge |
| To implement a Media
Gateway (MG) Simulator that will enable functional
and traffic testing of a high capacity Media Gateway
Controller (MGC) in a Class 5/4 scenario. The simulator
had to be capable of generating up to 4 MBHCA (Mega
bits Busy Hour Call Average) of traffic. |
| |
| Wipro
solution |
Wipro was jointly
involved in requirement analysis with the customer.
We studied real system to actively identify code
re-use; code re-use was later done for all stacks
that the simulator had to use. The complete design
was developed using OOAD techniques (class and interaction
diagrams were drawn for the same).
 |
The system
was made multi-threaded so that it can run
faster on a shared memory multi-processor
Sun System |
|
The simulator was made
extremely robust by consciously plugging all
memory leaks using Rational purify and introducing
several negative test scenarios as part of
integration testing |
|
The simulator has a GUI
interface which provides the following support
|
Initiate
and control several instances of MG |
|
Each MG instance
can initiate different kinds of calls
– V5.2, GR303, SIP, H.323 and
feature simulation like conferencing,
call waiting, call transfer etc. Each
MG also supports ISDN User Part (ISUP)
calls (calls initiated by INET Simulator)
to simulate Class 4 scenario |
|
Each MG instance
has a SNMP interface to EMS to support
configuration |
|
GUI can be used to
introduce errors in specific MG instances
like wrong messages, delaying messages,
ignore received packets etc |
|
Tracing can be selectively
enabled on each MG instance |
|
|
| |
| Benefits |
|
Wipro helped
the client save costs by
|
Avoiding
use of costly protocol testers and traffic
generators that will work with the real
MGC and MG combination |
|
No contention for
limited lab resources – since
MGC was Sun Server based, by using a
simulator that was Sun Server based,
enabled designer testing without much
lab dependence |
|
|
o The MG was of very high
capacity and costly, so the solution enabled
MGC testing without using the costly MG |
|
| |
| Tools
and technologies |
Software:
C++ and Java (for GUI)
Hardware: Sun Solaris 9 and Sun Netra machines
Tools: Sun Workshop, Rational Purify, Rational Rose.
|
| |
| |
|
| |
|
|
