Hello,

I read
https://developer.skype.com/Docs/DevNotes?a...tes-2.5beta.pdf
but the procesure for sending SMS is not really written there step by step. The commands listed, but not the order in which they have to be executed.

Do I see it right, that I can sucessfully send an SMS message with the following three commands:

CREATE SMS OUTGOING +49160...
Gives back ID e.g. in message SMS 387 TARGET_STATUSES +49160...=TARGET_ACCEPTABLE

SET SMS 387 BODY [text of SMS]
Gives back SMS 387 BODY [text of SMS]

Can I now send it with the following?
ALTER SMS 387 SEND

Thanks

Have you looked at the two SMS examples on this page:

https://developer.skype.com/Docs/Skype4COMLib/Examples

These use the Skype4COM method. I just send the commands directly via Windows Messages, so no oSkype.SendSms available.

You should be able to see however the API commands being generated using msgapitest, SkypeTracer, or in some cases debugview when these examples are used.

Ah, that's how you mean it. ok. At least like that I can see what Skype is responding to the messages, and interprete what messages must have been sent before.

Yes, I think many people, not just you, do not realize that the Skype4COM examples can also be used for API questions because in most cases, you can see the API communications which may be helpful if you are having any doubt what the proper API request/response chain should look like using msgapitest or SkypeTracer and Debugview

Yes, in any case thanks.
Still I think these procedures or API request/response chains for Sending aMessage, makign a Call, SMS, etc. should also be published in the developer section, as it is done in other internet RFCs.

I get the error code

ERROR 587 SMS: SET SMS: failed

As response to SET SMS 361 BODY [Text with 145 chars, with special chars @,:, ü and .]

It works when I do not use the "umlaut" ü. How can I still send this letter which can be displayed by cell phones?

Thanks.

Would you mind filing a bug report here:

https://developer.skype.com/jira/secure/Cre...amp;issuetype=5

It's no bug.
In the meantime I found out how to convert my Commands to UTF-8 before sending them. Since then it's ok.