Change in free calling area 226-336 (Kitchener)?

[godot2012]

While it is nice to be able to call most of the Canadian without paying long distance, one must also consider the impact in incoming calls. Frankly I dd not expect any. However.......

It seems that my (still existing - Bell) NPA-nnx 519-896-xxxx has a wider free calling area (for incoming calls) compared to my FONGO given 226-336-xxxx area code/number. I was really surprised when I tried to call my FONGO home number 226-336-xxxx from Cambridge, using my cell pone (FIDO/Rogers 519-729-xxxx). I was getting a message to wait till we complete your long distance call. I tried the call several times and I consistently received same message from the FIDO/ROGERS network.

When I call home using my cell from the same location (Hespeler Rd/401) or for that matter all the way from Guelph Lake the call is not considered long distance. It might be worth mentioning that when I call from my 519 (Bell) phone my 223 (VoIP) number or vice verse all calls work as local calls as expected.

My questions are:
1. Is it possible the that the free calling areas are different for people given the 223 area code from the old 519 are code for Kitchener?
2. Is it possible that this issues related to the FIDO/ROGERS cell network and does not effect incoming landline calls?
3. Should I decide to transfer my 519-896-xxxx number to FONGO, will this resolve the problem?

Thanks.

[Jake]

While it is nice to be able to call most of the Canadian without paying long distance, one must also consider the impact in incoming calls. Frankly I dd not expect any. However.......

It seems that my (still existing - Bell) NPA-nnx 519-896-xxxx has a wider free calling area (for incoming calls) compared to my FONGO given 226-336-xxxx area code/number. I was really surprised when I tried to call my FONGO home number 226-336-xxxx from Cambridge, using my cell pone (FIDO/Rogers 519-729-xxxx). I was getting a message to wait till we complete your long distance call. I tried the call several times and I consistently received same message from the FIDO/ROGERS network.

When I call home using my cell from the same location (Hespeler Rd/401) or for that matter all the way from Guelph Lake the call is not considered long distance. It might be worth mentioning that when I call from my 519 (Bell) phone my 223 (VoIP) number or vice verse all calls work as local calls as expected.

My questions are:
1. Is it possible the that the free calling areas are different for people given the 223 area code from the old 519 are code for Kitchener?
2. Is it possible that this issues related to the FIDO/ROGERS cell network and does not effect incoming landline calls?
3. Should I decide to transfer my 519-896-xxxx number to FONGO, will this resolve the problem?

Thanks.

By the looks of it, a call to 226-336-xxxx from 519-729-xxxx should be local, and so free (ref: http://www.localcallingguide.com/lprefi ... xch=155080 < those should be all the numbers you can call for free from 519-729-xxxx)
This is not a fault of Fongo, but of Rogers not updating their rate table. You should call Rogers and tell them that you are being charged long distance for a local call and it should get corrected. If you have been charged for any calls others have mentioned that they might even reverse those charges.

[FONGO_mike]

This number is looking like it is free when i do a search in our system.
Can you PM me your number? I would like to test from your account if possible (please include a little reminder as to what the PM is for please as we receive a number of messages on any day)

[Bloodsong]

As Jake said, this is an issue with your cellular provider.

The rule of thumb is, if you place a call and are charged for it, it is the fault of the calling provider, not the receiving provider.

If your 226 number is indeed Kitchener-centric then it should fall within the LCA (local calling area) of any other Kitchener-centric location. Call your provider, in this case Rogers, and inform them that a Kitchener based number (provide them with the NPA-NXX) is being incorrectly charged. The squeaky wheel afterall.

In the meantime if you're not skittish, you could attempt to cold call a few other 226-336 phone numbers and see if you get the same long-distance issue, as this really should be in relation to the way that Roger's rate-table lookup is being done, and obviously need to be updated.

[godot2012]

By some "magic" the problem solved itself. All works now as it should I tried several times.

[TheHardy]

As I've posted countless times on other threads, incoming call issues to Fongo-numbers from NON-Fongo carriers are THOSE carriers NOT updating their 'Rates&Routing' table ... it lies solely with THOSE other carriers. Sometimes they are just slow to update, othertimes they are EXTREMELY slow. In all cases, a call to THEIR customer support # and filing a trouble ticket with THEIR Rates&Routing dept concerning your specific Fongo # not being a free call when it should be, SHOULD resolve the issue.

In my experience, with Telus Mobility, my avg turn around time is 48h; Bell Mobility is 72-96h ... Wind -- MONTHS

[godot2012]

Very useful suggestion.

Thanks

[TheHardy]

Very useful suggestion.
Thanks

Unfortunately, it is not a suggestion, it is actually THE ONLY fix. Unless the originating telco fixes it on it own, someone needs to let them know that it is broken in the first place! Like I say, "RATES & ROUTING" is the actual department ... what they do is manage the behind the scenes stuff as to which calls are free, which are toll, etc .... by default any new (not pre configured) number is TOLL until the system is told otherwise.

I do have more details and stuff in a few of my other posts previously, in case you are interested in the nuts and bolts of it all...