Tim -
My device did not re register on its own and required a powercycle. In order to figure this out I needed to place a call into a support to find out why I had the number is not in service message. Couple of problems with this - my number had a not in service message on it for the majority of the morning and the fail over did not kick in. I understand that there are going to be times when the service goes down, but it is my understanding that the failover should kick in and prevent any type of disconnect message or busy signal (in my case my failover is the voicemail system). Getting a "this number is no longer in service" message is not something that should ever go out.
Wondering why this message was sent out to callers? I understand that my device might have lost registration, but even without a powercycle it should still be active in VoIPo's servers just without a IP to send the calls to.
Also is it possible to implement some type of warning to users outside of the forums or users noticing there are problems? i.e. send a text message when a device loses registration or there is some type of outage? I am guessing that most people did not know there was a problem if they did not need to make a outbound call out this morning until someone called them on their cell phone and let them know. Something proactive like this should not only improve customer satisfaction but also lesson the load on your internal support personal which will free up internal resources when problems arise to fix them instead of deal with incoming customer calls/tickets. Something like this should have multiple ways of getting to customers with their choice of how to receive them - email, text message, forum posting - just making sure people can choose.
Bookmarks