IMSWorkX, Inc. brings you superior voice services using our flagship product, the XpressWorkX™ Application Server. This platform offers rapid customization and adaptation of existing applications as well as the ease and flexibility of creating new applications; all of which can be built and delivered reliably across a wide variety of networks including IMS, VoIP, VoLTE, VoWifi, IN, GSM, CDMA and converged TDM/IP.
The XpressWorkX Application Server is a hybrid server that understands and works natively with both SIP and AIN messaging. IMSWorkX has implemented the upper layers of the SS7 protocol (SCCP and TCAP) to be able to send and receive AIN messages and provide the AIN services. Our Application Server also has a fully implemented SIP interface to accept SIP messages from gateways and soft-switches. There are even Diameter and RADIUS interfaces to interoperate within an IMS. These implementations mean that an application can simply process the call treatment regardless of the call origin or destination.
The XpressWorkX Application Server interoperates with all of these messages at the same time so that an application is not limited to a single interface. During the call flow the messaging can change to interact with another part of the network. A feature or service can truly migrate as the network rolls out so you can plan your network migration from a legacy TDM infrastructure to the all-IP network and maintain your current service offerings.
The Application Server is a cluster of machines that work together to serve network applications to the clients. The server communicates with several network peers in order to best serve the intended clients.
The server consists of several machines (usually a minimum of 3) that can be either physical hardware servers or virtual machines. The first machine in the Application Server is the Network Interface Unit (NIU). The NIU is the machine that has the public IP address for external communication. All calls that come into the server are first received by the NIU.
The remaining machines in the server are Application-Processing Servers (AS). These machines actually process the calls by executing the service logic for the applications that are running and performing all the call treatments. Each AS contains an embedded media server so it can act as an endpoint during the call to play or receive media. This feature is useful for IVR applications, collecting digits, and call recording. The AS contains the session and media licenses so the actual call session state machine is maintained in these machines.
Failover State Machine
When the active NIU goes down, a failover automatically switches all incoming traffic to the standby NIU.
This high availability configuration ensures that revenue generating services stay running under any failure scenario.
Software-Based Media Server
The built in media server supports a variety of media processing functions, including announcement playout, DTMF detection and generation, message play and record, conference recording, audio bridging for conferences with up to 10-parties, audio transcoding, and other advanced capabilities. These functions can be logically combined and embedded in a service logic execution environment to implement a wide variety of basic and advanced services. Pre-recorded prompts are available in more than 20 languages, and media support includes:
VoIP – RTP and RCTP
Audio Codecs – G.711 µ-law, G.711 A-law, G.729, G.723, G.726-40, G.726-32, G.726-24, G.726-16
Recording via disk/HTTP/NFS
Audio File Formats for Play/Record
-G.711 µ-law, G.711 A-law
-All of the above in .wav format
-G.726, G.723, G.729
TheXpressWorkX Service Creation Environment (SCE)is an industry-leading visual service development environment that enables developers to build sophisticated applications using drag-and-drop Plug-in Action Components (PACs) to enable a variety of built-in operations and link them in a visual call flow. This windows-based, intuitive interface makes applications faster to develop, customize, and modify to meet changing market needs.
Visual call flow representation provides intuitive development user interface.
Plug-in Action Components allow straightforward drag and drop development of next generation network applications - including actions for:
Third Party Call Control
"Drop to Java" feature allows full programmatic control for custom features directly in the call flow
Applications are automatically translated into XTML to deliver enhanced voice services with speed and flexibility comparable to XML-based internet applications.
Protocol support includes SIP, HTTP (REST/SOAP), RADIUS, SIGTRAN, Mail and select DIAMETER interfaces
Visual Call Flow Representation
Developers build applications using drag and drop PACs to enable a variety of built-in operations and then link them in a visual call flow. This simple, intuitive interface makes applications faster to develop, customize, and modify to meet changing market needs.
XTML Language Flexibility
Applications built with the XpressWorkX SCE are automatically saved into XTML (eXtensible Telephony Markup Language), an XML-based service description language. These XTML-based applications run natively on the XpressWorkX Application Server. With its extensive use of XTML, users of the XpressWorkX SCE are able to deliver enhanced voice services with speed and flexibility comparable to XML-based Internet applications.
SIP, IN, and IMS Protocol Support
Just like the XpressWorkX Application Server, the XpressWorkX SCE supports SIP (RFC 3261 and others), AIN via SIGTRAN (RFC 2719 and others), as well as important IMS protocols. Developers need not become SIP or signaling “experts” because the SCE abstracts protocol specifics and handles implementation details; developers simply specify the policies to be applied to the multimedia sessions the application creates and controls. The environment offers native support for protocols including HTTP, RADIUS, Mail, and select DIAMETER interfaces.
Built-In Programming Tools
Extensive Set of Plug-in Action Components and Plug-in Event Components
The XpressWorkX SCE has a rich set of PACs and PECs for creating next generation network services.
Plug-in Action Components (PACs)
PACs are the building blocks of a function and each one performs a specific action. These PACs are selected, customized, and then linked in the call flow to create the application.
Plug-in Event Components (PECs)
The comprehensive set of PECs can be specified as call flow functions to trigger logic at any point during a call. PECs simplify the design of call flows by eliminating embedded conditional logic that would otherwise be needed to handle these events explicitly.
Facilities to Provision XTML Applications
Once an application is created, developers can transfer application XTML files from the SCE directly to an XpressWorkX Application Server.
The XpressWorkX Management Console (Console) is a robust Element Management System that offers views into the applications, process, and events running on the XpressWorkX Application Server. The Console allows Application Servers to be managed as a system regardless of the number of physical servers. The Console is fully backwards compatible with all versions of XpressWorkX servers, and provides some of the same functionality as an Element Management System commonly used in telecommunications.
The Console supports the following features:
Configuring and monitoring SIP, IN (AIN) applications running on application servers
Connecting to both secure and unsecure servers
Monitoring the server inventory
Monitoring endpoints on media servers
Viewing connection states between message peers
Viewing log files
Receiving and displaying SNMP traps
The Secure Console Feature
The console can connect to the Application Server using a secure TLS connections. This connection can be configured with or without a trusted certificate.
The console displays service hosts in the Object Panel. These hosts can be explicitly added, or they can be found using the Discover feature. When a service host has been added, they can be saved in a configuration file and be reopened upon subsequent use of the console. Each service host can have any of the following three types of service agents:
The service agents are either manually configured or automatically added through the Discover feature. The console allows you to navigate and obtain more detailed information about service agents. For example, if you select message peers, you can view outage logs for its peers.
You can also use the console to perform management functions, such as starting and stopping sessions or applications. Viewing the details of a specific session can help to quickly diagnose problems during that session. This type of system monitoring is similar to using a debugging tool for a process, but is implemented at the application level.
Complete Voice Service Solution
IMSWorkX provides powerful service layer applications for VoIP, VoLTE, IMS and Converged IP/TDM networks that are flexible to meet the needs of any network and subscriber. The highly scalable XpressWorkX software platform brings added value to service providers because of its proven ability to provide current services on legacy networks while simultaneously allowing rapid development of new services for evolving networks.