Some of you may already be aware that more carriers other than Verizon now support OTASL. I, unfortunately, was not one of those until I started poking around earlier this evening.

To figure out nearly all of this information, you can look in the BES tables with the DSU prefixes. I'm not sure if someone wants to do some mining on these tables to make use of them outside of BlackBerry Manager, but nevertheless, I will keep this information as updated as possible.

North America
AT&T
OTASL: Yes
Device: BlackBerry Bold 9700
Device OS: 5.0.0.296 (Apps) / 5.1.0.83 (Platform) / 5.0.0.463 (Package)
OTASL Version: 5.0.0.405 (Apps) / 5.1.0.112 (Platform) / 5.0.0.645 (Package)

Device: BlackBerry Bold 9000
Device OS: 4.6.0.154 (Apps) / 4.0.0.152 (Platform) / 4.6.0.282 (Package)
OTASL Version: 4.6.0.167 (Apps) / 4.0.0.157 (Platform) / 4.6.0.298 (Package)

Device: BlackBerry Bold 9000
Device OS: 4.6.0.167 (Apps) / 4.0.0.157 (Platform) / 4.6.0.298 (Package)
OTASL Version: 4.6.0.167 (Apps) / 4.0.0.217 (Platform) / 4.6.0.438 (Package)

Device: BlackBerry Bold 9000
Device OS: 4.6.0.167 (Apps) / 4.0.0.157 (Platform) / 4.6.0.298 (Package)
Device OS: 4.6.0.167 (Apps) / 4.0.0.217 (Platform) / 4.6.0.438 (Package)
OTASL Version: 4.6.0.297 (Apps) / 4.0.0.243 (Platform) / 4.6.0.508 (Package)

Device: BlackBerry Bold 9000
Device OS: 4.6.0.167 (Apps) / 4.0.0.157 (Platform) / 4.6.0.298 (Package)
Device OS: 4.6.0.167 (Apps) / 4.0.0.217 (Platform) / 4.6.0.438 (Package)
Device OS: 4.6.0.297 (Apps) / 4.0.0.243 (Platform) / 4.6.0.508 (Package)
OTASL Version: 4.6.0.297 (Apps) / 4.0.0.247 (Platform) / 4.6.0.517 (Package)

Device: BlackBerry Bold 9000
Device OS: 4.6.0.167 (Apps) / 4.0.0.157 (Platform) / 4.6.0.298 (Package)
Device OS: 4.6.0.167 (Apps) / 4.0.0.217 (Platform) / 4.6.0.438 (Package)
Device OS: 4.6.0.297 (Apps) / 4.0.0.243 (Platform) / 4.6.0.508 (Package)
Device OS: 4.6.0.297 (Apps) / 4.0.0.247 (Platform) / 4.6.0.517 (Package)
OTASL Version: 4.6.0.304 (Apps) / 4.0.0.247 (Platform) / 4.6.0.519 (Package)

Device: BlackBerry Curve 8900
Device OS: 4.6.1.152 (Apps) / 4.2.0.91 (Platform) / 4.6.1.241 (Package)
OTASL Version: 4.6.1.199 (Apps) / 4.2.0.102 (Platform) / 4.6.1.307 (Package)

Device: BlackBerry 8820
Device OS: 4.5.0.110 (Apps) / 2.7.0.90 (Platform) / 4.5.0.152 (Package)
OTASL Version: 4.5.0.182 (Apps) / 2.7.0.106 (Platform) / 4.5.0.306 (Package)

Device: BlackBerry Curve 8320
Device OS: 4.5.0.110 (Apps) / 2.7.0.90 (Platform) / 4.5.0.152 (Package)
OTASL Version: 4.5.0.182 (Apps) / 2.7.0.106 (Platform) / 4.5.0.306 (Package)

Device: BlackBerry Curve 8310
Device OS: 4.5.0.110 (Apps) / 2.7.0.90 (Platform) / 4.5.0.152 (Package)
OTASL Version: 4.5.0.182 (Apps) / 2.7.0.106 (Platform) / 4.5.0.306 (Package)

Device: BlackBerry Pearl 8120
Device OS: 4.5.0.110 (Apps) / 2.7.0.90 (Platform) / 4.5.0.152 (Package)
OTASL Version: 4.5.0.182 (Apps) / 2.7.0.106 (Platform) / 4.5.0.306 (Package)

