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.
Call links are classified either as in database or ad hoc. When a call link is clicked, the Cisco Jabber Guest web client opens and checks if the link exists in the database. If the link exists in the database, the following operational parameters for the call are taken from the database:
If the link is not listed in the database, the server checks the Allow ad hoc links setting (in Cisco Jabber Guest Administration > Settings > Links). 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 Allow ad hoc links is disabled, the call is not routed unless the link exists in the database.
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.
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 | If you want to allow guest clients to specify their own caller names, check Allow customized caller name. Guest clients can append additional URL query parameter callerName to override Caller name with a customized value. This customized value will be displayed on the destination endpoint in the enterprise and could be specified in different languages other than just English. See Call Link Format.
See Cisco Unified Communications Manager Configuration Guide for more details.
| ||||||||||||
Step 8 | 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 contain only the following characters: A-Z, a-z, 0-9, hyphen (-), underscore (_), period (.), and the plus sign (+). | ||||||||||||
Step 9 | 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 10 | For State, choose when the link is active. | ||||||||||||
Step 11 | For Auto call, select the Disable or Enable option. Disable is selected by default. If you select Enable, you must enter the timer in the Seconds field to start a call automatically. The permitted range of values is between 0 and 60.
| ||||||||||||
Step 12 | For Guest video policy, select the option as per the privacy control you wish to set:
| ||||||||||||
Step 13 | 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.
Complete this task to set a timer to automatically start a call for ad hoc links.
Note | This setting is supported only in Cisco Jabber Guest 10.6(9) and its later releases. |
You can set controls on the guests' ability to conduct video calls. That way, you can ensure that the guest users can be permitted to make audio calls and you can set restrictions on their video call capability.
Note | This setting is supported only in Cisco Jabber Guest 10.6(9) and its later releases. |
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.
Complete this task if you want to allow guest clients to specify their own caller names for ad hoc calls. See Call Link Format for more information on customizing a guest caller name.
The selected language locale is supported and installed on Cisco Unified Communications Manager and the destination endpoint(s).
The destination endpoint User Locale matches locale setting of Common Device Configuration in SIP trunk setting.
Transmit UTF-8 for Calling Party Name in SIP trunk setting is checked for Unicode support.
See Cisco Unified Communications Manager Configuration Guide for more details.
Note | This setting is supported only in Cisco Jabber Guest 11.1(0) and its later releases. |
Note | If the guest client specifies the customized caller name on Microsoft Internet Explorer 10 or earlier version with different language other than English, the customized value cannot be displayed correctly on destination endpoints as the URL query parameter cannot be encoded with UTF-8. On Microsoft Internet Explorer 11, guest client needs to follow these steps to enable UTF-8 encoding on URL query parameter to ensure customized caller name is displayed correctly on destination endpoints:
|
Step 1 | From Cisco Jabber Guest Administration, choose . |
Step 2 | Check Allow customized caller name for ad hoc links . |
Step 3 | Click Update. |