Lab 2 - Jabber Guest

Lab 2-‐Jabber Guest

Lab written by: Kristin Gioberto, Collaboration CSE [email protected]

JabberC is a new consumer to business (C2B) solution being developed by CMBU, which will be renamed at FCS as Jabber Guest. The idea is to extend the reach of Cisco's enterprise telephony to people outside the corporate firewall who do not have phones registered with CUCM. For instance, a large retailer wants to provide a convenient way for customers to have a video chat with an in-‐house expert. The retailer can post a link on their website that embodies a "click to call" link. A customer browsing the site clicks on the link and initiates a video call to a support line, which transfers the call to a waiting expert. The customer was not required to open an account, create a password, or otherwise authenticate. She just clicks to call. We think this is a powerful new tool for Cisco customers.

This is a very short and simple lab that enables the new JabberCallme/Consumer/C *functionality. The OVA for Jabber Guest has been loaded which integrates directly into Communications Manager in the EAP build available, as the Reverse Proxy functions* are yet to be added to Expressway. In a production environment, JabberC requires that your Cisco Unified Communications Manager (CUCM) be configured to work with Cisco VCS. The goal of this lab is to become familiar with JabberC without the additional overhead VCS; again mainly because the functionality is not available.

*Reverse proxy server

The reverse proxy server sits in the DMZ and sends traffic to the JabberC server in the enterprise. The use of a reverse proxy server provides an extra layer of protection for the network. It is recommended that the reverse proxy be configured to proxy only certain JabberC URLs, such as:• /call • /jabberc • /jc. Additionally, if a request is not HTTPS, it redirects to HTTPS, and traffic between the reverse proxy and JabberC should be HTTPS.

Server Configuration The virtual machine has been deployed and assigned the appropriate network information/

JabberC Links Configuration JabberC links, users and other call features are controlled from the application’s web interface. To manage these features you must log into the Web Common Administration console. Currently, access to WCA is only supported on Firefox and Chrome. Call links are constructed in the following format: https://example-‐jabberc/call/<DN or UserID>@example.com BEFORE BEGINNING, BE SURE BROWSER WIDOW IS MAXIMIXED

1. Navigate to https://10.5.0.85/admin (Username: admin and Password: jabbercserver)

2. Create a new user a. Click Users > New. b. Enter Alias, First Name, Last Name, Display Name and click Create. Add

SIP URI and click Update. The user details should be as follows.

i. Update password, by clicking on Password when within the user.

Set as Cisco12345 ii. Add link, by clicking Links when within the user. Click New. Enter

Destination: [email protected], Display Name: Steve Rogers, Caller Name: JabberC Call

Click Create.

iii. Note the link URL at the top.

Note: When a JabberC client tries to place a call to a link, the JabberC server first checks to see if the link exists in the db. If so, the operational parameters (destination endpoint, caller ID, called ID, and time the link is valid) are taken from the database. If the link is not listed in the database, the server next checks the Ad Hoc link setting. If that is enabled, the server sends the call to VCS or CUCM using the string to the left of /call/ as the route string. If the setting is disabled, the call will not route unless the link exists in the database. Ad hoc links are enabled from the Web Common administration console. With JabberC, calls can be made to any production CUCM endpoint by dialing its directory number (DN). Additionally, if the system administrator has enabled URI dialing, calls can be placed to the endpoint with either it is a DN or the URI.

Verify Communications Manager is Configured Properly Build SIP Trunk to JabberC Server and observe URI dialing.

1. Login to Communications Manager at 10.5.0.60 (username: administrator and password: Cisco12345)

2. Review: Observe URI dialing for Steve Rodgers is configured appropriately

Device>Phone>CSFSROGERS>Click on Line1>look for Directory URI under

Directory Number

3. Configure SIP Trunk to JabberC server a. Go to Device>Trunk>Add New b. Enter the below Trunk Configuration and click next

i. Trunk Type: SIP ii. Device Protocol: SIP iii. Trunk Service Type: None (Default)

c. For Trunk Configuration enter: i. Device Name: JabberC ii. Device Pool: Default iii. Inbound Calls>Calling Search Space: css-‐lab iv. Destination Address: 10.5.0.85 v. SIP Trunk Security Profile: Non Secure SIP Trunk Profile vi. SIP Profile: Standard SIP Profile

d. Click: Reset>Reset for changes to take affect. (Reset may take up to 20 seconds to take effect)

Make Browser Based Call

1. Usign RDP, remote desktop to PC1, Steve Roger’s PC at 10.5.0.90, password: Cisco12345>connect

a. Start Jabber on desktop>use Phone Mode>Enter [email protected] and password: Cisco12345

2. Open a second remote desktop session to PC3, at PC3.collab.com (username: collab\nfury and password: Cisco12345)

a. Open Firefox and enter the JabberC link you created: https://10.5.0.85/call/[email protected]

Note: the caller requires a compatible browser running on a multimedia capable PC (with camera and microphone).

• The Windows® client requires Vista or above and, any of: Firefox 10+, Chrome 18+, and Internet Explorer 8+ (32-‐bit only).

• The Mac OS X client requires Mac OS X 10.7 or 10.8, and any of: Safari 5+, Firefox 10+, or Chrome 18+.

b. Click I understand risks, click, click c. You will be prompted to “Install plugin”. Ensure you Open and Run this

download.

Note: The JabberC solution includes a browser plugin that is downloaded and installed by the caller on the local machine. The JabberC web page prompts the client to download the plug-‐in the first time the service is used. Periodically new code with fixes or new functionality is deployed. When that happens, the user is prompted to update the plug-‐in the next time an attempt is made to place a call. The plug-‐in update procedure is the same as for a new install: download and install.

d. Always Allow access to your microphone and camera.

e. Place Call and observe video the video.

Note: You may test from a non-‐lab PC, but you must have only one active NIC. A major source of one-‐way/no media problems is a result of crude handling multiple interfaces. We plan to fix this before we ship.

Resources Some go-‐to resources:

• All current documentation is in the JabberC EAP community: • Here is an excellent JabberC wiki:

http://wikicentral.cisco.com/display/PROJECT/JabberC+External+Link+Deployment

• To add to your email signature easily click here: https://jabberc-‐dev.cisco.com/call/email_signature.html

Optional SSH

The below configuration performs a quick check on the SIP config that was entered on install.

• Remote desktop to PC1, Steve Roger’s PC at 10.5.0.90

• Open Putty from the desktop and SSH to the JabberC server at 10.5.0.85. • Click Yes to trust the security warning. • Login to JabberC with Username: root AND Password: boxgrinder • Go to this directory where the configuration files are stored

§ Enter the etc path by [root@JabberC jabberc]# cd /opt/cisco/jabberc/etc

§ Enter a turn config [root@JabberC etc]# vi sipconfig.xml. § It should look as follows:

<?xml version='1.0' encoding='UTF-‐8'?> <sip-‐config> <sip-‐server>10.5.0.60</sip-‐server> </sip-‐config>

You have now completed the JabberC section. Please continue onto the next section!

Lab 2 - Jabber Guest

Documents

Transcript of Lab 2 - Jabber Guest