09/23/2010, 07:17 PM
|
#1 (permalink) |
|
Member
![]() Join Date: Apr 2009
Location: GMT -8
Posts: 575
Likes Received: 1
Thanks: 333
Thanked 55 Times in 44 Posts
|
My work's OCS messaging server is accessible on the web (outside of firewall) by going to https://im.companyname.com I installed the 2.5 messaging plugins patches and all appears to be installed correctly. When I enter username, domain\username, server address and password it still will not connect.
The only part I am unsure of is the field called "user agent". Anybody know what goes there?
Last edited by mk3; 09/23/2010 at 07:34 PM. |
09/24/2010, 10:17 AM
|
#2 (permalink) |
|
Member
![]() ![]() Join Date: Dec 2009
Location: Mexico
Posts: 2,392
Likes Received: 225
Thanks: 88
Thanked 944 Times in 475 Posts
|
This should be put on the other thread, but...
I don't use https://webmessenger.xxxxxx.com/ In fact, I just leave the server part alone: On the Preferences and Accounts page, enable "Accept Bad Cert", this will enable the Messaging App to get your server certificate in case it doesn't have it, and trust it. And, when adding your account: Username: username@domain.com Logon: WINDOWS_DOMAIN\username Enable Proxy: False User Agent: Empty Server: Empty (my company uses some sort of autodiscovery) Port: 5061 (default) Use TLS: True Enable Avatars: False Password: ********* I hope this works for you, it works for me.
__________________
Just remember: If I helped you, press the thanks button! ![]() Owner of: Pre Sprint, Pre Telcel, Pre Plus AT&T, Pre 2 Unlocked, Pixi Plus AT&T, TouchPad, and a shiny new AT&T Pre3. Needs: Veer (anyone?) Apps: Subnet Calculator, FreeCam, PhotoFun, NuttyPad (work in progress) HomeBrew: meta-doctor and Messaging Plugins collaborator Twitter: @cesarneg |
09/24/2010, 10:25 PM
|
#3 (permalink) |
|
Member
![]() Join Date: Apr 2009
Location: GMT -8
Posts: 575
Likes Received: 1
Thanks: 333
Thanked 55 Times in 44 Posts
|
Thanks for the help but can't get anything to work for me. I enabled the accept bad certs, and tried to let it auto-discover the server. Either way doesn't seem to work.
Do I need to manually get the cert from the server and install it myself? |
09/24/2010, 10:37 PM
|
#4 (permalink) | |
|
Member
![]() ![]() Join Date: Dec 2009
Location: Mexico
Posts: 2,392
Likes Received: 225
Thanks: 88
Thanked 944 Times in 475 Posts
|
Quote:
You could try downloading Pidgin, and the "sipe" pidgin plugin, in which the Pre messaging system is based, and try to connect to your server using it. Google it, Pidgin, and "sipe pidgin". If you can't connect with Pidgin, it should be an issue in how your corporate servers are configured and there's not much we could do about it. In few words, if pidgin can connect, you should be able to with your Pre
|
|
09/24/2010, 10:38 PM
|
#5 (permalink) |
|
Member
![]() Join Date: Feb 2010
Posts: 132
Likes Received: 0
Thanks: 36
Thanked 15 Times in 15 Posts
|
I can't get it to connect to my universities SIP (oc) won't connect either. I'm not what 'user agent' is supposed to be either. Based on the debugging logs it says 'connection refused' so I'm thinking that the problem with mine has to do with the port used.
|
09/24/2010, 11:31 PM
|
#8 (permalink) |
|
Member
![]() Join Date: Apr 2009
Location: GMT -8
Posts: 575
Likes Received: 1
Thanks: 333
Thanked 55 Times in 44 Posts
|
So do I need to enter something in user agent?
What are the odds they are using a different port number than default? [edit] Okay so got the sipe plugin thing figured out (FAQ says two dll files are missing in newer versions of pidgin). Damn thing wont connect either! Is it possible the OCS server is configured to allow connection via the webpage but not from a mobile device? Last edited by mk3; 09/25/2010 at 12:01 AM. |
![]() |
|
| Tags |
| communicator, messaging, microsoft |
| Thread Tools | |
| Display Modes | |
|
|



