When your phone is returned from the search, check the box next to the
phone icon and then click Save Selected/Changes. This will associate your user with his
or her IP phone.
Back in the user confi guration page, click on the Capability assignment button. This
gives your user access to CUPS and allows presence information to be gathered and published
for every user who is enabled for CUPS. The CUPC client checkbox is needed only when
you are using the Cisco CUPC client; because we are using the OCS client we don??™t need
to check this box.
Check the Enable CUPS (Cisco Unifi ed Presence) box, but do not check the
Enable CUPC (Cisco Unifi ed Presence Client) box. Click Save.
Configuring Application Dial Rules
When we confi gured CallManager for Enterprise Voice/SIP integration with OCS, I noted
that CallManager cannot handle the + sign that OCS sends with all its outbound calls. The
way we dealt with it then was by limiting the signifi cant digits on the SIP trunk and thus
stripping off the leading +.
Figure 9.25 User Device Association
Integration with PBX and IP-PBX Systems ??? Chapter 9 309
Unfortunately, Remote Call Control does not work the same way because, once again,
calls do not come through the SIP trunk in this type of integration. The OCS client sends
the digits to dial to CUPS and CUPS passes these digits to CallManager. The only way for
us to strip out the + is to confi gure an application dial rule.
Open the CallManager administrative Web site and click on Call Routing | Dial
Rules | Application Dial Rules.
Pages:
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335