[gmendoza]

We are running BES Exchange 4.1.2 with about 300 Exchange users and approximately 70 bb users. The BES and Exchange servers are wired directly so there is no latency between the two. This past week, we have been experiencing slow email delivery (user will receive in Outlook but BB will receive the email between 1-10 minutes).

I ran messageflow.exe and the difference in time is in the Router Recv and Router Del columns (receive and delivered). Here are 3 examples:
BES received at 20:02:41, Router Recv is 20:02:41, Router Del is 20:08:24BES received at 20:04:15, Router Recv is 20:04:15, Router Del is 20:08:25BES received at 20:04:57, Router Recv is 20:04:57, Router Del is 20:08:26

Basically, the BES had 3 messages in Pending Messages and delivered them all at once at 20:08.

The handheld (8800) is on Cingular's EDGE with 3 bars.

Based on the times I posted above, is the latency at RIM's servers? To me, it looks as if the BB router received the emails immediately from the BES but it didn't hit my wireless device until 20:08.

Any solution/suggestions on how to get rid of this latency? This only started happening a week ago... and it doesn't happen all the time. In fact, I just sent a test from my gmail account and I received it on my handheld before Outlook received it.

Thanks.

[Spydertech]

I am having the exact same issue here... Except that I have 900 Exchange users and 130 BB users. I've noticed the problem on my 8100 (Cingular), and I've had a couple of complaints.

Just this morning I received an email in Outlook at 10:19 - only to receive it on my 8100 at 10:24. The strange thing is that I received an email in Outlook at 10:24, and it appeared on my 8100 at 10:24. It does act like it is processing the emails in a queue format, instead of as they are recieved.

I started seeing this about a week ago also.

Is something going on at RIM?

Spydertech

[65shelby]

The plot thickens.....

I say, it was Cingular in the study with the candle stick!

http://www.blackberryforums.com/bes-...-messages.html

[Spydertech]

I'm noticing this problem posted in a few places on the boards....

So far I think I can honestly say - it isn't my BES server....

BTW - we have users on different carriers. And Cingular users are the only ones complaining....

Spydertech

[65shelby]

Just spoke with Cingular.

There was an outage and there were issues due to cingular to AT&T conversion.

Fix is to go to Options, Advanced , Host Routing Tables, click on first one shown, click register now.

[65shelby]

Fix no worky, the hunt continues....

[pingooi]

I've spent the last 3 days with Tsupport on the phone and today, it's escalated to their network team. Same issues as you guys / gals.
This bites!!

[Spydertech]

Be sure to keep us posted.

While I love my Blackberry - I can't stand TSupport....

Spydertech

[65shelby]

Originally Posted by pingooi

I've spent the last 3 days with Tsupport on the phone and today, it's escalated to their network team. Same issues as you guys / gals.
This bites!!

Try talking to Cingular "let me transfer you" Wireless.

I'd rather talk to ANYONE at Rim rather then those Union City Workers rejects at Cingular.

They define the phrase, "not my job"

[pingooi]

Just got off the phone with T-Support. So they had me blow out my handheld and reload the firmware. (i have a new 8800) It's working for the few messages he sent. I reiterated the problem is on and off. Some get there on time, some don't. It was never all or nothing.
The current move is to monitor it through the day and see where it goes.

The good thing is that he is starting to think it's a Cingular issue (much as we all already do) and with a bit more evidence of late emails and some timely ones, will escalate it further.

[geast]

I'm having the exact same issue, on the phone now with TSupport, terminal hold. I have about 290 users, all Cingular, and a lot of my users are experiencing delays, or burst of emails. Any solution I would be happy to know.

[pingooi]

Well, geast... i have bad news. I don't think they can help you much.
I'm now seeing latency again on MY handheld and have conveyed this to T-support.
I also had one of my techs reload the firmware on his 8800 and still same issue. This cingular crap has got to get fixed. The only happy users i have are Verizon which doesn't help since 97% are on Cingular!

[Spydertech]

Originally Posted by pingooi

Well, geast... i have bad news. I don't think they can help you much.
I'm now seeing latency again on MY handheld and have conveyed this to T-support.
I also had one of my techs reload the firmware on his 8800 and still same issue. This cingular crap has got to get fixed. The only happy users i have are Verizon which doesn't help since 97% are on Cingular!

DITTO!!!!

[geast]

T-Support is saying it is a MAPI problem, BES and Exchange not playing well. That may be my problem, but with so many others in so many places having the same problem, I'm not sure

[gmendoza]

I don't see it being a MAPI problem... in the example I used on the original post, it was already at the BB router stage (where it delivers to the handheld) and had nothing to do with the BB/Exchange talking to each other (it had already done this process because the messages were sitting in PENDING.

[65shelby]

Originally Posted by geast

T-Support is saying it is a MAPI problem, BES and Exchange not playing well. That may be my problem, but with so many others in so many places having the same problem, I'm not sure

HEY RIM T-SUPPORT!!!!

IT"S NOT A MAPI PROBLEM!!!!

Have them (t-support) contact internal RIM networking (I am working with them now. Cingular called me yesterday while I was at lunch, waiting for a call back) and have them look up the cingular issue.

I am floored that this is not all over RIM t-support by now.

Anyone know any media contacts to out Cingular on this?

I did hear from Cingular earlier between transfers that they did a network upgrade a couple of weeks ago. This was to facilitate the change from Cingular to AT&T

[geast]

Yeah, I see lots of pendings sitting on my BES so I know that it is already gone from Exchange to the BES, and that is where the holdup seems to be.

[65shelby]

Originally Posted by geast

Yeah, I see lots of pendings sitting on my BES so I know that it is already gone from Exchange to the BES, and that is where the holdup seems to be.

Working with the RIM networking and server groups, we have excluded the following.

Exchange Servers
BES servers
Handhelds
and all carriers EXCEPT Cingular.

Mail flow is fine from Desktop to exchange to BES to RIM and then it hangs at Cingular

From handheld to Cingular it hangs, then it's fine to RIM to BES to Exchange to deskop.

I did this test yesterday....

PIN message from handheld on t-mobile to to rim to Cingular (HANG) to handheld on Cingular

PIN message from handheld on Cingular to Cingular (HANG) to rim to handheld on Verizon

I would bet my hands that it is a 100% Cingular issue.

What would be an added bonus is it t-support would stop this useless "recreate your mapi connections" and "restart the server" and restart the services" and the upgrade to this version or that version

They are acting like they did when they had the outage a few weeks back.

They need to communicate better with thier frontline troops at t-support.

[gmendoza]

Well after I originally posted the first message on 5-21, everything was back to normal beginning on 5-23. However, as of last night, I'm getting the lag again with numerous pending messages. Like we've all noted, it comes and goes...

As for the BlackBerry Messenger application, that is lagging as well (pin to pin messaging).

I agree with 65Shelby that this is certainly a Cingular issue.

[65shelby]

Good news gang.
Mine's fixed now.

Bad news is that Cingular's network support team needed to remove my PIN from the relay, remove my data plan, re-add my dataplan and PIN in the relay and then perform a enterprise activation.

Not to mention a number of battery out resets in the process.