Open GoogleCodeExporter opened 9 years ago
I should add that I was sending to a number on o2 Ireland, we just discovered
it seems to work ok sending to a number on 3 Ireland
Original comment by christop...@gmail.com
on 6 Oct 2011 at 10:52
Which connector are you using?
Original comment by fint...@gmail.com
on 6 Oct 2011 at 11:18
sorry, sd have sid... fishtext
thx, chris
Original comment by christop...@gmail.com
on 7 Oct 2011 at 8:20
My first suspicion is that the "random" sender number is being caused by the
"send from" option somehow being set to anonymous. In this case I believe
fishtext use one or more of their own (probably virtual) UK mobile phone
numbers as the sender. When I tested this I got +447266696687 as the sender.
Could you please test by using the fishtext.com website to send texts to the o2
Ireland recipient - the first by choosing your own number from "send from" and
the second by choosing anonymous. If the first message has your sender number
correctly and the second behaves like you saw before, then I know where the
problem lies.
Just to confirm that you are using the newer connector -
https://market.android.com/details?id=com.fairmichael.fintan.websms.connector.fi
shtext ?
Original comment by fint...@gmail.com
on 7 Oct 2011 at 10:19
Original comment by fint...@gmail.com
on 7 Oct 2011 at 10:21
I did as you asked and whether sending from the real number or
anonymously the result is a message from an apparently random number
in the UK
Original comment by christop...@gmail.com
on 7 Oct 2011 at 2:49
If you're experiencing this issue when using the fishtext.com website, then
you'll need to take the issue up with them, it is not a problem with websms or
the fishtext connector.
If you login to fishtext.com and click on the support link there you can send
them a message. They answered me within 24hrs when I had issues before.
Original comment by fint...@gmail.com
on 7 Oct 2011 at 2:53
The issue lies with fishtext.com, there's nothing I can do in the WebSMS
Fishtext connector.
Original comment by fint...@gmail.com
on 28 Feb 2012 at 9:17
Original issue reported on code.google.com by
christop...@gmail.com
on 6 Oct 2011 at 10:07