11-06-2016 09:46 AM - edited 01-04-2022 06:05 PM
Solved! Go to Solution.
11-30-2016 09:57 AM
I am in the same situation. After porting my number from voip.ms, calls work, but text messages are not delivered to my phone.
I have already updated @Mary_M and waiting patiently
11-14-2016 04:15 PM - edited 11-14-2016 04:16 PM
Public Mobile tech support (level 2) just fixed my text message sending/receiving. Apparently the port from voip.ms was incomplete and left my text messaging setup still pointing back at their service. Hope this turns up in the search for the next person.
Also, no $25 fee for me (I ported the number into voip.ms a year ago for safe-keeping).
11-14-2016 03:03 PM
Alright it seems the charge is there because you're porting from landline to mobile. Alright, fair enough, because I have a number originally with Vonage that I ported to Ooma. I suppose if I wanted to port it to mobile I'd expect a charge.
11-14-2016 12:10 PM
11-14-2016 10:44 AM
According to the voip.ms rep.
If you ported your number in, then there is no port out fee.
They sell numbers expecting to be used with voip.ms so there may be a port out fee if you purchase a number from voip.ms and try to port it out.
However if you have used the number for some time, then there should not be a port out fee even for the numbers purchased from voip.ms
I think it's just to discourage people from abusing the system.
11-14-2016 09:41 AM
Wow, I'm surprised to hear about the $25 fee. Is this normal? Are companies allowed to charge for porting? I thought the number was yours, so you shouldn't be charged. Maybe it's different with VOIP but I'm wondering why the charge.
11-14-2016 08:39 AM
Any insight what changed? I have the exact same situation - ported in from voip.ms, and texting doesn't work. Sent messages show as sent but never arrive. Messages to me get rejected with an error "Destination number _______ is not a valid SMS recipient". I've done the basic troubleshooting steps Public Mobile support has walked me through so far but no success.
11-14-2016 04:35 AM
11-14-2016 04:13 AM
11-09-2016 02:28 PM
Everything is working but still no luck with sending or receiving text messages.
However I am still able to text with my old carrier VOIP.MS so I think my porting is still stuck.
Will need help pls to fix issue.
@Shazia_K | @Mary_M | @Saray_O | @Caroline_D
11-09-2016 10:44 AM
11-09-2016 10:38 AM
I think I may not have to pay the fee to port as this number was orginally mine, as I ported it to voip.ms about 5 months ago from Rogers and was charged a fee to do so. Are you porting a number you obtained from voip.ms?
I guess all I can do now is wait.....
11-09-2016 10:35 AM
11-09-2016 10:28 AM
Very strange as I have not obtained any communication from voip.ms at all and was not charged anything and everything is working except incoming calls.
My DID is still assigned to me in my voip.ms console/website and I have not recevied a text or confirmation from PM indicating a sucessful port.
11-09-2016 10:20 AM
11-09-2016 10:13 AM
@Tammer I am also trying to port from Voip.ms to Public mobile, I have been waiting over 5 days now.
I can send/receive text messages and make outgoing calls, still can not receive calls though.
Did voip.ms e-mail you asking to provide approval for the port at all? Is the DID (telephone number) still in assigned to you in your voip.ms account?
11-09-2016 08:52 AM
11-06-2016 10:41 AM - edited 11-06-2016 10:42 AM
Yes, voip services are notoriously slow porting. Use this process, Contact moderator if
a) no change after 7 days, or
b) incoming calls to your voip account stop and you cannot receive those calls with your PM account.
Landlines and voip port-ins test one's patience.
Welcome aboard. Well at least you have one foot on the deck!