#include <calloutgoing.h>
Inheritance diagram for CallOutgoing:
Public Member Functions | |
CallOutgoing (Capi *capi, _cdword controller, string call_from, string call_to, Connection::service_t service, int timeout, string faxStationID, string faxHeadline, bool clir) | |
Constructor. Create object. | |
void | mainLoop () throw (CapiExternalError, CapiMsgError) |
Initiate connection, wait for it to succeed. | |
void | callConnected () |
Finish if we got connection. | |
void | alerting () |
activate the timeout in the moment the other party starts getting alerted | |
Connection * | getConnection () |
return reference to the established connection | |
int | getResult () |
return result of connection establishment | |
Private Attributes | |
Connection::service_t | service |
service with which we should connect | |
string | call_from |
CallingPartyNumber. | |
string | call_to |
CalledPartyNumber. | |
string | faxStationID |
fax Station ID to use | |
string | faxHeadline |
fax headlint to use | |
Capi * | capi |
reference to object of Capi to use | |
_cdword | controller |
controller to use | |
bool | clir |
enable CLIR? (don't show own number to called party) | |
int | result |
result of the call establishment process (0=success, 1=timeout exceeded, 2=aborted w/o reason, 0x3301-0x34FF=CAPI errors) | |
int | saved_timeout |
we'll save the given timeout for later as first phase (wait for alerting) doesn't need timeout |
This module serves to initiate an outgoing call and wait for the connection establishment. The module can finish for three reasons:
The timeout will be counted from the moment the other party is alerted, not from the moment we initiate the call!
You can get the reason for exiting with getResult().
|
Constructor. Create object.
|
|
activate the timeout in the moment the other party starts getting alerted
Reimplemented from CallModule.
|
|
Finish if we got connection.
Reimplemented from CallModule.
|
|
return reference to the established connection
|
|
return result of connection establishment 0: connection is up, call was successful 1: call timeout exceeded 2: connection not successful, no reason available 0x3301-0x34FF: connection not successful, reason given in CAPI coding. See CAPI spec for details.
|
|
Initiate connection, wait for it to succeed. This call module does never throw CapiWrongState! see getResult() if you need to know if conneciton succeeded.
Reimplemented from CallModule.
|
|
CallingPartyNumber.
|
|
CalledPartyNumber.
|
|
reference to object of Capi to use
|
|
enable CLIR? (don't show own number to called party)
|
|
controller to use
|
|
fax headlint to use
|
|
fax Station ID to use
|
|
result of the call establishment process (0=success, 1=timeout exceeded, 2=aborted w/o reason, 0x3301-0x34FF=CAPI errors)
|
|
we'll save the given timeout for later as first phase (wait for alerting) doesn't need timeout
|
|
service with which we should connect
|