<div class="content" name="SetCallQualityOfService" uuid="5bca39b0-6693-4180-833f-99426cf617a9"><p>The SetCallQualityOfService packet is transmitted from a
TAPI <a href="489de77f-16d8-4c4f-939a-f795e8b42893#gt_60e0e1fa-66fe-41e1-b5e3-ceab97e53506" data-linktype="relative-path">client</a> to a TAPI <a href="489de77f-16d8-4c4f-939a-f795e8b42893#gt_434b0234-e970-4e8c-bdfa-e16a30d96703" data-linktype="relative-path">server</a> in a <a href="489de77f-16d8-4c4f-939a-f795e8b42893#gt_8a7f6700-8311-45bc-af10-82e10accd331" data-linktype="relative-path">remote procedure call</a>.
Sending this packet MUST allow a change to the quality of service parameters
(reserved capacity and performance guarantees) for an existing call. Except for
basic parameter validation, this is a straight pass-through to a service
provider.</p><table>
 <tbody><tr>
  <th><p><br/>0</p></th>
  <th><p><br/>1</p></th>
  <th><p><br/>2</p></th>
  <th><p><br/>3</p></th>
  <th><p><br/>4</p></th>
  <th><p><br/>5</p></th>
  <th><p><br/>6</p></th>
  <th><p><br/>7</p></th>
  <th><p><br/>8</p></th>
  <th><p><br/>9</p></th>
  <th><p>1<br/>0</p></th>
  <th><p><br/>1</p></th>
  <th><p><br/>2</p></th>
  <th><p><br/>3</p></th>
  <th><p><br/>4</p></th>
  <th><p><br/>5</p></th>
  <th><p><br/>6</p></th>
  <th><p><br/>7</p></th>
  <th><p><br/>8</p></th>
  <th><p><br/>9</p></th>
  <th><p>2<br/>0</p></th>
  <th><p><br/>1</p></th>
  <th><p><br/>2</p></th>
  <th><p><br/>3</p></th>
  <th><p><br/>4</p></th>
  <th><p><br/>5</p></th>
  <th><p><br/>6</p></th>
  <th><p><br/>7</p></th>
  <th><p><br/>8</p></th>
  <th><p><br/>9</p></th>
  <th><p>3<br/>0</p></th>
  <th><p><br/>1</p></th>
 </tr>
 <tr>
  <td colspan="32">Req_Func</td>
 </tr>
 <tr>
  <td colspan="32">Reserved1</td>
 </tr>
 <tr>
  <td colspan="32">dwRequestID</td>
 </tr>
 <tr>
  <td colspan="32">hCall</td>
 </tr>
 <tr>
  <td colspan="32">lpSendingFlowspec</td>
 </tr>
 <tr>
  <td colspan="32">dwSendingFlowspecSize</td>
 </tr>
 <tr>
  <td colspan="32">lpReceivingFlowspec</td>
 </tr>
 <tr>
  <td colspan="32">dwReceivingFlowspecSize</td>
 </tr>
 <tr>
  <td colspan="32">Reserved2</td>
 </tr>
 <tr>
  <td colspan="32">Reserved3</td>
 </tr>
 <tr>
  <td colspan="32">Reserved4</td>
 </tr>
 <tr>
  <td colspan="32">Reserved5</td>
 </tr>
 <tr>
  <td colspan="32">Reserved6</td>
 </tr>
 <tr>
  <td colspan="32">Reserved7</td>
 </tr>
 <tr>
  <td colspan="32">Reserved8</td>
 </tr>
 <tr>
  <td colspan="32">VarData (32 bytes)</td>
 </tr>
 <tr>
  <td colspan="32">...</td>
 </tr>
 <tr>
  <td colspan="32">...</td>
 </tr>
</tbody></table><p><b>Req_Func (4 bytes): </b>An unsigned 32-bit
integer. The identifier of the function that will be invoked on the remote
server. This value MUST be set to 74. </p><dl>
<dd>
<p><b>Return Values</b></p>
</dd>
<dd>
<p>On completion of <a href="c28c36d0-579b-4e20-a100-f4e71012d5f8" data-linktype="relative-path">ClientRequest</a>, this field
MUST contain the result of the encapsulated telephony request. A nonzero
request ID value indicates that the request is in progress and will complete
asynchronously, and a <a href="e0e8af90-24f1-4dbc-8d4e-01b8e4e7cb53" data-linktype="relative-path">LINEERR_Constants</a>
value indicates synchronous failure.</p>
</dd>
<dd>
<p>Returns a positive request identifier if the
asynchronous operation starts; otherwise, the function MUST return one of these
negative error values:</p>
</dd>
<dd>
<table><thead>
  <tr>
   <th>
   <p>Name</p>
   </th>
   <th>
   <p>Value</p>
   </th>
  </tr>
 </thead><tbody><tr>
  <td>LINEERR_INVALCALLHANDLE</td>
  <td>0x80000018</td>
 </tr><tr>
  <td>LINEERR_INVALCALLSTATE</td>
  <td>0x8000001C</td>
 </tr><tr>
  <td>LINEERR_INVALPARAM</td>
  <td>0x80000032</td>
 </tr><tr>
  <td>LINEERR_INVALPOINTER</td>
  <td>0x80000035</td>
 </tr><tr>
  <td>LINEERR_INVALRATE</td>
  <td>0x80000037</td>
 </tr><tr>
  <td>LINEERR_NOMEM</td>
  <td>0x80000044</td>
 </tr><tr>
  <td>LINEERR_NOTOWNER</td>
  <td>0x80000046</td>
 </tr><tr>
  <td>LINEERR_OPERATIONUNAVAIL</td>
  <td>0x80000049</td>
 </tr><tr>
  <td>LINEERR_OPERATIONFAILED</td>
  <td>0x80000048</td>
 </tr><tr>
  <td>LINEERR_RATEUNAVAIL</td>
  <td>0x8000004A</td>
 </tr><tr>
  <td>LINEERR_RESOURCEUNAVAIL</td>
  <td>0x8000004B</td>
 </tr><tr>
  <td>LINEERR_UNINITIALIZED</td>
  <td>0x80000050</td>
 </tr></tbody></table>