Device: BlackBerry Pearl 8110
Device OS: 4.5.0.158 (Apps) / 2.7.0.106 (Platform) / 4.5.0.252 (Package)
OTASL Version: 4.5.0.182 (Apps) / 2.7.0.106 (Platform) / 4.5.0.306 (Package)

Verizon
OTASL: Yes
Device: BlackBerry Pearl 8230
Device OS: 4.6.1.234 (Apps) / 3.3.0.78 (Platform) / 4.6.1.357 (Package)
OTASL Version: 4.6.1.309 (Apps) / 3.3.0.95 (Platform) / 4.6.1.454 (Package)

Device: BlackBerry Storm 9530
Device OS: 4.7.0.65 (Apps) / 4.0.0.82 (Platform) / 4.7.0.92 (Package)
Device OS: 4.7.0.75 (Apps) / 4.0.0.94 (Platform) / 4.7.0.107 (Package)
OTASL Version: 4.7.0.148 (Apps) / 4.0.0.181 (Platform) / 4.7.0.203 (Package)

Device: BlackBerry Tour 9630
Device OS: 4.7.1.40 (Apps) / 4.1.0.40 (Platform) / 4.7.1.77 (Package)
Device OS: 4.7.1.53 (Apps) / 4.1.0.65 (Platform) / 4.7.1.105 (Package)
Device OS: 4.7.1.61 (Apps) / 4.1.0.75 (Platform) / 4.7.1.117 (Package)
OTASL Version: 4.7.1.61 (Apps) / 4.1.0.81 (Platform) / 4.7.1.124 (Package)

Sprint
OTASL: Yes
Device: BlackBerry Curve 8350i
Device OS: 4.6.1.83 (Apps) / 3.0.0.41 (Platform) / 4.6.1.142 (Package)
OTASL Version: 4.6.1.128 (Apps) / 3.0.0.62 (Platform) / 4.6.1.225 (Package)

Device: BlackBerry Curve 8350i
Device OS: 4.6.1.128 (Apps) / 3.0.0.62 (Platform) / 4.6.1.225 (Package)
OTASL Version: 4.6.1.204 (Apps) / 3.0.0.73 (Platform) / 4.6.1.316 (Package)

Device: BlackBerry Curve 8350i
Device OS: 4.6.1.204 (Apps) / 3.0.0.73 (Platform) / 4.6.1.316 (Package)
OTASL Version: 4.6.1.313 (Apps) / 3.1.0.31 (Platform) / 4.6.1.459 (Package)

Device: BlackBerry Pearl 8130
Device OS: 4.5.0.131 (Apps) / 3.4.0.25 (Platform) / 4.5.0.188 (Package)
OTASL Version: 4.5.0.175 (Apps) / 3.4.0.55 (Platform) / 4.5.0.295 (Package)

Device: BlackBerry 8830
Device OS: 4.5.0.135 (Apps) / 3.4.0.28 (Platform) / 4.5.0.201 (Package)
OTASL Version: 4.5.0.175 (Apps) / 3.4.0.55 (Platform) / 4.5.0.295 (Package)

Device: BlackBerry Curve 8330
Device OS: 4.5.0.131 (Apps) / 3.4.0.25 (Platform) / 4.5.0.188 (Package)
OTASL Version: 4.5.0.175 (Apps) / 3.4.0.55 (Platform) / 4.5.0.295 (Package)

Device: BlackBerry 8830m
Device OS: 4.5.0.135 (Apps) / 3.4.0.28 (Platform) / 4.5.0.201 (Package)
OTASL Version: 4.5.0.175 (Apps) / 3.4.0.55 (Platform) / 4.5.0.295 (Package)

Device: BlackBerry Curve 8330m
Device OS: 4.5.0.131 (Apps) / 3.4.0.25 (Platform) / 4.5.0.188 (Package)
OTASL Version: 4.5.0.175 (Apps) / 3.4.0.55 (Platform) / 4.5.0.295 (Package)

Device: BlackBerry Tour 9630
Device OS: 4.7.1.40 (Apps) / 4.1.0.40 (Platform) / 4.7.1.77 (Package)
OTASL Version: 4.7.1.57 (Apps) / 4.1.0.70 (Platform) / 4.7.1.110 (Package)

