Overview
Message Automation & Protocol Simulation (MAPS) designed for SIP testing can simulate User Agents (User Agent Client- UAC, User Agent
Server-UAS), Proxy, Redirect, Registrar and Registrant servers. This test tool/traffic generator can be used to simulate any interface in a SIP
network and perform protocol conformance testing (SIP protocol implementations).
The MAPS - SIP Conformance Suite tool is designed with 300+ test cases, as per SIP specification of ETSI TS 102-027-2
v4.1.1 (2006-07) standard. 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, , 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 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 equipments needed to test are reduced.
The application is available as
- MAPS SIP Protocol Test Tool(Item # PKS120 )
- MAPS SIP Conformance Test Suite (Item #PKS121)
Main Features:
- Simulates UAC, UAS, Proxy, Registrars, Registrants, Redirect Servers, and so on
- Supports full customization of all SIP headers and message body
- Provides fault insertion, and erroneous call flows testing capability
- Supports call generation using scripts (only signaling)
- 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
- Handles strict routing & loose routing, when requests are routed through proxies
- Supports both UDP and TCP
- Commands in the script supports conditional branching loops and user defined variables
- Support end-to-end gateway testing
- Supported on Windows XP/2000 Operating System
Supported Protocols
- Conformance testing of SIP entities - UAC , UAS, Proxy, Registrars, Registrants, Redirect Servers
- Supported standards - RFCs - 3261 and test scripts are according to the ETSI TS 102-027-2 v4.1.1 (2006-07)
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-operability 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 (MAPS acting as UAS and testing UAC):
MAPS acting as UAS receive messages from UAC (DUT). DUT can be configured as UAC to generate SIP messages.
Scenario 2 (MAPS testing Redirect server and / or UAS):
MAPS can be configured to act as UAC and test Redirect Server. This allows the redirection call scenarios
to be automated and test DUTs.
Scenario 3 (MAPS acting as UAS and UAC and testing Proxy):
MAPS can be configured to act as UAC and UAS simultaneously so that entire Proxy testing can be automated.
Scenario 4 (MAPS acting as Registrar and testing Registrant):
DUT is configured to act as Registrant (Ex: PacketGen™) and to generate REGISTRATION SIP messages. Here MAPS
acts as Registrar and processes received registration request messages from Registrant (DUT) while conforming Registrant.
Scenario 5 (MAPS acting as Registrant and testing Registrar):
MAPS can be configured to act as Registrant and to generate registration request messages to automate the entire
Registrar (DUT) testing.
Scenario 6 (End-to-End Gateway Testing):
MAPS is an ideal tool to evaluate Gateway / ATA product features such as call connectivity, call signaling, traffic
generation, voice quality testing, codec, and hundreds of other features. For more details, contact GL Communications.
Other notable features include
- Interfaces to Portable T1E1, and VoIP
- Support for SIP protocol conformance testing
- Test Echo canceller performance and compliance
- Multi-protocol call trace for TDM / VoIP
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).
- SIP Configuration - consists of User Agent (UA), Proxy, Registrar/ Device under Test (DUT) configuration parameters. MAPS is configured with Display URI, Contact URI, Via address, Media IP Address, Media Port, Route, Redirect URI, and Registration Parameters to generate and receive calls to/from valid IP Address in the SIP network.
- SIP Authentication Configuration - SIP is designed with HTTP like text based elements and hence the Authorization configuration is essential. The Authorization contains the username and password for User Agent’s account needed for validating credentials.
Simulate User Agent Server (UAS) and Registrar using MAPS
MAPS includes inbuilt UAC_conformance scripts (*.gls) that allows itself to act as User Agent Server (UAS) performing,
UAC conformance testing and Registrar to test Registrant Server
UAC conformance testing
To simulate UAS, users can execute the set of UAC_Conformance inbuilt scripts. The first active instruction of UAC
script is a Recv instruction. A UAC script always waits for an incoming message before execution. If any incoming message is received, then MAPS
checks the method of incoming message with the first '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
Registrant Conformance Testing
MAPS includes inbuilt Registrant conformance scripts (*.gls) that allows itself to act as Registrar performing
Registrant Conformance testing.
The first active instruction of Registrant script is a Recv instruction.
Execute a Registrant SIP_RG_RT_V001.gls script. This test is performed to ensure that the IUT in order to be registered, sends a REGISTER request to its registrar, without user name in the Request-URI and with a SIP-URI as request-URI.
Simulate User Agent Client (UAC)
MAPS includes inbuilt conformance scripts (*.gls) that allows itself to act as User Agent Client and to perform
Proxy, Redirect Server, Registrar and UAS conformance testing.
Proxy Conformance Testing
For Proxy conformance, users can execute the set of Proxy Conformance inbuilt scripts. Here MAPS acts as both UAS and UAC sending and receiving
SIP messages while testing proxy (DUT).All the requests received from UAC (MAPS) are replied back with the unmodified messages as seen in the
message sequence window below.
Redirect Server Conformance Testing
In Redirect Server conformance, MAPS executes a set of inbuilt Redirect Server scripts. MAPS acts as UAC and sends messages to test Redirect Server (DUT).
Redirect Server (DUT) sends response to the caller UAC (MAPS) as seen in the Message Sequence window.
The MAPS processes the 3xx (Ex: 302 Moved Temporarily) messages received from the redirect server and acts as UAC to test the
Redirect Server Conformance test cases.
This test is performed to ensure that the Redirect Server (DUT) on receipt of an INVITE, sends a 3XX (301 or 302) redirection response to the caller
including a Contact header set to the registered location of the callee.
- Redirect Server (DUT) is executed at the specified IP Address, and receives INVITE request from UAC (MAPS)
- Redirect Server sends a 3XX (301 or 302) response to the caller UAC
- UAC sends back an acknowledgement ACK message to the Redirect Server
Registrar Conformance Testing
MAPS acts as Registrant to execute the Registrar Conformance test cases.
- If MAPS is executing at the specified IP Address, it sends REGISTER request.
- If DUT challenges the request with 407 Authentication required
- Maps sends a new REGISTER request with proper credentials
- If credentials matches, then DUT responds with 200 OK message to MAPS request
UAS Conformance Testing
- The first active instruction (active instructions are Send or Recv instructions) of a UAC (MAPS) script is ‘Send instruction’.
UAC starts execution immediately after receiving first instruction
- If UAS (DUT) is executing at the specified IP Address, it receives INVITE request.
- The UAS should respond with 200 OK for the INVITE and wait for the ACK message from UAC
- As per the written script UAC waits for 32 sec and sends BYE message to DUT.
- Once UAC receives 200 OK to BYE message from the DUT, Calls are torn down
SIP Call Flow
Buyer's Guide:
Specifications are subject to change without notice.
Back to Message Automation & Protocol Simulation
Index Page
