This is a known issue that AT&T is investigating. No ETA on a fix, though.