So, to circle back on this.
First, the number port completed perfectly. All things working.
But my concern about the number being entered and routable was 100% valid.
I received an email about 6pm that the number for port A had a FOC and was now entered into my Skyetel dashboard.
I then dialed said number from my personal Skyetel account and it was terminated to my client's PBX.
From any other service the number still terminated at the losing carrier.
The next day was a repeat of an email near 6pm for port B.
I did not specify an endpoint as @Skyetel describes in post 4 because I didn't know I needed to. But as this was a new turn up to Skyetel I only had one endpoint and it was pointed there by default I assume.
The ports completed as scheduled and calls flowed in as they should.
But during that couple of days it was 100% possible that calls could have went the wrong place if I had multiple endpoint groups setup and such as I wold on a bigger design.
A revamp of this process to include the ability to specify the endpoint group or documentation at the least to instruct users to note an endpoint group on the port request will definitely smooth this bump out.
