pg17 wrote: » @mickotools Can you tell me which site you used to check your HLRs - I tried https://phonenumber-lookup.info/ but it now only gives minimal information and says "Operator's HLR rejected the request" for all numbers I tried VF, GoMo, 3, Tesco and one foreign number.
mickotoole wrote: » I've attached 2 screenshots. One from a Virgin Mobile number ported to GoMo (the one with the errors) and the other screenshot from a GoMo number that was not ported (everything looks good there). Have we any recourse here? How do we make GoMo listen and take action?
jimbob1255 wrote: » Anyone get any closer to fixing this? I'm still back and forth with them and not really sure if they are actually contacting my previous network or just kicking the can down the road everytime I message them.
jimbob1255 wrote: » Did you get a chance to check did this work?
mickotoole wrote: » They rang me. They said that they were going to chase this up with Virgin Media on my behalf and also asked if I could get some extra information from the app developer that was sending the OTP. I got an email to say that Eir had been chatting to Virgin and that they updated the routing for this GoMo number. This suggests an issue on the Virgin Media side. I haven't had a chance to test it yet but once I do I will update the thread. If this in fact the case then it really is not a GoMo issue and, if you're cynical, you could argue that this was Virgin Media trying to cause problems for customers moving to GoMo. More updates when I have them.
jimbob1255 wrote: » Did you ring Eir directly to get this info? Are Eir going to handle this case for you or did they pass it back to the Muppets on GOMO customer service?
mickotoole wrote: » Ok some progress at least for me. I got to talk to a guy in Eir. Very knowledgeable guy too. I got some insight into what was going on. It seems, at least for my particular case that the port of the number didn't go through properly. They are going to follow up with Virgin to see what went wrong. Hopefully this will lead to some kind of resolution for all affected. I'll post an update when or if this all gets sorted out.
jimbob1255 wrote: » Cheers for this update. Did you do anything or have to contact 48 when you ported over to them to fix it or did the porting to 48 and porting back simply fix it?
Renjit wrote: » Fibonacci them.
mickotoole wrote: » Yeah, I'm writing up an email now that will go to the CEO of Eir and the Director of Customer Operations. I will also be adding complaints@gomo.ie to the list. I will send the email daily until I get a reply and after a week if I don't get a reply I will email twice daily ...
Unfortunately we have given you all the information we have and cannot assist in this issue. The lack of customer details for 2 Factor Authentication is solely with the SMS provider, not the operator (GoMo). We have completed extensive testing on this issue and we have proved with Bank of Ireland and AIB that they are receiving the 2FA requests, however, it takes time on their systems for your details to be populated after first registration with a new mobile network. Thanks for chatting with me today. Representative Mathew has left the session Chat session ended
mickotoole wrote: » The plot thickens ... My wife was trying to sign up to our kids school app but she couldn't because she could not receive the OTP. I logged a call with the app developer and this is what I got back ...Our SMS provider, Twilio, who issues the OTP codes for registration with our App has generated the OTP code and attempted to send it to your wife's phone on 7 occasions. We have received the error message below in return so the OTP was not delivered to her phone: 30005 The destination number you are trying to reach is unknown and may no longer exist. I have included here a screenshot of the initiation of the OTP code if that might help you. Our SMS provider has generated and sent codes to your wife's phone since 20/02 without successful delivery of any of the codes. If you could let me know if GoMo respond with any clarification to this issue that would be a great help to us if any of our other users face the same problem. I will try once more with GoMo to see if I can get any traction.
Our SMS provider, Twilio, who issues the OTP codes for registration with our App has generated the OTP code and attempted to send it to your wife's phone on 7 occasions. We have received the error message below in return so the OTP was not delivered to her phone: 30005 The destination number you are trying to reach is unknown and may no longer exist. I have included here a screenshot of the initiation of the OTP code if that might help you. Our SMS provider has generated and sent codes to your wife's phone since 20/02 without successful delivery of any of the codes. If you could let me know if GoMo respond with any clarification to this issue that would be a great help to us if any of our other users face the same problem.
As I've mentioned earlier in the thread, I had the same problem (damaged HLR record), but for some reason GoMo decided to fix mine. I have a suspicion that no-one communicates with each other at GoMo. No-one at GoMo will give their name to customers, which means when a problem is fixed, your can't even ask a specific person who knows how to fix the problem.
irishchris wrote: » Just ported back today to gomo again. First time with them in November was a disaster. Calls not getting through and 2fa texts never arriving. My local new mast was just 4g enabled for eir so tonight would give them another chance. Port went through Tuesday straight away on time. Number seeing correctly this time in mygomo and so far banking 2fa texts coming through straight away. Tested Amazon 2fa also and they came through so seems finally had worked with this Port back from 48 this time. Previous Port was from lycamobile
mickotoole wrote: » Same as you. Problem number cannot execute the lookup however all other numbers at my disposal can (including the non ported GoMo number)
jimbob1255 wrote: » phonenumber-lookup.info Could you try inputting the number having the issues into this website. Mine can't execute the lookup however all other numbers I know work can. Be interesting just to see another number that doesn't work. If yours is the same I will definitely be pushing the fact as to why ours can't execute it but the numbers that work can.