I will, however, point out the
two things that you must do to get basic functionality:
1. Confi gure ACLS
2. Confi gure users for use with Microsoft Offi ce Communicator (MOC)
Figure 9.27 Dial Rule Confi guration
Integration with PBX and IP-PBX Systems ??? Chapter 9 311
Confi guring OCS for a CUPS Integration
The OCS Standard Edition Server (or the Enterprise Edition front-end server pool) requires
some confi guration to integrate with CUPS and CallManager. The main objectives of this
section are to:
?– Allow OCS to listen on port 5060
?– Set CUPS as a trusted host
?– Create an OCS static route to CUPS
?– Confi gure users for RCC
?– Enable your Communicator client for integration to the PBX
Configure OCS to Listen on Port 5060
By default, the OCS front-end server only listens for SIP connections on port 5061 because
5061 is the port used for secure SIP communications using a multiline telephone system
(MTLS). CUPS will not support this secure SIP signaling, so we need to confi gure OCS to
use SIP over port 5060.
312 Chapter 9 ??? Integration with PBX and IP-PBX Systems
Summary
OCS 2007 does not yet support any direct integration with CSTA-capable PBXes. However,
Microsoft expects to offi cially support this in the near future. Currently, you can integrate
with Cisco CUPS to allow your Offi ce Communicator client to act as a remote control for
your Cisco IP phone. To make this happen, you need to confi gure CallManager, CUPS, and
the OCS Front End server all to communicate.
Pages:
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337