bcatalin
Wed Mar 26 2008, 14:22
With the Automatically answer incomming calls checked in Options->Privacy I've received two times the INPROGRESS API
CALL 2248 CONF_ID 0
CALL 2248 STATUS INPROGRESS
CALL 2248 STATUS INPROGRESS
CALL 2248 VAA_INPUT_STATUS FALSE
CALL 2248 DURATION 1
I've hoped that this feature will resolve the problem with the ALTER CALL xx ANSWER when the SKYPE is sending sometimes junk
to DBUS and my DBUS interface is crashing. In the best case a ERROR is received from SKYPE over DBUS even the call is answered.
ALTER CALL 3161 ANSWER
ERROR 559 CALL: Action failed but the call is going on normally. This is the best case!
It's hard to work like this if from one release to other the behavior is changing so much
Avo Nappo
Wed Mar 26 2008, 17:55
Looks as if it might be a bug. Forwarded to our linux folks for further investigation.
Felipe Fujiy Pessoto
Mon Jun 30 2008, 21:17
I have same problem using COM, last version.
I just do cl = cSkype.PlaceCall(Number, null, null, null);
Its always worked, then one time it stopped....
And what is more bizarre? If I put a breakpoint in this line, and when get this line I press F5(continue) i get this error, but if I press F10(step over) i can continue without error
Anyway, skype make the call....with error or not, but throw this exception and stop my program.
Sorry for bad english
TheUberOverlord
Mon Jun 30 2008, 22:39
I am just curious.
What Skype Windows client version(s) are both of you having problems with and what Skype4COM version are you using?
Felipe Fujiy Pessoto
Tue Jul 1 2008, 00:34
I am just curious.
What Skype Windows client version(s) are both of you having problems with and what Skype4COM version are you using?
I am not at work pc now. But i downloaded last COM(0.29 i think) and Skype client(last stable windows version, 3.8, not bussiness, normal version)
TheUberOverlord
Tue Jul 1 2008, 01:04
I am not at work pc now. But i downloaded last COM(0.29 i think) and Skype client(last stable windows version, 3.8, not bussiness, normal version)
My mistake, I thought this was a Windows problem.
Felipe Fujiy Pessoto
Tue Jul 1 2008, 11:46
Skype 3.8.0.139
I think that problem just occurs in try catch block
TheUberOverlord
Tue Jul 1 2008, 12:05
Skype 3.8.0.139
I think that problem just occurs in try catch block
The original problem was/is on Linux. I tried on Windows 3.8.0.139 not able to re-create ("With/Without try/catch").
Felipe Fujiy Pessoto
Tue Jul 1 2008, 12:30
Its not every time.
Now i having the problem outside try =/
TheUberOverlord
Tue Jul 1 2008, 14:41
Its not every time.
Now i having the problem outside try =/
This is from the API message or the CallStatus event handler fires twice for the same call in progress, or both:
NOTE: The initial post ("Top - First Post") about this is for Linux and the API message, nothing to do with Windows, or Skype4COM.