Is there a problem with service today?

[rfgrossi]

I can access voice mail but can't make any outgoing calls as of this morning (March 28, 2012) in London, ON.

[tbrummell]

Working fine for me.

[rfgrossi]

Still having a problem here. Glad to hear yours is working though. As mentioned earlier, voice mail works perfectly. Outgoing calls to non FPL numbers will either go straight to a busy signal or a recorded message "The number you have dialed is incorrect..."

Worked perfectly last night.

[guy009]

Having the same problem this morning here.

[guy009]

Having the same problem this morning here too

[Steve_K]

I'm having the same problem. I'm in London, too.

[maxkuku]

The same problem in Toronto now but the incoming call is fine

[maxkuku]

Thank you Steve

[cu2o2o2]

Around 7:30A.M. today, I get the message, "Blah, blah can not be completed as dialed". From my cellphones the call would go through. FPL to FPL calls also go through.

FPL is my primary phone but am glad that each family member has a cellphone as backup.

[FONGO_steve]

It appears as though certain outbound calls routing through a specific system are encountering the occasional failure - teams are actively investigating as we speak.

[cu2o2o2]

Update:

9:07 A.M.

Incoming calls work. Outgoing calls to non-FPL number do not work. The calling party using FPL would hear a normal ring however the called party's phone never rings (tested on Mobilicity, Speakout, Bell landline).

[hanke]

I have same problem here In Burlington. Sorry call cannot be completed as dialed message.

Update - As of 930am...outbound calls seem to working now.

[rfgrossi]

It appears as though certain outbound calls routing through a specific system are encountering the occasional failure - teams are actively investigating as we speak.

Thanks for letting us know! Patienly waiting a return to normal service.

[cu2o2o2]

Yes, mine too! Incoming and outgoing calls are working now. Thanks. 9:31 A.M.

[rfgrossi]

Back up and running! Thanks Freephoneline, or Fongo...or FONGO_steve!

[FONGO_steve]

This should have been resolved about ~30 minutes ago - all internal tests are clear.

[dks]

Oh good. This morning I was able to call Ottawa, but non of my Halifax numbers would work. They are working now. This is the first time for me to experience downtime with this service.

[TheHardy]

It appears as though certain outbound calls routing through a specific system are encountering the occasional failure - teams are actively investigating as we speak.

Hi Steve -- although I was at work and this did not affect me, I am interested in this issue a bit ... "CERTAIN OUTBOUND" ..."SPECIFIC SYSTEM".

How does Fongo handle outbound calls? Is it based on the Fongo/FPL # that calls OUT (ie: like say 3-1-1 access, based on geography of the #), or is it based on the IP-geo-address of the ORIGINATION point of the call/internet connection? Or is it based on the DESTINATION # entered?

I ask so that us mere users can have a better understanding of "things under the hood" and what may cause failures or certain errors.

For an example, how are the following calls handled by Fongo?

A1) Vancouver-BC-based FPL # calling (from Vancouver area) to a Vancouver-based-Telus-landline?
A2) Toronto-ON based FPL # calling (from Vancouver area) to a Vancouver-based-Telus-landline?

B1) Vancouver-BC-based FPL # calling (from Vancouver area) to a Calgary-based-Telus-landline?
B2) Toronto-ON based FPL # calling (from Vancouver area) to a Calgary-based-Telus-landline?

C1) Vancouver-BC-based FPL # calling (from Vancouver area) to a Toronto-based-Bell Mobility-mobile?
C2) Vancouver-BC-based FPL # calling (from Calgary area) to a Toronto-based-Bell Mobility-mobile?

D1) Vancouver-BC-based FPL # calling (from Vancouver area) to a Vancouver-based-Telus-landline?
D2) Vancouver-BC-based FPL # calling (from Vancouver area) to a Toronto-based-Bell-landline?

Changing the variables, interested as to how the NETWORK decides which "SYSTEM" to send the call to ... follow what I am after??

Maybe I am asking too technical a question ... maybe I just like to know too much how things work. I have an idea how it all works for POTS ILECs and also for (Telus) MOBILITY operations, as I have had to trouble-shoot with their respective NOCs on connection issues, but the whole VOIP thing is all "Wizard of Oz" to me ...

[FONGO_steve]

Unfortunately I'm not at liberty to publically discuss our infrastructure - sorry.

[TheHardy]

Unfortunately I'm not at liberty to publically discuss our infrastructure - sorry.

Okay, fair enough. Can I get a vague answer then, if I two-point it?

"Is the outbound call routing based MORE on the originating NUMBER or on the PHYSICAL LOCATION of either the ORIGINATION or TERMINATION number?"

Is that vague enough to be able to get an answer?

I appreciate the proprietary nature of some information, but as I am somewhat newer to VOIP than other services, I am trying to get a handle on some of the nuts and bolts.

[wwooda]

I'm in Kingston. Incoming calls work fine. Out calls go directly to fast busy, including 898 dialing to voicemail. Worked fine until I recieved an email stating my land line would be ported on Mar 23 (tomorrow). Are these related?

[wwooda]

sorry, that's *98 to voicemail.

[Fongo Support]

sorry, that's *98 to voicemail.

Hi there,

Looks like your ATA is no longer connected to our servers.

Have you tried a power off for 10 minutes?

Let me know.

Thanks,

[wwooda]

Powered off ATA for 10 minutes, reconnected power, waited 5 minutes, no change. Still get fast busy when anything dialled. Incoming calls still work fine.

[Fongo Support]

Powered off ATA for 10 minutes, reconnected power, waited 5 minutes, no change. Still get fast busy when anything dialled. Incoming calls still work fine.

Hi there,

If that's the case, I suggest to open a support ticket for this issue:

http://support.fongo.com/anonymous_requests/new

Once you have the ticket#, please send me a PM:

http://forum.fongo.com/ucp.php?i=pm&mode=compose&u=7852

Thanks,