1 <h1>Etel Server</h1>

     2 <p>Panic caused by incorrect use of the ETel Core API- e.g.

     3 passing bad or contradictory values to class constructors or member functions.</p>

     4 <p>The client thread causing the panic is terminated.</p>

     5 <code>0</code>

     6 <p>The subsession handle is not recognised by the server.</p>

     7 <code>1</code>

     8 <p>An attempt to read or write across the client-server boundary

     9 has failed. This usually indicates that the descriptor sent is incorrectly

    10 formatted.</p>

    11 <code>2</code>

    12 <p>The message type- sent by the client- is not recognised by the server.</p>

    13 <code>3</code>

    14 <p>Client code has attempted to re-post an asynchronous request

    15 before the original request has completed.</p>

    16 <code>4</code>

    17 <p>The client has attempted to open a sub-session without first

    18 opening its parent object. </p>

    19 <code>5</code>

    20 <p>The client has attempted to use a zero length

    21 descriptor.</p>

    22 <code>6</code>

    23 <p>The size field of a descriptor indicates that it contains a

    24 negative amount of data.</p>

    25 <code>7</code>

    26 <p>Not used.</p>

    27 <code>8</code>

    28 <p>Client failed to call <code>Open()</code>.</p>

    29 <code>9</code>

    30 <p>Client failed to call <code>Open()</code>.</p>

    31 <code>10</code>

    32 <p>Client code request to access an element outside the array

    33 range.</p>

    34 <code>11</code>

    35 <p>The <code>Open()</code> function has been called twice by the

    36 same sub-session.</p>

    37 <code>12</code>

    38 <p>The client has passed a bad phone call type.</p>

    39 <code>13</code>

    40 <p>The client has specified a bad name for a phone line or phone

    41 call object.</p>

    42