06-17-2010 12:33 PM - edited 03-19-2019 01:06 AM
Hi,
We are doing the POC with CUCM , CUPS , OCS RCC integration. I want to clarify some of the features using Desk phone control.
CUCM - 7.1.2
CUPS -8.0.0 , CUPS 7.0
OCS R2
CUCM CUPS are integrated and features soft phone , desk phone , IM , IPPM , LDAP are working fine.
1) In desk phone mode , CUPC A is call with CUPC B ( soft phone or Desk Phone) . In that time CUPC C will able to the Phone status of CUPC A
such as Busy , Idle like the Presence status in the phone ?
2) In the OCS RCC i'm able to call from the MOC to the Phone , but for incoming call there is no pop up from the MOC ?
3) OCS FQDN should be resolved in the CUPS ? ( test.domain.com)
4) From the MOC is it able to see the User Phone status as mentioned in the 1st Point.
Thanks
06-17-2010 01:14 PM
In RCC scenario,
1) There's no "phone presence" while ringing. "Phone presence" will only show up when the call is connected.
2) That means the INFO message was not able to delivered to OCS (or OCS does not trust it).
3) I don't think that matters. CUPS should be able to figure the return path via the SIP header.
4) See #1 above.
You may also take a look at http://www.lulu.com/content/5552336. It discussed RCC in detail.
Michael
06-18-2010 12:29 AM
Hi Michael,
Thanks for your response.
We already placed the order & waiting for the shipment.
Could you please clarify the following points.
1) DNS entry is really required in the CUPS towards the OCS server ( ex ocs.lab.com)
2) When the incoming call to the RCC phone , OCS will pop up the Incoming call to the MOC.
3) How important MOC RCC plugin we have to install in the MOC? how its work with MOC ?
Thanks
06-18-2010 06:11 AM
1) DNS entry is really required in the CUPS towards the OCS server ( ex ocs.lab.com)
[Michael] Technically, it will work without DNS. Tweaking might required. Since you already have OCS entry in DNS, you may just point your CUPS to the DNS server. That'll make thing's easier.
2) When the incoming call to the RCC phone , OCS will pop up the Incoming call to the MOC.
[Michael]Yes.
3) How important MOC RCC plugin we have to install in the MOC? how its work with MOC ?
[Michael] MOC RCC plugin is only required when the Line URI in Active Directory cannot uniquely identify a phone device and a line. For example:
Scenario 1: shared-line across multiple devices
Line URI is "tel:1234;phone-context=dialstring". If there's only one phone with DN 1234, you don't need the plug-in. Otherwise, you may
a) Use the plug-in to choose the phone you want to control.
or
b) Change the Line URI to "tel:1234;phone-context=dialstring;device=SEPAABBCCDDEEFF" (then you don't need the plug-in)
Scenario 2: same DN in different partitions
Line URI is "tel:1234;phone-context=dialstring;device=SEPAABBCCDDEEFF". If there's only one line on phone SEPAABBCCDDEEFF with DN 1234, you don't need the plug-in. Otherwise, you may
a) Use the plug-in to choose the phone you want to control (even though there's only one device)
or
b) Change the Line URI to "tel:1234;phone-context=dialstring;device=SEPAABBCCDDEEFF;partition=partition1" (then you don't need the plug-in)
Michael
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide