QUOTE(ssozonoff @ Aug 17 2006, 11:08 AM) [snapback]288370[/snapback]
Well for the moment this is really proving to be annoying since it seems that when voicemail is active for the remote Skype user we don't really get a consistent answer when the call is finished. As in ....clsFinished.
I have been doing several tests and for moment I either get back TCallStatus.clsVoicemailCancelled or then clsVoicemailUploading followed by clsVoicemailSent which is making things a little dificult to detect when the call is really over!!! Surely once I have hung up I the last event I should get from Skype is clsFinished irespective of what happened during VoiceMail since those I can trap as they happen....... but utlimately Skype should still say clsFinished for VoiceMail answered calls like it does when there is no Voicemail on the other end.
Thanks,
Serge
Just for the heck of it, what happens if you monitor the CallHistory event?
Maybe you could add events CallStatus, CallHistory and VoicemailStatus events to this:
http://forum.skype.com/index.php?showtopic=61740and use it as a tool?
It is easy to quickly add events and can be used to compare what is going on in case there are events you are missing and would need to add tons of logic just to experiment with in your own code, using this all it takes is really a few lines of JavaScript and new events can be added and monitored in their entirety to at least see what is really going on event wise. If the event fires it speaks it "Like it or Not"
In your case, you would want to disable the Text-To-Speech engine pause/resume during calls, just comment the two pause and resume lines out.
I hate breakpoints

they are so non real-time batch like

Event debugging is so time sensitive you also can easily miss things that you may not have coded to look for or have things queued while looking at a debug prompt. Maybe even cause timeouts on somethings because you were at a breakpoint.
Even if you are debugging your code, you can hear events fire and know what to expect when your code being debugged receives the events your heard already

without the need to be clicking OK on message boxes that display events firing or adding tons of debugging logic to isolate event problems which will only in the end slow down your development efforts.
Event debugging with message boxes is so 80's like

Disco is dead

and Elvis HAS left the building.
But before he left he sang..."One for the Money...Two for the Show...Three to get ready...and Four to Go..I'm hearing...Hearing my Skype Events now!"