Do not disturb not working in iOS 7

Ok guys I have an update for you. No surprise but I to a rogers txt telling me my ticket was closed, even though tier 2 told me yesterday that I would be contacted personally with a follow up. When I called rogers back, tier 1 suggested they route my call to the Wireless Customer Advocacy Group. They have higher authority than tier 2 and work to escalate issues and promised to personally follow up with me on Tuesday next week. They agreed that the workaround of disabling name display is not a valid solution, and that they will follow up with their engineers and reach out to apple to work on a resolution. Unlike apple senior support, they do not communicate via email nor do they have dedicated phone numbers, but they promised me that this group is designed to work 1-on-1 with customers facing issues that are not being resolved. So it's really starting to sound like we're getting some momentum going here. If you have a rogers ticket which is no doubt closed, please call them back and request to speak to this customer advocacy group. They will reopen the ticket and claim to keep it open until the matter is fixed.

yes, DND feature seems unreliable

thanks for the info

I am on an iphone4, with ios7

set up to allow calls from all contacts

using it this way all of the time

the feature sometimes works and sometimes it doesn't

frequently, calls come through that are not in my contacts

but what seems like about half the time, it works perfectly, and these calls show up as missed calls, without ringing

this is a pretty simple application really, if you are in my contact list, my phone should ring, but if you are not, then go directly to voicemail. I hope they fix it. And it sounds like many people with newer phones are having similar issues.

I may try the wiping thing, and starting over, maybe without restoring back up, but this sounds like a full day of work

I look forward to someone, maybe even apple, coming up with a fix, because this is a great idea for a feature.

@hcharton Are you on Rogers or Fido? If so, there is a known issue in iOS 7 where Rogers Name Display causes iPhone DND and Call Block to not work properly on incoming calls containing names as part of the Caller ID. It's not about newer phones, it's about the latest iOS. See earlier posts in this thread. The workaround is to have Name Display temporarily disabled on your Rogers/Fido wireless account.

Here's an email I received today from a supervisor at Apple....

Hello Peter,

Hope all is well. I wanted to follow up with you about the conversation we had on Tuesday about your Do Not Disturb feature. I was able to get a reply for the engineers and there is currently an open ticket already active for this issue. Apple is still investigating the issue, and is working quickly to resolve it. When more information is available I will follow up with you. Once again, I apologize about the inconvenience in this matter.

Sincerely,

Monica Jones

Apple

P.S If you need to contact me about your case, please contact me at 1-877-416-4271 Ext. 68285. I work Sunday-Thursday 1:00 pm - 9:30 pm EST. If you reach my voicemail, please leave your name, phone number, case number, and the best time to reach you.

Need help with a different issue? Save time by starting your support request online.

Contact Apple Support

Wow. My wife and I were both so irritated that our DND is no longer working (she has an iPhone 5 and I have an iPhone 5S). I thought it may have been something new on iOS 7. But alas, I think it's a bug in the "Carrier Update" pushed by Rogers. If you go into Settings->General->About you will see a section called "Carrier" and it will say Rogers 15.5. I think in this latest update, they broke it with new accounts. I had a 3 year plan before and had no problems, but when I switched to a share everything plan, I noticed this. Maybe it was coincidental.

Is everyone on here using a 2 year plan or Share Everything plan?

Btw, I'm glad there's all of you having the same problem and getting on Rogers/Apple to fix this!

I'm having the same problems except I'm with T-Mobile and I have 15.5 in mine i'm also in the family plan to

Update

went to apple they send it is was t-mobile and not the phone. tmbole said its apple and replaced the phone. When i got the new iphone audio problem. then went back to apple and got the phone replace and they said that they where coming out with a fix not just my iphone is not working now is my ipad ad ipod on do not disturb feature.

