Browse Prior Art Database

Determination of Primary and Secondary Reliable Messaging Clients to a Call Processing Server

IP.com Disclosure Number: IPCOM000005342D
Original Publication Date: 2001-Aug-23
Included in the Prior Art Database: 2001-Aug-23
Document File: 2 page(s) / 24K

Publishing Venue

Motorola

Related People

Daniel J. McDonald: ATTORNEY [+4]

Abstract

In a communication that contains console dispatch positions connected to a call processing server, a mechanism is needed to select a primary and a secondary client for the reliable transfer of call control messages

This text was extracted from a WORD97 document.
This is the abbreviated version, containing approximately 58% of the total text.

Determination of Primary and Secondary Reliable Messaging Clients to a Call Processing Server

By

Daniel J. McDonald, John W. Maher, David P. Helm, Brian R. Poe

Abstract:

In a communication that contains console dispatch positions connected to a call processing server, a mechanism is needed to select a primary and a secondary client for the reliable transfer of call control messages.

Background:

Communication systems exist that require participation in service from console dispatch positions (also known as "console". These console dispatch systems typically are grouped such that multiple console dispatch positions reside on a common LAN. Each of these grouped console dispatch positions requires communication with a system call processing server. A reliable messaging scheme to assure that control plane information is transferred between the system call processing server and the console dispatch positions is required.

To assure a high availability connection to a call processing server, it is desirable to have both a primary and a secondary link session from the call processing server. Generally, one console dispatch position client would be the primary link session and a second console dispatch position client would serve as the secondary link session.

Problem Description:

The problem being solved is how multiple consoles dispatch positions on a LAN know which other console dispatch position clients is currently acting as either the primary and or secondary link session to a given server. It also addresses exception cases where a console, which was acting as a link session, fails.

Solution:

Any console dispatch position which has previously established a primary or secondary reliable link session with the server will advertise such to all console clients on that subnet on a regular basis (at a given sound-off interval). Any time the primary or secondary link state of a client changes, it will immediately advertise this change to all other consoles clients on its subnet.

Normal Operation

In order to determine whether or not a console client should request a reliable link session with the server, the console client will first wait for the sound-off interval to elapse so that this console client can build a database of reliable sessions that currently exist to which servers.

Upon determining that either a primary or secondary link does not exist to the desired server, the console client sends a request to the server to establish a reliable session. The server will grant reliable session request to the client and designate the client as the secondary link session to the server. The console will then immediately advertise this fact to all consoles on its subnet, and will continue to advertise this fact at the sound-off interval. If a primary link is absent, then the server will send an additional message to the client indicating th...