[cisco-voip] CUPC without AD?

[Wes Sisk]

unfortunate. the subscribe css model is no longer used in CM as chris 
ward kindly informed us on this list recently.

On Tuesday, July 21, 2009 4:48:04 PM , Jonathan Charles 
<jonvoip at gmail.com> wrote:
> No Presence Information After Login
> Solution
>
> Complete these steps:
>
>    1.
>
>       Ensure that the DNS server the PC is pointed to can resolve the
> fully qualified name of the CUPS server.
>
>       The host entry will not suffice, you must resolve via DNS.
>    2.
>
>       Check the SUBSCRIBE CSS on the SIP trunk to CUP.
>
>       This CSS must include the partitions of the devices you are
> trying to receive status on.
>    3.
>
>       The CUP SIP proxy incoming access control list (ACL) is not
> allowing incoming SIP presence messages to reach the presence engine.
> As a test, set the incoming ACL to ALL and reset the SIP proxy and
> presence engine. Then, re-login to the CUPC. After this, you can try
> to reconfigure the incoming ACL properly.
>
>
> Interestingly, there is no DNS on the lab either...
>
>
> Jonathan
>
> On Tue, Jul 21, 2009 at 3:42 PM, Ryan Ratliff<rratliff at cisco.com> wrote:
>   
>> Check the troubleshooting guide for CUPC.  You have to get presence before
>> you can IM.
>>
>> -Ryan
>>
>> On Jul 21, 2009, at 4:32 PM, Jonathan Charles wrote:
>>
>> Well, I can get CUPC to control phones, I can login with CUCM
>> credentials...  but no IM, and no presence stuff...
>>
>> J
>>
>> On Tue, Jul 21, 2009 at 3:22 PM, Ryan Ratliff<rratliff at cisco.com> wrote:
>>     
>>> It may not.  The 7.0 deployment guide actually mentions that you can
>>> integrate CUCM with AD and not CUPS but it is not recommended as it
>>> basically neuters CUPC and causes performance issues.  It also notes that
>>> if
>>> CUCM ldap authentication is enabled CUPC will use CUCM for authentication
>>> (because CUPS syncs the enduser table from CUCM) so maybe it will work,
>>> but
>>> not well.
>>>
>>> -Ryan
>>>
>>> On Jul 21, 2009, at 4:16 PM, Jonathan Charles wrote:
>>>
>>> Wait, the CCIE V lab uses CUPS and CUPC but does not have AD... so no
>>> LDAP... how does CUPC work then?
>>>
>>>
>>>
>>> J
>>>
>>> On Tue, Jul 21, 2009 at 3:14 PM, Ryan Ratliff<rratliff at cisco.com> wrote:
>>>       
>>>> Welcome to CUPS :)
>>>>
>>>> As I said CUCM is no longer an ldap server so you will need to build an
>>>> ldap
>>>> to point CUPS to.  If you don't want to do ldap sync on CUCM then the
>>>> userids must be the same in ldap server CUPS is using and in CUCM.  You
>>>> also
>>>> cannot add contacts via CUPC when CUCM is not enabled for ldap sync (you
>>>> have to use the CUPS User pages).
>>>>
>>>> -Ryan
>>>>
>>>> On Jul 21, 2009, at 4:10 PM, Jonathan Charles wrote:
>>>>
>>>> Well, I have CUCM 7 and CUPS 7 and I want to be able to query CUCM for
>>>> users from CUPC (so I can add users, etc...)
>>>>
>>>> CUCM is NOT AD integrated, and I want to set up CUPS to  point at CUCM...
>>>>
>>>>
>>>> Jonathan
>>>>
>>>> On Tue, Jul 21, 2009 at 3:04 PM, Ryan Ratliff<rratliff at cisco.com> wrote:
>>>>         
>>>>> Since CUPS is not supported with any Windows-based CUCM I seriously
>>>>> doubt
>>>>> it
>>>>> was ever tested using DCD as the ldap source.
>>>>>
>>>>> CUPS does _require_ ldap.  The ldap source can be anything that CUCM
>>>>> supports (AD, ND, etc).  Any CUCM that supports CUPS is not an ldap
>>>>> server.
>>>>>
>>>>> -Ryan
>>>>>
>>>>> On Jul 21, 2009, at 3:43 PM, Jonathan Charles wrote:
>>>>>
>>>>> How do you configure it?
>>>>>
>>>>> Do you set up LDAP to point to CUCM?
>>>>>
>>>>> Cuz I cannot search for users in DC Directory (CUCM) for CUPC.... am I
>>>>> missing something?
>>>>>
>>>>>
>>>>> J
>>>>> _______________________________________________
>>>>> cisco-voip mailing list
>>>>> cisco-voip at puck.nether.net
>>>>> https://puck.nether.net/mailman/listinfo/cisco-voip
>>>>>
>>>>>
>>>>>           
>>>>         
>>>       
>>     
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20090722/f280a161/attachment.html>