05-23-2020, 04:49 PM
(05-23-2020, 01:12 PM)janw Wrote:(05-23-2020, 11:10 AM)mil Wrote: Yeah there's some work to do on internationalization (well really just the weather script and dialing); dialing stuff is what I'm more concerned about right now, curious if calls / sms works for you / anyone not in the US? I'm removing the +1 prefix currently so I think it'll probably break
Let's see, I've just put my SIM-card in my pinephone to do some tests.
When I enter a number that starts with +32 (+32 = Belgium) in the dialer of sxmo, I get the message that it is not a number. If I leave out the +32 part (and add a 0) I can call my normal phone at home.
In the other direction, I can make a call from my normal phone to the pinephone and pick it up. But the number gets stored in the dialer without the + (3212345678 instead of +3212345678).
I've also logged in to PC-banking, because they send an SMS with a code to log in. I have successfully received that code.
Because I have a very bad reception at home, I had to do these tests while standing before my window. This is a little bit cumbersome... so enough testing for today
Thanks for helping test - first i've heard of calls/texts working via the scripts in sxmo outside the US
Maybe there's a way to have mmcli query the actual international number called - issue originally was that if you put a request into mm to call some number without the international prefix, it'll work fine but then on the receiving end for a text message the prefix / country code like +1 is always prefix appended. So for text message logs if you append without prefix processing normalization it would go to two different log files. So I scripted around that for the US, but it seems like this definitely break's with variable length country codes.
Will have to play around more with it; hopefully mm can report back out the actual number (with the prefix accounted for even if the user didn't enter it); if not could always make the country prefix required as a last resort.