Asia Pacific
CSL
OTASL: Yes
Device: BlackBerry Bold 9000
Device OS: 4.6.0.162 (Apps) / 4.0.0.155 (Platform) / 4.6.0.292 (Package)
Device OS: 4.6.0.190 (Apps) / 4.0.0.172 (Platform) / 4.6.0.331 (Package)
Device OS: 4.6.0.216 (Apps) / 4.0.0.183 (Platform) / 4.6.0.365 (Package)
Device OS: 4.6.0.247 (Apps) / 4.0.0.206 (Platform) / 4.6.0.418 (Package)
Device OS: 4.6.0.266 (Apps) / 4.0.0.223 (Platform) / 4.6.0.451 (Package)
OTASL Version: 4.6.0.282 (Apps) / 4.0.0.235 (Platform) / 4.6.0.477 (Package)

Device: BlackBerry Curve 8310
Device OS: 4.5.0.108 (Apps) / 2.7.0.89 (Platform) / 4.5.0.150 (Package)
OTASL Version: 4.5.0.176 (Apps) / 2.7.0.105 (Platform) / 4.5.0.297 (Package)

NTT DoCoMo
OTASL: Yes
Device: BlackBerry Bold 9000
Device OS: 4.6.0.224 (Apps) / 4.0.0.187 (Platform) / 4.6.0.378 (Package)
Device OS: 4.6.0.224 (Apps) / 4.0.0.216 (Platform) / 4.6.0.442 (Package)
OTASL Version: 4.6.0.294 (Apps) / 4.0.0.230 (Platform) / 4.6.0.504 (Package)

Latin America
Telefonica
OTASL: Yes
Device: BlackBerry Curve 8310
Device OS: 4.5.0.108 (Apps) / 2.7.0.89 (Platform) / 4.5.0.150 (Package)
OTASL Version: 4.5.0.176 (Apps) / 2.7.0.105 (Platform) / 4.5.0.297 (Package)

Device: BlackBerry Bold 9000
Device OS: 4.6.0.162 (Apps) / 4.0.0.155 (Platform) / 4.6.0.292 (Package)
OTASL Version: 4.6.0.266 (Apps) / 4.0.0.223 (Platform) / 4.6.0.451 (Package)

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

So it appears that I learned something else about OTASL. It apparently will only populate the database with the information from devices that are actually on the BES server at the time of the update (from what I can tell, if a device was previously on the BES server and the DSU table was updated for that device, it is not purged once that device is removed). I can only make this assumption based on one of my colleagues purchasing a Verizon Storm while visiting the States a couple months ago and activating it in Hong Kong when he returned to his 'home away from home'. Due to this discovery, I have added a section for CSL, as well.

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

can this information be added to the Database so that it allows the upgrade via the besmanager

This information is found in the database and initiated through BlackBerry Manager and/or BlackBerry Administration Service. If you're talking about them being converted to a software configuration, then no. These are 'delta' updates that will rely on the exact package/applications/platform versions for both the current and new device software in order to make only the changes that are needed from one version to the other. These can only be initiated by the administrator and then the device will query RIM's servers for the update.

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

Hi Everyone,
Anyone know if there is site that list which carriers support OTASL Globally?

Once's I'm personally curious to know about:

• Canada - Rogers Wireless
• EU - T-mobile
• Switzerland - Swisscom
• Singapore - Starhub

M@

There's nothing that I'm aware of, hence this list. We have a fairly distributed environment across the globe, so I would imagine that it is about as close as such a list can be. We're looking to see if there's a way to manually query the OTASL server to get a full overview of what is available. More to come (hopefully).

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

4.6.0.297 (AT&T) is now available for OTASL.

Attached Thumbnails

 

__________________

AT&T launched this for the Bold earlier, so that's what it is. I'll update my list when I get into the office. They haven't posted it to the website yet, but it is available from the device.

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

Oddly enough, it's not showing up in my production environment. According to RIM's document on wireless software upgrades, it has the following line:

The BlackBerry® Enterprise Server contacts the BlackBerry Infrastructure
once daily to check for updates to the software upgrade packages.

I'm not sure if there is a way to force these. I'm on with DART now to see if there is, as I'm more than interested in getting this to my users.

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

