I was with smarty network for a while but the signal was weak in the building so I got an eSIM from Lyca as they use EE which I’ve heard is much better with signal.

I want to keep my old number (smarty), I got my PAC code and filled in a form on Lyca website, got no confirmation, so I clicked submit again and then they showed my a duplicate request message.

I emailed Lyca support just in case as well with my details and porting details too just in case.

Next day, I didn’t get any updates, so I called Lyca, I spoke with some Indian girl who said the transfer was successful, I checked my phone and suddenly I lost signal with Smarty (old provider), and when entering *132# using Lyca eSIM it would show my old number, so I thought it’s all good now.

However the network signal came back on my old SIM (Smarty), I disabled that card in the settings, so only Lyca was active. I changed my number to the one I want to keep in iphone settings, but then iMessage won’t activate for my old number.

Whenever I call someone it shows my correct old number, but when people call me, I need to have the old SIM card (Smarty) active showing No Service, otherwise people will hear I’m not available, then as soon as they disconnect I will get a text message saying I missed a call.

Anyone knows what’s going on? Surely something is wrong as I shouldn’t have to have my old Smarty SIM card installed showing no service just so people can call me. Also iMessage still won’t activate with the old number…

I ported my number before from Three to GiffGaff (o2), then to Smarty and it was always a smooth process with text updates. With Lyca I got nothing at all through the whole process. Only difference is I’m trying to move from a physical SIM to an eSIM…

  • HolidayGreed@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    I had an identical experience with some other networks. It was some time ago, so difficult to recall fully, but I believe restarting my phone regularly was helpful. It may just have been that patience was required for the network side changes to be propagated, but the issue was resolved after one of those restarts.