I am investigating the same scenario and from what I can conclude CUPS seems to be a spiteful product. OCS does have this capability by simply adding a route of "samedomain.com" pointing to the CUPS server. In doing this OCS will query it's local databse first to find a match, and if nothing is found will forward the query to the next route, which will be cups.
So I have managed to get this working from OCS to CUPS, but unfortunately I see no way of CUPS responding back. CUPS it appears has to completely own the domain and will not share. I have tried adding routes to no avail.
Maybe someone else has had some success in getting this working both ways.
You'll have to bare with me here as I have very little knowledge of CUPS and even less of OCS.
Is it the actual users that will be configured on the CUPS/OCS that need to be in different domains or just the FQDN of the SIP Proxy on the CUPS server needs to be different from the equivalent in OCS
What I was thinking of doing was changing the SIP Proxy domain on CUPS to cups.domain.com. THis will make all my users on CUPS firstname.lastname@example.org, the OCS server is then in the top level domain.com.
I find that saying "different domains" is very ambigious.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...