• View
• Edit
• History
• Print

XymphonyAdjunctProtocol

The combination of the Telesis system and a call processing adjunct server may offer organizations to manage incoming or originating calls. When a call comes into a Telesis system or originates from a Telesis user, the Telesis system may ask to an Adjunct Server about how to proceed with this call attempt.

In this operation, Telesis system acts as a client and send requests to the adjunct call processing server on a predefined UDP port. The adjunct call processing server listens the requests. The adjunct server may also be combined with a database and may do search within this database before responding.

Applications

An adjunct call processing server may be critical to some organizations. Some typical operations and applications, where the adjunct call processing is critical, are:

• Automatic voice response to customers, which are listed in a database
• Pre-paid telephony
• Black lists (blocking customers, which are listed in a database)
• Forwarding customers, which are listed in a database, to right representatives or service groups

XAP - Xymphony Adjunct Protocol

The XAP adjunct data protocol between Telesis system and adjunct server is very simple. Consequently, software enthusiasts (from novice to profesional) may easily develop their own adjunct server applications, which may respond requests from Telesis systems.

Request Data

The request data from Telesis system to adjunct server includes fields like:

• Protocol version
• Type of request like a request for an incoming call
• Reference number of the request
• Access code of the user originating the call or receiving an incoming call
• Calling line identification information
• Received dialed or incoming digits, which is to be used in routing the call

Response Data

The response data from adjunct server to Telesis system includes fields like:

• Protocol version
• Type of request
• Reference number of the request
• New digit sequence, which is to be used in routing the call

Route after Response Data

The route that is decided on after response from the adjunct server may be:

• Disconnection (i.e., rejecting the call attempt)
• A local termination (i.e., subscriber)
• A trunk group from which the call is to be routed outward
• A physical address of a digital/analog subscriber/trunk port available in the Telesis system
• A subscriber service
• A system service for maintenance and administrative purposes
• A system resource like integrated voice mail, message-storage hardware etc.
• A tone or a system message stored in the Telesis system

The XAP adjunct protocol is standard in Telesis systems. It is also simple. The result is a cost-effective and easily maintained solution for organizations needing external call processing.