on 10-31-2011 7:19 PM
We have a custom iPad2 app that we've been using fine since July but suddenly around Oct 19th it quit working in both our production and development environments.
The strange thing is that only the Verizon 3G is the piece not working.
When an iOS(5 or 4.3.3) device on an Internet connected WiFi network syncs with our SUP instance, it works fine.
When WiFi is turned off on the iOS(5 or 4.3.3) device and that same device attempts to connect to SUP using Verizon 3G, the sync fails.
When a similarly configured iOS(5 or 4.3.3) device performs the same tests on AT&T iPad. SUP syncs fine both on WiFi and 3G.
The network infrastructure does not have any specific rules or routes to treat incoming 3G IP addresses differently from any other Internet address.
Is anyone else experiencing this or have any idea what could be going on?
Opened an OSS message and it turns out this is a known issue specific to Verizon 3G. Here is what SAP told us and their work around that fixed us:
This is a known issue with Verizon devices.
Issue:
On iOS devices using Verizon 3G and on some airlines's Wifi, data is not displayed on the devices. This impacts SUP applications - both Workflow and native apps.
Cause
Verizon has content filtering that blocks delivery of data on iOS
devices. Verizon acknowledged this issue but will have to manually
remove the content filtering for every device.
Work-around
Work-around is to configure the relay server to use a non default port
(other than 80). Engineering tested this workaround and confirmed that
this workaround resolves the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
98 | |
11 | |
11 | |
10 | |
10 | |
8 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.