</dd></dl><p><b>Reserved1 (4 bytes): </b>An unsigned 32-bit
integer. MUST be set to zero when sent and MUST be ignored on receipt. </p><p><b>dwRequestID (4 bytes): </b>An unsigned 32-bit
integer. The identifier of the asynchronous request. </p><dl>
<dd>
<table><thead>
  <tr>
   <th>
   <p>Value</p>
   </th>
   <th>
   <p>Meaning</p>
   </th>
  </tr>
 </thead><tbody><tr>
  <td>0x00000000</td>
  <td>The server MUST generate a unique positive request ID to return as the Ack_ReturnValue.</td>
 </tr><tr>
  <td>0x00000001 — 0x7FFFFFFF</td>
  <td>The server MUST use this value instead of generating a unique positive request ID.</td>
 </tr></tbody></table>
</dd></dl><p><b>hCall (4 bytes): </b>An <a href="7f4089a0-7432-4ef0-8eeb-5aafe407c07e" data-linktype="relative-path">HCALL</a>. The handle to the
call. One way of obtaining a valid hCall is by sending the <a href="c9acdfde-22de-43ff-b491-23a9ed72fb31" data-linktype="relative-path">MakeCall</a> packet. Also a
valid hCall can be obtained from <a href="0a8905e3-647f-4e98-aca8-2fa77eedb2e7" data-linktype="relative-path">LINE_CALLSTATE</a> packet sent
by the remote server. The application MUST have OWNER privilege. </p><p><b>lpSendingFlowspec (4 bytes): </b>An unsigned
32-bit integer. The offset, in bytes, in the VarData field of a WinSock2 <a href="b0353f6f-b187-4357-9b89-e4233f3e9a4b" data-linktype="relative-path">FLOWSPEC</a> packet that is
followed by provider-specific data. </p><p><b>dwSendingFlowspecSize (4 bytes): </b>An unsigned
32-bit integer. The total size, in bytes, of the FLOWSPEC packet and
accompanying provider-specific data. This is equivalent to what would have been
stored in SendingFlowspec in a QoS packet. </p><p><b>lpReceivingFlowspec (4 bytes): </b>An unsigned
32-bit integer. The offset, in bytes, in the VarData field of a WinSock2
FLOWSPEC packet, followed by provider-specific data. </p><p><b>dwReceivingFlowspecSize (4 bytes): </b>An unsigned
32-bit integer. The total size, in bytes, of the FLOWSPEC and accompanying
provider-specific data. This is equivalent to what would have been stored in
ReceivingFlowspec in a QoS packet.</p><p><b>Reserved2 (4 bytes): </b>An unsigned 32-bit
integer. This field is used for padding and MUST be ignored on receipt. It can
be any value.</p><p><b>Reserved3 (4 bytes): </b>An unsigned 32-bit
integer. This field is used for padding and MUST be ignored on receipt. It can
be any value.</p><p><b>Reserved4 (4 bytes): </b>An unsigned 32-bit integer.
This field is used for padding and MUST be ignored on receipt. It can be any
value.</p><p><b>Reserved5 (4 bytes): </b>An unsigned 32-bit
integer. This field is used for padding and MUST be ignored on receipt. It can
be any value.</p><p><b>Reserved6 (4 bytes): </b>An unsigned 32-bit
integer. This field is used for padding and MUST be ignored on receipt. It can
be any value.</p><p><b>Reserved7 (4 bytes): </b>An unsigned 32-bit
integer. This field is used for padding and MUST be ignored on receipt. It can
be any value.</p><p><b>Reserved8 (4 bytes): </b>An unsigned 32-bit
integer. This field is used for padding and MUST be ignored on receipt. It can
be any value.</p><p><b>VarData (32 bytes): </b>MUST Contain a WinSock2
FLOWSPEC packet that is followed by provider-specific data that is indicated in
the lpSendingFlowspec field; and a WinSock2 FLOWSPEC packet that is followed by
the provider-specific data that is indicated by the lpReceivingFlowspec field.</p><dl>
<dd>
<p>The contents of this field are DWORD-aligned.</p>
</dd></dl></div>