Re: Reason for LINEDISCONNECTMODE_NOANSWER
- From: "Andreas Marschall [MVP TAPI]" <Andreas.Marschall@xxxxxxxxxx>
- Date: Wed, 19 Oct 2005 11:07:35 +0200
"Martin Richter [MVP]" <martin.richter@xxxxxxxx> schrieb im Newsbeitrag
news:dj5638.7mg.1@xxxxxxxxxxxxxxxxxxx
> Hi!
>
> I always get in trouble with the callstates used by some TSP's.
>
> The Docs say simply about:
> LINEDISCONNECTMODE_NOANSWER
> The remote user's station does not answer
>
> I can also read in the LINECALPARAMS docu:
> dwNoAnswerTimeout
> Number of seconds, after the completion of dialing, that the call should
> be allowed to wait in the PROCEEDING or RINGBACK states, before it is
> automatically abandoned by the service provider with a
> LINECALLSTATE_DISCONNECTED and LINEDISCONNECTMODE_NOANSWER. A value of 0
> indicates that the application does not desire automatic call abandonment.
>
> Now this is the reason were I get into trouble:
> If I dial a number via lineMakeCall that is not complete (missing last
> digit)
Martin,
Do use partially dialling for this?
See my TAPI and TSPI FAQ:
Q: How do I partially dial with TAPI2 ?
http://www.i-b-a-m.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm#_Q:_Who_do
> it takes some time and the connection is disconnected and nearly
> all tapi drivers I checked (4 up to know, elmeg, Alcatel) returned as
> disconnect reason LINEDISCONNECTMODE_NOANSWER. And I can understand
> this, because I get no answer. Shouldn't it be
> LINEDISCONNECTMODE_BADADDRESS (The destination address is invalid)?
Now I'm confused:
At 1st you said you understand why it is _NOANSWER, then you suggested it
should be _BADADDRESS !?
Btw. why should it be _BADADDRESS? The address isn't invalid but only
incomplete.
> But in the case above, when the TSP disconects due to timeout reasons I
> get a LINEDISCONNECTMODE_NOANSWER too. But the situation is different.
> In one case had a connection but nobody gets on the phone, in the other
> case there is no connection at all.
Are you refering to UniModem.TSP that is firing LINECALLSTATE_CONNECTED
immediately after dialling is complete?
> What events should be and are covered by LINEDISCONNECTMODE_NOANSWER.
As you have already noticed the the TAPI specification has only a brief
description of this,
it is actually up to the TSP developer to decide.
This decision is of course influenced by the information the TSP has available
from the corresponding telephone devices.
Conclusion: a TAPI app needs to be tested with _every_ TSP it desires to
_properly_ run with!
Btw. what is your actual problem with this (or is this "only" academically)?
For further discussion it will be helpfull to post TB20.logs (incl. logged
params) for the various scenarious and TSPs.
--
Best Regards
Andreas Marschall
Microsoft MVP for TAPI / Windows SDK
TAPI / TSP Developer and Tester
http://www.I-B-A-M.de/Andreas_Marschall's_TAPI_and_TSPI_FAQ.htm
* Please post all messages and replies to the newsgroup so all may
* benefit from the discussion. Private mail is usually not replied to.
* This posting is provided "AS IS" with no warranties, and confers no rights.
.
- Follow-Ups:
- Re: Reason for LINEDISCONNECTMODE_NOANSWER
- From: Martin Richter [MVP]
- Re: Reason for LINEDISCONNECTMODE_NOANSWER
- References:
- Q: Reason for LINEDISCONNECTMODE_NOANSWER
- From: Martin Richter [MVP]
- Q: Reason for LINEDISCONNECTMODE_NOANSWER
- Prev by Date: Nortel - lineBlindTransfer fails with error: LINEERR_OPERATIONFAILED
- Next by Date: Re: Reason for LINEDISCONNECTMODE_NOANSWER
- Previous by thread: Q: Reason for LINEDISCONNECTMODE_NOANSWER
- Next by thread: Re: Reason for LINEDISCONNECTMODE_NOANSWER
- Index(es):
Relevant Pages
|
