Cisco Unified Presence APIs Developer Forums

« Back to SOAP API

CUP reference Application

Combination View Flat View Tree View
Threads [ Previous | Next ]
Hi, I am using the CUP reference application (starter kit) (.NET based window application), whenever I try to Login through the application, it throws an error, Invalid session key for End user login, I tried debugging the application, it works fine for the Application User login but the code breaks at end user level login, don't know why? I think code seems to be fine, any help or suggestions???
 
Is the Application UserName and End User Name same or is there some difference??

Application user is different from that of the end user.
 
To have a End-user logging in, you need the App-user login 'session key'.
 
This is explained with a sample codes in'Developer Guide for Cisco Unified Presence'
under section 'About the Client Configuration Web Service Functions' & 'Presence Web Service'
 

Hi Giggesh,
 
I am using the starter kit for MS Visual Studio, and the code is doing the same thing... Passing the Application session key to login the end user, but the output for end user login comes out to be --> Invalid session key for end user.
 
I assumed that both the Application User Name and End User Name are similar, may be because of that it is throwing this error, could you please help in distinguishing between Application UserName and End UserName?
 
Thanks.

To explain in Detail:
To log in to the Client Configuration Web Service, a client application sends a username and password in the login request for authentication. Cisco Unified Presence creates a session key, an opaque string, if the user credentials are verified. The client includes the session key in the SOAP header portion of subsequent SOAP requests to the Client Configuration Web Service, including logout requests.
The Client Configuration Web Service supports the following login scenarios:
¿The client application sends a username and password for an end user in the login request for authentication, and Cisco Unified Presence returns a unique session key for the end user.
¿The client application logs in to Cisco Unified Presence as an ¿application user¿ using an application username and password. The client application can then log in an end user by passing the session key for an application user, and the username for an end user in the login request; a unique session key for the end user is returned.
 
FYI:
The Application Users is created via Cisco Unified Presence server(CUP) and End User is created via Cisco Unified Communications Manager (CUCM) associated to the CUP server.
 
For further explanation please refer : CUP Developer Guide at http://developer.cisco.com/web/cup/home
 

Hello,
 
We developed a Windows Console Application (CLI) for CUP presence.
http://www.loukola.com/apps/cup2ad/cup2ad.htm
 
The software reads CUP end user presence status and writes it to Active Directory + creates a web page with CUP presence status info.
 
A trial version of the application is available for testing. It is limited to updating AD+html for 4 CUP users only, but it displays status of all contact users on the cli.
http://www.loukola.com/apps/cup2ad/cup2ad-trial-v108.zip
 
Trial package includes config guide with instructions on how to prepare CUP and CUCM servers for this applet: one application user for CUP and an extra end user for CUCM.
 
Tested with CUP 8.0(1) + AD 2003. Should work with CUP 7.X as well.
 
Regards,
 
Mika Loukola
 
P.S. We are starting a new sw development project for subscribed CUP presence. I'll make a new post once we can deliver trial software for testing.