![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Major version number. |
|
Minor version number. |
|
Build number. |
The standard e32 error codes can be found in the topic System error codes.
etel.h
-2000 |
The client is not the call owner and has attempted to perform an operation that requires ownership. |
|
-2001 |
An attempt has been made to load an ETel (TSY) module which contains a phone with the same name as one already loaded. |
|
-2002 |
An attempt has been made to acquire call ownership when the requesting client is already the call owner. |
|
-2003 |
A connection has been terminated because the carrier has been lost. |
|
-2004 |
An attempt to establish a connection with the RCall::Dial() function has failed because the remote partys line was busy. |
|
-2005 |
An attempt has been made to transfer call ownership, but no other clients are interested in acquiring ownership. |
|
-2006 |
The TSY has failed to initialise the modem. This may be occur if the modem is disconnected during initialisation, or if an attempt is made to initialise an unsupported modem. |
|
-2007 |
An attempt has been made to perform an operation which requires the call to be connected when the call is not connected. E.g. RCall:LoanDataPort(). |
|
-2008 |
A connection request has failed because there is no answer. |
|
-2009 |
A connection request has failed because there is no dial tone. For example, if there is no connection between the modem and the network. |
|
-2010 |
An attempt to configure the port has failed because the hardware cannot match the desired configuration. For example, if an attempt is made to configure the comms port to a baud rate it cannot support. |
|
-2011 |
Out of memory error global chunk cannot be created. |
|
-2012 |
The client is not the fax owner and has attempted to perform an operation that requires fax ownership. The fax client should be used to access fax functionality. Consequently, client code should not return this error. |
|
-2013 |
An attempt has been made to perform an operation which requires port ownership. However, the client does not own the port. |
|
-2014 |
An operation has failed because the modem has been incorrectly configured. |
|
-2015 |
An operation has failed because the modem does not understand the request possible bug in modem. |
|
-2016 |
The call has already placed an answer incoming call request. Only 1 request of a type (e.g. fax, voice, data) can be outstanding on the server at a time. |
|
-2017 |
An attempt to establish a connection with the modem has failed because the modem cannot be detected. |
|
-2018 |
Operation failed because the modem settings are corrupt. |
ETel panics are caused by incorrect use of the client-side API e.g. passing bad or contradictory values to class constructors or member functions.
The client thread causing the panic is terminated.
etelext.h
The subsession handle is not recognised by the server. |
|
An attempt to read or write across the client-server boundary has failed. This usually indicates that the descriptor sent is incorrectly formatted. |
|
The message type sent by the client is not recognised by the server. |
|
Client code has attempted to re-post an asynchronous request before the original request has completed. |
|
The client has attempted to open a subsession without first opening its parent object. |
|
Not used. |
|
The size field of a descriptor indicates that it contains a negative amount of data. |
|
Not used. |
|
Client failed to call Open(). |
|
Not used. |
|
Client code request to access an element outside the array range. |
|
The Open() function has been called twice by the same subsession. |
|
Not used. |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |