Some Callisto features (Gadgets) can be integrated in various platforms and using different authentication methods.

Standalone page

To add a standalone page in Windows, open the respective URL in Edge and then choose Apps > Install this site as an app. You can then create a desktop shortcut using the option Apps > Manage apps.

Authentication with URL query strings

You can create a URL that includes login credentials. In the following example, the user with the name username is logged in and redirected to the SmallAgentDesk page.

http://<callisto>/LogonPage.asp?page=/Applications/inbound/ProfACD2/src/SmallAgentDesk.asp&user=username&pwd=password

<callisto> is the root path of your Callisto installation. The three query strings are:

• page: The page to which user will be redirected after authentication.
• user: The username which is used to login to Callisto.
• pwd: The respective user password.

Login using the default Callisto authentication HTML form

To use the default authentication form, use the following URL, where <callisto> is the root path of your Callisto installation:

http://<callisto>/Jabber/Messages/Messages.asp

After entering valid credentials, the user gets redirected to the page. If you use this authentication method, checking the option Remember last used credentials in the user settings dialog is recommended.

Login using SSO (Single Sign-On)

To use single sign-on authentication, use the following URL ,where <callisto> is the root path of your Callisto installation:

http://<callisto>/LgonPageSSO.asp?page=/Jabber/Messages/Messages.asp

This will authenticate the user with the defined Single Sign-On provider.

Integration with COC

COC provides HtmlPanes that can be used to integrate Callisto Gadgets. For details on configuring HtmlPanes, refer to the COC configurator manual.

All the authentication methods described in the section Standalone page can be also used in COC integration, but the recommended method is authentication with URL query strings. When using this method, the URL should be modified in the following way, where <callisto> is the root path of your Callisto installation:

http://<callisto>/LogonPage.asp?page=/Applications/inbound/ProfACD2/src/SmallAgentDesk.asp&user=%user%&pwd=%pwd%

COC will automatically replace the %user% and %pwd% placeholders with the credentials of the currently logged in user.

If you use one of the other two authenentication methods, the URLs to be used are identical to the ones described in the section Standalone page.

Integration with Cisco Jabber client

To integrate Callisto in Jabber, a custom tab needs to be created. A custom tab can be created in two ways:

Integration using Cisco Jabber GUI

In Jabber, click the menu icon and choose File > New > Custom Tab.

The window Create new custom tab will open. Enter the name of the tab, and the URL of the respective Jabber tab (see below). After entering the link, click Create and the custom tab will appear in the tab bar on the left.

Integration by uploading a configuration file

A more reliable way to deploy custom tabs is by adding or editing a Jabber configuration file.

Here is an example of a Jabber configuration file:

<?xml version="1.0" encoding="utf-8"?>
<config version="1.0">
	<Client>
		<jabber-plugin-config>
			<browser-plugin>
				<page refresh="false" preload="true">
					<tooltip>Recent Calls</tooltip>
					<icon>http://<callisto>/Jabber/RecentCalls/JabberIcon.png</icon>
					<url>http://<callisto>/Jabber/RecentCalls/RecentCalls.asp</url>
				</page>
				<page refresh="false" preload="true">
					<tooltip>Recording</tooltip>
					<icon>http://<callisto>/Jabber/Recording/JabberIcon.png</icon>
					<url>http://<callisto>/Jabber/Recording/Recording.asp</url>
				</page>
				<page refresh="false" preload="true">
					<tooltip>Messages</tooltip>
					<icon>http://<callisto>/Jabber/Messages/JabberIcon.png</icon>
					<url>http://<callisto>/Jabber/Messages/Messages.asp</url>
				</page>
			</browser-plugin>
		</jabber-plugin-config>
	</Client>
	<Options>
		<ShowTabLabel>true</ShowTabLabel>
	</Options>
	<Policies>
		<EnableSIPURIDialing>true</EnableSIPURIDialing>
	</Policies>
</config>

Replace <callisto> in the URLs with the domain name or IP address of your Callisto installation. Save the file using UTF-8 encoding, name it Jabber-config.xml and upload it it to the CUCM TFTP server. Once the file is uploaded, you will have to restart the TFT server.

After the next login, the respective Jabber users will find the defined tabs in the Jabber navigation bar.

More information about setting up custom tabs in Cisco Jabber is available on the official Cisco website:

• On-Premises Deployment for Cisco Jabber 11.5 – Create and Host Client Configuration Files
• Feature Configuration for Cisco Jabber 12.7 – Custom Embedded Tabs