Cisco Jabber Guest 10.6 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.
- Updated:
- December 11, 2015
Chapter: Reference
Contents
Reference
Call Link Format
Call links are constructed in the following format:
https://example-jabberguest/call/directory number (DN) or UserID@example.com
The following table provides some examples of how links are constructed.
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. |
 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 ) for this server is used. |
Mapping Between Link Fields and SIP Headers
Link Field |
SIP Header |
||
|---|---|---|---|
Destination |
Request-URI in the INVITE |
||
Caller SIP Alias
|
User portion of the From: and Remote Party ID: (RPID) headers |
||
Caller name
|
Display name of the From: and Remote Party ID: (RPID) headers |
||
Append unique identifier to SIP alias |
Adds a unique identifier to the From: and Remote Party ID: (RPID) headers |