I came across something interesting with the CUPS to OCS integration… In OCS, you have a SIP ID for each user; it’s usually best to have that match the SMTP address. So it would be something like: Jim@domain.com. That’d be the SIP and SMTP addresses. No problem there. And this can even be different from the NT account name. So jim@domain.com could be logging in as domainjimsmith and have things still work.
HOWEVER (what would be the point of a blog post without a good "however"?) here’s the interesting bit: when integrating to CUPS, the cisco user ID has to match the SIP ID, not the NT account name.
"Big deal," you say, "just use the SIP id when creating Cisco usernames." Well, that works just fine. HOWEVER (yes, it merits a second "however") if you are synchronizing CallManager with AD – CallManager is going to take… the NT username and use it for the cisco ID. This, of course, will not match the SIP ID and presence and RCC will break.
I’m trying to find the best way to handle the situation en masse.
I have to say that I don’t like integrating CallManager with AD. It never seemed to go as cleanly as it should have. In all the Cisco IPT implementations I’ve done or seen done, I would say that around 1% of my customers ended up sticking with the AD integration. So maybe the answer is to just not integrate CallManager with AD.
But I’d like to be able to do it cleanly with CUPS and OCS… I’ll post something if/when I come up with it.
