Overview
The Message Automation & Protocol Simulation (MAPS) -SIP supports testing SIP proxy servers, Redirect servers,
Registrars and user agents such as SIP phones.
The MAPS - SIP Conformance Suite tool is designed with 300+ test cases, as per SIP specification of ETSI TS 102 027-2
document. Test cases include general messaging and call flow scenarios for multimedia call session setup and control over
IP networks. Logging and pass/fail results are also reported. Test cases verify conformance of actions such as registration,
call control, capability queries and messaging for registrars, proxies and redirect servers.
The application gives the users the unlimited ability to edit SIP messages and control scenarios (message sequences).
"Message sequences" are generated through scripts. "Messages" are created using message templates. MAPS can also be
used as a Bulk call generator, which generates and receives SIP calls up to 100,000 calls per system.
MAPS can be used to simulate any interface of the VoIP network. A single MAPS can act as more than one SIP entity at a
time and can generate any SIP message on wire in VoIP network and hence most of testing can be automated and also
equipments needed to test are reduced.
The application is available as
- MAPS for SIP (Item # PKS120 )
- MAPS - SIP Conformance Suite (Item #PKS121)
Main Features:
- Simulates UAC, UAS, and Registrars
- Supports full customization of all SIP headers and message body
- Provides fault insertion, and erroneous call flows testing capability
- Ready scripts makes testing procedure simpler, less time consuming and hence time to market SIP products
- Allows user to create early media (media can be transferred or received even before call is established) scenario
- Tests instant messaging and push-to-talk features
- Handles Retransmissions and remote Retransmissions
- Supports both UDP and TCP
- Commands in the script supports conditional branching loops and user defined variables
- Supported on Windows XP/2000 Operating System
Supported Protocols
- Conformance testing of SIP entities - UAC / UAS / Registrar
- Supported standards - RFCs - 3261 and ETSI TS 102-2 V3.1.1
Coming Soon…
- Conformance testing of IP Multimedia Subsystems (IMS) entities according to 3GPP spec's and RFC's
- Simulation of IMS nodes and its inter-operabity testing
- Components testing of IMS entities - Proxy Call Session Control Function (P-CSCF), Interrogating Call Session Control
Function (I-CSCF), Serving Call Session Control Function (S-CSCF), Media Resource Function Controller (MRFC), and BCCF
- Testing of Service entities - Presences and Instant messaging
Configurations
MAPS comprises of inbuilt test scenarios for testing SIP based components for feature conformance and functionality.
The various scenarios for MAPS testing tool to simulate messaging (SIP methods) from different components, such as the
client-to-server, client-to-proxy, client-to-device under test, and so on are explained below.
Scenario 1 (SIP messages through proxies):
MAPS can be configured to generate SIP messages and simulate the process of routing these messages through
various proxies. Messages being generated by UAC are routed through many proxies to the SIP entity (DUT). The application
includes options to configure routers as loose or strict routers.
Scenario 2 (MAPS acting as Redirect server and UAS):
MAPS can be configured to act as Redirect Server and/or UAS. This allows the redirection call scenarios to be automated
and test DUTs.
Scenario 3 (MAPS acting as UAS and UAC):
MAPS can be configured to act as UAC and UAS simultaneously so that entire Proxy testing can be automated.
SIP Testing Configuration Window
This Window allows users to setup the required test environment. The configuration window consists of
User Agent (UA), Proxy, and Device Under Test (DUT).
- UA (User Agent) is a SIP entity, which can generate and or receive calls. It is configured with
Display URI, Contact URI, MediaIPAddress and Media Port to generate and to receive calls to/from valid IP Address.
- Proxy is a SIP entity, which forwards requests and responses on behalf of User Agents. This is
optional and is configured by entering the proxy IP addresses.
- LR (Loose Routing per RFC 3261) - SIP proxy rewrites the Request-URI as a request moves
throughout the network. The mechanism specified in RFC 2543 is known as a strict routing. Strict routing can be changed
through a new mechanism called UA loose routing specified in RFC 3261. MAPS' allows simulating both types of proxies,
by enabling or disabling LR parameter.
- DUT (Device Under test) is the SIP entity being tested and can be a User Agent Client /Server or
an IP Phone, Softphone, Proxies, Registrar's or any SIP server. DUT is configured with URI, IP Address and Port on which
it listens to incoming SIP requests.
Simulate User Agent Server (UAS)
MAPS includes inbuilt UAC_conformance scripts (*.gls) that allows itself to act as User Agent Server perform Proxy
and UAC conformance testing.
The script in the figure below tests a simple functionality of UAC. When a call is placed from DUT, an instance of active
script appears in MAPS. The first active instruction (active instruction is Send or Recv instruction) of UAC script is a Recv
instruction.
Any UAC generating INVITE to establish Call must not contain ToTag. Here MAPS receives INVITE message and
checks for ToTag in message. MAPS respond with 200OK response messages as written in script
Simulate User Agent Client (UAC)
MAPS includes inbuilt Registrar_conformance and UAS_conformance scripts (*.gls) that allows itself to act as User
Agent Client and perform Registrar and UAS conformance testing.
Registrar Testing
- If MAPS (DUT) is executing at the specified IP Address, it sends REGISTER request.
- The Registrar generates the ACK reply for the request received
- Registrar sends 200 OK message to MAPS request
UAS Testing
- The first active instruction (active instructions are Send or Recv instructions) of a UAC script is ‘Send instruction’.
UAC starts execution immediately after receiving first instruction
- If DUT (UAS) is executing at the specified IP Address, it receives INVITE request.
- The DUT should respond with 1XX/2XX for the INVITE and wait for the ACK message from MAPS
- As per the written script MAPS waits for 1 sec and sends BYE message to DUT.
- Once MAPS receives 200 ok to BYE message from the DUT, Calls are torn down
Buyer's Guide:
Specifications are subject to change without notice.
Back to Message Automation & Protocol Simulation
Index Page
