Panic caused by incorrect use of the ETel Core API- e.g.
passing bad or contradictory values to class constructors or member functions.
The client thread causing the panic is terminated.
0
|
The subsession handle is not recognised by the server.
|
1
|
An attempt to read or write across the client-server boundary
has failed. This usually indicates that the descriptor sent is incorrectly
formatted.
|
2
|
The message type- sent by the client- is not
recognised by the server.
|
3
|
Client code has attempted to re-post an asynchronous request
before the original request has completed.
|
4
|
The client has attempted to open a sub-session without first
opening its parent object.
|
5
|
The client has attempted to use a zero length
descriptor.
|
6
|
The size field of a descriptor indicates that it contains a
negative amount of data.
|
7
|
Not used.
|
8
|
Client failed to call Open() .
|
9
|
Client failed to call Open() .
|
10
|
Client code request to access an element outside the array
range.
|
11
|
The Open() function has been called twice by the
same sub-session.
|
12
|
The client has passed a bad phone call type.
|
13
|
The client has specified a bad name for a phone line or phone
call object.
|
|