[erpam]

I have a BES 414 server and Sametime 751 server.

If I use the SameTime client from Notes everything works perfectly.

When I try to connect using the BlackBerry Enterprise Messenger for Sametime client I get teh following error when I try to log on:
"Please contact your system administrator to enable this service"

Now, the service is evidently enabled because it works using the Lotus Sametime Mobile client, so how do I enable it for the BB client? I tried to remove both applications from my device and install only the BB one, but I get the same problem.

Any help will be really appreciated

Thank you

[noname]

Try this:
BlackBerry Search Results

Else this:
BlackBerry Search Results

Good Luck!

[erpam]

I tried all those suggestions but nothing changed.

Thank you anyway

[andy9841]

I'm having the same problem. I spoke to Blackberry support and they said port 1533 needs to be open on the BES.

Now I have no idea how to do this, so if you have any clue, let me know.

TC says you need to be able to Telnet to port 1533 on the BES

[x14]

The Lotus Sametime Mobile client use a different protocol than the BlackBerry Enterprise Messenger for Samtime.

The Mobile Client uses HTTP tunneled client connection (default port of 8082) while the Enterprise Messenger uses client connection (default port of 1533).

To use Enterprise Messenger you need to add the IP address as a trusted hosts on the Sametime server. This setting does not take effect immediately. You need to either restart the server or wait a while.

[erpam]

OK - I added the IP address of the BlackBerry server into the field "Community Trusted IPs" of the document called "Community Connectivity" in the STConfig.nsf database and restarted the SameTime server.

Still no luck.

Thank you all for your help - this is driving me crazy!

[ashleyneiltaylor]

Make sure these ports are open. They are the dfault TCP Ports for Sametime Connectivity.

TCP Ports 8084, 1533, 8081, 8082

[x14]

What errors are you getting in sametime.log?

[erpam]

No errors at all in Sametime.log. All ports are open, no firewalls in between the servers.

[erpam]

My apologies to all of you, it was something I omitted to do.

I did not create the IT Policy Rule in the BES server. I assumed it was not necessary since the Lotus Sametime client worked without the rule. I guess the BlackBerry Messenger wants it.

Once I created the IT rule and pushed the IT rules (and the Service Books even though I am not sure whether this was necessary) I was able to log on to SameTime using the BlackBerry Messenger.

Now I have to decide which client I like better....

Thanks again to everyone.

[x14]

[QUOTE=erpam;644938]Now I have to decide which client I like better....QUOTE]

We went with the BlackBerry Enterprise Messenger for 2 reasons.

1. We presume RIM's version would have little issue with the handheld OS and BES because its from RIM.

2. The Sametime Moblie Client does not make good use of space displaying the contact list. You will see more people per screen on the Enterprise Messenger than the Sametime Mobile Client.

[erpam]

Totally agree with you on both points.
And let me add another one: the icon of the SameTime client does not change according to whether you are logged on or not, so you never know if you are logged on. The BB Mesenger has a little dot that changes according to your status.

However, the overall look of the SameTime Mobile Client is much nicer. Also, the SameTime client displays your contact's photo when you look at the contact details, the BB client doesn't.

[x14]

Originally Posted by erpam

However, the overall look of the SameTime Mobile Client is much nicer.

Everyone I've shown it to hates it.

[batrad]

appreciate if someone can share what rules are required on BES to make the RIM Sametime client work

Having the same issue

thanks

[erpam]

couple of basic things you should look at (provided you are using SameTime 7.5 and BES 4.1.4):

On the SameTime server:
- Open the STConfig.nsf database and add the IP address of your BES server in the Community Trusted IPs field of the Community Connectivity document

On the BlackBerry server:
- You should have an element called yourservername_BBIM_1: edit the properties and add the sametime server in the Host field and leave the port as 1533

[Jadey]

Hmmm... for the record we use the RIM client too. So far it seems very robust. I likey!

[ARXXBES]

Originally Posted by erpam

I did not create the IT Policy Rule in the BES server. I assumed it was not necessary since the Lotus Sametime client worked without the rule. I guess the BlackBerry Messenger wants it.

What items did you include in the IT Policy? Can you include what your policy is? I'm having somewhat of the same issue, running the following:

Win2k Server
BES v4.1.1.23 (10 License)
Domino v7 (Full License)
Sametime v7.5.1 (Limited Use)
===
Domino, Sametime and BES are all on the same box, using SQL (2005) DB connectivity.

I am able to add users to BES, activate BBerrys wirelessly, assign software configs, and have deployed Sametime messaging on a test BBerry wirelessly (Model# 8703e).

As for Sametime, the login stays at "Connecting" indefinately, with no errors and no timeouts in sametime.log.

I'm able to sign in with credentials via a client machine running Sametime/Notes v7, as well as the web-enabled Sametime.

I have included the extra Client IDs (1001,1003) in sametime.ini and I have included the BES IP in the CommunityTrustedIPS document.

Where am I going wrong here???

> FIXED >

There was a problem (for me) running the Sametime v1.1.32 runtime on the BBerry's. They would hang at "Connecting" and would connect with v1.1.16

We now have connectivity between the BBs and Sametime. Onward to MDS!