[Brutus4583]

Has anyone successfully implemented Blackberry Messenger with OCS 2007?
We have a BES 4.1.4 and OCS 2007 Infrastructure in place, Blackberry Messenger is returning a (315) error, which is a TCP issue. My feeling here is that it's related to the configuration of the BBIM using only ports 443 or 80, not our default 5061 for OCS IM.

Any Thoughts, or gotten this to work successfully?

Thanks!

[hdawg]

Have you configured the alternate port within the BES Manager? Do you have any firewalls between the BES and your OCWA server?

[Brutus4583]

Yes, I used Default and port 5061. The server name is the Front End server internal to our network, so there is no firewall between them.

[hdawg]

And if you go to the OCWA interface you can login with no problem?

[Brutus4583]

By OCWA, do you mean Office Communiator Web Access?

[hdawg]

Originally Posted by Brutus4583

By OCWA, do you mean Office Communiator Web Access?

Yes

[Brutus4583]

We do not have Web Access deployed, only Front End server, Edge Server archiving server roles. Is the Web Access Server a requirement for BBIM to work with OCS? I didn't see that documented anywhere.

Office Communicator works perfectly from the BES to the Front End Server.

[hdawg]

Originally Posted by Brutus4583

We do not have Web Access deployed, only Front End server, Edge Server archiving server roles. Is the Web Access Server a requirement for BBIM to work with OCS? I didn't see that documented anywhere.

Office Communicator works perfectly from the BES to the Front End Server.

Yes, it is required. (2 different links)

[Brutus4583]

Well Geez. I guess I missed that one!!!!
Sorry for the apparently dumb question, but thanks for your help.

[hdawg]

Let us know how the install goes ... good luck!

[Brutus4583]

Ok. CWA installed Successfully and Functional both internal and External.

This is what I see in the CWA IIS logs:

MDS_4.1.4.17+(MSIE) 484 0 0

My guess is that it's an authentication issue between the BES and CWA server due to a MDS certificate? Is this right?

How do you manually apply a certificate to the MDS services, or am I off base here?

Thanks again.

[saver@intermedia.net]

I am having the exact same issue. I have a feeling that OCS 2007 CWA is incompatible with BB. Any thoughts?

GET /cwa/AsyncDataChannel.ashx AckID=0&Ck=&UA=true&Timestamp=1201570399151 8443 - 484 0 0

All requests to CWA from BlackBerry are returned with a 484 error code.

From BlackBerry logs:
:<INFO >:<LAYER = BBIM, DEVICEPIN = XXX, USERID = u3f, SIP URI = >
:<INFO >:<LAYER = BBIM, DEVICEPIN = XXX, USERID = u3f, Account = >
:<DEBUG>:<LAYER = SCM, EVENT = Finished JobRunner: IMLoginJobRunner-0, available threads in IMLoginJobPool = 5, time spent = 516ms>
:<DEBUG>:<LAYER = BBIM, DEVICEPIN = XXX, USERID = u3f, OPEN GET response code = 484>
:<WARNG>:<LAYER = BBIM, SERVER ERROR>
and it just ends there...
Nothing in the system event log.
Login requests from the device simply hang.

Running BES 4.1.4 (Exchange) and OCS 2007.
Blackbery knowledgebase doesnt event mention OCS2007.

[Brutus4583]

According to BB support this is unsupported, but others maybe seem to have made it work. According to RIM, this will be addressed in a future release, due probably this quarter.

By the way, I love the 484 IIS error that doesn't exist, don't you?

[homeroarg]

I think 484 is a reserved error...

[1badtwo]

Running 4.1.4 and just migrated from OCS 2005 to OCS 2007.

We have never had OCWA installed.

Before I was running the BES IM connector connecting to my internal OCS2005 server.
i.e. serverxxx.mydomain.local using port 5060 TCP

I was getting the 315 error when trying to login from my blackberry client.

I changed the IM connector to use my edge server (don't know if you are running one)
i.e. serverxxx.mydomain.com and changed it to port 5061 TLS.

It may also have something to do with the client version filter as I had to do some configuring to to get the WM6 OC Client to work a few days ago.
You can find it here on your OCS and Edge server
c:\Program Files\Common Files\Microsoft Office Communications Server 2007\ClientVersionFilterConfig.exe

Hope this helps.

[WillFulmer]

when you ran the upgrade/new install for 4.1.4, did you select "Office Communicator", or "Office Communicator/Windows Messenger?"

[1badtwo]

LCS/Windows Messenger

[WillFulmer]

Same issue here. last line of log:

BBIM Log:
<2008-04-24 23:23:24.307 EDT>:[229]:<BBIM_WIL-BB01_BBIM_1>:<DEBUG>:<LAYER = BBIM, DEVICEPIN = 24051051, USERID = ud2, OPEN GET response code = 484>
<2008-04-24 23:23:24.307 EDT>:[230]:<BBIM_WIL-BB01_BBIM_1>:<WARNG>:<LAYER = BBIM, SERVER ERROR>

Line from IIS Log:
2008-04-25 03:46:43 W3SVC175074822 172.16.x.xxx GET /cwa/AsyncDataChannel.ashx AckID=0&Ck=&UA=true&Timestamp=1209095202704 443 - 172.16.x.xx - 484 0 0

Anyone able to resolve this issue and OCS 2007 (CWA Login)

[TFoug]

I am receiving similar errors in my IIS log. CWA is not working and our handhelds return Error 300... i.e. server error.

OCS is working fine CWA works fine from a browser.

[penguin3107]

Originally Posted by TFoug

I am receiving similar errors in my IIS log. CWA is not working and our handhelds return Error 300... i.e. server error.

OCS is working fine CWA works fine from a browser.

You need at least BES 4.1.6 for OCS 2007 support.
BES 4.1.4 is not supported.