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.
A Cisco Jabber Guest call link allows anyone to click-to-call an endpoint in the enterprise without creating an account, setting a password, or otherwise authenticating.
The Cisco Jabber Guest web client or mobile client launches when a link is clicked. This process greatly simplifies how a user places a call; they simply click on the provided link. This process allows the user to easily place a video call to the destination associated with the link.
The Cisco Jabber Guest server checks to see if the link exists in the database when a call is placed using it. The following operational parameters for the call are taken from the database if the link exists:
The server checks the Allow ad hoc links setting if the link is not listed in the database. If ad hoc links are enabled, the server sends the call to Cisco Expressway or Cisco Unified Communications Manager using the string to the right of /call/ as the route string. If the setting is disabled, the call is not routed unless the link exists in the database. Ad hoc links are enabled from Cisco Jabber Guest Administration.
Calls can be made to any Cisco Unified Communications Manager endpoint by dialing the directory number (DN). Calls also can be placed using a URI if URI dialing has been enabled.
Call links are constructed in the following format:
https://example-jabberc/call/DN or UserID@example.com
The following table provides some examples of how links are constructed.
URL | Notes |
---|---|
http://example-jabberc.com/call/janedoe@example.com |
URI links work only for endpoints with URI dialing enabled. |
http://example-jabberc.com/call/5309@example.com |
4-digit DNs work only for endpoints homed on the same cluster. |
http://example-jabberc.com/call/17011701@example.com |
8-digit DNs work for all endpoints on the same domain. |
Note | The domain is optional. If it is supplied it must match the enterprise domain configured in Cisco Unified Communications Manager. If a domain is not supplied on an ad hoc link, the SIP domain (in ) for this server is used. |
Ad hoc links are disabled by default and are enabled from Cisco Jabber Guest Administration.
A call link is either an entry in the Cisco Jabber Guest Server database, or an ad hoc link that is not in the database.
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.