Ask
Reply
Solution
06-10-2010
04:56 PM
- last edited on
14-07-2014
04:53 PM
by
Jenny
This issue has the following symptoms:
For version 1 Sure Signal (the one with four lights on the front):
For version 2 Sure Signal (the one with 3 lights on the front):
For version 3 Sure Signal (the plug in version):
Troubleshooting steps:
Check for planned maintenance:
Planned maintenance can cause periods of downtime, so check the forum for any planned maintenance. If there is, this will be announced at the top of the Sure Signal forum.
Reset your Sure Signal:
For versions 1 and 2:
For version 3:
The Sure Signal will be back online in around 1 hour.
If you’re still unable to make calls, there may be a compatibility issue with your Sure Signal and your location information (also known as SAC/LAC compatibility).
A SAC (Service Area Code) connects to a mast and is used to determine the rough location of where a call’s made. It's needed for the emergency services to know where a call was made from.
As a Sure Signal can be used anywhere in the country, it doesn't automatically come with a SAC. The SAC is generated based on the postcode you enter when registering your Sure Signal and it's created based on the nearest cell to your location.
In order for calls to be made, they must go over an MSC (Mobile Switching Centre). If the MSC doesn't hold the SAC for your area on its database, the call will fail.
The MSCs should now hold all SACs for Sure Signal calls. For anyone who is still affected please post in this thread and we can look into it further.
Thanks,
Jenny
04-08-2011 12:33 PM
Lee,
My experience has been exactly the same as yours. Before upgrading to iOS 4.3.5, I could repeatably reproduce the problem with my SSv1. If I hadn't used my iPhone for a while, the first call would always fail, then callback would always work. I've had iOS 4.3.5 installed a few days now. I've only had two failed calls in that time, while many calls have connected first time.
Dewi
04-08-2011 04:56 PM
05-08-2011 12:11 PM
Further update - I reproduced the result with my wife's iPhone4 with the same results - that phone was on 4.3.4 and was having the call connection issues when connected to the VSSv1.
Upgrading the phone to 4.3.5 seems to have fixed the issue.
Still a bit worried about it in case Apple change something back in the next patch and also, given the intermittent behaviour, it's hard to say for sure unless we know what's caused the problem and it has actively been resolved.
Best regards
Lee
05-08-2011 02:45 PM
My iPhones are on 4.3.5 and have the problem every day, both "called failed" on outbound and callers going direct to VM inbound. That is when the iPhones/iPads actually flip over to use the SureSignal box at all - most of the time they don't which is also documented within this thread.
05-08-2011 06:57 PM
06-08-2011 02:13 PM - edited 06-08-2011 02:14 PM
Six failed calls so far today, no sign of a fix. I'm on the latest iOS and have been for a while. Farce.
06-08-2011 11:03 PM
09-08-2011 08:21 AM - edited 09-08-2011 08:21 AM
Hi Guys.
Just to let you know I do not have any more information at this moment in time. All the examples have been passed over to our support teams and we request updates into this issue on a daily basis. As soon as we can have any further information I will update the thread.
Regards
Trev
eForum Team
15-08-2011 11:06 AM
I've been following this thread, as I too am having exactly the same issues - namely, outbound calls always fail the first time (but work quite straightforwardly on 2nd and subsequent attempts) and then, much more frustratingly, once the outbound call is connected, more often than not the call is dropped, and Sue Signal resets itself. The only way I have found of quickly recovering the call is to unplug Sure Signal and hope that the very weak reception that I have without it is sufficient for me to make the call. Like so many others who have posted here, all of this is enormously frustrating - when Sure Signal and my iPhone 4 do work it is an excellent service. Does anyone have any idea how much longer we will all have to wait for this problem to be resolved?
17-08-2011 02:55 PM
@nicholasreeves wrote:Does anyone have any idea how much longer we will all have to wait for this problem to be resolved?
No. Nobody does. None of the staff, who told us the issue had been identified over three weeks ago. Nobody here does.
Face it, it's another of those issues that isn't affecting enough people for Vodafone to care or do something about it. They'll say they care, they'll say they're working on it, but all evidence, once again, points to the contrary.