<div class="content"><p> </p><p>The <b>FaxObs_StartClientServer (Opnum 29)</b> method is
called by the client to register itself to receive notifications of fax events
from the server.</p><p>On success, the server MUST start notifying the client about
the occurring fax events.</p><p>If the server receives a <b>FaxObs_StartClientServer</b>
request for a client machine name and client name that are already registered
to receive fax event notifications with a previously executed <b>FaxObs_StartClientServer</b>
call, the fax server MUST consider the new request a success and keep the
existing fax client registration.</p><p>To notify the client about a fax event, the server MUST
first open a connection with the client by calling the <b>FAX_OpenConnection</b> (section
<span><a href="6a8d8440-25a7-49aa-a4a1-7043b040dde4" data-linktype="relative-path">3.2.4.5</a></span>)
method. Then the fax server MUST notify the client by calling the <b>FAX_ClientEventQueue</b> (section
<span><a href="c123443a-b672-4bce-ad30-50d2eb4d6cf9" data-linktype="relative-path">3.2.4.2</a></span>)
method. Finally, the server SHOULD close the connection with the client by
calling the <b>FAX_CloseConnection</b> (section <span><a href="71fcdc39-0e2a-4025-96f8-f96d81d8694b" data-linktype="relative-path">3.2.4.4</a></span>) method. <a id="Appendix_A_Target_213"></a><a aria-label="Product behavior note 213" href="056171e7-80bc-45ff-8107-66ba3abb2023#Appendix_A_213" data-linktype="relative-path">&lt;213&gt;</a></p><dl>
<dd>
<div><pre> error_status_t FaxObs_StartClientServer(
   [in] handle_t hBinding,
   [in, string, unique] LPCWSTR MachineName,
   [in, string, unique] LPCWSTR ClientName,
   [in] ULONG64 Context
 );
</pre></div>
</dd></dl><p><b>hBinding: </b>A handle that is provided by the
client <span><a href="46aba9c4-ebb1-4b10-86ac-4bb3025657b9#gt_8a7f6700-8311-45bc-af10-82e10accd331" data-linktype="relative-path">RPC</a></span> layer when the
RPC call is made.</p><p><b>MachineName: </b>A pointer to a null-terminated
character string containing the name of the fax client machine. The machine
name MUST be NULL for a local machine and a <span><a href="46aba9c4-ebb1-4b10-86ac-4bb3025657b9#gt_1769aec9-237e-44ed-9014-1abb3ec6de6e" data-linktype="relative-path">fully qualified domain name
(FQDN)</a></span> for a remote machine.</p><p><b>ClientName: </b>A pointer to a null-terminated
character string containing the friendly name of the fax client application.
This name MUST be unique for each fax client application running on the same
fax client machine.</p><p><b>Context: </b>A <b>ULONG64</b> (<span><a href="../ms-dtyp/cca27429-5689-4a16-b2b4-9325d93e4ba2" data-linktype="relative-path">[MS-DTYP]</a></span>
section <span><a href="../ms-dtyp/2dc4c492-95db-4fa6-ae2b-8546b13c9141" data-linktype="relative-path">2.2.54</a></span>)
value that can be passed to <b>FAX_OpenConnection</b> as a notification
context. This context is equivalent to the subscription context used in the Fax
Server Interface methods <b>FAX_StartServerNotification</b> (section <span><a href="693ea4ae-60cd-4043-b775-1a1f19920cbb" data-linktype="relative-path">3.1.4.1.100</a></span>),
<b>FAX_StartServerNotificationEx</b> (section <span><a href="b73163aa-5f4b-45b3-9c5b-f95077f103c2" data-linktype="relative-path">3.1.4.1.101</a></span>), and <b>FAX_StartServerNotificationEx2</b> (section
<span><a href="55770fa2-8c93-40c1-a56e-2c17e8ff707b" data-linktype="relative-path">3.1.4.1.102</a></span>),
with the difference that the <b>FaxObs Server Interface</b> (section <span><a href="1c8fe732-62a3-45b2-9190-7f6e76f89cae" data-linktype="relative-path">3.1.4.2</a></span>)
does not have a method similar to <b>FAX_EndServerNotification</b> (section
<span><a href="59663586-4f1a-4f10-a548-c9b088995028" data-linktype="relative-path">3.1.4.1.17</a></span>)
that the client calls to close this context.</p><p><b>Return Values: </b>This method MUST return
0x00000000 (ERROR_SUCCESS) for success; otherwise, it MUST return the following
error code, one of the fax-specific errors that are defined in section <span><a href="cbe6c4fb-4dda-4f6c-9701-0d490ba0d105" data-linktype="relative-path">2.2.52</a></span>,
or one of the other standard errors defined in <span><a href="../ms-erref/1bc92ddf-b79e-413c-bbaa-99a5281a6c90" data-linktype="relative-path">[MS-ERREF]</a></span>
section <span><a href="../ms-erref/18d8fbe8-a967-4f1c-ae50-99ca8e491d2d" data-linktype="relative-path">2.2</a></span>.</p><dl>
<dd>
<table><thead>
  <tr>
   <th>
   <p>Return value/code</p>
   </th>
   <th>
   <p>Description</p>
   </th>
  </tr>
 </thead><tbody><tr>
  <td>
  <p>ERROR_NOT_ENOUGH_MEMORY</p>
  <p>0x00000008</p>
  </td>
  <td>
  <p>The fax server cannot allocate memory necessary for
  the fax client connection.</p>
  </td>
 </tr></tbody></table>
</dd></dl><p><b>Exceptions Thrown:</b> No exceptions are thrown
except those that are thrown by the underlying RPC protocol, <span><a href="../ms-rpce/290c38b1-92fe-4229-91e6-4fc376610c15" data-linktype="relative-path">[MS-RPCE]</a></span>.</p></div>