The users
3. The application dial rules
Configuring a SIP Trunk
The SIP trunk that we will confi gure for CUPS/Remote Call Control integration will look
like the one we confi gured for Enterprise Voice/SIP integration, except for one major difference:
The destination IP address of our SIP trunk is that of your CallManager.
Integration with PBX and IP-PBX Systems ??? Chapter 9 305
To create the new trunk, open the CallManager administrative Web site. Click on
Device | Trunk and then click Add New. Give the trunk a name and description that
will differentiate it from the SIP trunk we created in the previous sections (see Figure 9.21).
You can leave the Call Routing Information section at its defaults (see Figure 9.22).
Figure 9.21 Trunk Confi guration
Figure 9.22 Call Routing Information
306 Chapter 9 ??? Integration with PBX and IP-PBX Systems
The SIP Information section, once again, is the most important. Notice in the example
shown in Figure 9.23 that the destination IP address is 192.168.100.200??”which is my
CallManager. This may seem strange, but you do not confi gure a SIP trunk to OCS in any
way here. OCS only pulls status information from CUPS, which gets its information from
CallManager.
Notice also that I haven??™t fi lled in any information in the Calling Search Space section.
This is because we won??™t actually be using the SIP trunk to route calls; it will only be sending
signaling and presence information to and from CUPS. Remember, with Remote Call Control,
the Cisco IP phone is the device that does the actual calling, not OCS.
Pages:
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333