OCS 2007 R2, multiple Domains

I have an OCS 2007 R2 implementation running in testing that we are about to move into production. The issue that I have is we have setup the users to SIP with their email addresses. Those with domaina.com work perfect, but those with domainb.com say server is un-available.

I added the SIP domain to the OCS Manager but still no luck. What do I have to do to get it to work? I am using the internal certificate server from my AD versus a 3rd party cert.

Thank You.
amedexittAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

adamg12345Commented:
Are you using automatic configuration for the Clients?

Adam
0
amedexittAuthor Commented:
I believe automatic config is setup. I have a slight workaround which is to change their sip login to the domaina with username@domaina.com but its a bit of a pain to do it that way.
0
adamg12345Commented:
If you use manual configuration and point the clients direct to the OCS Server, does that work for domainb users?

Adam
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

amedexittAuthor Commented:
adamg12345, I think manual will work, but this is about 60 of 350 employees and I'd like to avoid having to do that for them due to the headache of managing that.
0
adamg12345Commented:
If it works manually then it is either down to DNS or Certificates.

You need to create the SRV records for both domains, the A records that these points to must be the same domain.

so SRV for Domain A must point to ocs.domaina.com
SRV for Domain B must point to ocs.domainb.com

Then in turn the FQDN of the A record must be in the SAN list of the FrontEnd Cert.

I hope that makes sense.

Adam
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
amedexittAuthor Commented:
I decided to standardize and have everyone login with their SAM login acct@domaina.com, because theres 4 or 5 different domains and otherwise will be a mess to setup.
0
adamg12345Commented:
Ok, just one thing that is worth noting is that if you are going to Federate, it is often easier to have the SIP Address matche the email address, plus exposing the account name is never ideal.

Adam
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.