SMS support about csipsimple

[GoogleCodeExporter]

I am using webSMS for sending sms from sip gateways.  It works very well.  My 2 
cents would be to simply add a link to that app somehow or add this feature at 
a much later date.  Keep focused on sip and voip...  This project is well on 
the way to becoming the best on the marketplace if you keep at it the way you 
are...

Original comment by [email protected] on 30 Aug 2010 at 7:09

[GoogleCodeExporter]

Indeed, that's a really low priority issue.

But here to keep it in mind for the future. Just like buddy list, sip SIMPLE 
(the extension of sip protocol), presence etc.

And if any contributor want to implement it... we will keep track on the 
progress on this issue.

Original comment by [email protected] on 30 Aug 2010 at 7:56

• Added labels: Type-Enhancement
• Removed labels: Type-Task

[GoogleCodeExporter]

SIP messages are now available as a first draft in 0.00-15-14. 

For SIP providers that supports SIP GW to GSM network it will send SMS.
For others that just forward MESSAGES, it will be just like an IM for SIP to 
SIP messages.

Thanks go to chrism and VTel for their help on this feature.

Keep in mind that's just the beginning of the implementation of the feature, 
and I'm absolutely aware of what is missing ;).

Original comment by [email protected] on 22 Nov 2010 at 9:13

• Changed state: Started

[GoogleCodeExporter]

Hi, as far as I know, supporting SMSs on most of the affiliate VoIP providers* 
is quite simple. Only a URL has to be called, something like this:

https://www.foobarprovider.com/myaccount/sendsms.php&username=xxxx&password=xxxx
x&message=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

*okay I've tried this on three different providers, but they are using the same 
infrasturcture anyway ;)

HTH!

Original comment by [email protected] on 22 Mar 2011 at 10:35

[GoogleCodeExporter]

