×
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

Voip MS Porting issue

Voip MS Porting issue

Voip MS Porting issue

(OP)
Hello,
Wondering if any of you have a suggestion for an issue of down time when porting a number. We recently ported a number through VOIP MS - we had everything configured in the UCX
and on VOIP MS for the FOC date - However, there was still 45 minutes of down time for the customer in the porting process. They want to port more of their numbers but
can not afford the down time. VOIP MS said there is nothing they can do. We were thinking we could forward the line to another number until the porting is complete....but since
the number will be in process of porting we don't think that forward will hold. If anyone has any ideas that have worked, we would appreciate it. Also, if any other VOIP carriers work
differently. I am only familiar with VOIP MS.

Hope

RE: Voip MS Porting issue

I just ported a number to Voip.ms last week. Never got a FOC date but the number ported anyway. Customer was out of service for 12 hrs.
When porting to other providers, I set up call forwarding to a temp. number on the pbx, build the inbound route for the ported DID. Usually works ok

RE: Voip MS Porting issue

(OP)
What other providers have you ported to? I wonder how common it is to be out of service for that long. That is just not
going to work. When you forward the number to another number on the UCX -are you still out of service for a while?

RE: Voip MS Porting issue

that was the first port to voip.ms. They gave no explanation as why there was no FOC date. Fifteen minutes after I notified them the customer was out of service, the number was in their portal. 2 minutes later got a FOC date. 1 minute later port complete.
I've ported to Telasip and FaxSipIt. Only noticed brief outage using call forward, there has to be some time to transition from one provider to another provider.

RE: Voip MS Porting issue

(OP)
That's interesting. VOIP MS told me that the losing carrier must be turning the number off on the FOC date. That we can request for them not to cancel the number until the port is complete. but I don't think that explains it. I don't think they turn it off immediately anyway.

RE: Voip MS Porting issue

We have ported to Voip.MS many times and have not had any outages that long. Maybe 15 or so minutes depending on how many numbers are porting. The problem we have with VOIP.MS is that you cannot schedule the port. It just happens on the FOC date and you do not know when. Based on what I know, Level 3 does all of VOIP.MS's ports so there is no local coordintation, it just happens.

There are ways to work around this issue that we have found successful though, so we continue to use VOIP.MS with good success.

RE: Voip MS Porting issue

(OP)
Thanks for the response. What workarounds have you found successful

RE: Voip MS Porting issue

It depends on the type of lines you are moving to SIP. If Pots, there are a couple of ways.

If 4 or 8 Pots, Install a FXO card and install the system pre-port using the Pots lines. Build all you inbound routes as as if the calls were coming in Pots or SIP. When they port to SIP the pots will stop ringing and the calls will come in SIP. You then have to go back to site and remove your FXO unless you sell it to them to keep a few Pots lines for Failover in the event the server becomes unreachable.

If you use a External FXO gateway then all you have to do once the port is done is to go to site and unplug it and leave.

This will work for PRI or Pots lines. We have done it numerous times.

another option; let's say you have 8 pots lines. Setup a Voip.ms account and order 8 DID's. You are talking $8 so it's not a big deal for the month or so you will need to get the port done. Install the UCx and forward your 8 POTs lines to the 8 SIP DID's. build all your routes using the temporary 8 DID's and then also build the routes for 8 numbers that are going to port. When the port happens everything will just keep on working and you do not need to be there. You can confirm from your office.

These are just a few ways of being able to accomplish this. The key is to have the system in and working prior to the port and in such a way that the impact to the customer is minimal of course.

Hope this helps.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close