I have just spent the better part of the last 2 days bashing my head against my desk trying to figure out why my intradomain federation isn’t working and why my FES OCS server keeps sending me back 404 not found errors for all SIP SUBSCRIBE/NOTIFY requests, turns out you have to map
msRTCSIP-PrimaryUserAddress in the configuration file for your windows Jabber client. It would have been a lot more helpfull to include this information or at least a reference to it in the Partioned Intradomain Federation Guide!
Anyway, I am wondering how I map SipUri in CUPS to msRTCSIP-PrimaryUserAddress in LDAP for other Jabber clients such as Jabber IM for iPhone, I cant add another field to the LDAP profile/settings in CUPS and I cant find any documentation referencing a config file for other Jabber clients.
Thats rather odd, I am running CUPS version 184.108.40.20600-28 and it would seem that the SipUri is not mapped to
msRTCSIP-PrimaryUserAddress by default.
As you can see in the screenshot we are using the msRTCSIP-PrimaryUserAddress in email address format, yet all of my SIP messaging from CUPS to OCS is using samAccountName@domain.com.au I have renamed our domain and hidden the account names in the below outputs for privacy reasons but you can see what I mean.
11:30:46.461 |b1961b90| debug| SIPTransportMgr.cpp:446 [SIP RCVD] id=0xb1961b90: SIP/2.0 404 Not Found \r
Any advice would be apreciated, in the Jabber for windows client guide it states you have to configure
msRTCSIP-PrimaryUserAddress in the clients xml config file for intradomain federation only, this makes me infer that it's the only way to get it working based on what I am currently seeing in my logs and if thats the case I dont see how it can work with other clients that don't use the config files.
I am having the same problem as Brendon with clients other than the Windows client being able to reference the msRTCSIP-PrimaryUserAddress field in AD. Correct me if I'm wrong Brendon, but you've got the windows client working, right? It's the other clients, Mac, iPhone, and iPad that are having problems. I am running into the same issue, that these clients don't pull a config file, and therefore don't reference the msRTCSIP-PrimaryUserAddress field.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.