Sorry for the late reply.

To make life easier, you should consider procuring Unified Communications certificates that are specifically certified (or designed) to work with Exchange 2007/2010 or OCS 2007 R2. As you have discovered, Subject Alternate Name (SAN) is one of those tricky fields that must be properly setup in addition to the normal Subject Name (CN).

How did you configure your digital certificate when you purchased it from your provider (godaddy)? The process should not be very different from a certificate request step (using the built-in OCS Wizard) if you have your own internal CA, such as Windows Server 2003 or 2008.

I’ve done this, and still I get the same message. I’m beginning to think something’s wrong with my cert. I’m,using a public trusted CA, godaddy normal, simple cert for internal OCS 2007 r2. I only have 1 enterprise server in my pool.

one sip. domain.com
domain is same internally and externally - domain.com

godaddy cert is for the fqdn of the pool.

The only thing that makes me think the cert won’t work is that during ocs cert setup it asks for a subject alternate name for the SIP. Can a normal cert do this? I don’t have a UCC for this, but i thought i didn’t need one for the internal.

I do not have an internal CA setup.

Josh