Oops!
I was wrong, I tested as follows:
1) remove battery from HH
2) Dismiss a newly created appointment (i.e. after battery was removed I created using Outlook client) that popped up in Outlook, then waited a few minutes and turning on the handheld.
Sure enough there is no updating of...
Oops!
I was wrong, I tested by leaving the battery out of the handheld, dismissing a new appointment that popped up on the Outlook client, then waiting a few minutes and turning on the handheld and sure enough there is no updating of appointments (like, if they have been Dismissed) occurring...
Bullsh!t. There is syncing between HH and BES happening here but it's only happening one way. I just started a thread on this very problem today before reading this one.
Not sure if this is helpful here, but I do know that emails deleted on my handheld WILL also be deleted from my Exchange mailbox, of course I do have Email Reconciliation on the handheld (curve 8330) set to "Mailbox & Handheld", Wireless Reconcile is "On", and On Conflicts is set to "Mailbox Wins".
Do you have pre-processing turned on (where it counts the bytes in the job to give you an ETA on job completion)? If so, disable it and see if that speeds things up.
Thank you in advance for your help.
This is a minor issue, but annoying as he11:
System:
Exchange 2003 (SP2) runs Blackberry Enterprise Software (BES) 4.1, handheld (HH) is an Enterprise Activated Blackberry Curve 8330.
Problem:
(this is NOT the one-way sync problem between HH and BES!)...
Ask him to give you as much detail as possible about one of the "vanished" appointments then search Outlook using the Advanced Find for any of the keywords.
I solved this by downloading the latest BCM Element Manager from Nortel's (Support > Software Downloads) site.
It was released on 6/17, so it was a good thing I waited to install the latest major release until after the 17th!https://support.nortel.com/go/main.jsp?cscat=SWDETAIL&id=734128&poid=17141
FALSE ALARM IT WAS MY FAULT
After rebuilding the Mailbox to be used for OPN, I failed to change it to the Class of Service I had previously defined, so it was using a Class of Service set to dial the 1st number 5 times, on the hour, before rolling to the next number.
Sorry to waste people's...
Hawks, thanks for the idea!
Unfortunately that is not it (I think) because I know it is capable of handling this situtation because it used to go to my cell phone 3rd, leave a voicemail, then roll to the 4th number which was previously setup to be a pager. So whether it leaves a VM or I answer...
When I changed the first number dialed to my cell (a local cell phone, before it was dialing a LD cell 1st) it did ring this different number, but it's still not rolling to the next number.
OK. I set the Retry Interval back to 15 minutes and monitored the system dialing the 1st phone and this time it stayed connected for 1:57 (the user didn't answer the phone, so this was connected to that provider's VM system) before going Idle.
I'll try and monitor the next dialout attempt (if...
DigitelD, thanks for trying to help!
I did have the Retry Interval set to 15, and the number of Retry Attempts set to 1 all day yesterday while I was troubleshooting this. I'll change it back since you said that is a requirement for it to roll to the next phone, and monitor the BCM.
Endlesswinter, good idea. I can't believe I haven't tried that yet. I watched the BCM Monitor and saw it dial the first number, then it Connected (assumingly to VM) then it showed Idle after about 2 seconds, then it disconnected. Is this my problem?
I had changed the Retry Interval to 2...
We have a BCM 400 (software version 4.0.2.03) with a Mailbox setup for off-premise notification. I now have it programmed to dial 4 cell phones in 15 minute intervals if a new voicemail is left on this Mailbox. It is calling the first cell phone, a long distance number (the other 3 are all...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.