12-19-2012 10:50 AM
Can I port a BlackBerry Bold 9900 with BES from Bell to Rogers by just unlocking the device? Both are HSPA Networks and I've been told and voice and texting will work, but no one can give me an answer to BES data.
I understand that the software load for Bell could be different than Rogers, thus I was wondering if installing the Rogers device software would also be needed.
12-19-2012 10:58 AM - edited 12-19-2012 11:01 AM
Hi and Welcome to the Community!
It matters not what carrier from which you obtain an OS package...they all originate at RIM, and there is nothing forcing a Rogers user to run only Rogers released BB OS packages. Rather, using the BB-specific services (including BES) is a matter of your carrier providing those to you (by virtue of the data plan that you obtain). And there are some things that must happen for them to do so.
Any BB can be used on any carrier that runs the same radio frequencies that the BB is capable of (and I've no idea if your's are such...you likely should ask Rogers specifically). But, to bring a BB onto a carrier network that they did not sell to you, there are several hurdles to cross:
1) The carrier must say "yes" to the fact...they own their network and have every right to say what devices will be allowed to connect to it. If they say "no", then that's the end of it.
2) You must be sure that your BB is properly unlocked from it's originally manufactured-for carrier...see this helpful thread for details:
3) You must get all of your voice level services functioning on the carrier, before you even try anything about data
4) You must subscribe, from the carrier, to an adequate data plan to enable the BB-proprietary services you desire. In your case, if your BES is BES-X, then a BIS plan will be adequate. But, if your BES is full BES, then you need a full BES plan from Rogers. Further, you must be 100% certain that Bell has fully released your BB PIN from all of their systems. Plus, you should remove the BB from BES and reactivate it on BES after the carrier shift has been completed.
5) Since Rogers directly supports your specific model BB, then you can proceed with registering the BB onto their network, generating the proper Service Book delivery to your BB, and proceeding to function. Followed by activation on BES.
You also should review this:
You should also be certain that your BES admins are completely involved in this entire process.
Good luck and let us know!
02-11-2013 08:41 PM
Would someone be able to explain why Rogers must provide a BES data plan instead of a regular data plan for a bb device?
a) I have a BES 5 or 10 server sitting in a colo.
b) I have a Blackberrry Bold or Blackberry 10 devices.
In the previous thread it states:
" ... if your BES is BES-X, then a BIS plan will be adequate. But, if your BES is full BES, then you need a full BES plan from Rogers. "
1) I understand the difference between BIS and BES. What is the distinction between BES and FULL BES in the above quote?
2) Why is a BES data plan required to support FULL BES?
3) Furthermore, why is a BIS data plan required at all? I can understand it from a service providers perspective that wants to offer a hosted BIS experience and manage the devices for the users for a fee (where users either don't want to or know how to run their own BES server). Can a BB not simply run over a plain data plan and a user could (theoretically) run their own equivalent of a BIS server (whateve that might be, I am just curious about the technical aspects of all of this).
4) It seems to me, that all that is happening here is that Rogers is simply offering normal data plans and redirecting specific BES ports to their servers and using their servers to proxy the data fo the corporate BES servers. Is that correct? If so, as per above I guess, why can't we bypass their proxy servers and just speak to our own BES servers via DNS?
Thank you for your assitance in helping clarify some of the basics here.
02-12-2013 09:16 AM
Hello holycow, and Welcome to the Community!
There used to be a white paper somewhere (that I cannot find right now) that listed the differences between BES and BES-X. I think it basically came down to the number of users as well as IT Policies...on BES-X, you can have fewer users (I think) than on full BES, and on BES-X, you do not get to institute IT Policies to control things on the associated BBs. There likely are more reasons.
As for the carrier plan requirement, that always did seem odd to me to have BES-X function on a BIS plan but require a BES plan for full BES. It probably has to do with some infrastructure they must host internally (at the carrier) to support all of the functions of full BES, but I am not sure of the specifics of that.
If you want, you can likely get more detailed replies from other BES admins in the BES section of this site: