The problem seems to have solved itself. On Wed, Apr 13, 2016 at 5:31 PM, Verizon Wireless Customer Support <