Otto, it took me a few refreshes to get it to show up.
Eventually I got it working. I have two users in the middle of the OTA upgrade right now. One is in Japan, so I have my fingers crossed that it goes through without a hitch.

__________________

It's showing up in BES 5.0, but not in BES 4.1.x. I found the timestamp for the last refresh in the database and it should have refreshed again 3 minutes ago. But, it didn't find it. Here's the latest timestamp: Tue, 25 Aug 2009 14:06:14 UTC (1251209174).

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

Ah, look at that.
I only checked my BES 5 box. You're right... not finding anything on the 4.1.6 server.

__________________

FYI, you can check the OTASLLastRefreshTime by looking at the HandheldMgmtConfigProperties column in the GlobalSettings table in the database. An example would be:

SQL Query:
SELECT HandheldMgmtConfigProperties
FROM GlobalSettings

You can then take that time and convert from Unix time by pasting it in the following website:
http://www.onlineconversion.com/unix_time.htm

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

FYI, setting the policy option to Allow Non Enterprise Upgrades does, in fact, allow the users to bypass the BES to get the update. However, I believe this means that no information for that user's upgrade will be available should something go wrong and need to be looked into further.

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

mine updated last night around 7PM and the refresh timer is 24 hours so i guess i will have to wait till tonight.

i did set allow non-enterprise upgrade to yes, however if you do so be aware it could cause some lag in your bes since it has to resend policy to every user then.

EDIT: check that, forgot to convert from GMT, 2:30PM yesterday. so i guess i'll wait another hour and see...

__________________
Two months ago, I saw a provocative movie on cable TV. It was called The Net, with that girl from the bus.

*taps fingers*

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

i think i was wrong again. stupid daylight savings time. i'm not having a good day. waiting till 3:30 ::facepalm::

__________________
Two months ago, I saw a provocative movie on cable TV. It was called The Net, with that girl from the bus.

*taps fingers again*

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

well my timestamp updated but its still not available in bes manager 4.1.6

Instant Fail

__________________
Two months ago, I saw a provocative movie on cable TV. It was called The Net, with that girl from the bus.

Thanks for checking man. I just checked my last domain that would be updating today and nada! It'd be one thing if this only limited my ability to send the update request from the server, but this is actually preventing the basic essence of OTASL in our environment (we don't have the policy option enabled, as it shouldn't need to be, to be honest) with users requesting it from their own devices! So annoying!

...and I feel like I've been banging my head against the wall with the ticket I have open. Sigh.

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

No update here in 4.1.6, though if you run the update twice from the handheld it downloads the new update. Very strange

__________________

Do you also have the 'Allow Non Enterprise Upgrade' enabled in the IT policy? I've yet to be able to get the update otherwise, and I've tried no less than 30 times on one of my colleague's Bold.

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

why cant you just change the policy? its not like ur disabling the password requirement or something.

__________________
Two months ago, I saw a provocative movie on cable TV. It was called The Net, with that girl from the bus.

I agree. But pushing the policy to every user on the environment would be a bit of an overhead on the Policy Service that I don't care to make if it's not needed. Not to mention that I would have to put in a change control to make the change, which would mean it would be a week out, etc. Plus let's really get down to the point that there is an obvious issue with this version of BES and RIM's infrastructure.

