Message Automation & Protocol Simulation (MAPS™)
MAPS™ Software for TDM / VoIP / Wireless Networks (64-bit Only) | Download Now!
GL's Message Automation & Protocol Simulation (MAPS™) is a protocol simulation and conformance test tool that supports a variety of protocols such as SIP, MEGACO, MGCP, SS7, ISDN, GSM, MAP, CAS, LTE, UMTS, SS7 SIGTRAN, ISDN SIGTRAN, SIP I, GSM AoIP, Diameter and others. This message automation tool covers solutions for both protocol simulation and protocol analysis. The application includes various test plans and test cases to support the testing of real-time entities. Along with automation capability, the application gives users the unlimited ability to edit messages and control scenarios (message sequences). "Message sequences" are generated through scripts.
MAPS™ supports transmission and detection of various traffic types over IP (RTP, GTP), ATM, GSM (TRAU), & TDM - such as, digits, voice file, single tone, dual tones, fax, sms, email, http, ftp, and video. MAPS™ also includes support for wide range of codec rates – visit www.gl.com/traffic-simulation.html and www.gl.com/voice-codecs.html webpage for more details. Verify your latest mobile features over the network with various types of traffic generators and receivers. In GPRS, packet data traffic can be generated and validated with GTP traffic modules. Circuit switched traffic can be generated and recorded using RTP core module.
GL's MAPS™ is designed to work on TDM interfaces as well as on the IP/Ethernet interfaces. TDM signaling protocols such as SS7, ISDN, MLPPP, CAS, MAP, CAP, GSM, INAP, and BICC operate over TDM networks, where as VoIP protocols SIP, SIP-I, MEGACO, MGCP, SIGTRAN, Diameter, INAP, MAP, CAP, and BICC operate over IP transport layer.
MAPS™ also supports 3G & 4G mobile protocol standards for testing the rapidly evolving mobile technologies. MAPS™ can simulate radio signaling protocols such as LTE (S1, eGTP, X2) interfaces and UMTS (IuCS, IuPS, IuH), GPRG Gb, and GSM A over IP transport layer.
MAPS™ test suite is enhanced to simulate multiple UEs and IMS core elements such as P-CSCF, I-CSCF, S-CSCF, PCRF, MGCF in IMS core network. With the help of mobile phones, and other simulated wireless networks, the VoLTE Lab setup can be operated in real-time for making VoLTE calls and also for interworking with PSTN and VoIP networks.
GL’s MAPS™ is enhanced to a High Density version and a special purpose 1U network appliance that is capable of high call intensity (hundreds of calls/sec) and high volume of sustained calls (tens of thousands of simultaneous calls/1U platform).
MAPS™ for Wireless Network
General MAPS™ Features
- Call Simulation & Control
- Multi-protocol, Multi-interface Simulation
- Script based and protocol independent software architecture
- Auto generate and respond to signaling messages
- Traffic Handling Capabilities (requires additional license)
- Pre-processing tools
- Easy script builder for quick testing to advance testing
- Customization of test configuration profiles
- Unlimited ability to customize the protocol fields and call control scenarios
- Centralized Control and Remote Access
- Command Line Interface (requires additional license)
- Option to send reports to database accessible via web interface
- Centralized control of multiple MAPS™ applications remotely from single client application
- Reports and Statistics
- Call Status, Link Status, Message Statistics and RTP Voice Quality Metrics (LMOS, CMOS)
- User Defined Statistics for RTP traffic parameters
- Capture Events, and Error Events
Call Simulation and Control
The signaling and traffic simulation in a call is completely implemented using scripts. Commands in the scripts are executed in controlled way to simulate protocol and traffic behavior. Most of the commands used in the scripts are generic and independent of specific protocol.
MAPS™ application acts as either the Caller or resides at the network terminal acting as Callee. The Call Generation feature simulates an outgoing call by sending call control messages to the DUT using scripts and profiles. The profiles allow necessary parameters of call control messages to be changed during runtime. Call generated from other entity can be automatically detected in call reception window by pre-setting the required answer scripts in the Incoming Call Handler.
Message Sequence - Each call scenario provides the trace with full decoding of the messages exchanged between the MAPS™ and the DUT, and graphical ladder diagrams of the call flow with time stamp. Impairments can be applied to messages to simulate error conditions that occur in real-time networks.
Event-Driven Control - Scripts execution, being event-based, allows redirection of script execution on-the-go with user-defined events. The custom parameters in the events can also be changed during script execution using event profiles.
Script Contents & Script Flow - The script flow and the contents window displays the Script Name, Sub-script Name, Script line number, and script statements to be successfully executed, which help the users in troubleshooting a particular call scenario.
The call control scripts can also automatically handle the traffic over the established call. MAPS™ supports transmission and detection of various traffic types over IP (RTP, GTP), ATM, & TDM over established calls with the support of necessary hardware. The types of traffic supported are -
- Analog and TDM Traffic (digits, voice files, single tones, dual tones, Dynamic VF, fax, sms, and IVR)
- RTP Traffic (digits, voice files, single / dual tones, fax, video, and IVR)
- Mobile Traffic (User-plane GTP and Gateway – SMS, HTTP, Email, FTP, Video)
- Short Message Service (SMS) Test Solutions.
For more information, visit http://www.gl.com/traffic-simulation.html
MAPS™ also includes support for wide range of codec rates – visit www.gl.com/voice-codecs.html
webpage for more details.
Bulk Call Simulation and Load Testing
MAPS™ supports automated stress/load testing capabilities through Load Generation and Bulk Call Simulation features. Bulk Call Simulation allows quick configurations to easily create multiple test entries with different scripts and profiles. Multiple tests can be run simultaneously or sequentially (queue up tasks in succession). Load generation feature further allows specifying the patterns with which the bulk calls can be generated. Load generation can be customized with different statistical distribution patterns such as Uniform, Ramp, Sawtooth, Fixed, Normal, Step, and Step-Sawtooth distribution. Load Generation supports Unique and Multi Distribution patterns. Unique Distribution pattern option allows to configure single distribution pattern for each loaded script, whereas with Multi Distribution pattern, multiple patterns can be configured for each loaded script. Call duration also can be randomized using similar statistical distribution. This feature also helps users configure Stress/Load Testing parameters such as Call per second (CPS), Max Active Call, Minimum and Maximum Call Rates, Start Call Rates, and other parameters.
Scheduler can be used to schedule the simulation of bulk calls or manual calls at a specific start time. The pre-saved master configuration files for test setup and call simulation are automatically loaded to automate the test procedure.
Customization of Test Setup Parameters
The test setup profiles (.xml files) allow users to configure the necessary parameters in order to establish communication between MAPS™ and the DUT. It includes configuring parameters of the network nodes, the network properties, and transport related configurations such as T1/E1 timeslots, IP Address and port numbers for both MAPS™ and the DUT.
Once the transport layer is configured properly, protocol specific signaling messages and traffic can be transmitted and received successfully. All parameters setup in test setup are global and are accessible to all scripts. These parameters initialize protocol engines and the transport modules specific to the protocol.
Customization of Test Parameters, Call Flow, and Protocol Messages Using Pre-Processing Tools
- Message Editor - The Message Templates (GL’s proprietary *.HDL files) comprises of protocol encoding parameters with preset values. It is required to create a message template for every message in a protocol. The message templates are called within the scripts to perform scenario based testing.
- Profile Editor – Profiles (*.xml files) are used to change the values of the fields in the messages (i.e. Message Template in MAPS™) during the course of a call. The multiple profiles with varying parameter values that allow users to configure call instances in call generation and to receive calls.
- Script Editor - The script editor allows the user to create / edit scripts and to define variables for the fields in the messages. The script uses pre-defined message templates to build call flow and perform send and receive actions. Script editor provides options to run the test for multiple iterations in sequential or random flow. Commands allow retransmission of messages with specific interval.
Command Line Interface
Supports scripting through a Command Line Interface (CLI) such as the TCL, Python, VBScript, Java, and .Net , using MAPS™ client-server functionality (requires additional license)
MAPS™ can be configured as server-side application, to enable remote controlling of the application through multiple command-line based clients. Supported clients include TCL, Python, VBScript, Java, and .Net. TCL provides a simple scripting language, with programming facilities such as looping, procedures, and variables. The TCL Client application includes a MapsTclIfc.dll file, a packaged library that enables communication with the Server from a TCL environment.
User can remotely perform all functions such as start test bed setup, load scripts and profiles, apply user events such as send digits/file/tones, detect digits/file/tones, dial, originate call, terminate call, start and stop traffic and so on. User can also generate and receive calls through commands. This client application is distributed along with MAPS™ Server application. Multiple MAPS™ CLI servers can be controlled remotely from single client application.
Call Statistics, Events, Link Status, User Defined Statistics
Call Status & Message Statistics - By default, all call handling scripts (irrespective of the type of the functions) are assessed by MAPS™ to provide statistical information about Total Calls, Active Calls, Completed Calls, Passed Calls, Failed Calls, and Calls/Sec. It is also possible to categorize the statistical information as per the call handling scripts. In addition, Call Generation and Call Reception windows provide useful call status & script execution results.
In addition, Message Stats option for any specific protocol, logs number of times the messages are being transmitted (Tx Count) and received (Rx Count), thus allowing user to monitor the occurring events.
User Defined Statistics – Users can customize the global statistics for RTP audio and video traffic. These global parameters are defined in the call generation scripts, which are calculated and updated periodically providing call quality metrics such as Listening MOS, Conversational MOS, PacketLoss, Discarded Packets, Out of Sequence Packets, Duplicate Packets, Delay and Jitter.
Events Reporting – MAPS™ provides Event Log, Error Events, and Captured Errors windows that log the captured events and errors encountered during the progress of the call.
Link Status - Link Status window indicates transport related information of the protocol, for example, if SCTP is used as transport, it indicates if the association is Up or Down in the Link Status window. MAPS™ IuCS ATM uses SSCOP transport and the associated link status is indicated as Up or Down in the Link Status window.
MAPS™ Working Principle
Working Principle of MAPS™ Application
Call Control (Call Generation and Reception)
- Protocol Engine
Forms the backbone of MAPS™ application that contains Message Templates, and Call Handlers to help MAPS™ encode and decode protocol messages, exchange user-defined protocol field values at run time, and generate call flows.
- Transport Handlers
Support send & receive protocol messages over various transport layers - UDP, TCP, SCTP, LAPD, MTP2, and ATM.
- Global Configurations
Handles parameter configurations that are common across different test scenarios, such as protocol timers, inter-call duration, and so on.
- Impairment and Retransmission Modules
These modules support unexpected call behaviors to test system performance under realistic network conditions. These include – tests to introducing impairments at the traffic level or at the communication protocol level, retransmission of messages at defined interval of time, and so on .
- Traffic Handlers
These modules support generating and received traffic from the other network entities using different traffic type – Traffic over TDM / Analog, over IP, and encapsulation of IP traffic over GTP (Mobile Gateway / Packet Traffic)
- Allows users to build valid and invalid test cases
- Includes ready-to-run scripts for simulating important call scenarios / procedures.
- Offers ‘syntax-ready commands’ to easily build scripts
- Reusability, easy maintainability and reduced ‘time-to-market’.
- Allows users to modify any signaling message, message parameters, and/or information elements.
- Add, modify or remove any optional parameters depending on specific feature of interest.
- Perform packet level fault insertion by impairing any bit / byte of a message.
- Allows users to create multiple user-configuration profiles to suit different testing needs
- Values from the profiles replaces the original values in the messages during run-time
MAPS™ can be configured as server-side application, to enable remote controlling through multiple command-line based clients. Supported clients include Java, VBScripts, TCL, Python and others. The MAPS™ APIs allows for programmatic and automated control over all MAPS™ platforms. Each MAPS™ server can receive multiple client connections and offer independent execution to each client. Likewise, a single client can connect to multiple MAPS™ servers, including servers running different protocols, permitting complex cross-protocol test cases.
Client provides a simple scripting language, with programming facilities such as looping, procedures, and variables. The Client application includes a MapsClientIfc.dll file, a packaged library that enables communication with the Server from the client environment. The advantage of such communication enables user to control MAPS™ by sending commands and receiving responses in a scripting language already familiar with many users.
Clients can remotely perform all functions such as start testbed setup, load scripts, and profiles, apply user events such as send digits/file/tones, detect digits/file/tones, dial, originate call, terminate call, start and stop traffic and so on. User can also generate and receive calls through commands. This client application is distributed along with MAPS™ Server application.
The following depicts MAPS™ SIP TCL Client Interface used to place call and handle RTP traffic between two SIP terminals. Also, observe the executed commands in the MAPS CLI Server window after completing the call.
For more information, please visit MAPS™ APIs for Complete Automation page.
Please Note: The XX in the Item No. refers to the hardware platform, listed at the bottom of the Buyer's Guide, which the software will be running on. Therefore, XX can either be ETA or EEA (Octal/Quad Boards), PTA or PEA (tProbe Units), UTA or UEA (USB Units), HUT or HUE (Universal Cards), and HDT or HDE (HD cards) depending upon the hardware.
- What is MAPS?
- GL's Message Automation & Protocol Simulation (MAPS™) is a protocol simulation and conformance test tool that supports a variety of protocols such as SIP, MEGACO, MGCP, SS7, ISDN, GSM, MAP, CAS, LTE, UMTS, SS7 SIGTRAN, ISDN SIGTRAN, SIP I, GSM AoIP, Diameter and others. This message automation tool covers solutions for both protocol simulation and protocol analysis. The application includes various test plans and test cases to support the testing of real-time entities. Along with automation capability, the application gives users the unlimited ability to edit messages and control scenarios (message sequences). "Message sequences" are generated through scripts.
For Details visit : signaling-and-traffic-simulator.html
- What platforms does MAPS™ run on and what kind of hardware do I need?
- PC Requirements –Windows® 7 / 8.1 (32 bit or 64 bit).
- Minimum CPU Requirements – Core i3 or Higher with 4 GB RAM, USB 2.0 Ports.
- MAPS™ software is licensed EITHER using a hardware dongle or through hardware.
- MAPS™is supported over TDM and OPTICAL platforms which make use of GL'sT1 E1 analyzers or LightSpeed1000™ products
- What protocols are currently Supported?
- The protocols supported in this architecture are listed in the table below. For Details visit : signaling-and-traffic-simulator.html
LTE X2 AP
UMTS (IuCS, IuH)
SIGTRAN (SS7 over IP)
ISDN SIGTRAN (ISDN over IP)
UMTS Gn Gp
SS7 INAP (ANSI, ITU)
SS7 INAP IP (ANSI, ITU)
GSM A IP
MAP (ANSI, ITU)
MAP IP (ANSI, ITU)
GPRS Gb IP
- What is the difference between 32-bit and 64-bit versions of MAPS™ Application?
- Basically both 32-bit and 64-bit Implementations of MAPS™ work exactly similar. MAPS™ 64-bit compilations have significant performance advantages over 32-bit, if only signaling is considered (without traffic) by making use of Large amount of RAM (Random Access Memory ) available on the 64-bit machine. Currently only IP based MAPS™ have 64-bit versions.
- Can I run 32-bit MAPS™ on a 64-bit computer?
- MAPS™ 32-bit versions will work on 64-bit machines. But is is adviced to use 64-bit versions when high performance is desired.
- Can I run 64-bit MAPS™ on a 32-bit computer?
- MAPS™ 64-bit application is designed for the 64-bit version of Windows® will not work on the 32-bit version.
- MAPS™ is not invoking, throwing load MAPS™ dll error. How to resolve?
- This error occurs when installation is not proper or certain steps in installation are skipped. Please install the software again with run as administrator and do not cancel winpcap installation which is essential for MAPS™ application.
- I am getting Error “Security Error: Application is not licensed”, what should I do?
- If you see this error when you run MAPS™ application it indicates a problem with either your dongle or license file.
- First verify that the dongle is plugged in and the red light is on
- Navigate to C:\Program Files\GL Communications Inc\GLDONGLE
- Run haspinfohl.exe. Verify that Status is OK and make a note of the Serial #.
- Run appl_list.exe. Verify that there is a line in the table reading PKSXXX MAPS™ Application with the serial number you noted above.
If the dongle does not appear in haspinfohl.exe, verify that it appears as a USB device in the Windows Device Manager. If it does not appear even in the device manager, remove the dongle and plug it into a different USB port, preferably one directly on the motherboard.
- I am getting 192.168.56.63: 3566 : please verify IP/Port not in use Unable Create Sctp Socket Error. What could be wrong?
- Check if you are using an invalid ip ddress or port number which is either invalid or in use by any other application. Try to change the IP address and Port number which should resolve the issue.
- Error: Unable to connect to MAPS when it uses TCP as transport & configured as Server ?
- - Please verify if you have configured proper IP address & port number.
- Please verify if any Firewall or Anti-virus software is installed on your computer which might be blocking incoming TCP connections.
The easiest way to verify if the incoming TCP connection actually reaches the Windows TCP/IP stack. Please use any web browser and access with http://IPAddress:port. For example if MAPS is installed on IP 192.168.1.1 then use http://192.168.1.1:8045. Here port number must be unused/free. So use port numbers which are not used by any applications. Capture the TCP traffic with GL's PacketScan or Wireshark to see if you see any response for TCP SYNC packet. If you see no response & SYNC packet is retransmitted, then most likely your firewall or antivirus is blocking any incoming TCP connection request.
- Error: “Unable to create GLIpHandler:Invalid Arguments”
- If you see this error when you start the testbed from MAPS™ application, it indicates that the Network Adaptor is not configured correctly.
From Help menu -> run Display Adaptor Info and obtain the Adapter Index for the IP address in use, which has to be appropriately configured in the Testbed.
- Error: Unable to Connect to WCS. Start GL Server.
- This error is related to MAPS™ Applications which simulate traffic with GL's WCS servers such as TDM traffic, and mobile IP Core.
If you see this error follow the steps below -
- Verify if the MobileIpCore basic server is installed on the PC and also verify if the ETH101 licenses are installed.
- In T1 E1 check if the server is invoked and started.
- SCTP Connection is NOT established. How to Resolve?
- SCTP Connection problem may be related to various reasons.
- Run the MAPS™ application as ADMINISTRATOR
- Turn OFF Windows Firewall
- Check if the SCTP Mode is proper / whether Device under test is acting as Server /Client. Configure the MAPS™ application accordingly.
- Check if the proper IP addresses and Port numbers are configured
- Check if the Adapter index is configured properly by verifying the adapter information under help
- Check for ICMP Packets with Protocol Unreachable Information in WireShark®/PacketScan™ applications. If so, assign a free IP address to MAPS™ application instead of system IP Address
If the problem still persists please contact GL for support at email@example.com
- MAPS™ is NOT responding to any incoming messages
- Check the Link Status of the SCTP/TCP Link. If the link status is not UP, stop the Testbed, verify the parameters configured in the Testbed and restart the testbed.
Open Events from Reports menu and check if any of the following Errors are logged in the Captured Errors tab.
- No Valid Script Assigned for "MESSAGE TYPE"
- Check the Incoming Handler Configuration whether any script is configured for the Message type, If not set the appropriate script against the required message type.
Parsing Error or Script not accessible error: If this error is logged in Captured Errors tab, check if the configured script is present in \Scripts folder in the installation directory. If the script is present, check if the script has any parsing errors with the help of Script Editor.
Decode Error: If Decode Error is observed in Captured Errors tab, it indicates that the message received is not understood by MAPS™.
Stop MAPS™ application. Create ‘Debug’ folder in \MAPS™ working folder where you can find Scripts and Message Folder. Invoke the MAPS™ application and start the Testbed. Check if any log is created under debug folder when Decode Error is received. Send the ErrorLog to GL technical support person. If you do not know your technical support contact, please reach us at firstname.lastname@example.org.
- Can MAPS™ be executed remotely?
- Yes. MAPS™ recently introduced a client/server option. This option will allow a client (located on Windows® 7/8) to control a single MAPS™ or many MAPS™ applications over a LAN, WAN, or Internet. The client will incorporate a DLL that can be used for development of a user GUI.
- Can MAPS™ impair or corrupt outgoing messages?
- We can corrupt any outgoing message by applying impairments. Impairment implementation is based on low level bit manipulation. User can specify the offset from the beginning of the frame & do various bit level operation to achieve impairment. At this level we are just playing with Hex Values & cannot give protocol field names
Impairments are applied with the send function only – crc is still correct. Impairments are applied on Message portion which MAPS™ simulates. For example in ISUP-Sigtran only M3UA and ISUP layers are simulated using MAPS, and the message over these layers can be impaired. MAC/IP/SCTP layers are emulated using real protocol stacks so you cannot impair these layer contents. Same is applicable to MTP & HDLC (CRC) which cannot be impaired.
Calculating the offset then the XOR pattern is a bit tedious –can it be made simpler? Message Editor displays the exact offset which can be used directly similar to protocol analyzer.
- What if my question isn’t answered here?
- We encourage your questions, comments, and feedback. Please reach us at email@example.com to send us an email with your questions.
Description of Various Errors in Captured Errors:
- Failed to Initiate Call: Parsing for the Script <ScriptName>: <Error>
- This error is displayed in captured errors when there is a syntax error in script run. This error also displays the Line number and error Type
- Message Template Does not Exist
- This error is displayed when send instuction attempts to send a non existant message template.
- Send Message Failed
- This error is logged when MAPS™ tries to send a message without Transport established.
- Error: Another Script is active for the same callId
- Theis error is logged when Call is attempted using same call parameters
- Decode Failed : No Message Received
- When decode instruction is used without any recv message , this error is logged.
- There is no Infinite Wait Executed for Resume to Jump
- In scripts there should be an infinite wait command to be executed before using Resume instruction, where resume will transfer the script control to previous executed wait command. If no wait is executed before the Resume instruction, the script exits with this error.
- Error: Disc is full- Free the Disk Space, Unable to Log Message Sequences
- This error is logged when MAPS™ is unable to display message sequence .
- There are two resons for this error
- MAPS™ is not having Administrator previleges which is blocking MAPS™ from creating Message log files which are necessary to show Message Sequence in MAPS™
- There is no physical space available in the Harddrive which MAPS™ is currently Located
- Error:Call Purged,Unable to display Message Sequence
- This indicates Message sequence is purged for the selected call. In Call Reception there is a limitation of dipalying 500 calls at a time, when the calls are getting accumulated the calls will be purged and call reception window will have the latest 500 calls at any point of time. When a call is active from very long time and most of the calls later that call are purged there is a possibility that the details of the selected call are purged. In that case if MAPS™ unable to display the details theis error will be logged
- Error: Missing Impairment file
- Send instruction is attemping to use a non existant impairment file.
- If Decode Error is observed in Captured Errors tab, it indicates that the message received is not understood by MAPS™. Stop MAPS™ application. Create ‘Debug’ folder in \MAPS™ working folder where you can find Scripts and Message Folder. Invoke the MAPS™ application and start the Testbed. Check if any log is created under debug folder when Decode Error is received. Send the ErrorLog to GL’s technical support person.
If you do not know your technical support contact, please reach us at firstname.lastname@example.org.
- No Valid Script Assigned for Received Message : <Message Type>
- MAPS™ is received a message which is not associated to any of the running calls and there is no script configured for the message to handle it.
- Importing Variables to Message Template Failed
- This indicates that certain variables are unable to import in the send instruction rfor the selected message. This can occur when wrong Template is selected with Import variables of a different message
- Variable <Variable Names> not present for sendmsg parameter <Absolute Names>while sending <Message Type>message
- This error indiacates the variable name along with the absolute path which is not present in the message type. Which is a resultant of the message template is invalid or does not have the specified information element used in the import parameter
- Getting Variable <Variable Names>value Failed from script for Importing to Message Template
- This error displays a list of parameters which do not have any vale assigned while sending a message
- Error: Bind Instruction is called with Un-Initialized Variable
- This error is logged wheevr BIND instruction is used for a variable which is not initialized
- Label <LabelName> Not Found for goto instruction :Line Number = <Line #>
- When there is no Label defined for a label used in GOTO Instaruction above error is displayed
- Getting Variable <variable Name>failed for goto instruction :Line Number <line #>
- When there is no value initialized for a variable used in goto instruction
- Return Instruction Has improper return point : Line Number = <Line #>
- This error is popped when return insrtuction does not have any return point. Normally occurs when a section is called using UserEvents, where return point is undefined. In this case script handling should be corrected
- Getting Variables <Variable Names> failed for Assignment instruction :Line Number = <line #>
- This error is displayed when the variables in an assignment instaruction having null values
- Getting Rhs Variable %s failed for Assignment instruction :Line Number = %d
- This error is displayed when the variables in Right hand side in an assignment instaruction having null values
- Disconnected From Server
- This error is logged when MAPS™ application disconnects for GL WCS Server in T1 E1 applications
- Encode Error: Invalid Message Template <MessageTemplateName>
- Decode Error: Invalid Message Template <MessageTemplateName>
- These errors are expectd when the mesage template selected is invalid or MAPS™ application cannot understand the
- Missing <var1> In Log String.
- This error is displayed when there is mismatch in the Log string and variables
- Timer Already Running for the TimerName = <Timer Name>
- When Timer is started when a previous instance of the same timer is still running this error is logged.
- Raw WCS Command : Variable %s value not available
- This error is logged when any of the variable is not initialized with a value in any rawcommand.
- Task Failed
- This error is logged whenever a TDM task is failed because of any reason say Timeslot unavailability or parameter unavailability.
- Socket to Protocol Std Mapping Failed : Uinique Str : <CallId>
- This error is logged in Multiinterface environment when MAPS™ unable to asociate any incoming message to any of the MAPS™ applications started with that instance because of the wrong Connection Id or Protocol String mismatch in MAPS™ Init script
- Failed to add UDP transport for %s: please verify IP/Port not in use
- This error is logged when any MAPS™ application using UDP Port is started with an IP / Port in use or an invalid IP address.
- Unable to open log file <File Name>
- This error is logged when MAPS™ is unable to open any log file because of the unavilability of the file/ having no permissions to access the logfile.
- StreamId & ConnectionId not Found
- When any message is sent with non existant Stream and Connection Ids this error will be logged.
- Message Decode Failed : <Message Name>
- This error is logged for the following
-> Decode error for the message in Ladder diagram
-> In recv instrtuction, if MAPS™ failed to decode from the message.
- No Connections Available
- This is error is logged when transport itself is not created and trying to send the message.
RTP Traffic Relarted Error Codes:
- Missing Media Source Ip Address
- - Media IP Address is unavailable
- Missing Media Source Port Number
- Media Port is unvailable for creating RTP session.
- Rtp Session Not Created
- RTP Session creation Failed. Which may cause due to parameters unavailability or RTP Core is not connect
- Cannot Execute Rtp Commands
- RTP Core is not licensed. Check if the dongle is plugged in and RTP license is installed
- Missing Media Peer Ip Address
- Peer Media IP Address is unvailable to start RTP session.
- Missing Media Peer Port Number
- Peer Media Port is unvailable to start RTP session.
- Missing Media Packetization Time
- Packetization time is unavailable to start RTP session.
- Codec not supported
- The Codec used is not supported by MAPS.
- Codec is missing
- Codec parameter is unavailable to start RTP session.
- Payload is missing
- Payload type is unavailable to start RTP session.
- Rtp Session Not Started
- -RTP session failed to start because of any above errors
- Rtp Action:: LoopBack Is Enable .Cannot Perform Send Action
- This error is displayed when any other transmit option is attempted with loopback enabled
- Rtp Action:: Tx File <FileName> missing in Folder
- This error is displayed when Transmit action unable to find the file specified.
SIP Related Error Codes
- HeaderName <HeadreName> Not Present
- Import/Export files contins a header which is not present in a message sent or Received at that time this error is logged
- MGCP Header Parsing Failed for the header <HeaderName> at the <position>
- Header in received MGCP message is failed to parse by MAPS™ or message is incorrect
- Unable to Import the Header <Header Name>from the Message
- Import/Export files contins a header which is not present in a message sent or Received at that time this error is logged
- UserName,Password,Nonce not Provided in Profile for Authentication
- Whenever the Registration procedure could not find the UserName,Password,Nonce values in the profile/ if the profile itself is not selected then this error is logged
- Could not calculate Authorisation credentials
- This error is logged when there is failure in calculating the authorisation credentials
- Could not prepare Authorisation header
- This error is logged when there is failure in calculating the authorisation credentials
- Response Code didn't match for the message = <Message Name>
- if the response code in the received message type and decode instruction is mismatch then this error is logged.
- SIP Header Parsing Failed for the header <Header name> at the <position>
- Header in received SIP message is failed to parse by MAPS™ or message is incorrect
- Unable to Retrive the Header <HeaderName>from the Message
- This error is logged when an Export parameter is defined for a header which is not present in the received messae.
- Adding IP <IPAddress> Failed
- In spoofing, if MAPS™ failed to add the IP Address to the adapter since that IP Address is already in use.
- Unable Export SDP Parameter
- This error is specific to MAPS™ BICC IP which is logged when MAPS™ Fails to Export SDP parameters from a received application Transport message.
Database Related Errors:
- Send Report Error: Reporting Varibles undefined
- Any variable present in Send Report instruction is not initialized this error is displayed
- Send Error, Not able Send Records
- If MAPS™ is unable to send record this error is logged
- Execute Query Command : Variable value not available
- In Execute query instruction if any variable is not assigned with any value this error will be logged.
- Error while connecting to Database
- This error logs when MAPS™ failed to connect to Database
- Send Error, Not able Send KeepAlive
- When failed to send Keepalive message this error is logged
- Disconnected from Database, Not able Send Records
- This error is logged when MAPS™ disconencts from database