Office Communications Server 2007 and Speech Server (2007)
Do you want to have OCS place calls to Speech Server? Well OCS doesn't support the 302 redirects, but don't worry there is a work around.
You'll need to setup a static route between OCS and Speech Server. You'll need to have certificates on both the Speech Server and OCS server and they must trust the CA. You probably already have certificates on the OCS server (or at least should) but you'll need them on Speech Server as well.
Speech Server:
First to get around the 302 redirect messages, you'll need to change the ports on your Speech Server application to listen on non default ports, specfically the TLS port. In the Administrator Console of Speech Server, in the properties of your application, click the Advanced button.
Change the default listening ports to something else, say 5062 for TCP and 5063 for TLS. (The TLS port is the important one in this implementation as OCS only supports TLS)
Next add your OCS server as a trusted SIP Peer.
OCS:
On the OCS machine, go to the Office Communication Server 2007 Management Console
Right click on your server
Select Properties -> Front End Properties
Select “Routing” Tab and click on Add: (This needs to be done per-app.)
Domain: This is the regular expression that the route will match; for example, *.microsoft.com will cause all calls to *@foo.microsoft.com and *@bar.microsoft.com to take this route.
Next Hop: FQDN: The FQDN of the MSS box (e.g., mss.microsoft.com)
Select TLS (TLS is only way that OCS can talk to its trusted peers)
Port: 5063 **This is the TLS port of your application)
Click OK
Select the “Host Authentication” Tab and add the FQDN of the MSS box; check 'Treat As Authenticated'. (You will only need to do this once)
Click OK