?? constnts_90j7.htm
字號:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML DIR="LTR"><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=iso8859-1">
</HEAD>
<TITLE>LINEDISCONNECTMODE_ Constants</TITLE>
<SCRIPT SRC="/library/psdk/linkcss.js"></SCRIPT>
<META NAME="MS-HKWD" CONTENT="LINEDISCONNECTMODE_ Constants">
<META NAME="MS-HAID" CONTENT="_tapi2_linedisconnectmode__constants">
</HEAD>
<BODY TOPMARGIN="0">
<!--TOOLBAR_START-->
<!--TOOLBAR_EXEMPT-->
<!--TOOLBAR_END-->
<!--SYNC_START-->
<script language="JavaScript" src='/library/synch.js'></script>
<!--SYNC_END-->
<H1><A NAME="_tapi2_linedisconnectmode__constants"></A>LINEDISCONNECTMODE_ Constants</H1>
<P>The LINEDISCONNECTMODE_ bit-flag constants describe different reasons for a remote disconnect request. A disconnect mode is available as call status to the application after the call state transitions to <I>disconnected</I>.
<DL>
<DT>LINEDISCONNECTMODE_BADADDRESS </DT>
<DD>The destination address is invalid. </DD>
<DT>LINEDISCONNECTMODE_BLOCKED </DT>
<DD>The call could not be connected because calls from the origination address are not being accepted at the destination address. This differs from LINEDISCONNECTMODE_REJECT in that blocking is implemented in the network (a passive reject) while a rejection is implemented in the destination equipment (an active reject). The blocking can be due to a specific exclusion of the origination address, or because the destination accepts calls from only a selected set of origination address (closed user group). (TAPI versions 2.0 and later)
<P>LINEDISCONNECTMODE_BLOCKED is appropriate as a <I>blacklisted</I> response. For example, a modem has received an answer, gone more than six seconds without detecting Ringback, failed to connect a defined number of times, determines that the phone number is not valid to call, and issues a 'blacklisted' response.
</DD>
<DT>LINEDISCONNECTMODE_BUSY </DT>
<DD>The remote user's station is busy. </DD>
<DT>LINEDISCONNECTMODE_CANCELLED</DT>
<DD>The call was cancelled. (TAPI versions 2.0 and later)</DD>
<DT>LINEDISCONNECTMODE_CONGESTION </DT>
<DD>The network is congested. </DD>
<DT>LINEDISCONNECTMODE_DONOTDISTURB </DT>
<DD>The call could not be connected because the destination has invoked the Do Not Disturb feature. (TAPI versions 2.0 and later)</DD>
<DT>LINEDISCONNECTMODE_FORWARDED </DT>
<DD>The call was forwarded by the switch. </DD>
<DT>LINEDISCONNECTMODE_INCOMPATIBLE </DT>
<DD>The remote user's station equipment is incompatible with the type of call requested. </DD>
<DT>LINEDISCONNECTMODE_NOANSWER </DT>
<DD>The remote user's station does not answer. </DD>
<DT>LINEDISCONNECTMODE_NODIALTONE </DT>
<DD>A dial tone was not detected within a service-provider defined timeout, at a point during dialing when one was expected (such as at a "W" in the dialable string). This can also occur without a service-provider-defined timeout period or without a value specified in the <B>dwWaitForDialTone</B> member of the <A HREF="struc2_30xe.htm" tppabs="http://msdn.microsoft.com/library/psdk/tapi22/struc2_30xe.htm"><B>LINEDIALPARAMS</B></A> structure. (TAPI versions 1.4 and later)</DD>
<DT>LINEDISCONNECTMODE_NORMAL </DT>
<DD>This is a normal disconnect request by the remote party. The call was terminated normally. </DD>
<DT>LINEDISCONNECTMODE_NUMBERCHANGED </DT>
<DD>The call could not be connected because the destination number has been changed, but automatic redirection to the new number is not provided. (TAPI versions 2.0 and later)</DD>
<DT>LINEDISCONNECTMODE_OUTOFORDER </DT>
<DD>The call could not be connected or was disconnected because the destination device is out of order (hardware failure). (TAPI versions 2.0 and later)</DD>
<DT>LINEDISCONNECTMODE_PICKUP </DT>
<DD>The call was picked up from elsewhere. </DD>
<DT>LINEDISCONNECTMODE_QOSUNAVAIL </DT>
<DD>The call could not be connected or was disconnected because the minimum quality of service could not be obtained or sustained. This differs from LINEDISCONNECTMODE_INCOMPATIBLE in that the lack of resources may be a temporary condition at the destination. (TAPI versions 2.0 and later)</DD>
<DT>LINEDISCONNECTMODE_REJECT </DT>
<DD>The remote user has rejected the call. </DD>
<DT>LINEDISCONNECTMODE_TEMPFAILURE </DT>
<DD>The call could not be connected or was disconnected because of a temporary failure in the network; the call can be reattempted later and is expected to eventually complete. (TAPI versions 2.0 and later)
<P>LINEDISCONNECTMODE_TEMPFAILURE is appropriate as a <I>delayed</I> response. For example, a modem getting a busy signal or equivalent too many times in a particular time period concludes that the number should not be called again until a defined time has elapsed and issues a 'delayed' response.
</DD>
<DT>LINEDISCONNECTMODE_UNAVAIL </DT>
<DD>The reason for the disconnect is unavailable and will not become known later. </DD>
<DT>LINEDISCONNECTMODE_UNKNOWN </DT>
<DD>The reason for the disconnect request is unknown but may become known later. </DD>
<DT>LINEDISCONNECTMODE_UNREACHABLE </DT>
<DD>The remote user could not be reached.
</DD>
</DL>
<P>The high-order 16 bits can be assigned for device-specific extensions. The low-order 16 bits are reserved. </P>
<P>A remote disconnect request for a given call results in the call state transitioning to the <I>disconnected</I> state and a <A HREF="msgs_1xid.htm" tppabs="http://msdn.microsoft.com/library/psdk/tapi22/msgs_1xid.htm">LINE_CALLSTATE</A> message is sent to the application. The LINEDISCONNECTMODE_ information provides details about the remote disconnect request. It is available in the call's <A HREF="struc1_7vxu.htm" tppabs="http://msdn.microsoft.com/library/psdk/tapi22/struc1_7vxu.htm"><B>LINECALLSTATUS</B></A> structure when the call is in the <I>disconnected</I> state. While a call is in this state, the application is still allowed to query the call's information and status. For example, user-user information that is received as part of the remote disconnect is available then. The application can clear a <I>disconnected</I> call by dropping the call. </P>
<P>For backward compatibility, it is the responsibility of the service provider to examine the negotiated API version on the line, and to not use this LINEDISCONNECTMODE_ value if it is not supported on the negotiated version (LINEDISCONNECTMODE_NORMAL or _UNKNOWN could be used instead). </P>
<H4><A HREF="javascript:if(confirm('http://msdn.microsoft.com/library/psdk/sdkintro/guide_927n.htm \n\n這個文件不能通過 Teleport Pro 取回, 因為 地址在一個域或為它的開始地址設定的邊界的外部路徑上. \n\n你想從服務器打開它嗎?'))window.location='http://msdn.microsoft.com/library/psdk/sdkintro/guide_927n.htm'" tppabs="http://msdn.microsoft.com/library/psdk/sdkintro/guide_927n.htm">Requirements</A> </H4>
<P><B> Windows NT/2000: </B>Requires Windows NT 4.0 SP3 or later.<BR>
<B> Windows 95/98: </B>Requires Windows 95 or later.<BR>
<B> Version: </B>Requires TAPI 2.0 or later.<BR>
<B> Header: </B>Declared in Tapi.h.</P>
<H4>See Also</H4>
<P><A HREF="msgs_1xid.htm" tppabs="http://msdn.microsoft.com/library/psdk/tapi22/msgs_1xid.htm">LINE_CALLSTATE</A>, <A HREF="struc1_7vxu.htm" tppabs="http://msdn.microsoft.com/library/psdk/tapi22/struc1_7vxu.htm"><B>LINECALLSTATUS</B></A>, <A HREF="struc2_30xe.htm" tppabs="http://msdn.microsoft.com/library/psdk/tapi22/struc2_30xe.htm"><B>LINEDIALPARAMS</B></A> </P>
<DIV CLASS="footer">Built on Monday, August 14, 2000</DIV>
<!--FOOTER_START-->
<DIV CLASS="footer" STYLE="color:#000000;font-size:90%;">
<A HREF="mailto:sdkfdbk@microsoft.com">Send feedback</A> to the Platform SDK.</P>
<P><A HREF="javascript:if(confirm('http://msdn.microsoft.com/isapi/gomscom.asp?TARGET=/info/cpyright.htm \n\n這個文件不能通過 Teleport Pro 取回, 因為 地址在一個域或為它的開始地址設定的邊界的外部路徑上. \n\n你想從服務器打開它嗎?'))window.location='http://msdn.microsoft.com/isapi/gomscom.asp?TARGET=/info/cpyright.htm'" tppabs="http://msdn.microsoft.com/isapi/gomscom.asp?TARGET=/info/cpyright.htm" TARGET="_top">© 1999 Microsoft Corporation. All rights reserved. Terms of use.</A></P>
</DIV>
<!--FOOTER_END-->
</BODY>
</HTML>
?? 快捷鍵說明
復制代碼
Ctrl + C
搜索代碼
Ctrl + F
全屏模式
F11
切換主題
Ctrl + Shift + D
顯示快捷鍵
?
增大字號
Ctrl + =
減小字號
Ctrl + -