Browse Prior Art Database

Method for an asynchronous multithreaded barge-in test utility

IP.com Disclosure Number: IPCOM000006197D
Publication Date: 2001-Dec-12
Document File: 6 page(s) / 1K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method for an asynchronous multithreaded barge-in test utility. Benefits include improved call simulation capabilities.

This text was extracted from a Microsoft Word document.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 50% of the total text.

Method for an asynchronous multithreaded barge-in test utility

Disclosed is a method for an asynchronous multithreaded barge-in test utility. Benefits include improved call simulation capabilities.

Description

              The disclosed method uses an asynchronous call-back model (see Figure 1). Forty-eight threads are invoked for 24 inbound lines and 24 outbound lines. Another thread waits for events and at reception sends a flag to a channel notifying it to proceed to the next state. Barge-in is tested during each connected call, and the results are recorded. The program begins by setting the required parameters for the T1 interface and voice resources. Each device handle is opened and handlers are set up for the following events:

·        TDX_BARGEIN

·        TDX_ERROR

·        TDX_PLAY

·        TDX_CST

·        Any voice event

·        GCEV_CONNECTED

·        GCEV_OFFERED

·        GCEV_ANSWERED

·        GCEV_DROPCALL

·        Any event on any device handle

              Next, the program kicks off a thread that calls SR_WAITEVT in a continuous loop. When one event is received, the thread waits for the next event. Subsequently, the dialer and answer threads are kicked off for the 24 outbound channels and 24 inbound channels. At this point, the main thread waits for the user to press <Ctrl-C> to exit the program. When <Ctrl-C> is pressed, a signal flag is triggered that notifies all threads to shutdown gracefully. The handlers are disabled for all devices, and all devices are closed.

              The dialer thread initially routes the voice devices to the T1 interface, sets the appropriate continuous speech processing and voice device parameters (see Figure 2). The thread begins a loop in which it first checks to see if <Ctrl-C> was pressed. If yes, the thread ends. Otherwise, the dialer thread proceeds with placing the call. The dialer thread waits for the appropriate connect event to be returned from the network device on the far end. If within the allotted response time of 3 seconds, an invalid event is received or no event is received, the dialer thread requests the call reference number and releases the call. If a connection is made, the voice device begins recording and playing a prompt. If the application detects voice activity during the prompt, the prompt is...