Verizon tech support has marked the thread with this title as SOLVED. It is DEFINITELY NOT solved and the title should be changed to reflect that fact. All you have to do is read the thread AFTER it was supposedly solved to see the problem is not solved and appears to be ignored by Verizon at this point.
It's disappointing (at the very least) to see this thread marked as solved and no communication to those of us that have reported the problem and continue to "work around" the issue.
Since Verizon tech support was so quick to call this solved, how about stepping up to the plate and telling us what's REALLY going on. Is this going to be fixed or not????