Porting process - time to complete?

Today my port from an ex-BT number that I migrated to Talktalk and then to Utility Warehouse in 2019 began, I now have the ability to make outgoing calls via my VoIP phones on A&A's VoIP service.

Incoming calls are a different matter, from my mobile I get pretty much an immediate call ended response, earlier a couple of calls showing as Private number rang my old landline phones but on answering the call dropped immediately.

Given that it's now mid-evening has something gone wrong with the porting process? I've seen some comments that it can take until the next day for everything to be working, I assume that the original number owner (Openreach these days>?) needs to put in a redirect to A&A's platform (Magrathea really?

Any thoughts on this?

Yes, I think it best to port a number to an independent VOIP ISP and then keep it there regardless of the broadband connection.

I ported to A&A earlier this month and it was a sour ear of a migrate.

I could make outgoing calls, but incoming were going to old non VOIP landline connected to the VF router, then some to A& A and others to DECT, took a week to sort out and not sure if every number does work as only time will tell.

They said it was to do with routing tables that VF had added number to or something.

In reply to a post by Ahmedg:

I ported to A&A earlier this month and it was a sour ear of a migrate.

I could make outgoing calls, but incoming were going to old non VOIP landline connected to the VF router, then some to A& A and others to DECT, took a week to sort out and not sure if every number does work as only time will tell.

They said it was to do with routing tables that VF had added number to or something.

It sounds like you had a more complex previous setup than I did, which may have required some manual intervention from you before the port.

In my case I couldn't work out what was happening so I phoned A&A support this afternoon and it turned out that the SIP routing string entered into their system had @@ in it instead of @. Once that extraneous @ was removed it instantly sprang to life.

What was interesting was that calls that were not routed in yesterday or this morning are showing up in my missed calls list. That suggests that they reached Magrathea but the A&A server couldn't route them, a symptom being that the failure reason was different depending where the call originated. Some networks would not even place the call, so my EE mobile hung up with no audio heard and Call Ended on the screen. Virgin mobile gave a digital Dot message about being unable to connect the call, please try again later while a call from another VoIP phone from a different supplier was getting a busy tone.

Perhaps some input sanitising scripts could be usefully deployed.

TBH wasn't to complex in my layman knowledge, just moved the number from VF to A&A.
I found A&A to be really good and knowledgable. .

In reply to a post by Ahmedg:

TBH wasn't to complex in my layman knowledge, just moved the number from VF to A&A.
I found A&A to be really good and knowledgable. .

They certainly are that, took about 2 seconds to fix my problem.

It might make their job easier if they had automation to find and correct simple errors, we all make typos.