[HACK] (16/05/2010) Native SMS over IP

[drizztje]

Here is what it says in 1st post about prefix:

My country (I assume that this is country I'm calling FROM ... is USA, so prefix will be 1 )



So I'm in USA and my number is +1 (AAA) BBB-CCCC and I'm calling Russia +7 (XXX) YYY-ZZZZ. According to this algoritm
Number (+7 ...) DOES NOT start with prefix (1)
Number (+7 ...) DOES NOT start with 0

So we and up with "prefix with country code", but you say that "prefix is your country code (e.g. 90 for Turkey, 32 for Belgium, 49 for Germany, ...)"
and what it gives me ? "11" ?

Anyway, I'm not sure how with this algorithm I will end up with proper destination number of 007XXXYYYZZZZZ

Another thing ... for option 5 (for international SMS only) how you determine if destination# is "foreign" ?

I agree this might cause confusion, there is some information missing. That is, I receive one more info from the upper layer that says whether it is a foreign number or not. My function does not receive the + or 00, in your case the function receives 1AAABBBCCC.. for US (if your numbers are stored in international format) and 7AAABBBCCC... for Russia. In your case, for Russia I'll get the info from upper layer that it is a foreign number. So, here is the algorithm:

if ((foreign_number) || (number starts with prefix)) {
no change
}
else if (number starts with 0) {
remove the 0 and prefix with country code
}
else {
prefix with country code
}

BTW: Would you mind sending me a Google Voice invitation?

 

[dsip]

It may be completely random, but after I disabled the "message sent" popup again, sending an sms worked; while I got the above described error message earlier..

 

[drizztje]

It may be completely random, but after I disabled the "message sent" popup again, sending an sms worked; while I got the above described error message earlier..

Can you try the attached version with message sent popup enabled?

 

[dsip]

Thanks for the quick reaction!

Can you try the attached version with message sent popup enabled?

Tried to send one with popup enabled and got the bug I've mentioned earlier:
When I click on "yes" when asked whether I want to send the message via IP, the message program closes; when I restart it, the popup comes immediately and asks again, closes again when I say yes etc. Disabled Pop-up, did not change anything.
The message is in the "outbox" folder; I moved it to trash, everything works normal again.
Copied the message back to "drafts", tried to send it again - same thing. Edited the message (Old Message was: "Sounds fine.See you!" - new message had "!" replaced with "."..) - sending worked.

I re-enabled the pop-up, wrote the same message (with "!") again, this time tried to send it to me: Same thing happens. Moved the message from trash to drafts, disabled pop-up - same thing happens again.


I have no idea, what this is about, but if you want me to test something specific, instead of just guessing around (it's not the "!"! - "Test!" worked fine, haha)..?

(I installed this to save money, and now I find myself sending useless messages to myself all the time.. )

edit: Looking into my account it turns out that the first message was actually sent every time I clicked 'yes', the other one was not..

 

[drizztje]

Thanks for the quick reaction!


Tried to send one with popup enabled and got the bug I've mentioned earlier:
When I click on "yes" when asked whether I want to send the message via IP, the message program closes; when I restart it, the popup comes immediately and asks again, closes again when I say yes etc. Disabled Pop-up, did not change anything.
The message is in the "outbox" folder; I moved it to trash, everything works normal again.
Copied the message back to "drafts", tried to send it again - same thing. Edited the message (Old Message was: "Sounds fine.See you!" - new message had "!" replaced with "."..) - sending worked.

I re-enabled the pop-up, wrote the same message (with "!") again, this time tried to send it to me: Same thing happens. Moved the message from trash to drafts, disabled pop-up - same thing happens again.


I have no idea, what this is about, but if you want me to test something specific, instead of just guessing around (it's not the "!"! - "Test!" worked fine, haha)..?

(I installed this to save money, and now I find myself sending useless messages to myself all the time.. )

edit: Looking into my account it turns out that the first message was actually sent every time I clicked 'yes', the other one was not..

I think it is because of the !. I revised my url encoding and attached version should work fine. I also noticed that some special characters can't be sent properly even using betamax software (e.g. \,@,[,],{,}, ...).

I also added one more registry value type dword name enabledebug. If set to 1, more messegaboxes will pop up to show the resulting url after encoding.

 

[oruam57]

I also noticed that some special characters can't be sent properly even using betamax software (e.g. \,@,[,],{,}, ...).

Hi drizztje,
Due to the URL/URI format (see http://en.wikipedia.org/wiki/Percent-encoding) a bunch of special charactes can not be sent but must be percent-encoded using %xx (xx is the exadecimal character code) as you did for <CR> and <LF> to solve the multiline bug.

 

[drizztje]

Hi drizztje,
Due to the URL/URI format (see http://en.wikipedia.org/wiki/Percent-encoding) a bunch of special charactes can not be sent but must be percent-encoded using %xx (xx is the exadecimal character code) as you did for <CR> and <LF> to solve the multiline bug.

Yes, I know, but for the characters I mentioned, it doesn't work properly even if you percent-encode them. It's a betamax bug.

The version attached in my previous post still gives problems with message "Sounds fine.See you!". I don't understand why. I removed reading and checking the page for string "success" after sending the http request, now it works. But this ofcourse assumes http sending always succeeds. Here is that version:

 

[dsip]

I still get the same bug with that message, even with the newest sms.dll..

 

[drizztje]

I still get the same bug with that message, even with the newest sms.dll..

Sorry but I can't find a solution for this problem. I think it is httpsendrequest that hangs the system when the request ends with an exclamation mark. Try to send such an sms using pie or opera, you'll see that your system will become very slow.

 

[dsip]

Should adding some other sign avoid that problem? Any idea what distinguishes "Test!" from the other message..?

 

[drizztje]

Should adding some other sign avoid that problem? Any idea what distinguishes "Test!" from the other message..?

I tried adding a character after the exclamation mark, but that also didn't work. So, I have no idea

 

[tulster]

Hi drizztje,

I was hoping something like this would come along someday. Thank you for your efforts.

I have a problem though. I use Exetel and when I use the url from your first post on my PC I can receive a text to my phone but when I send a text from the phone using the same url I get the error message "url string in the registry should contain .com/"

Could this be because Exetel is ".com.au/"?

Any help will be much appreciated.

 

[drizztje]

Hi drizztje,

I was hoping something like this would come along someday. Thank you for your efforts.

I have a problem though. I use Exetel and when I use the url from your first post on my PC I can receive a text to my phone but when I send a text from the phone using the same url I get the error message "url string in the registry should contain .com/"

Could this be because Exetel is ".com.au/"?

Any help will be much appreciated.

Hi tulster,

That's the problem indeed. In the meantime I changed the code to launch the final url with the default browser to send the sms over ip. this version doesn't check for .com/ anymore so it will work for you.

 

[ccristal]

Hi!
I've tried to install the cab. Unfortunately, it doesn't seem to overwrite the original sms.dll in the \Windows directory. Could it be because I'm using a custom ROM?

Thank you!

ccristal

 

[dsip]

Any news on the bug? Did you try to contact Betamax about it? Any new stuff?

 

[drizztje]

Any news on the bug? Did you try to contact Betamax about it? Any new stuff?

no, no news. I'm just back from holiday. it seems to work better with touch-x 2 rom of smaberg. I had to change sms option to use cdma for some reason. I personaly use the version that launches browser to send the sms.

 

[m_kharboutly]

Problem with copying sms.dll

I search everywhere on how to copy sms.dll or extract it from image ROM and i didn't find anything. Can you please give me some hints or post a link on how to do it?
thank you

 

[drizztje]

I search everywhere on how to copy sms.dll or extract it from image ROM and i didn't find anything. Can you please give me some hints or post a link on how to do it?
thank you

you can overwrite sms.dll using total commander or resco explorer. soft reset afterwards. you shouldn't need to extract it from rom normally, the sms_orig.dll has worked for me with many different roms.

 

[dsip]

I'm just back from holiday. it seems to work better with touch-x 2 rom of smaberg. I had to change sms option to use cdma for some reason. I personaly use the version that launches browser to send the sms.

I hope they were enjoyable.

I just tried to use the one from the zip file you attached earlier; the one which is supposed to launch the browser. I don't know why, but it added a bunch of weird signs (€€ ¿¿0 Ç) and my phone number to the message.

The browserpath in the registry is set to launch the internet explorer, but it still launches opera mobile. Any way to change that?

 

[drizztje]

I hope they were enjoyable.

I just tried to use the one from the zip file you attached earlier; the one which is supposed to launch the browser. I don't know why, but it added a bunch of weird signs (€€ ¿¿0 Ç) and my phone number to the message.

The browserpath in the registry is set to launch the internet explorer, but it still launches opera mobile. Any way to change that?

thanks, holiday is good but always too short
I don't know the reason for the strange chars. you can try to send the same message using your voip providers software or using the browser on a pc.

about the default browser problem, did you check hkcr/https/shell/open/command?