Nov 6, 2013 at 1:48 PM
Edited Nov 6, 2013 at 1:56 PM
Thank you for the answer Jeff.
I have some new input about this problem.
I was debugging all day long today and put dial/hang-up logic into the loop. Most of times the dotras dialer gets connected OK, but some times it gets frozen.
I logged every step of this operation and here are steps:
- right away RasDialer.IsBusy == true
- ....some time of dialing until freeze...and
- RasDialer.IsBusy == false !!!
- RasConnection.GetActiveConnections() returns null
So! No events were fired form the RasDialer, no active connections were established and RasDialer.Timeout also was not involved when the RasDialer itself stopped dialing and changed it's status IsBusy to false.
And when I call RasDialer.DialAsync() after that freeze by hands (button click) the RasDialer gets connectd OK.
How can it be that the RasDialer looses its task to dial without any event notification back?
The only solution for me I see is to add my own timer to check RasDialer.IsBusy status and start DialAsync again if it's lost.
Yes, this is rough but what else can be done?