5ut1, port my cell from koodo to chatr, can't dial from fp

[jason1416]

Hi, I just ported my phone # 416-xxx-xxxx from koodo to chatr, I can not dial my cell from my free phone line anymore, it was good before, got recorded message "5UT1, you have reached a number that is not equipped for incoming calls, please check the number and try again."

some time it says 5UT2, 5UM2 instead of 5UT1

There is no problem to call my cell from bell landmine .
Thank you

[TheHardy]

Hi, I just ported my phone # 416-xxx-xxxx from koodo to chatr, I can not dial my cell from my free phone line anymore, it was good before, got recorded message "5UT1, you have reached a number that is not equipped for incoming calls, please check the number and try again."

some time it says 5UT2, 5UM2 instead of 5UT1

There is no problem to call my cell from bell landmine .

ROFLMAO

Sorry, that just killed me!

Umm, back to a serious side of the post, I would give a quick call to ChatR and ensure that they have ported your number correctly -- just state to them that you are having problems in receiving calls. How long ago did you port over? The fact that you could call it before, and cannot now seems to indicate that something has not gone 100% correct in the porting procedure. Bell's "landmine" may be somewhat more tolerant of whatever is not provisioned correctly than FPL.

That failing, and if you don't mind a call from the West Coast, feel free to PM me your 416-former-Koodo-now-ChatR number and I will give you a shout from either my FPL or DV account here and see if it goes thru!

[TheHardy]

I am having trouble also completing the call to you (as per your PM). The call does not seem to set up whatsoever in my softphone. It shows in the logs at the bottom as a 0-second call (very bottom of the call log) but nothing goes thru.

The message you are getting, sounds like a TELUS ERROR message (Telus being the carrier behind Koodo). I am thinking it might be a port error, even though you confirm you have contacted ChatR. It seems reminicent of a 0-balance error to a Telus Prepaid message ...

I am continuing to try to place a call to you to see if this is indeed a Fongo issue, but you may want to PM to Steve or Mike to look into this also from the Fongo side of things, as they would be able to see how the call is being processed on the FONGO-network side of things and where the call routing is breaking down. Your test results that you sent to me in PM would prove helpful to them also!

[TheHardy]

You have reached a number which is not equipped for incoming service.....

and you are correct, the end digits change.

The fact that I can reach the ERROR message when dialing it means that there is an error in the way the call is being routed; and with a new-port, I still think that it is something in the way the port was affected. As the receiving carrier, ChatR is responsible, but I suspect, based on the error message that it is a Koodo error. Open a trouble ticket with ChatR and have them backtrace the port procedure to ensure that Koodo has done it correctly on their end.

[TheHardy]

1778300yyyy 14163**xxxx 0:00 22.10.12 19:17:18 22.10.12 19:17:18 Destination out of order Toronto ON $ 0.00
1778300yyyy 14163**xxxx 0:00 22.10.12 19:18:09 22.10.12 19:18:09 VPCI VCI assignment failure Toronto ON $ 0.00

[jason1416]

Hi TheHardy
Thank you for your help.
Are you sure the message from TELUS?

It's kind of weird.

I did following voice call test, here cell means my mobile # ported from koodo to chatr
Bell land line --> cell, ok
fido mobile--> cell, ok
Google voice --> cell , ok
chatr --> cell , ok
italkbb -->cell , ok

text message from international, ok.

and only fpl ->cell , not ok.

I think the problem is from fpl end.
I will PM Steve or Mike,

thank you again.

[TheHardy]

I am still trying to call your number as PM'd, and I alternately (not 50%) get either complete dead air, or the failure message. Even when I hear nothing on my softphone when dialing, I still end up with a log entry in my call log.

Fongo's handling of error messages/failed calls is suspect at best and has been a hotbutton topic in the past. However, as Fongo just routes the calls for termination, somewhere they are getting incorrect info as to how to finish processing the call.

This is where Steve/Mike/someone@Fongo needs to dig deeper into the call-handling log on a network level and track down the problem.

As I stated, I am almost sure that when this hits their inbox and they have 10 minutes or so to throw at the problem that they will be able to track down where the failure is -- IF it is within the Fongo system. At the very least, even if it is not, with the aid of someone "deeper down in the building" they will be able to target where the fault likely lies if it is outside of the Fongo network.

[FONGO_mike]

Please try again, this issue should now be resolved.

[jason1416]

Hi Mike
It's solved

Thank you very much

[FONGO_mike]

Hi Jason,

thank you for responding back letting us know it is now working for you

[TheHardy]

Seeing I invested a little time into this also, may I ask WHAT WAS THE PROBLEM? Just curious to add it to my tool bag of answers, should we run across this again .... ??? Unless it is a state secret, of course ... in which case just WHISPER it to me, and I promise not to repeat it!!!

Jason: thanks for all the troubleshooting and in getting back that it is resolved! Hope things work out, and you can toss Fongo some more referrals!

Mike: thanks for the quick turn-around --- in PM's to Jason yesterday, I had stated that if it was a Fongo-controllable issue that yourself or Steve usually manage to get out the Fix-It-Hammer and beat the problems into submission relatively quickly!