Intel IP Media Server 5.5 Event Handling

IP Media Server for HMP Demo Guide — July 2005 41

Demo Details

5.5 Event Handling

This section describes how the IP Media Server for HMP demo handles events. It contains the

following topics:

•Event Mechanism

•Handling Keyboard Input Events

•Handling SRL Events

•Handling Application Exit Events

•TSUsrEvent Structure

5.5.1 Event Mechanism

The IP Media Server demo uses the SRL mechanism to retrieve events. When an event occurs, SRL

calls event handlers automatically. All events are received by the SRL and then passed to the

CallbackHdlr() function for handl ing.

In the initialization phase of the demo, the main( ) function sets up the call-back handler, by calling

PDLsr_enbhdlr( ).

5.5.2 Handling Keyboard Input Events

There is an endless loop {while(0)} in the main( ) function in the Main.cpp file. In that loop, the

application waits forever for a keyboard event by calling the waitForKey() function. The event

must be handled immediately and event-specific information should be retrieved before the next

call to waitForKey( ).

5.5.3 Handling SRL Events

When the R4/Global Call event is received, the application performs the following:

1. Get METAEVENT by calling gc_GetMetaEvent().

2. Get channel ID through device handle to channel mapping.

3. Get device type through device handle to type mapping.

4. Route meta event to the module specified by device type.

5.5.4 Handling Application Exit Events

Normal application exit events, such as pressing either q or Q, don’t enter the SRL. The main()

function calls PDLSetApplicationExitPath() befo re initialization. In Linux, this function sets the

signals (SIGINT, SIGTERM, SIGABRT) for making the appropriate exit from the application. In

Windows, this function enables the detection of CTRL_CLOSE_EVENT (closing the window).

Contents

Main IP Media Server for HMP Demo Guide July 2005 Contents Figures Tab le s Page Revision History This revision history summarizes the changes made in each published version of this document. Page About This Publication Purpose Intended Audience How to Use This Publication Related Information Page Page 2.1 Hardware Requirements Memory Requirements IP Endpoints 2.2 Software Requirements 3.1 Editing Configuration Files 3.1.1 Configuration File Location 3.1.2 Editing the IPMediaServer.cfg Configuration File Page Preparing to Run the Demo Sample Configuration File 3.2 Compiling and Linking 4.1 Starting the Demo 4.2 Demo Options Example 4.3 Using the Demo 4.3.1 Keyboard Commands 4.3.2 Using the Media Server Page Page Running the Demo Figure 1. Demo Voice Menu Flowchart Page 5.1 Files Used by the Demo 5.1.1 Demo Source Code Files Page Table4. Files in Modules Folder Used by the IP Media Server Demo (Continued) 5.1.2 PDL Files 5.2 Programming Model 5.2.1 Module Structure 5.2.2 EventRouter 5.2.3 Interfaces 5.2.4 Classes Table6. Application Classes (Continued) Table7. IP Module Classes Page Table7. IP Module Classes (Continued) Table8. Voice Module Classes Page Table8. Voice Module Classes (Continued) Table9. Fax Module Classes Table9. Fax Module Classes (Continued) 5.3 Threads 5.4 Initialization Keyboard Main Thread SRL Sub-Thread IP R4/GC Page 5.5 Event Handling 5.5.1 Event Mechanism 5.5.2 Handling Keyboard Input Events 5.5.3 Handling SRL Events 5.5.4 Handling Application Exit Events 5.6 Typical Scenario Call Offered Figure 6. Typical Scenario: Call Offered gc_extension( ) gc_listen( ) gc_AnswerCall( ) Play Prompts dx_getdig( ) dx_listen( ) Fax Mailbox Establish Fax Session gc_extension( ) gc_setUserInfo( ) gc_unlisten ( ) gc_setConfigData( ) Fax Session Established fx_sndfax( ) Fax Sent gc_listen( ) gc_extension ( ) gc_stop( ) Fax Session Closed Fax Complete Page Glossary Page Page Page Index A C D E M O P R S