Jabber Guest Administration Guide 10.5
Jabber Guest Administration Guide 10.5
5 Administration Guide
First Published: July 30, 2014
Last Modified: March 29, 2015
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,
INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH
THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,
CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version
of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS" WITH ALL FAULTS.
CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT
LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS
HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network
topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional
and coincidental.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://
www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership
relationship between Cisco and any other company. (1110R)
CHAPTER 1 Introduction 1
Introduction 1
CHAPTER 7 Reference 27
Call Link Format 27
Mapping Between Link Fields and SIP Headers 28
CHAPTER 8 Troubleshoot 29
Locate chip.log File 29
Locate chip.dmp File 29
Reset Admin Password for Cisco Jabber Guest Administration 30
Reset Root Password for Cisco Jabber Guest Server 30
Introduction
Cisco Jabber Guest is a consumer-to-business (C2B) solution that extends the reach of Cisco's enterprise
telephony to people outside of a corporate firewall. Cisco Jabber Guest provides these people with the ability
to use existing Unified Communications assets to communicate with your enterprise. Features are controlled
by an administrator by using Cisco Jabber Guest Administration. Administrators are responsible for managing
links, users, and system settings that control the functionality of the product. Administrators also have access
to logs for troubleshooting purposes. To manage these features you must sign in to Cisco Jabber Guest
Administration.
Procedure
Step 1 From a compatible browser, navigate to the IP address or host name of your Cisco Jabber Guest server and
append /admin/ to the URL.
Step 2 For Alias, enter admin.
Step 3 For Password, enter jabbercserver.
The first time that you sign in you must change your password.
Step 4 Enter a new password.
Procedure
Procedure
Step 1 From Cisco Jabber Guest Administration, choose Settings > Mobile.
Step 2 To set up Android support, do the following:
a) For Android Package Name, enter the package name that uniquely identifies your application.
b) For Android URL scheme, enter the URL scheme for the Android application.
c) For Redirect URL for Android, enter the URL that you want the server to redirect Android users to when
they click a call link. The server can redirect users to another domain.
Step 3 To set up iOS support, do the following:
a) For iOS App Store link, enter the URL to the application in the iOS App Store.
b) For iOS URL scheme, enter the URL scheme for the iOS application.
c) For Redirect URL for iOS, enter the URL that you want the server to redirect iOS users to when they
click a call link. The server can redirect users to another domain.
Step 4 Click Update.
Create User
Procedure
Update User
Procedure
Procedure
Delete User
Procedure
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.
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.
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 Settings >
Call Control and Media) for this server is used.
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.
Create Link
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.
Procedure
Important 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.
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.
What to Do Next
If you chose start and end dates for any of the links that you created, you can Set Your Links to Automatically
Delete, on page 15
Related Topics
Set Default Display Name for Links, on page 14
Mapping Between Link Fields and SIP Headers, on page 28
Related Topics
Cisco Jabber Guest API
Procedure
Step 1 From Cisco Jabber Guest Administration, choose Settings > Links.
Step 2 For Default display name, enter the name to display on the client when calls are placed. If a Display name
is set for an individual link, that name overrides the Default display name.
Step 3 Click Update.
Procedure
Step 1 From Cisco Jabber Guest Administration, choose Settings > Links.
Step 2 For Default caller SIP alias, enter the caller ID that you want to display on the destination endpoint. If a
Caller SIP alias is set for an individual link, that value overrides the Default caller SIP alias.
The caller ID can only contain the following characters: A–Z, a–z, 0–9, hyphen (-), underscore (_), period
(.), and plus sign (+).
Procedure
Step 1 From Cisco Jabber Guest Administration, choose Settings > Links.
Step 2 For Expired links deleted after n days, choose how many days after the end date passes that you want to
delete the links.
If you do not enter a value or if you enter a value of 0, expired links are kept in the database indefinitely.
Procedure
Step 1 From Cisco Jabber Guest Administration, choose Settings > Links.
Step 2 Check Append unique identifier to SIP alias for ad-hoc links.
A unique number is appended to the SIP alias. Each time the link is clicked, the number increments.
Step 3 Click Update.
Step 1 From Cisco Jabber Guest Administration, choose Services > Passwords.
Step 2 Check Complexity check if you want passwords to meet the following requirements:
• Passwords must be eight or more characters in length.
• Passwords must include three of the following characters:
◦At least one uppercase letter
◦At least one lowercase letter
◦At least one number
◦At least one symbol
Step 3 For History size, enter the number of passwords that are remembered.
For example, if you enter 3, the user's previous three passwords are remembered. If a user tries to change the
password and reuses one of the previous three passwords, the user is prompted to specify a different password.
Step 4 For Maximum failed sign ins, enter the number of sign in attempts allowed before the user account is locked.
Step 5 Click Update.
Related Topics
Unlock User Account, on page 8
Download Logs
Complete this task to download log files as a zip archive for troubleshooting or maintenance.
Procedure
Procedure
Procedure
Procedure
Step 3 Open the usage log with an application that can open CSV-format files, such as Microsoft Excel or Notepad
++.
The data appears in the format: mm/dd/yyyy hh:mm:ss, number of active call sessions.
Procedure
Procedure
Step 1 In vSphere Client, verify that the virtual machine involved in the disaster does not appear in the virtual machines
and templates inventory tree.
Step 2 If the virtual machine appears in the virtual machines and templates inventory tree, turn off and delete this
virtual machine:
a) Right-click the virtual machine.
b) Choose Power > Power Off.
c) Right-click the virtual machine and click Delete from Disk.
Step 3 In the virtual machines and templates inventory tree, select the location where you want to deploy the backed
up OVA.
Step 4 Choose File > Deploy OVF Template.
Step 5 In the Source screen, browse to the location of the OVA, and then click Next.
Step 6 Verify the details in the OVF Template Details screen, and then click Next.
Step 7 In the Name and Location screen, enter a name for the template, select its location, and then click Next.
Step 8 In the Host / Cluster screen, select where you want to run the template, and then click Next.
Step 9 In the Storage screen, select where you want to store the virtual machine files, and then click Next.
Step 10 In the Disk Format screen, select the format in which you want to store the virtual disks, and then click Next.
Step 11 In the Networking Mapping screen, select the appropriate Destination Networks for OVA deployment, and
then click Next.
Step 12 In the Properties screen, enter the properties that are appropriate for your network, and then click Next.
Step 13 On the Ready to Complete screen, make sure that Power on after deployment check box is unchecked.
Important Before you turn on the virtual machine, you must update its MAC
address.
Step 14 Click Finish.
Step 15 Repeat Steps 1 through 14 for each virtual machine in the cluster that you need to restore.
Related Topics
Update the MAC Address of Each Virtual Machine, on page 23
Procedure
Important Make sure that you back up your server cluster before you upgrade.
Procedure
Important Adding a date and time or a description can help you determine which snapshot to
restore.
Step 5 Select whether the snapshot includes the virtual machine's memory. If the snapshot includes the memory state,
the virtual machine will be in the same power state as when you created the snapshot:
Virtual Machine State When Parent Snapshot Is Virtual Machine State After Restoration
Taken
Powered on (includes memory) Reverts to the parent snapshot, and the virtual
machine is powered on and running.
Powered on (does not include memory) Reverts to the parent snapshot and the virtual machine
is powered off.
Powered off (does not include memory) Reverts to the parent snapshot and the virtual machine
is powered off.
Important Mixed version clusters are not supported outside of an upgrade or revert maintenance window.
Procedure
When the snapshot is restored, in the Recent Tasks list, the status of the Revert task shows Completed.
Step 6 Repeat Steps 4 and 5 to restore the other virtual machines in the cluster.
Step 7 Verify that the cluster restored correctly by signing in to Cisco Jabber Guest Administration as an administrator.
The Cisco Jabber Guest version number to which you restored appears at the bottom of the screen.
Step 8 Check to make sure that all users and links look as you expect.
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.
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.
Caller SIP Alias User portion of the From: and Remote Party ID:
Note If you do not enter a value in the Caller SIP (RPID) headers
alias field, the value in the Default caller Example:
SIP alias field is used.
• From: <sip:alice@cisco.com>
• Remote-Party-ID: <sip:alice@cisco.com>
Caller name Display name of the From: and Remote Party ID:
Note If you do not enter a value in the Caller (RPID) headers
name field, the caller name is Jabber Guest. 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>
Procedure
Procedure
Step 1 Open a console session for the Cisco Jabber Guest server and restart the server.
Step 2 Press any key to interrupt the start process.
Step 3 Press e to edit.
Step 4 From the entries, select kernel and press e to edit.