Welcome to Port3101.org : Your BES Connection Mark forums read | View Forum Leaders
Port3101.org : Your BES Connection

Rate this Entry

What can't you do in BES?

Submit "What can't you do in BES?" to Digg Submit "What can't you do in BES?" to del.icio.us Submit "What can't you do in BES?" to StumbleUpon Submit "What can't you do in BES?" to Google
Posted 03-04-2010 at 05:05 AM by hdawg

So I figured I'd start a little wish list of things I wish I could do with BES, but can't ... please add on whatever yours are. Perhaps it is possible and you just don't know about it!
  • The ability to identify when a call is dropped / ended prematurely. Sure we can get call log info, but what about reporting back to carriers lots of dropped calls ... especially for a particular user
  • The ability to restart a single messaging agent. When a single agent gets hung / stopped the only supported way to get it back is to reboot the BES.
  • Force device information to sync on demand. Instead of waiting that 4 hour period for the device to push data back to the BESMgmt database (such as free memory / apps installed) I'd like to be able to initiate an update in real time
So that is the start of my list ... what do y'all have?
Posted in Tips & Tricks
Views 2573 Comments 4 Edit Tags Email Blog Entry
« Prev     Main     Next »
Total Comments 4


  1. Old Comment
    d_fisher's Avatar
    The ability to push 3rd party applications from the BES while at the same time restricting end-users from installing 3rd party apps on their own.
    Posted 03-04-2010 at 10:02 PM by d_fisher d_fisher is offline
  2. Old Comment
    That's already possible using software configurations and application policies.
    Posted 03-06-2010 at 04:29 PM by Abe Abe is offline
  3. Old Comment
    d_fisher's Avatar
    Yeah, but its an administrative nightmare and only gets worse the more apps you push.
    Posted 03-06-2010 at 09:22 PM by d_fisher d_fisher is offline
  4. Old Comment
    You can restart a single messaging agent by looking in the agent log for "current process id" to find the PID, then in Task Manager, add the column for PID and look for the appropriate PID to tell you which agent to stop. Dispatcher should automatically respawn a new agent after you kill it.
    Posted 03-10-2010 at 11:53 AM by jdizzle jdizzle is offline

All times are GMT -4. The time now is 04:56 PM.
Powered by vBulletin® Version 3.8.9
Copyright ©2000 - 2019, vBulletin Solutions, Inc.


Content Relevant URLs by vBSEO 3.3.2 PL2