Page 3 - Contents
Global Call API for HMP on Windows Programming Guide – August 2006 3 Contents Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11 About This Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . ....
Page 7 - Figures
Global Call API for HMP on Windows Programming Guide – August 2006 7 Contents Figures 1 Global Call Architecture for IP Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2 Global Call Architecture for E1/T1 and ISDN Technologies . . . . . . . . . . . . . ....
Page 9 - Tables
Global Call API for HMP on Windows Programming Guide – August 2006 9 Contents Tables 1 Call Control Library States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 2 Supported Target Types . . . . . . . . . . . . . . . . . . . . . . . . . ....
Page 13 - About This Publication; Purpose; Applicability
Global Call API for HMP on Windows Programming Guide — August 2006 13 About This Publication The following topics provide information about this publication: • Purpose • Intended Audience • How to Use This Publication • Related Information Purpose This publication provides guidelines for using the G...
Page 14 - How to Use This Publication
14 Global Call API for HMP on Windows Programming Guide — August 2006 About This Publication • Original Equipment Manufacturers (OEMs) How to Use This Publication Refer to this publication after you have installed the hardware and the system software, which includes the Global Call software. This pu...
Page 17 - Product Description; Global Call Software Overview
Global Call API for HMP on Windows Programming Guide — August 2006 17 1 1. Product Description This chapter describes the Global Call software. Topics include: • Global Call Software Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 • Global Call Featu...
Page 18 - Global Call Feature Categories; Operation, Administration and Maintenance Features
18 Global Call API for HMP on Windows Programming Guide — August 2006 Product Description 1.2 Global Call Feature Categories The Global Call development software provides many features allowing for the development of flexible and robust applications. The features fall into one of two main categories...
Page 19 - Global Call Architecture
Global Call API for HMP on Windows Programming Guide — August 2006 19 Product Description Event Handling Functionality Provides the ability to handle and process events, including the ability to disable and enable events and to retrieve event information. See Chapter 4, “Event Handling” for more inf...
Page 22 - Call Control Libraries; Starting Call Control Libraries; Call Control Library States
22 Global Call API for HMP on Windows Programming Guide — August 2006 Product Description 1.4 Call Control Libraries Each supported network technology requires a call control library to provide the interface between the network and the Global Call library. The call control libraries currently suppor...
Page 23 - Global Call Object Identifiers
Global Call API for HMP on Windows Programming Guide — August 2006 23 Product Description Figure 3. Call Control Library States Table 1 describes the different states of a call control library. Each configured call control library is assigned an ID number by Global Call. Each library also has a name...
Page 24 - Line Device Identifier
24 Global Call API for HMP on Windows Programming Guide — August 2006 Product Description group of resources using a single device identifier. Certain features, such as Feature Transparency and Extension (FTE), Real Time Configuration Management (RTCM), and Global Call Service Request (GCSR) operate...
Page 25 - Object Identifiers and Resource Sharing Across Processes; Target Objects
Global Call API for HMP on Windows Programming Guide — August 2006 25 Product Description one call may exist on a given line). A line device can have a maximum of 20 CRNs associated with it. At any given instant, each CRN is a unique number within a process. After a call is terminated and the gc_Rel...
Page 27 - Target Object Availability
Global Call API for HMP on Windows Programming Guide — August 2006 27 Product Description Target Object Availability Except for the GCTGT_GCLIB_SYSTEM target object, all target IDs are generated or assigned by the Global Call API when the target object is created (for physical targets) or loaded (fo...
Page 29 - Programming Models; Programming Models Overview; Asynchronous Mode Programming; Asynchronous Model Overview
Global Call API for HMP on Windows Programming Guide — August 2006 29 2 2. Programming Models This chapter describes the programming models supported by Global Call. Topics include: • Programming Models Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 •...
Page 30 - Asynchronous Model with Event Handlers
30 Global Call API for HMP on Windows Programming Guide — August 2006 Programming Models and gc_GetMetaEvent( ) functions. When these functions return with an event, the event information is stored in the METAEVENT data structure. The event information retrieved determines the exact event that occur...
Page 31 - Asynchronous with Windows Callback Model; Asynchronous with Win32 Synchronization Model; Extended Asynchronous Programming Model
Global Call API for HMP on Windows Programming Guide — August 2006 31 Programming Models Individual handlers can be written to handle events for each channel. The SRL handler thread can be used when porting applications developed for other operating systems. 2.2.3 Asynchronous with Windows Callback ...
Page 33 - Call State Models; Call State Model Overview
Global Call API for HMP on Windows Programming Guide — August 2006 33 3 3. Call State Models This chapter describes the call state models provided by Global Call. Topics include the following: • Call State Model Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ....
Page 34 - Basic Call States at the Inbound Interface
34 Global Call API for HMP on Windows Programming Guide — August 2006 Call State Models 3.2.1 Basic Call States at the Inbound Interface The basic inbound call states are as follows: Null state (GCST_NULL) This state indicates that no call is assigned to the channel (time slot or line). This is the ...
Page 35 - Basic Call States at the Outbound Interface; Basic Call States for Call Termination
Global Call API for HMP on Windows Programming Guide — August 2006 35 Call State Models 3.2.2 Basic Call States at the Outbound Interface The basic outbound call states are as follows: Null state (GCST_NULL) This state indicates that no call is assigned to the channel (time slot or line). This is th...
Page 36 - Basic Call Model Configuration Options; Call State Configuration
36 Global Call API for HMP on Windows Programming Guide — August 2006 Call State Models Call Idle (GCST_IDLE) This state indicates that the local user has dropped the call. This may be a termination initiated by the local user or a response to the remote side disconnecting the call. While the call n...
Page 37 - Call State Event Configuration
Global Call API for HMP on Windows Programming Guide — August 2006 37 Call State Models The GCACT_ADDMSK, GCACT_SUBMSK and GCACT_SETMSK parameter IDs can be assigned one of the following values (of type GC_VALUE_LONG), or an ORed combination of the values: • GCMSK_ALERTING_STATE • GCMSK_CALLROUTING_...
Page 38 - Call Acknowledgement Configuration; Call Proceeding Configuration
38 Global Call API for HMP on Windows Programming Guide — August 2006 Call State Models See the Global Call API Library Reference for more information on the gc_SetConfigData( ) function. 3.3.3 Call Acknowledgement Configuration Note: This functionality applies to E1, T1 and ISDN technologies only. ...
Page 39 - Basic Call Control in Asynchronous Mode; Inbound Calls in Asynchronous Mode; Inbound Calls in Asynchronous Mode Overview
Global Call API for HMP on Windows Programming Guide — August 2006 39 Call State Models 3.4 Basic Call Control in Asynchronous Mode This section describes and illustrates the basic call model and state transitions for call control in asynchronous mode. This section also describes the process for cal...
Page 42 - Channel Initialization
42 Global Call API for HMP on Windows Programming Guide — August 2006 Call State Models The following sections describe the asynchronous inbound call processes. 3.4.1.2 Channel Initialization To establish calls, the following conditions must be met: • The condition of the line device must be unblock...
Page 43 - Call Detection
Global Call API for HMP on Windows Programming Guide — August 2006 43 Call State Models is opened using the gc_OpenEx( ) function. However, if the gc_ResetLineDev( ) function was issued, gc_WaitCall( ) must be reissued. In asynchronous mode, it is not necessary to issue gc_WaitCall( ) again after a ...
Page 44 - Call Routing
44 Global Call API for HMP on Windows Programming Guide — August 2006 Call State Models 3.4.1.5 Call Routing After the call has been offered, a call proceeding indication can be sent to the remote party to indicate that all the information has been received and the call is now proceeding. This indic...
Page 45 - Scenario 1; Scenario 2; Scenario 3
Global Call API for HMP on Windows Programming Guide — August 2006 45 Call State Models then the call is offered to the application regardless of the amount of information available. The application can then request and collect more information as required. The following sections describe various co...
Page 46 - Scenario 4
46 Global Call API for HMP on Windows Programming Guide — August 2006 Call State Models address (caller ID) by issuing the gc_GetCallInfo( ) function. If more information is required, the application may also request more address information using the gc_CallAck(GCACK_SERVICE_INFO) function. Since a...
Page 47 - Abandoned Calls
Global Call API for HMP on Windows Programming Guide — August 2006 47 Call State Models the gc_ResetLineDev( ) function to reset the line device to the Null state. For more information, see the gc_DropCall( ) , gc_ReleaseCallEx( ) and gc_ResetLineDev( ) function descriptions in the Global Call API L...
Page 52 - Outbound Calls in Asynchronous Mode
52 Global Call API for HMP on Windows Programming Guide — August 2006 Call State Models Figure 10 shows an asynchronous call scenario for an incoming call with call acknowledgement controlled by the call control layer and call proceeding controlled by the application. Figure 10. Call Acknowledgement...
Page 56 - Call Dialing; Call Proceeding
56 Global Call API for HMP on Windows Programming Guide — August 2006 Call State Models The following sections describe the asynchronous outbound call processes, as shown in Figure 11, “Basic Asynchronous Outbound Call State Diagram” , on page 54. 3.4.2.2 Channel Initialization To establish calls, t...
Page 57 - Overlap Sending
Global Call API for HMP on Windows Programming Guide — August 2006 57 Call State Models established. This event changes the call to the Connected state. In the Connected state, the call is connected to the called party and call charges begin. When the call is answered (the remote end makes the conne...
Page 58 - Outbound Call Scenarios in Asynchronous Mode
58 Global Call API for HMP on Windows Programming Guide — August 2006 Call State Models 3.4.2.9 Outbound Call Scenarios in Asynchronous Mode This section shows various asynchronous outbound call scenarios. For call scenarios used for a specific signaling protocol, check the Global Call Technology Gu...
Page 60 - Call Termination in Asynchronous Mode
60 Global Call API for HMP on Windows Programming Guide — August 2006 Call State Models Figure 14 shows an asynchronous call scenario for outgoing calls with overlap sending. Note: This scenario applies to E1, T1 and ISDN technologies only. Figure 14. Asynchronous Outbound Call Scenario With Overlap...
Page 61 - User Initiated Termination
Global Call API for HMP on Windows Programming Guide — August 2006 61 Call State Models 3.4.3.1 Call Termination in Asynchronous Mode Overview Figure 15 illustrates the call states associated with call termination or call teardown in the asynchronous mode initiated by either a call disconnection or ...
Page 62 - Call Release; Call Termination Call Control Scenarios in Asynchronous Mode
62 Global Call API for HMP on Windows Programming Guide — August 2006 Call State Models gc_ReleaseCallEx( ) function must be issued to release all internal resources committed to servicing the call. 3.4.3.4 Call Release Once in the Idle state, the call has been disconnected and the application must ...
Page 64 - Handling Unsolicited Events; Advanced Call Control with Call Hold and Transfer; Advanced Call State Model Overview
64 Global Call API for HMP on Windows Programming Guide — August 2006 Call State Models 3.4.4 Handling Unsolicited Events The application must handle unsolicited events in the synchronous mode, unless these events are masked or disabled. The gc_SetConfigData( ) function specifies the events that are...
Page 65 - Advanced Call States for Hold and Transfer; Call Hold
Global Call API for HMP on Windows Programming Guide — August 2006 65 Call State Models describes the call state transitions that occur when the functions are used. This section also provides figures that illustrate the call state transitions for advanced call model functions. Note: The hold, retrie...
Page 66 - Call Transfer; Call Transfer Overview
66 Global Call API for HMP on Windows Programming Guide — August 2006 Call State Models The gc_HoldCall( ) function places an active call in the On-hold (GCST_ONHOLD) state. The gc_RetrieveCall( ) function retrieves the call from the GCST_ONHOLD state and returns it to the Connected (GCST_CONNECTED)...
Page 67 - Supervised Transfers
Global Call API for HMP on Windows Programming Guide — August 2006 67 Call State Models Supervised transfers use the following Global Call API functions: gc_SetupTransfer( ) initiates a supervised transfer gc_CompleteTransfer( ) completes a supervised transfer gc_SwapHold( ) switches between the con...
Page 69 - Unsupervised Transfers
Global Call API for HMP on Windows Programming Guide — August 2006 69 Call State Models Figure 20. Call Termination by the Network or Application During a Transfer Note: In Figure 20, when gc_DropCall( ) is issued, an unsolicited GCEV_CONNECTED event is received for call 1 transitioning it back to t...
Page 71 - Overview of Event Handling; Event Categories
Global Call API for HMP on Windows Programming Guide — August 2006 71 4 4. Event Handling This chapter describes how Global Call handles events generated in the call state model. Topics include: • Overview of Event Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...
Page 72 - Blocked and Unblocked Event Handling
72 Global Call API for HMP on Windows Programming Guide — August 2006 Event Handling 4.3 Blocked and Unblocked Event Handling Global Call uses the concept of blocked and unblocked conditions for line devices. By default, when the gc_OpenEx( ) function is used to open a line device, the line device i...
Page 73 - Event Retrieval
Global Call API for HMP on Windows Programming Guide — August 2006 73 Event Handling critical events. In addition, if the GCEV_BLOCKED event is disabled, some functions will fail with a reason of EGC_INVALIDSTATE, which may cause confusion. For more information on blocking alarms and the GCEV_BLOCKE...
Page 74 - Events Indicating Errors; Masking Events; Event Handlers
74 Global Call API for HMP on Windows Programming Guide — August 2006 Event Handling 4.5 Events Indicating Errors Events that explicitly provide error indications are as follows: GCEV_TASKFAIL Received when an API function call fails When this events is received, the application should call gc_Resul...
Page 77 - General Programming Tips
Global Call API for HMP on Windows Programming Guide — August 2006 77 5 5. Application Development Guidelines This chapter provides some tips when developing programs using Global Call. Topics include: • General Programming Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ....
Page 78 - Tips for Programming Drop and Insert Applications
78 Global Call API for HMP on Windows Programming Guide — August 2006 Application Development Guidelines threads. Asynchronous programming uses system resources more efficiently because it handles multiple channels in a single thread. Asynchronous models let you program complex applications easily, ...
Page 79 - Routing Overview
Global Call API for HMP on Windows Programming Guide — August 2006 79 Application Development Guidelines connected so as to provide the calling party with immediate outbound line status and voice cut-through. For a drop and insert application in which a call cannot be completed, the application can ...
Page 80 - Working with Flexible Routing Configurations; Determining Channel Capabilities (Flexible Routing)
80 Global Call API for HMP on Windows Programming Guide — August 2006 Application Development Guidelines 5.3.2 Working with Flexible Routing Configurations The following topics provide more information about using Global Call with Digital Network Interface boards that use the flexible routing config...
Page 81 - Initializing an Application (Flexible Routing)
Global Call API for HMP on Windows Programming Guide — August 2006 81 Application Development Guidelines 5.3.2.2 Using Device Handles (Flexible Routing) When using Digital Network Interface boards, application performance may be a consideration when opening and closing devices using Global Call. If ...
Page 83 - Device Initialization Hint (Flexible Routing)
Global Call API for HMP on Windows Programming Guide — August 2006 83 Application Development Guidelines 5.3.2.6 Device Initialization Hint (Flexible Routing) In some applications, when xx_open( ) functions (Global Call, Voice, Fax) are issued asynchronously, it may cause slow device-initialization ...
Page 85 - Error Handling; Error Handling Overview
Global Call API for HMP on Windows Programming Guide — August 2006 85 6 6. Error Handling The chapter describes the error handling capabilities provided by Global Call. Topics include the following: • Error Handling Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ....
Page 87 - Call Control; Call Progress Analysis when Using IP Technology; Call Progress Analysis Definition
Global Call API for HMP on Windows Programming Guide — August 2006 87 7 7. Call Control This chapter describes Global Call capabilities relating to call control. Topics include: • Call Progress Analysis when Using IP Technology . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 • Call Progress...
Page 88 - Configuring Default Call Progress Analysis Parameters; Configuring Call Progress Analysis on a Per Call Basis
88 Global Call API for HMP on Windows Programming Guide — August 2006 Call Control 7.2.2 Configuring Default Call Progress Analysis Parameters Call Progress Analysis (CPA) is characterized by parameters such as CaSignalTimeout (the maximum time to wait to detect a call progress tone), CaAnswerTimeou...
Page 90 - Setting Call Analysis Attributes on a Per Call Basis
90 Global Call API for HMP on Windows Programming Guide — August 2006 Call Control See the Global Call API Library Reference for more information about the gc_ResultInfo( ) function. When an option that enables call analysis is selected, a GCEV_MEDIADETECTED event can be received. The gc_GetCallInfo...
Page 91 - Configuring Call Progress Analysis on a Per Channel Basis
Global Call API for HMP on Windows Programming Guide — August 2006 91 Call Control CCPARM_CA_PAMD_QTEMP PAMD Qualification Template. Specifies which PAMD template to use. Possible values are: • PAMD_QUAL1TMP – First predefined qualification template. This is the default value. • -1 – No qualificatio...
Page 92 - Setting Call Analysis Attributes on a Per Channel Basis; Customizing Call Progress Tones on a Per Board Basis
92 Global Call API for HMP on Windows Programming Guide — August 2006 Call Control GCPR_CALLPROGRESS and GCPR_MEDIADETECT parameters. See the Global Call E1/T1 CAS/R2 Technology User’s Guide for more information. Table 12 shows how the CCPARM_CA_MODE values correspond to the GCPR_CALLPROGRESS and GC...
Page 93 - Resource Routing; Feature Transparency and Extension; Feature Transparency and Extension Overview
Global Call API for HMP on Windows Programming Guide — August 2006 93 Call Control 7.3 Resource Routing The Global Call routing functions use the device handles of resources such as a voice channel, a media resource, or a network time slot. The gc_GetResourceH( ) function can be used to obtain the n...
Page 94 - Technology-Specific Feature Access
94 Global Call API for HMP on Windows Programming Guide — August 2006 Call Control The Global Call API functions provided for FTE are: gc_Extension( ) provides a generic interface extensible for technology-specific features gc_GetUserInfo( ) (for E1, T1 and ISDN technologies only) retrieves technolo...
Page 95 - Technology-Specific User Information
Global Call API for HMP on Windows Programming Guide — August 2006 95 Call Control The gc_Extension( ) function can also be used to transmit information to the remote endpoint. In this case, while the application at the local end point receives a GCEV_EXTENSIONCMPLT, the application at the remote en...
Page 97 - Alarm Handling; Alarm Handling Overview; Alarm Management System Components
Global Call API for HMP on Windows Programming Guide — August 2006 97 8 8. Alarm Handling This chapter describes the Global Call Alarm Management System (GCAMS). Topics include the following: • Alarm Handling Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ....
Page 99 - Operation and Configuration of GCAMS; Generation of Events for Blocking Alarms
Global Call API for HMP on Windows Programming Guide — August 2006 99 Alarm Handling responsible for starting and stopping the transmission of alarms and setting and getting alarm parameters, such as timing parameters. 8.2 Operation and Configuration of GCAMS The primary functions of GCAMS are as fo...
Page 100 - Generation of Alarm Events
100 Global Call API for HMP on Windows Programming Guide — August 2006 Alarm Handling The GCEV_BLOCKED and GCEV_DISCONNECTED events may arrive in any order. When the blocking condition(s) clears, an unsolicited GCEV_UNBLOCKED event is sent to the application indicating complete recovery from the blo...
Page 101 - Configuration of Alarm Properties and Characteristics
Global Call API for HMP on Windows Programming Guide — August 2006 101 Alarm Handling In addition, the alarm source object must meet the alarm flow configuration requirements, which are set using the gc_SetAlarmFlow( ) function or the gc_NotifyAll( ) function. (See Section 8.2.3, “Configuration of A...
Page 102 - Configuring Alarm Notification
102 Global Call API for HMP on Windows Programming Guide — August 2006 Alarm Handling network ASO ID. This define is useful in many contexts. For example, notification of all alarms on a line device can be configured using the call: gc_SetAlarmNotifyAll(..., ALARM_SOURCE_ID_NETWORK_ID, ...) The ALAR...
Page 103 - Alarm Configuration Tips
Global Call API for HMP on Windows Programming Guide — August 2006 103 Alarm Handling synchronization must be present before the ASO declares a loss of sync alarm or alarm handling mode. Use of the gc_SetAlarmParm( ) function, as well as the gc_GetAlarmParm( ) function, is highly alarm source object...
Page 104 - Starting and Stopping Alarm Transmission; Alarm Numbers and Names; Alarm Source Object IDs and Names
104 Global Call API for HMP on Windows Programming Guide — August 2006 Alarm Handling 8.2.4 Starting and Stopping Alarm Transmission Note: This section applies to E1, T1 and ISDN technologies only. GCAMS is automatically started when Global Call is started. However, to begin the transmission of alar...
Page 105 - Sample Alarm Scenarios
Global Call API for HMP on Windows Programming Guide — August 2006 105 Alarm Handling The following functions are used to retrieve ASO names and IDs and to convert them from one to the other: gc_AlarmSourceObjectID( ) retrieves the alarm source object ID, for a given event gc_AlarmSourceObjectIDToNa...
Page 107 - Scenario 2: Default Behavior for Alarm Notification
Global Call API for HMP on Windows Programming Guide — August 2006 107 Alarm Handling 8.3.2 Scenario 2: Default Behavior for Alarm Notification The default behavior is that the application is not notified of alarm events. See Figure 23. Figure 23. Default Behavior for Alarm Notification Application ...
Page 108 - Scenario 3: Alarm Transmission
108 Global Call API for HMP on Windows Programming Guide — August 2006 Alarm Handling 8.3.3 Scenario 3: Alarm Transmission Note: This scenario applies to E1, T1 and ISDN technologies only. Figure 24 shows a scenario that demonstrates the sequence of function calls and the actions that they cause in ...
Page 109 - Real Time Configuration Manager Overview
Global Call API for HMP on Windows Programming Guide — August 2006 109 9 9. Real Time Configuration Management This chapter describes the Global Call Real Time Configuration Manager (RTCM). Topics include the following: • Real Time Configuration Manager Overview . . . . . . . . . . . . . . . . . . ....
Page 110 - RTCM Components
110 Global Call API for HMP on Windows Programming Guide — August 2006 Real Time Configuration Management • Troubleshooting software and hardware • Performance tuning • Dynamic alteration of a target object’s behavior based upon past behavior • Generation of status reports • Dynamic configuration of...
Page 111 - Customer Application Using Global Call RTCM
Global Call API for HMP on Windows Programming Guide — August 2006 111 Real Time Configuration Management 9.2.1 Customer Application Using Global Call RTCM The customer application interfaces with the Global Call RTCM Manager via Global Call RTCM API functions. The primary function of an application...
Page 112 - RTCM Parameters; Using RTCM Parameters
112 Global Call API for HMP on Windows Programming Guide — August 2006 Real Time Configuration Management the target object is located. The customer application must ensure that the target object and requested parameters match. 9.2.3 RTCM Parameters The third component of the RTCM feature are the RT...
Page 113 - Parameter Dependencies
Global Call API for HMP on Windows Programming Guide — August 2006 113 Real Time Configuration Management parameter IDs are only guaranteed to be unique within a given set ID. Note that some configurable parameters are defined only for a specific software module, while others may be used across diff...
Page 114 - Getting and Setting Parameter Information; Control Parameters
114 Global Call API for HMP on Windows Programming Guide — August 2006 Real Time Configuration Management 9.4 Getting and Setting Parameter Information The Global Call RTCM feature supports the retrieval (E1, T1 and ISDN technologies only) or updating (all technologies) of multiple parameters of the...
Page 115 - Programming Mode
Global Call API for HMP on Windows Programming Guide — August 2006 115 Real Time Configuration Management • the update condition; that is, whether the update should occur either at the Null call state or immediately when updating the parameters of a target object with an active call. (This parameter...
Page 116 - Timeout Option
116 Global Call API for HMP on Windows Programming Guide — August 2006 Real Time Configuration Management gc_SetConfigData( ) (all technologies) Asynchronous Mode: The Global Call application receives the GCEV_SETCONFIGDATA event if all the requested parameters in a given target object are successfu...
Page 117 - Handling RTCM Errors; Configuration Procedure
Global Call API for HMP on Windows Programming Guide — August 2006 117 Real Time Configuration Management The gc_ResetLineDev( ) function is used to speed the update of the parameters that are waiting for the arrival of the Null state. For example, the customer application can call the gc_SetConfigD...
Page 118 - Sample Scenarios Using the RTCM API Functions
118 Global Call API for HMP on Windows Programming Guide — August 2006 Real Time Configuration Management Figure 26. Run Time Configuration Procedure Note: In Figure 26, for IP technology, only the gc_SetConfigData( ) function is supported for changing the parameter values of a board device. See Sec...
Page 123 - Setting Line Device Configuration in Asynchronous Mode
Global Call API for HMP on Windows Programming Guide — August 2006 123 Real Time Configuration Management 9.7.4 Setting Line Device Configuration in Asynchronous Mode Note: This section applies to E1, T1 and ISDN technologies only. The Global Call RTCM allows the customer application to retrieve or ...
Page 127 - Handling Service Requests; Service Request Overview
Global Call API for HMP on Windows Programming Guide — August 2006 127 10 10. Handling Service Requests This chapter describes the Global Call Service Request (GCSR) feature. Topics include the following: • Service Request Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ...
Page 128 - Service Request Components
128 Global Call API for HMP on Windows Programming Guide — August 2006 Handling Service Requests Figure 32. Service Request Architecture 10.2 Service Request Components Using the Global Call Service Request (GCSR) feature involves the following API components: gc_ReqService( ) function to make a req...
Page 129 - Service Request Data; General Service Request Scenario
Global Call API for HMP on Windows Programming Guide — August 2006 129 Handling Service Requests 10.3 Service Request Data All information transmitted and received using the Service Request feature is done using the generic GC_PARM_BLK data structure. Three parameter IDs, under the GCSET_SERVREQ set...
Page 131 - Using Global Call to Implement; Introduction to Call Transfer; Blind Call Transfer
Global Call API for HMP on Windows Programming Guide — August 2006 131 11 11. Using Global Call to Implement Call Transfer The information in this chapter is technology independent, however it describes a method of call transfer that is supported by IP technology only . For more specific information...
Page 132 - Supervised Call Transfer; Call Transfer State Machine
132 Global Call API for HMP on Windows Programming Guide — August 2006 Using Global Call to Implement Call Transfer Figure 34. Blind Call Transfer (Unsupervised Transfer) 11.1.2 Supervised Call Transfer In a supervised call transfer scenario, party A transfers the call between A and B (Call 1) to a ...
Page 139 - Building Applications; Compiling and Linking; Include Files; Required Libraries
Global Call API for HMP on Windows Programming Guide — August 2006 139 12 12. Building Applications This chapter provides general information for build applications that use the Global Call software. For additional technology-specific information, refer to the appropriate Global Call Technology Guid...
Page 140 - Variables for Compiling and Linking Commands
140 Global Call API for HMP on Windows Programming Guide — August 2006 Building Applications 12.1.3 Variables for Compiling and Linking Commands The following variables provide a standardized way of referencing the directories that contain header files and shared objects: INTEL_DIALOGIC_INC Variable...
Page 141 - Debugging
Global Call API for HMP on Windows Programming Guide — August 2006 141 13 13. Debugging This chapter provides references to other documents that provide detailed information for debugging applications that use Global Call. For general Global Call debugging information, see the “Runtime Trace Facilit...
Page 151 - Index
Global Call API for HMP on Windows Programming Guide — August 2006 151 Index A abandoned calls 47 alarm flow 102 alarm handling 97 alarm source objects 97 ALARM_SOURCE_ID_NETWORK_ID usage 101 alarms 97 blocking 99GCEV_UNBLOCKED event 99non-blocking 99recovery 99 application-handler thread, Windows 7...