Cisco Jabber Guest 11.2 Administration Guide

Bias-Free Language

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.

Book Contents
Find Matches in This Book
Available Languages
Download Options

Book Title

Cisco Jabber Guest 11.2 Administration Guide

Chapter Title

Reference

Results

Updated:
January 17, 2020

Chapter: Reference

Reference

Call Link Format

Call links are constructed in the following format:

https://example-jabberguest.com/call/directory number (DN) or UserID@example.com[?callerName=customized-caller-name]

The following table provides some examples of how links are constructed.

Table 1. Example Call Link URLs

URL

Notes

http://example-jabberguest.com/call/janedoe@example.com

URI links work only for endpoints with URI dialing enabled.

http://example-jabberguest.com/call/5309@example.com

4-digit DNs work only for endpoints homed on the same cluster.

http://example-jabberguest.com/call/17011701@example.com

8-digit DNs work for all endpoints on the same domain.

http://example-jabberguest.com/call/janedoe?callerName=Alice

Destination endpoint will display the guest caller name as “Alice” if setting of allow customized caller name is enabled.

Note

The domain is optional. If the domain 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 Settings > Call Control and Media) for this server is used.


Note

URL query parameter callerName is supported only in Cisco Jabber Guest 11.1(0) and its later releases, it allows guest clients to have the ability to specify their own caller names. The administrator can enable this feature by accessing Links > Individual Link > Allow customized caller name and Settings > Links > Allow customized caller name for ad hoc links.

Mapping Between Link Fields and SIP Headers

Link Field

SIP Header

Destination

Request-URI in the INVITE

Caller SIP Alias

Note 

If the administrator does not enter a value in the Caller SIP alias field, the value in the Default caller SIP alias field is used.

User portion of the From: and Remote Party ID: (RPID) headers

Example:

  • From: <sip:alice@cisco.com>

  • Remote-Party-ID: <sip:alice@cisco.com>

Caller name

Note 

If the administrator allows customized caller name and guest client specifies his/her own caller name, the customized value overrides this field, otherwise, if the administrator doesn't enter a value in the Caller name field,the caller name displayed is Jabber Guest.

Display name of the From: and Remote Party ID: (RPID) headers

Example:

  • From: "Alice" <sip:alice@cisco.com>

  • Remote-Party-ID: "Alice" <sip:alice@cisco.com>

Append unique identifier to SIP alias

Adds a unique identifier to the From: and Remote Party ID: (RPID) headers

Example:

  • From: <sip:alice-123@cisco.com>

  • Remote-Party-ID: <sip:alice-123@cisco.com>

Was this Document Helpful?

FeedbackFeedback

Contact Cisco