We are experiencing a strange issue and was wondering if anyone else has come across the same issue....
BES10, Exchange 2010
Users are unable to send/receive emails on the device for say about 1hr.
What we have found so far:
-This is a intermittent issue and can last from 15mins to 2hrs
-mostly happens when user is travelling but once back in wifi area, its OK
-sent emails show a 'clock' on the sent message but stays on the device and go fine once connected to wifi
-Also PIN to PIN messages are not delivered
- users can receive call or make calls, whatsapp works
all these users are on OS 10.3.2
no changes on our side have been made on BES so the only change is the OS - wondering if others have experienced any issues
Depending on the carrier, location and network congestion this can happen to the delivery. Carriers do delay data based on packet type if overloaded.
doing a search on the internet you will see this is a common issue. Sadly some carriers tell users it's caused by old SIM chips. Hopefully not all are that naive
I agree, however, we haae tried various different device models (all running 10.3.2) and new and old SIM - all still experiencing the same issues.
we know from the device losg collected from various users, that its showing "no carrier" and PIN to PIN messages failing also indicate its not our BES. since no changes have been made, the task now is to see if its the OS, hence wanted to see if anyone else has/is experiencing this issue.
I had a similar issue once, random connections, nothing made sense and in the end I told AT&T to remove all data plans from the line and rebooted phone. Then 30 minutes later I added in back the plan and all worked well. Seemed to be some lingering BIS connection on the account when I switched to a BES plan. We had same issue with one person going to iphone too. We were all on cingular years ago and AT&T bought them out. was odd to see my AT&T device boot up with Cingular logo
I had to fall
To lose it all
But in the end
It doesn't even matter
I have been working with BB support on this, and they think it could be a bug in the radio module of the 10.3.2 so their design team is investigating... I am very surprised that no one else has experienced this issue.
BB support confirmed others have reported the same issue and believe its probably something the carrier had changed since teehy are able to reproduce this issue. They have made changes and so far we havent had the issue