310 numbers redux

[TheHardy]

I am revisiting the issue of 310 numbers and their non-dialability on the Fongo network. A plug-and-play approach finds that the only area code that works is 416-310-xxxx, with all others coming up as "not included in your tariff"

I understand the technicalities of 310 numbers and their "regional" nature. That being the case, I am wondering why they cannot be made to operate much like the current traditional wireline 3-1-1, 2-1-1, 8-1-1 types of services --- in the case of VOIP lines, it would either need to read one of two things: either the physical address supplied by the account holder, or the actual phone number, and route based on the geography of whichever choice is made ... therefore people with a registered VANCOUVER-area address would reach the Vancouver 2-1-1 service, BC-based 310- numbers etc (or alternately, 604/778 area coded numbers would reach those...).

With 310-numbers you can even go a step further, and require them to be dialed as 10D numbers with the leading area code to assist in routing them to the correct region.

The reason that I bring this up AGAIN, is the widespread use of 310-numbers and the round-about quest that one must embark upon to locate the correct 10D equivalent number. Ever try to reach customer service for say cable tv, landline (Bell/Telus/Aliant) or restaurants and other services whom ONLY advertise or supply 310-numbers?

As most cellular providers already offer service to 310-numbers based on the geography of the processing cell site, it should not be that hard to implement a translation over VOIP based on area codes ....

And even though the "number dip" may result in the call being routed to the incorrect primary telephone number based on the large geographical swath, whomever you do contact is THEN usually able to either transfer you to the correct local, or at least provide you at that point with the correct 10D number to reach the service you are trying to reach.

This is becoming an issue as several GOVERNMENT agencies begin to use 310 numbers (so it is MORE critical to be able to reach them, than just the local pizza joint!).

Hopefully this does not fall on deaf ears and is taken as a serious request for service improvement!

[TheHardy]

A week ... no official Fongo reply. Not surprised. I know it is a low priority thing, and with all the other massive failings going in, rates very low. But no acknowledgement or anything. Maybe I say too much and my stuff gets lost in the clutter ... ???

[FONGO_steve]

This will certainly be taken into consideration for future updates to the service. However, the time that would be required to develop such a system means that it won't be happening overnight by any means 310 numbers are often not supported by VOIP providers (it can be hit and miss) and at this time we do not provide any official support for 310 numbers even though some users have managed to find a way to make the occasional one work by adding an area code in front.

[TheHardy]

This will certainly be taken into consideration for future updates to the service. However, the time that would be required to develop such a system means that it won't be happening overnight by any means 310 numbers are often not supported by VOIP providers (it can be hit and miss) and at this time we do not provide any official support for 310 numbers even though some users have managed to find a way to make the occasional one work by adding an area code in front.

Parsing thru your tariff sheet (COMPLETE one) and assuming it is accurate, the only NPA-310 that is $0.00 is 416-310 ...

Again, as I have previously stated, if the 310 numbers are PROVINCIAL in nature by the ILEC, then it should be no problem to "force" Fongo customers to dial the "7-digit" 310 number as a 10-D 310 number and then route it to the major city in that area code in which Fongo has coverage.

I am not a telco genius or employee by any means, but following this logic, there are currently only _36_ active or PENDING area codes for all of Canada ... so that is only 36 direct translation entries into the rates-routing database ... if there is already the provision for the few existing 3-1-1 numbers (as previously confirmed) then _36_ 310 numbers cannot be THAT huge a deal ... you would not even have to parse the callers "home" area code from their call if you did not want to go that far, just FORCE the caller to dial it as a 10D call indicating the regional location that they wish to route their 310 call to ...

Then if it works (which 90+% of the time it will, if it is routed to a major city in that area code, by the very nature of the way 310 numbers work), the terminating carrier will complete the call successfully.

FONGO gets around this by saying "While '310' calls are officially unsupported, and we cannot guarantee that 310 calls will work, we have made our best effort to support, route, and complete them within our current infrastructure. Please be aware of this limitation for '310' numbers when dialing them, and use them at your own risk." (or something along those lines, please ask your legal department...).

Know what I mean? Best effort ... seemingly (to me) simple solution. And as they should, according to the tariff crap I have read from other *LEC's terminate as local calls, there should not be a residual billing issue ...

I may have missed something, but it is neither like re-inventing the wheel ...

Just my two-non-technical "arm chair quarterback" cents worth ...

Thanks tho for taking it under advisement, and I realize it is not OVERNIGHT ... and it doesn't really need to be 100%, just better than _0%_ ...

[TheHardy]

The # 36 came from the CNAC website ....

204
226
236
249
250
289
306
343
365
403
416
418
431
437
438
450
506
514
519
579
581
587
604
613
639
647
705
709
778
780
807
819
867
873
902
905

(ref URL http://www.cnac.ca/co_codes/co_code_status_map.htm)