...and let's not forget that the policy option in question, which appears to be confusing in its vagueness, basically implies that carriers will be able to push upgrade requests to the devices, if enabeld (not just that users will be able to bypass the BES to get updates from the carriers in a device-initiated manner). I don't really want to give the carriers this much power (assuming I'm reading the policy correctly).

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

Nothing after this morning's refresh on two of my SP6 domains.

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

This evening's refresh finally populated the new packages in one domain. I performed a timestamp reset (not recommended) and it also populated in my QA domain and another domain. So I would say by your next refresh interval, these updates should now be visible in your BES 4.1.6 environments. WOOHOO!

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

Not sure I follow you when you say you did a timestamp reset. Is that done on the BES? If so, how and where?

still nothin for me.

__________________
Two months ago, I saw a provocative movie on cable TV. It was called The Net, with that girl from the bus.

OTASL - Official BES Provisioned Versions

The value in between <OTASLLastRefreshTime></OTASLLastRefreshTime> can be updated to 1 (or anything that would put the converted epoch time to be greater than 24 hours prior) and it should update the timestamp.

RH, let me check my NYC environment to see if it has it as of this morning. I was too busy with other things to look.

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

In looking at NYC, it didn't show up there either. UGH!

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

showing up now...

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

Okay, so just to share a lot of information that I've figured out (on my own and with DART):

- BlackBerry Manager facilitates the refresh update to RIM's infrastructure for the update (pas.otasl.na.blackberry.com or us.otasl.blackberry.com - the latter being a cname of the prior) when opened

- The OTASLLastRefreshTime timestamp is only updated when BlackBerry Manager is open. If BlackBerry Manager is closed, this timestamp will not update.

- If more than 24 hours pass and the OTASLLastRefreshTime timestamp is not updated, the next time you open BlackBerry Manager, the timestamp will update at that time (thus a new 24 hours starts at that time, so it should never technically be an 'exactly at this time every day' scenario).

- If the OTASLLastRefreshTime is updating like clockwork every single day at the same exact time, then there is likely a remote instance of BlackBerry Manager open on someone's console and is not updating the domain properly (I cannot duplicate this, but this is my hunch for my specific environment).

- In the event that the OTASL updates do not show up and the OTASLLastRefreshTime timestamp is updating at the same time every day, the workaround will be to open BlackBerry Manager from a BES (using an RDP session, for example) and leave it running at the time the next refresh is supposed to happen.

Basically, the issue I was seeing in my environment was that presumably some instance of BlackBerry Manager was open and either not detecting the packages or was simply unable to update the database but was still registering the new timestamp update. Since the timestamp was updating, any time I opened BlackBerry Manager, it was already detecting that a refresh had been run that day and no new packages were found, so it was unable to run. Certainly a head scratcher and I'm glad that this process was moved to a service-based task within BAS for BES 5.0, but that certainly doesn't resolve the issue that a lot of people on BES 4.1.6 seem to be having!

Needless to say, I hope this workaround will help you guys out.

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

Does anybody have what the different serverity levels in the OTASL dialog do? I have low, medium, high, critical, mandatory. Are these arbitrary labels or do they have technical differences?

After a bit more research it seems that the options boil down to Mandatory (forces install if user doesn't initiate upgrade within 72 hours) or everything else. Anybody use these?

Mandatory
• use to send a software upgrade package that the BlackBerry® device
retrieves and installs automatically if the user does not accept the software
upgrade request within 72 hours
• might fix one or more software issues that are critical to how the BlackBerry
device works
• might include one or more important new BlackBerry device features
Critical
• use to send a request that indicates that the user should download and
install the wireless software upgrade immediately
• might include one or more important new BlackBerry device features
• might fix one or more software issues that impact how the BlackBerry
device works
High
• use to send a request that indicates that the user should download and
install the wireless software upgrade as soon as possible
• might include one or more important new BlackBerry device features
• might fix one or more software issues that visibly impact BlackBerry device
features but are not critical to how the BlackBerry device works
Medium
• use to send a request that indicates that the user should download and
install the wireless software upgrade as soon as it is convenient to do so
• might include one or more new BlackBerry device features
• might fix one or more software issues that do not visibly impact BlackBerry
device features and are not critical to how the BlackBerry device works
Low
• use to send a request that indicates that the user can download and install
the wireless software upgrade when wanted
• might include one or more minor new BlackBerry device features
• might fix one or more minor software issues

I tested with Mandatory and Low. I personally think Mandatory is the way to go if you want to send this to a lot of people and ensure the upgrade takes place, obviously.

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

Is the OTASL push "severity levels" available in version 5.0 ?
I would like to give my users "low" so they can have the option of upgrading.

The new Bold MR update will be available tomorrow. Bundle 517. Same Apps version, but different platform. Just an fyi...

Yep, it's up.
The new version is Apps 4.6.0.297, Platform 4.0.0.247, Package 4.6.0.517

__________________

Updated.

__________________
BCSA (4.1, 5.0) | BCSD (4.1, 5.0)

The views expressed by me on Port3101.org are my own and do not necessarily reflect the views of my employer.

Does anyone know if the package for the 9630 that was released by Sprint will be available over OTASL?