Q: Reason for LINEDISCONNECTMODE_NOANSWER
- From: "Martin Richter [MVP]" <martin.richter@xxxxxxxx>
- Date: Wed, 19 Oct 2005 10:10:47 +0200
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) 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)?
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.
What events should be and are covered by LINEDISCONNECTMODE_NOANSWER.
Would be nice that some guys shed some lights about this. TIA
-- Martin Richter [MVP] WWJD "In C we had to code our own bugs. In C++ we can inherit them." FAQ : http://www.mpdvc.de Samples: http://www.codeguru.com http://www.codeproject.com .
- Follow-Ups:
- Re: Reason for LINEDISCONNECTMODE_NOANSWER
- From: Andreas Marschall [MVP TAPI]
- Re: Reason for LINEDISCONNECTMODE_NOANSWER
- Prev by Date: Re: Can I find how many there are calls in the address?
- Next by Date: Re: Help! LineCallBack not being called?
- Previous by thread: Help! LineCallBack not being called?
- Next by thread: Re: Reason for LINEDISCONNECTMODE_NOANSWER
- Index(es):
Relevant Pages
|
Loading