The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The Cisco Jabber Guest server is set up with default credentials.
You can access Cisco Jabber Guest Administration on Windows with:
Google Chrome 18 or later
Microsoft Internet Explorer 8 or later (32-bit only)
Mozilla Firefox 10 or later
You can access Cisco Jabber Guest Administration on Mac with:
Your session times out after 30 minutes of inactivity.
The Cisco Jabber Guest server command-line interface (CLI) is set up with default credentials.
Think of users as accounts that can be used as organizational units for links. There is no association between a user and a link at which they can be reached.
All users are administrators.
Complete this task to unlock a locked account, or provide users with a temporary password.
Call links are classified as either in database or as ad hoc. When a Cisco Jabber Guest client tries to place a call to a link, the Cisco Jabber Guest server first checks to see if the link exists in the database. If the link exists, the operational parameters (destination endpoint, caller ID, called ID, and time the link is valid) are taken from the database. If the link is not listed in the database, the server next checks the Allow Adhoc Links setting. If the link is enabled, the server sends the call to Cisco TelePresence Video Communication Server or Cisco Unified Communications Manager using the string to the right of /call/ as the route string. If the setting is disabled, the call will not route unless the link exists in the database. Ad hoc links must be enabled before calls can be placed with them.
For more information about call links and how they are constructed, see the About Call Links section in this guide.
When you create a click-to-call link on a Cisco Jabber Guest server that is a member of a cluster, you must allow a small amount of time before that link is active on all servers in the cluster. This applies whether you create the link by using Cisco Jabber Guest Administration or the link API. In both cases, the link information replicates automatically to all other servers in the cluster. The amount of time required for replication varies depending on factors such as the network connection speed between the servers. Complete replication can occur within a second or may take several seconds.
If you deploy an application that creates links dynamically by using the link API and pushes them to the Cisco Jabber Guest client, we recommend that you factor this replication delay into your design. If a Cisco Jabber Guest user attempts to use a link that has not yet been replicated to the Cisco Jabber Guest server that handles the request, the attempt will fail.
There is no hard limit on the number of links that you can create on a Cisco Jabber Guest single server or cluster. We have tested with upwards of 25,000 links.
Want to specify a time and date in which a link is active? For example, if your company is hiring, you can create a link that a candidate uses to call for an interview. You can specify that the link is active between 2:00 p.m. and 4:00 p.m. on the day of the interview.
| Step 1 | From Cisco Jabber Guest Administration, click Links. |
| Step 2 | Click New. |
| Step 3 | Set the
request path, which is the part of the link after
/call. The request path must be unique:
For more information, see Call Link Format. |
| Step 4 | For
Destination, do one of the following:
The destination must resolve to a DN or URI that is routable from Cisco Expressway-C and Cisco Unified Communications Manager. |
| Step 5 | For Display name, enter the name to display on the client when a call is placed using this link. For example, if the link calls a help desk, enter Customer Support. You can set a default display name for all links. |
| Step 6 | For Caller name, enter the name to display on the destination endpoint in the enterprise. For example, if the link calls a physician's hotline, enter MD Hotline caller. If you do not enter a value, the caller name is Jabber Guest. |
| Step 7 | For Caller SIP alias, enter the caller ID that you want to display on the destination endpoint
in the enterprise.
If you do not enter a value, the caller ID is the value in the Default caller SIP alias field. The caller ID can only contain the following characters: A–Z, a–z, 0–9, hyphen (-), underscore (_), period (.), and plus sign (+). |
| Step 8 | If the link calls a video conference bridge that requires a unique caller name, check Append unique identifier to SIP alias. A unique number is appended to the SIP alias. Each time the link is clicked, the number increments. |
| Step 9 | For State, choose when the link is active. |
| Step 10 | Click Create. |
If you chose start and end dates for any of the links that you created, you can Set Your Links to Automatically Delete
You can create links in bulk by using the Cisco Jabber Guest API.
To download a sample application from the Cisco Jabber Guest API web page, click .
You cannot change the request path of a link after the link is created. For example, if the request path of a link reflects the link destination and the link destination changes, you must create a new link. You cannot update the request path to reflect the updated destination.
Complete this task to set a default display name for all links, including ad hoc links.
Complete this task to set a default caller ID for all links, including ad hoc links.
A unique caller name is required to allow Cisco Jabber Guest callers into some video conference bridges. Complete this task to append a unique identifier to ad hoc links.
The settings on the Mobile page are for iOS support.
When iOS users click a call link, the server redirects them to the value set in the Redirect URL for iOS field. The default value of the Redirect URL for iOS field is a Cisco Jabber Guest welcome page.
On the client side, users are then redirected to a special URL using the scheme value set in the iOS URL scheme field , which allows the appropriately registered native application to launch into the call. The default value of the iOS URL scheme field is jabberguest.
If Cisco Jabber Guest is not installed, users are then redirected to the value set in the iOS App Store link field. By default, the iOS App Store link field contains a link to download Cisco Jabber Guest.
If your organization has developed its own iOS application that implements Cisco Jabber Guest, you can update these fields so that your application opens instead of Cisco Jabber Guest.
Alternatively, if you do not want an application to open when iOS users click a call link, you can edit the Redirect URL for iOS field to redirect users to another location, such as a web page.
Complete this task to download log files as a zip archive for troubleshooting or maintenance.
You can monitor product use in several ways.
Complete this task to view the number of unique (per device) browser plug-ins that have been downloaded since Cisco Jabber Guest was installed.
Complete this task to view the number of current active call sessions. This number includes all users who have clicked a link but have not yet clicked Call.
Complete this task to help you determine the capacity that is required for your deployment. Usage logs show the number of call sessions that were active each minute in a day.
Feedback