I think I got some SMS when I'm uisng CSipSimple, but I cannot read them 
because of broken characters(that's why I mentioned that I think I got). It 
seems encoding is the matter. I use Korean SIP provider and they're using 
KS5601C encoding (I'm not sure in detail..) but as far as I know, it's 
specified encoding for Korean and other encoding doesn't support right 
character for Korean. Could you support encoding selection for SMS?

Original comment by [email protected] on 22 Mar 2011 at 10:42

[GoogleCodeExporter]

@punny : the aim of this issue was to implement the *standard* SMS way using 
MESSAGE.
Actually that does not *ONLY* do SMS. 

It use SIP SIMPLE protocol to send MESSAGE. It could be used as chat messaging 
system. Some provider use this protocol to do the gateway between SIP MESSAGE 
and SMS of the mobile network.

All betamax clones support both MESSAGE and web api methods. Web api is a verry 
crappy way compared to a clean SIP MESSAGE ;). 
If your provider does not support SIP MESSAGE you really should ask them to do 
so. I'll never implement in CSipSimple a not normalized API specific to a 
provider. Only the normalized SIP MESSAGE way. CSipSimple is a sip application.
The support of SMS using SIP MESSAGE is already available in the application.

The task is entirely finished yet. level7systems and skhanzada are working on 
this point to improve the UI.


@Surie : there is probably something wrong I do with encoding. Can you open an 
new issue for that? I guess it's even possible to have the exact encoding from 
the message sent by the server but my code does not manage it (I guess that I 
assume it's utf8 which obviously could be wrong ;) ).

Original comment by [email protected] on 22 Mar 2011 at 11:16

[GoogleCodeExporter]

I didn't expect this feature to be there, not even in its infant form, but 
there it is. I am very much impressed. You really rock as a developer! Kudos to 
you!

Original comment by [email protected] on 24 Apr 2011 at 8:17

[GoogleCodeExporter]

---
Issue marked as closed since SIP MESSAGE is now there and almost fully 
functional. 


For integration with webservices of a specific provider (which is not relevant 
of SIP actually), there is very good apps for that : 
http://code.google.com/p/websmsdroid/

Original comment by [email protected] on 7 May 2011 at 3:40

• Changed state: Fixed

[GoogleCodeExporter]

Seems to be a a problem with non english languages and chars like ñ á é... 
etc. 

I'm using easyvoip and with his web interface it's the same, but it's ok if you 
use the desktop app.

Original comment by [email protected] on 16 May 2011 at 10:05

[GoogleCodeExporter]

Sounds something with encoding. What do you observe? I guess you have some very 
special characters.

By default csipsimple send using utf8 encoding. 
If the gateway of the sip provider does not support it, the guilt is more 
likely on the side of the server (the sip provider). This would be coherent 
with the fact they also have the problem on their web interface.

The only thing I could try on my side would be to explicitly add the encoding 
type to the mime type of what I send, but normally now all sip server should 
assume encoding is utf8 (unless that's old windows servers ;) ).

Original comment by [email protected] on 17 May 2011 at 9:37

[GoogleCodeExporter]

The characters received are in utf8 format... but in ascii.... i can see the 
two chars of the encoded string in the message ( Ñ is converted to Ñ ). 

Maybe EasyVoip sends it as ASCII (Max 160 chars) and not in UTF (Max 70 chars)

Maybe this could help (How SMS are encoded): http://bit.ly/jkjlNq

Original comment by [email protected] on 17 May 2011 at 3:26

[GoogleCodeExporter]

Ok.
So I think that what easyvoip do when receiving a SIP MESSAGE is just to apply 
raw ascii to what is sent encoded in utf8.

Normally all encoding stuff should be done by the gateway. It's never up to the 
SIP MESSAGE client to encode things in a special charset. The obvious very good 
reason is that the sip message client does not know that behind this will be 
tramsitted to the SMS network. Keep in mind that SIP messages can be exchanged 
between SIP clients, just like it's done for SIP calls. Here we are in front of 
SMS gateway. It's normally up to the gateway to do his job and to convert 
things.

It's a little bit like if it was required for a SIP client for voice calls to 
PSTN network to encode INVITE in a special way to be understood by the analog 
phone. That's not how things work, the gateway should do things to translate 
SIP signals to PSTN signals. Here, with SMS gateways, it should go the same.

The only thing I could try on my side is to specify that what is sent is 
text/plain;encoding=utf-8 instead of just text/plain, and then cross finger for 
:
 * the fact that it will not break things on most gateway that may implement things a crappy way expecting only for text/plain (without ";...."). 
 * the fact that it will be interpreted by easyvoip gateway, and that it will be converted correctly.

If you are ok, I could do a special build just to test this case by hard coding 
the extended mime-type. So that you could validate whether specifying encoding 
of sent text helps on easy-voip side helps. If so, I'll have some non 
regression tests to do in order to include that when talking to all sip servers 
and all sip clients.
As anyway I've planned to include the way to send something else than 
text/plain (for example to share pictures, or any mime type... cause that's 
allowed by SIP messages), it should will not be really a hack but could be 
considered as part of the feature enhancement about changing mime types of what 
is sent.

Original comment by [email protected] on 17 May 2011 at 3:51

[GoogleCodeExporter]

Not able to send SMS using DVCN'G server. It says method not supported.
Please tell what's the issue

Original comment by [email protected] on 30 Jun 2011 at 6:27

[GoogleCodeExporter]

Probably cause their server does not support sip messages ;)

Actually csipsimple supports SIP Messages (it's a part of the sip protocol).

If your sip provider does not allow gateway between sip messages and gsm sms, 
sending sip message to a gsm number will probably fail.

Original comment by [email protected] on 30 Jun 2011 at 8:22

[GoogleCodeExporter]

Thanks for your reply

Original comment by [email protected] on 13 Jul 2011 at 3:14

[GoogleCodeExporter]

It would be good support capability to encrypt the messages end to end via the 
SIP SIMPLE using OTR, and also gpg (for offline messages where OTR won't work)

Original comment by [email protected] on 30 Aug 2012 at 1:20

[GoogleCodeExporter]

any progress here ?

Original comment by [email protected] on 22 Dec 2012 at 11:11