Maximum number of devices that can be associated with a user

Version 1
    This document was generated from CDN thread

    Created by: Muhammad Sabir on 05-06-2009 08:15:17 PM
    For a push application, one has to use credentials to authenticate. Is there a maximum number of devices that can be associated with a user? In CUCM 5.x and above, there is an applicaiton user type as well -- and we hope that should let us use its credentials without associating any devices, but turns out we still have to create an "End User" and associate all devices with it.

    Subject: RE: Maximum number of devices that can be associated with a user
    Replied by: David Staudt on 05-06-2009 11:28:55 PM
    The maximum supported limit of user->phone associations is 2500, however that's a pretty unworkable number to configure via the web UI.  There is no 'super user' functionality built in, but you can offload the phone authentication mechanism to a separate application server.  See the IP Phone Services SDK's 'PushAuthenticate' sample code for some ideas on how this works:
     
    --------------------
     
    From the SDK Overview
     
    "PushAuthenticate is NOT is an IP Phone Service. PushAuthenticate is a sample script which can be used
    to offload authentication requests from the CallManager server. Many IP Phones Services (such as
    Push2Phone in this SDK) take advantage of the IP phone's HTTP server to PUSH information and
    commands. For large-scale applications, PUSHing to hundreds or thousands of devices, this can cause
    performance problems with the authenticate.asp script running on CallManager. The problem arises
    from the fact that all of these devices (phones) must be associated to a single userID/password (known
    by the PUSH application) so that the application can PUSH to all phones - this causes considerable
    overhead when processing the authenticate.asp script on CallManager.
    A better approach is to change the Authentication URL in CallManager Admin to point to an external
    authentication script, such as this one, which first checks for a specific userID/password (used by the
    PUSH application) and returns AUTHORIZED if it matches. If the userID/password is not matched by
    the PushAuthenticate script, it calls the authenticate.asp script on CallManager and "proxies" the
    authentication request from the phone. This allows you to offload the PUSH authentication to an
    external webserver while still using standard CallManager authentication for all other purposes."