After waiting for months for iOS 7.1 to finally offer a fix for this DEFECT I am sorry to say it does not. The problem persists. At this point I don't care who's fault it is, Apple's or Rogers. This is unacceptable. Doesn't Apple have the wherewithal to strongarm Rogers to the repair bench!?

Apparently not.

That's annoying. And this problem is definitly Apple's problem. I can only speculate that the fault of Rogers and some other carriers is that there is probably an urgent-flag with the paging request during phone calls and Rogers/et.al. are incorrectly issuing this flag with every call. Apple can ignore such situations or give the user the option to take calls with such flags.

In any case, there's no reason Apple cannot apply a fix that ignores phone calls when in 'Do No Distrub' mode, as is expected from all users.

Given that this "bug" is pretty much limited to Rogers and affiliates, and is not occurring anyplace else, how do you reach the conclusion it is Apple's problem? And why would Apple withhold DND from Roger's subscribers, what do they gain by doing this?

As was previously discussed, it appears to be Rogers 'Name Display' feature that causes the problem and some have had this disabled in order to regain a functioning DND.

However there was no such issue with iOS 6. DND worked perfectly even with Name Display. To me that suggests Apple and Rogers working together should be able to solve this.

I just explained my speculated source of the bug. As a software engineer with a focus on wireless networks (and a familiarity with GSM/3G/LTE), I am quite confident in my assertion. Furthermore, 'Do Not Disturb' mode is a feature in iOS that is unknown to the baseband processor, the low power, simplified processor that checks the GSM paging channel for notifications such as phone calls and messages, maintains a list of towers for seamless roaming (in the general sense), etc. So when your number is called, the next time the baseband processor wakes up to check the paging channel, it sees a notification for your number, it then establishes a connection to the tower and checks what notification it is, determines its a phone call, wakes the CPU which gets an interrupt that makes it communicate with the baseband processor. Once the CPU determines that there's an incoming phone call, it SHOULD check if the 'Do Not Disturb option is set and not make a sound, buzz, or turn on the screen, but otherwise proceed as usual.

What I suspect is that there is more meta data to a phone call (my speciality is mostly data, not voice) and that there may be an urgent flag that Apple decided to implement and ignore the "Do No Disturb" mode. But if the carriers are incorrectly using such a flag (lets say it's part of the standard but not popular), that MAY explain what is going on. Again this is speculation. If the problem is because of a flag that Apple decided to religiously use, they should give the option to the user to adhere to urgent calls. Another option is to contact carriers and let users know that the carriers are making the change to adhere to such a flag. Or as a last resort, Apple should do as their old baseband firmware did, and ignore such flags.

That's the long winded explanation of what may be going on. Whatever the case, the ball is in Apples court, which is why I'm particularly frustrated with their stubbornness with this problem. It's a problem and it requires a fix. How they go about fixing it is up to them.

Edit: If 'Name Display' causes the problem to be manifested, then it most likely is a problem with the baseband firmware sending an improper flag or the processor skipping over the 'Do Not Disturb clauses when it does a 'Name Display' branch of code. In every case, it's still Apple's fault since 'Do Not Disturb' mode is not a carrier feature, it's an iOS feature.

Your explanation points out why the ball would be in Rogers court, not Apple's.

Thats what everyone keeps telling me

FluxArc wrote:

it's still Apple's fault since 'Do Not Disturb' mode is not a carrier feature, it's an iOS feature.

And I'm on T-Mobile with my grandma and now my iPad and iPod are having problems

Good people, this issue is an apple problem. It has nothing to do with any carrier. I have Att in California. My DND feature does noel reliably. Other people in other places on various carriers have similar problems. Apple admits to having an open fix it ticket on this very thread. My phone sees a caller I'd and should not allow a call to come through that is not already in my contacts. But my apple phone frequently does allow these calls through. That is because their software doesn't work perfectly. And it is no secret that the test many times before releasing a product mentality, that rescued Apple, is no longer a priority for them. Maybe we will all get frustrated enough to buy a differently branded diss appointment.