UPDATE: Read our FAQ here. Below is the old article.
One of my customers reported that she had a problem sending a message to her iSocket fitted with a Truphone SIM from her Verizon phone. I tried to investigate the problem with Truphone, but they were unable to help. It turned out that I know more about the cause of the problem than their support does, but they’re just too big a company to care and accept my explanation.
The root of the problem is that Verizon sometimes (it was actually only twice out of some hundred) considers Truphone’s SIM numbers to be landline numbers. As soon as Verizon sees a landline number it wants to charge you extra for a message to a “landline” number. You will see the following reply from Verizon: "317XXX is a landline #. Reply Y to send all TXT messages to this # as voice messages for 0.25/msg. + std msg fee. Details @ vtext.com. TexttoLandline"
This problem is neither Verizon’s nor iSocket’s, but Truphone’s. They connect a phone number to their SIM card and for some reason this number is treated as a landline.
Here is how one customer overcame this problem. But this is workaround, not a solution. If you experience this bug, just ask Truphone to change your SIM and/or its phone number to another one (it would be better to change the number). This should help. Alternatively, use AlarmSIM – they have not had this problem so far.
Note that this only happened twice. It may never happen to you. A lot of my customers with Verizon phones use Truphone SIMs in their iSocket without any problems. Let me know if you come across this bug.