Solved When does a port-in number show up in the Skyetel portal
-
@JaredBusch said in When does a port-in number show up in the Skyetel portal:
So I started the process of porting two numbers in to a @Skyetel account for a client.
I have the confirmaiton email from Skyetel, but the numbers do not show in my portal yet.
I checked their knowledge base and it does not have nay information on this.
https://skyetel.atlassian.net/wiki/spaces/SUG/pages/59900006/Number+PortingSo, right now, I have no way, within the portal, to see my number port-in status?
I ask because, my normal process is to request a port-in, and then immediately setup the routing for the number so it is ready once it completes the port-in.
Obviously, I can come back to it later, but I find it easier to handle it all during the initial request time.
We add the numbers to your portal within a day or so of us getting FOC. (So keep an eye on your email).
We delay adding them because once they are added in our Inventory they route instantly on our network, and on our interconnecting peer's networks. To stay compliant with PSTN standards, we don't want to do that until we have FOC
-
@Skyetel said in When does a port-in number show up in the Skyetel portal:
We delay adding them because once they are added in our Inventory they route instantly on our network, and on our interconnecting peer's networks. To stay compliant with PSTN standards, we don't want to do that until we have FOC
This is why I like to setup routing in the provider portal as soon as I set up the number.
See if you begin to route the number immediately after putting it in a place I can access, that means I will immediately being to miss calls from anyone using Skyetel to call me.
Because I have not yet routed the number to point to any of my Endpoints.
Yes, calls from other carriers will still go to the existing provider, until the port completes. But for anyone else using Skyetel, the call will never leave your network and attempt to route to me potentially before I am ready.
-
@JaredBusch said in When does a port-in number show up in the Skyetel portal:
@Skyetel said in When does a port-in number show up in the Skyetel portal:
We delay adding them because once they are added in our Inventory they route instantly on our network, and on our interconnecting peer's networks. To stay compliant with PSTN standards, we don't want to do that until we have FOC
This is why I like to setup routing in the provider portal as soon as I set up the number.
See if you begin to route the number immediately after putting it in a place I can access, that means I will immediately being to miss calls from anyone using Skyetel to call me.
Because I have not yet routed the number to point to any of my Endpoints.
Yes, calls from other carriers will still go to the existing provider, until the port completes. But for anyone else using Skyetel, the call will never leave your network and attempt to route to me potentially before I am ready.
We go back and forth on this, but settled on this method because about 25% of our LNP orders occur before a PBX has even been spun up. Many integrators want to get the port started, and then install & configure the PBX on the FOC date.
For future reference, you can actually ask our LNP team to route the phone numbers to a particular endpoint group in the Port Notes for you.
-
@Skyetel said in When does a port-in number show up in the Skyetel portal:
For future reference, you can actually ask our LNP team to route the phone numbers to a particular endpoint group in the Port Notes for you.
Noted. That would, in fact, be an awesome additions to the port in page.
-
@JaredBusch said in When does a port-in number show up in the Skyetel portal:
@Skyetel said in When does a port-in number show up in the Skyetel portal:
For future reference, you can actually ask our LNP team to route the phone numbers to a particular endpoint group in the Port Notes for you.
noted. That would, in fact be an awesome additions to the port in page.
We are actually rebuilding the entire porting page and surrounding processes. In a future version, you'll be able to associate it yourself prior to submitting a port request, see all of your pending orders, and Port In fees will be charged upon submission. We also want Tenants to be able to submit LNP requests too.
Thats probably going to be a our next big project once Tenants and Tenant Portal are both out
-
We got word (yesterday) our incoming numbers are scheduled to port in tomorrow. The numbers are already in our portal, they were there when we got the notification about the port in. Although they will not port until mid morning tomorrow.
This is what they sent us two days before port, when the numbers were already in our portal.
Hey XXX,
Heads Up! We have just added the following phone numbers to your Skyetel account for configuration. Please make sure you configure them, enable/disable features and route them to their destination as soon as possible. As a friendly reminder, your FOC date is: 7-16-2019
For reference, these are the numbers that I have added:
11112223333
11112223334
11112223335
Thanks! -
@JasGot said in When does a port-in number show up in the Skyetel portal:
We got word (yesterday) our incoming numbers are scheduled to port in tomorrow. The numbers are already in our portal, they were there when we got the notification about the port in. Although they will not port until mid morning tomorrow.
This is what they sent us two days before port, when the numbers were already in our portal.
Hey XXX,
Heads Up! We have just added the following phone numbers to your Skyetel account for configuration. Please make sure you configure them, enable/disable features and route them to their destination as soon as possible. As a friendly reminder, your FOC date is: 7-16-2019
For reference, these are the numbers that I have added:
11112223333
11112223334
11112223335
Thanks!Right, but the point is that those numbers are immediately routing on the Skyetel network. As soon as they are entered. Before you ever see the email.
Yes, it is a very small issue at present. But it is 100% an issue.
It is also an issue with a simple work around as noted by @Skyetel a few posts ago.
It is also an issue that is being reworked in a new porting page as noted. So the entire problem will go away.
But that does not negate anything I have posted.
-
@JaredBusch said in When does a port-in number show up in the Skyetel portal:
Right, but the point is that those numbers are immediately routing on the Skyetel network. As soon as they are entered. Before you ever see the email.
Yes, it is a very small issue at present. But it is 100% an issue.
It is also an issue with a simple work around as noted by @Skyetel a few posts ago.
It is also an issue that is being reworked in a new porting page as noted. So the entire problem will go away.
But that does not negate anything I have posted.
Didn't say it did, your OP was a question. My experience on the same days was quite different than yours. Just thought you might like to know.
-
@JasGot said in When does a port-in number show up in the Skyetel portal:
@JaredBusch said in When does a port-in number show up in the Skyetel portal:
Right, but the point is that those numbers are immediately routing on the Skyetel network. As soon as they are entered. Before you ever see the email.
Yes, it is a very small issue at present. But it is 100% an issue.
It is also an issue with a simple work around as noted by @Skyetel a few posts ago.
It is also an issue that is being reworked in a new porting page as noted. So the entire problem will go away.
But that does not negate anything I have posted.
Didn't say it did, your OP was a question. My experience on the same days was quite different than yours. Just thought you might like to know.
In your rush to defend this service that you like so much I don’t think you actually understand a thing I’ve said. It is impossible for your experience to be different because my experience so far is standard and the same.. I have simply requested a port and I am now waiting.
Your numbers were not in the portal immediately after the port request.
-
@JaredBusch said in When does a port-in number show up in the Skyetel portal:
In your rush to defend this service that you like so much I don’t think you actually understand a thing I’ve said. It is impossible for your experience to be different because my experience so far is standard and the same.. I have simply requested a port and I am now waiting.
Your numbers were not in the portal immediately after the port request.
You must interact with Mangolassi from a very small phone. You miss so much of what is said, and misinterpret most of the words that are written.
I said we received notice that our number had a port date, and at that time they were in our portal. I did not say they were there when I made the port request. In fact the whole porting thing was a nightmare because of the losing party. The port request was made 4 weeks ago.
If you re-read my post; slowly and deliberately, you'll see that I was not defending Skyetel at all. I was simply indicating what my experience was. Which, and to the point, was different from yours, and different from what Skyetel said it should be in response to your question.
-
@JasGot Actually I read things very carefully. You clearly stated that our experiences were different. That means you had to of seen the numbers right after the port was requested because that is the current status of my port. As I clearly stated in the original post I just started the port request.
-
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.
