Flowroute ported DID not being routed inbound on new 3CX install

Status
Not open for further replies.

SpinksDV

Bronze Partner
Basic Certified
Joined
Apr 5, 2019
Messages
3
Reaction score
1
I have done this many times without issue but recently set up a new 3CX system and purchased a new DID from Flowroute as a temporary number until customer's main DID could make its way through the porting process. Porting was not as clean as I have had in the past. Several hours later than they quoted. Also, because porting happened late hour on a Friday I had to wait the weekend out for support (Flowroute support is M-F 5-5 PT) when the ported number would not route via Flowroute. Luckily, the old carrier was still routing through customer's old system. Monday afternoon, this issue was resolved by Flowroute but they said it was not a porting issue but a peer network issue??? The non-ported DID worked great the entire time, it was the ported DID that would not route.

FYI - was not told exactly what could have been done differently but hopefully this saves someone else from the hours waisted troubleshooting this, thinking it was a misconfiguration on my side.
 
  • Like
Reactions: YiannisH_3CX
Hi @SpinksDV

Thank you for sharing. Glad to see you were able to resolve your issue in the end. Unfortunately porting issues are more common than they should be.
 
  • Like
Reactions: N_G
Hi @SpinksDV

Thank you for sharing. Glad to see you were able to resolve your issue in the end. Unfortunately porting issues are more common than they should be.
I've ported some 550 DIDs into Flowroute with out issue. But call me a skeptic - their buy out by BCM One does not bode well long term. I've prepared my organization for the possibility of having a different cloud SIP provider because of the buy out. I've put their account team on notice as well - if I see anything that suggests that BCM is cost cutting and impacting the reliability of their services - I'll port away from them.
 
While not a huge Flowroute fan, it's entirely possible this wasn't their fault as they indicated. You mentioned it wouldn't route, but they can't route a call that isn't hitting their network. We've had this happen a few times with numbers porting where we had to call the ULC directly to release the numbers because they missed FOC. But that's one of the dangers of porting late in the day is LNP teams are M-F business hours only.
 
Status
Not open for further replies.

Latest Posts

Members Online Now

Forum statistics

Threads
111,831
Messages
589,276
Members
164,660
Latest member
RJenkinsROCK