free calling app for chromebook

Prepare your environment for Calling in Webex App (Incorporated CM)

Call control environment requirements

To enable Calling in Webex App (Unified CM), you must use one of the fostered Unified CM-founded Lake herring call control solutions, and guarantee that you're on the minimum dependent version or later.

Table 1. Supported Unified CM releases

Call solution	Adaptation
Cisco Unified Communications Manager*	Minimum
	Screen background and changeable (Mechanical man) Interconnected CM Release 11.5(1) SU3 and later for desktop. While not mandatory, this minimum also release supports Firebase Cloud Messaging (FCM) push notifications along Android. Screen background and seaborne (iOS) For an 11.5 release, Unified CM Unloosen 11.5(1) SU8 surgery a later SU is required minimum for Apple Push Notification (APN) servicing on iOS ambulatory devices. (This release is non gimbaled in China. Ensure below.) For a 12.5 release, Unified CM Release 12.5(1) SU3 or a later SU is required for iOS APN documentation. Secure calls (SIP Oauth) Unified Curium Turn 12.5(1) and later Bank note CAPF is non supported.
	Recommended
	Desktop and mobile Coordinated CM Release 12.5(1) SU3 or later.** This recommended release ensures that force out notifications work for all transferrable platforms in your environment and that secure calling is supported. See Force out Notifications for more info. Note If your organization is settled in Red China, you must employment this version at a minimum. If you use Mobile Inaccessible Approach (MRA) and want to configure MRA failover, Unified Centimetre Release 14.0 or later is required. SSO Redirect URI This sweetening has particularised Unified Atomic number 96 and Expressway requirements. See the SSO Redirect URI section in Recommended Configuration for more than data.
Coregonus artedi Business Variation	Mark off the package load summary certification for BE6K and BE7K to ensure the result is gushing a supported version of Unified CM.
Cisco Hosted Collaboration Solution	11.5 and later at a minimum. 12.5 and later is suggested for SIP Oath encrypted calls support. (CAPF is not supported.)
Cisco Integrated Communications Manager Cloud	—

_{* For voice mail integration in Webex App, we urge that the Coregonus artedi Unity Connection version equal the Unified CM version. However, make sure the certification method and credentials are the same across some servers.}

_{** In alignment with Apple's changes to the iOS notification architecture, Cisco Webex App is implementing Apple Push Notification support for notifications. We extremely urge that customers upgrade Cisco Unified Communication theory Manager, Cisco Expressway, and Cisco Webex App arsenic shortly as feasible. Failure to advance connected time will result in loss of voice notification for Lake herring Webex App users using Unified Communication theory Manager and IM notifications for Cisco Webex App iOS users. For up to date support information that is related to Push Notifications with iOS 13, including upgrade requirements, refer to Orchard apple tree Push Notification Service Updates.}

While not needful, if you want Changeable and Remote Access (MRA) support (so Webex App can be used in softphone modality unlikely the corporate network), you must use a Cisco Freeway traversal pair, and see that you'rhenium connected the minimum supported version or late.

Table 2. Supported Expressway releases

Call solution

Version

Cisco Expressway E and C traverse couplet for Mobile and Remote Memory access (MRA)

X8.11.4 or later is needful for Vocation in Webex App (Unified CM). Consider the "Important Data" section in the Motorway Release Notes for more information. This release and later provide added security. X12.6 operating theatre by and by for Push Notifications. If you use Mobile Unlikely Access (MRA) and want to configure MRA failover, Expressway Publish X14.0 or later is needed. Run into the Mobile and Outside Access via Expressway Deployment Template for more selective information.

Unified CM feature requirements

Some Unified Centimeter features are automatically available in Webex App afterwards you configure your environment. Nonetheless, certain features want to be preconfigured in Interconnected CM for them to exploit in Webex App.

Auto answer with tone on connect

You can configure auto answer on a directory act that is assigned to the user. See the System Configuration Point for Cisco Unified Communications Manager for your release at https://www.cisco.com/c/en/us/financial backing/coordinated-communications/unified-communications-director-callmanager/products-installation-and-shape-guides-list.html and see the Cisco Unified Centimetre Presidency online help for more information about the Auto Answer scene.

For an agent on Webex to hear a tone in front the call connects, choose True for the Tone on connect Cisco CallManager service parametric quantity. This parameter determines whether a tone plays to indicate that media starts to stream. The valid values for this parameter are Geographic, which plays a tone, or False, which does not play a tone, and the default is Faux. This Global Parameter affects altogether the users in the bundle.

Telephone call Park

The Call Park feature allows you to place a turn hold so that hind end be retrieved from another phone operating theater soft customer in the Unified Communications Manager organisation (for model, a phone in other post Beaver State the Webex app). If you are on an active call, you can parking lot the call to a call parkland lengthiness by clicking Park in Webex. Another phone or soft customer in your system can and so dial the telephone park extension to retrieve the call.

For more information approximately call park configuration, pick up "Call Park and Directed Call Park" in the Boast Configuration Maneuver for Cisco Unified Communications Manager for your unfreeze at https://www.cisco.com/c/en/us/reenforcement/unified-communication theory/co-ordinated-communications-manager-callmanager/products-installation-and-configuration-guides-list.html.

Call Recording

Yell Recording enables a recording server to archive factor conversations. Webex App supports this feature for Unified CM-based deployments.

Some releases of Unified Cm require a device package to enable transcription capabilities. To corroborate, verify that the Built In Bridge field is forthcoming in the Headphone Constellation window for the device. If the playing field isn't on tap, download and enforce the just about late gimmick packages.

For detailed information about how to configure call recording, see the "Recording" chapter in the Feature Configuration Guide for Cisco Unified Communications Manager.

For configuration parameters that you can configure in the Rav Config XML file OR client configuration service, see the Feature Parameters shelve in the Appendix in this guide.

Telephone dial Plan Mapping

You configure dial architectural plan mapping to ensure that dialing rules on Cisco Interconnected Communication theory Manager match dialing rules on your directory.

Application Telephone dial Rules

Application dial rules mechanically add or remove digits in phone numbers that users telephone dial. Practical application dialing rules manipulate numbers pool that users dial from the client.

For example, you tooshie configure a dial predominate that automatically adds the digit 9 to the start of a 7 digit phone number to provide entree to outside lines.

Directory Lookup Dial Rules

Directory lookup telephone dial rules transmute caller ID numbers into numbers that the customer can lookup in the directory. Each directory lookup linguistic rule you delimit specifies which numbers to metamorphose supported the initial digits and the length of the number.

For case, you butt make over a directory lookup rule that mechanically removes the expanse code and two-digit prefix digits from 10-finger's breadth phone numbers pool. An exercise of this eccentric of principle is to transform 4089023139 into 23139.

Dial Via Office Annul

The Dial via Office (DvO) feature allows users to initiate Webex App outgoing calls with their act numerate using the mobile voice electronic network for the gimmick.

Webex App supports DvO-R (DvO-Reverse) calls, which work as follows:

1. User initiates a DvO-R call out.

2. The client notifies Cisco Unified Communications Manager to call the mobile number.

3. Coregonus artedi Unified Communications Managing director calls and connects to the mobile telephone number.

4. Lake herring Unified Communications Manager calls and connects to the number that the user dialed.

5. Cisco Unified Communications Manager connects the two segments.

6. The user and the called party continue as with an mine run bid.

Note

The users do not receive next calls on Webex App in the shadowing situations: If users select the Moveable Voice Network calling option on any electronic network and the Single Number Hand down (SNR) is not configured for their gimmick, they wish non find incoming calls on Webex App. If users select the Mobile Voice Network calling option happening any web and the Single Number Reach into (SNR) is configured with the Ring out Schedule, they will not receive incoming calls on Webex App beyond the time kick in the Ring Schedule.

The shadowing table describes the calling methods used for incoming and outgoing calls. The calling method (VoIP, DvO-R, or cellular call) varies depending on the selected Calling Options and the network connection.

Set back 3. Calling Methods used with Calling Options all over Different Network Connections

Connection	Calling Options
	Voice finished IP		Mobile Voice Network		Autoselect
Wi-Fi	Outgoing: VoIP	Succeeding: VoIP	Outgoing: DvO-R	Incoming: VoIP	Outgoing: VoIP	Incoming: VoIP
Mobile Network (3G, 4G, 5G)					Outgoing: DvO-R	Incoming: VoIP

To set up DvO-R, follow the steps in Configuring Dial via Part-Turnaround to Crop with Mobile and Remote Accession.

Extend and Connect

The Extend and Connect feature allows administrators to deploy Integrated Communications Manager (UC) Reckoner Telephony Integration (CTI) applications that interoperate with any end point. With Carry and Unite, users privy access UC applications from any location using any twist.

Preeminence

Users can but add and edit numbers for existing devices. You must configure leastwise one device for users. If zero device exists, so even if this sport is enabled, users won't see it as an option in Webex App.

See Configure Stretch out and Connect for Sir Thomas More information.

Move call to mobile

Users can transfer an active VoIP call from the Webex App to their mobile phone identification number on the mobile network. This feature is useful when a substance abuser on a call leaves the Wi-Fi net (for example, leaving the edifice to walk bent the railroad car), operating room if on that point are vocalisation quality issues over the Wi-Fi network.

Before you begin

Set up a wandering identity for users.

Procedure

---

Step 1	From Coregonus artedi Unified Cm Administration, go to , and then hunting for the substance abuser's Webex App for moveable (TCT or BOT) device.
Whole tone 2	For Mobility Substance abuser Idaho, opt the user's ID (typically the same Eastern Samoa the Owner User ID.
Step 3	Choose the Associated mobile identity that you configured.
Stair 4	For Transpose to Mobile Network, choose Use Mobility Softkey (user receives call) When this scene is designed, Unified Cm calls the telephone number of the PSTN mobile service provider for the mobile device.
Pace 5	Save your changes, and so attend and locate any substance abuser accounts you want to MBD this lineament to.
Step 6	Hinderance the following settings: Enable Mobility Enable Mobile Voice Access
Step 7	Salvage your changes.

---

What to coiffure next

Users lav change the Terminus in the Self Care Portal:

1. In the Webex App settings, go to .

2. On the Self Care Portal page, select your mobile twist.

3. Click Edit Single List Hand over, change the entry for Phone Number or URI, and then click Save.

Multiline

You can configure multiple earpiece lines for your users to execute daily Webex App tasks. You can add up to 8 phone lines for each user. You can configure multiline for your users on the Coregonus artedi Services Framework (CSF) gimmick for desktop clients.

Multiline is based on Cisco Unified Communications Manager release 11.5 SU3 and later. However, if you are exploitation Cisco United Communications Coach release 11.5 SU3 or Cisco Unified Communications Manager release 12.0, you moldiness manually install the Cisco Options Package (COP) file on wholly clustering nodes and restart Cisco Unified Communication theory Manager to enable multiline.

To configure multiline, use the steps in Add a directory issue to the gimmick to add multiple lines to a device and then associate the device to users.

Note	Multiline is supported when using Webex App for background in Mobile and Remote Access (MRA) mode. This function stool be enabled on the Expressway-C in the traversal pair (Unified Communicating > Configuration > SIP Path headers and set it to Connected).

You can also configure the RemoteInUsePresencePrimaryLineOnly parametric quantity if you want to modify the bearing for shared pedigree scenarios. Hear Policy parameters for more information.

Note	This parameter is not a selectable predetermined in Unified CM. You must add it as a customer parameter under policies.

After you receive installed and configured Multiline, your users can:

• Select a preferred line for making calls.

• View lost calls and voicemails.

• Utilize call forwarding, transfers, and league calls on altogether lines.

• Assign custom ringtones to each line.

Multiline supports the following features on all lines:

• CTI control for the desk phone

• Hunt groups

• Common bloodline, dial rules, and directory lookup

• Accessory manager

If Multiline is enabled, these features are only procurable on the primary phone line:

• Call pickup

• Extend & Connect

Push Notifications

When your bundle is enabled for Drive Notifications, Coregonus artedi Unified Communications Manager use either the Apple or Google cloud's Button Notification service to base push notifications to compatible Webex clients that run on iOS (Apple Push Notifications operating theatre APNs) or Mechanical man (Firebase Cloud Messaging or FCM) devices. Button Notifications let your system communicate with the client, even subsequently it has entered into downpla mode (also known as suspended mode). Without Push Notifications, the system may not be capable to send calls to clients that have got entered into background mode.

For more information about how to configure Malus pumila and Humanoid push notifications (APNs), visualise Push Notifications (Happening-Premises Deployments) in the Drive Notifications Deployment Guide.

RedSky location reportage for emergency career

To abide by with Ray Baum's bi, in the US, you can take users to give accurate location information when they are outside the business office.​

If the Webex App determines users moved to a new location, they are prompted to update their address. When users make an emergency call from Webex App, right position information is automatically sent finished RedSky service to the open-safety answering point (PSAP), which is the local emergency call center that responds to emergency calls. This fashio, first responders have the necessary information needed to pinpoint the "dispatchable location" and quickly reach an emergency caller regardless of the device they dial from, Oregon their exact fix inside a large building.

Government note

This feature is limited to Windows, Mac, Linux, VDI, iPad, Humanoid Pad of paper and Chromebook. For mobile untoughened phone device with cellular, Webex App cross-launches the inbuilt phone app to make the emergency call off. Users connected MacOS Monterey need to grant web permit to Webex App, so that Webex can news report the BSSID to Redsky. If BSSID cannot be reported mechanically, each user moldiness manually minimal brain dysfunction their locations in the Webex App.

If you're environment uses Co-ordinated CM 12.5 Oregon earlier, you must upgrade to the underslung server variant:

Customer type	Required components and supported versions
Unified CM on-premises	Incorporated CM 12.5SU6 Cisco Pinch Responder 12.5SU6 Cisco Expressway X14.1
Unified CM Cloud	Unified Curium 12.5SU5a Cisco Emergency Responder 12.5SU5a Cisco Expressway X14.0.4

RedSky-related conformation goes through with the Unified CM service visibility powered by the UDS interface.

• <EnableEmergencyCalling>(Yes/None)

• <OrganizationId>

• <Secret>

• <LocationUrl>

• <EmergencyNumbers>

If you're using Unified Atomic number 96 14 or subsequently, your users must install the Redsky MyE911 app and report location from on that point. If you're using CER to report the on-premises wireless location, you posterior keep CER and consumption the RedSky solution to only track off-premises location.

Note	Webex App for Linux doesn't fend for CER. You moldiness deploy RedSky to report both on-premises and off-premises location for emergency calling.

For mobile soft phone devices (TCT/BOT), you must provision the emergency number (such A 911) in your Unified CM server, so that Webex App launches the built in telephone app to take a leak the emergency call. See "Create and Configure Webex Softphone Devices" in the deployment chapter.

Further documentation

Configuring Emergency Responder with a National E911 Service Supplier

Lake herring Emergency Responder integrates with National E911 Service of process Provider like RedSky for automatic Location update, MSAG (Schoolmaster Street Address Guide) for a User input localisation and Call Completion. Emergency brake Responder automatically finds and tracks the dispatchable locations of all your devices as they move throughout the enterprise so you can comply with E911 regulations.

https://www.cisco.com/c/dam/td-xml/en_us/voice-ip-comm/ucm_cloud/WebexCallingDI_Islands/National_E911_for_DedicatedInstance.pdf

Configuring Unified Communications Managing director for Peregrine E911 Support

Nomadic E911 enables administrators to address the requirements of RAY BAUM'S Act away letting users update their location natively in Webex App.

https://www.Coregonus artedi.com/c/dam/td-xml/en_us/voice-ip-comm/ucm_cloud/WebexCallingDI_Islands/National_E911_WebexApp_AdminGuide.pdf

Survivable Remote Site Telephony (SRST)

Cisco Unified Survivable Unlikely Site Telephony (SRST) provides Unified CM with fallback support for Webex App users. Lake herring Unified SRST enables routers to leave call-handling support for Webex App users when they lose connection to remote primary, low-level, or third Cisco Merged Cm installations Beaver State when the Pallid connection is down.

For more information about this feature, pick up "Configure SRST" in the Arrangement Configuration Guide for your Unified Cm release and picture the Cisco Unified SCCP and SIP SRST Organization Executive Guide (All Versions) for IOS constellation, feature support, and restrictions.

Voicemail

For voice mail to bring off in Webex App, you must ensure that Cisco Unity Connection and Unified CM habituate a matching assay-mark method acting (for example, legacy SSO, oAuth SSO, or non-SSO). When organic with Incorporated Centimeter, Cisco Unity Connection (the voicemail and electronic messaging system) provides voice-messaging features for users that you configure manually, through AXL services, or through LDAP integrating. After receiving voice messages in their mailboxes, users receive substance-waiting lights on their phones and integrated applications—in this case, Webex App.

Note	For server performance considerations, don't use Visual Voicemail with both Jabber and Webex App at the same prison term.

Users become a modality voicemail inbox in Webex App. They can play messages, delete messages, mark as read, and respond with an audio or telecasting call:

Users can also fall into place Call Voicemail , which accesses the voicemail system with an national or external call option. Users can past retrieve, listen to, reply to, forward, and delete their messages. For more information almost this feature for your users, figure the Webex App Voice mail software documentation.

Promissory note

Voicemail always uses Unified CM remainder user credentials. These credentials and the voicemail credentials happening Unity Joining must be consistent—either place leading both with single sign-on (SSO) Beaver State with not-SSO certificate, so that the sign in experience is the same. See Recommended conformation for many entropy.

For information active setting up Coregonus artedi Unity Connection and integrated it with your Interconnected CM environment, construe the following certification:

• Cisco Unified Communications Coach SIP Integration Channelis for Lake herring Unity Connective for your release at https://web.cisco.com/c/en/us/indorse/unified-communication theory/unity-connection/products-installation-and-constellation-guides-list.HTML

• "Managing the Phone System Integrations in Cisco Unity Link" in the System Administration Guide for Lake herring 1 Connection for your vent at https://www.Coregonus artedi.com/c/en/us/support/unified-communication theory/unity-connection/products-maintenance-guides-list.html.

Badger State-Fi to LTE Call Net Handoff

Badger State-Fi to LTE Call Handoff provides flexibility for Calling in Webex App (Unified CM) users to switch 'tween different networks (such as Wi-Fi and LTE) without disconnecting any proactive calls that the user may be patc switching network.

This have is mechanically enabled for desktop and perambulating users. Your calling environment must be on Merged CM 14 and tardive. Come across the Unified CM sackin notes for more information.

For far-famed issues and limitations for this feature, see the known issues in the deployment chapter.

Wireless Location Monitoring Overhaul

Webex App supports radio set access orient (AP) location monitoring. Wireless localisation monitoring service allows you to determine the strong-arm location from where your Webex App users connect to the corporate network. This information is stored in Lake herring Co-ordinated Communications Manager.

This characteristic is supported with on-premises and Mobile and Distant Access (MRA) Edge wireless connections.

Webex App monitors your users' locations, gathers Service Lay out ID (SSID) and Basic Service Countersink ID (BSSID) information, and sends this information to Unified Cm at to the lowest degree every 24 hours (desktop only), or whenever:

• Their current access point changes.

• They sign in to Webex App.

• They flip between networks for happening-premises and Expressway for MRA.

• Webex App resumes from sleep or is made active.

Notice

If Webex App for mobile gets suspended, information technology may not send the location all 24 hours.

• For on-premises deployments, configure wireless location monitoring using EnableE911OnPremLocationPolicy parameter with the value true.

• For Expressway for MRA deployments—you bum configure wireless placement monitoring using the EnableE911EdgeLocationPolicy with the value unfeigned and E911EdgeLocationWhiteList with a list of up to 30 SSIDs, separated by a semicolon.

For more details on these parameters, visualize the Appendix in this usher.

For more info about how to configure Cisco Emergency brake Responder (CER), see the Cisco Emergency brake Responder Administration Guide for your bring out at https://WWW.cisco.com/c/en/us/support/unified-communications/emergency-answerer/products-maintenance-guides-list.html.

Contact Center feature requirements

Webex App can integrate into your Cisco Contact Center solution (Unified Contact Middle-of-the-road Enterprise operating theatre Express) and be regimented in Finesse desktop as a softphone node. This integration supports contact center features such as multiline, recording, conferencing, and more.

To see the latest supported features in the Webex App, see Contact Center integration for Webex App.

For information about how to configure your Lake herring Physical contact Center solution, see the Feature article Guide documentation for your specific ware and release:

• Cisco Unified Contact Center Enterprise (UCCE)

• Cisco Unified Physical contact Center Convey (UCCX)

Electronic network requirements

When using Calling in Webex App (Unified Atomic number 96) o'er your corporate WI-Fi network, we recommend that you do the chase:

• Design your Wi-Fi network to rid of gaps in coverage as practically as possible, including in areas such as elevators, stairways, and out of doors corridors.

• Ensure that all access points impute the same IP address to the mobile device. Calls are dropped if the IP name and address changes during the call.

• Ensure that all access points have got the Lapplander service set identifier (SSID). Hand-remove whitethorn beryllium overmuch slower if the SSIDs do not match.

• Ensure that all admittance points broadcast their SSID. If the access points do not propagate their SSID, the mobile device may prompt the user to join another Wi-Fi mesh, which interrupts the call.

• Ensure that the Enterprise firewall is configured to allow the passage of Sitting Traversal Utilities for NAT (STUN) packets.

Transmit a thorough site survey to belittle network problems that could affect voice quality. We advocate that you do the following:

• Verify nonoverlapping channel configurations, access point coverage, and required data and traffic rates.

• Eliminate rogue access points.

• Identify and palliate the affect of potential interference sources.

For more information, see the following documentation:

• The "VoWLAN Intention Recommendations" plane section in the Enterprise Mobility Intention Guide.

• The Cisco Unified Wireless Information science Phone 7925G Deployment Guide.

• The Capacity Reportage & Deployment Considerations for IEEE 802.11g white paper.

• The Solutions Reference Network Conception (SRND) for your Cisco Unified Communications Manager release.

Ports and protocols

Calling in Webex App (United CM) uses the ports and protocols listed in the following table. If you plan to deploy a firewall between the client and a server, configure the firewall to grant these ports and protocols.

Port	Application layer protocol	Transport layer protocol	Verbal description
Configuration
6970	HTTP	TCP	Colligate to the TFTP server to download client configuration files.
6972	HTTPS	Transmission control protocol	Connects to the TFTP server to download client configuration files securely for Cisco Unified Communications Manager.
8443	HTTPS	TCP	Traffic to Cisco Unified Communications Manager.
Communication Manager signaling
2748	CTI	TCP	Electronic computer Telephony Interface (CTI) used for desk telephone control.
5060	SIP	TCP	Provides Academic session Initiation Communications protocol (SIP) bid signaling.
5061	SIP over TLS	TCP	SIP over TLS provides secure SIP song sign. (Secondhand if Secure SIP is enabled for device.)
5070 to 6070	BFCP	UDP	Double star Floor Contain Protocol (BFCP) for video sort sharing capabilities.
Voice or video media interchange
16384 to 32766	RTP/SRTP	UDP	Cisco Coordinated Communications Managing director media port range used for audio, video, and BFCP video desktop share.
33434 to 33598	RTP/SRTP	UDP	Lake herring Webex Hybrid Services media left range used for audio and video.
8000	RTP/SRTP	TCP	Allows users to receive video heritable to their desk phone devices on their computers through the client.

Financed codecs

Typewrite	Codec	Codec type	Webex App for Mechanical man	Webex App for iPhone and iPad	Webex App for Mackintosh	Webex App for Windows
Sound	G.711	A-law	Yes		Yes	Yes
		µ-law/Mu-law	Yes		Yes	Yes
	G.722		Yes		Yes	Yes
	G.722.1	24 KB/s and 32 kb/s	Yes		Yes	Yes
	G.729		No		No	No
	G.729a		Yes		Yes	Yes
	Opus		Yes		Yes	Yes
Video	H.264/AVC	Baseline visibility	Yes		Yes	Yes
		High visibility	Zero		Yes	Yes

Certificate requirements

Unified Atomic number 96 certificates (no MRA in deployment)

To establish a secure connection with Unified CM, Webex App validates the certificate that is presented past the server during the connection cognitive process. Unlike Jabber, Webex App does not prompting users with the option to take on an untrusted certificate.

United CM must Be configured with certificates that Webex App can formalise, preferably a CA root that signed the tomcat certificate (which is acknowledged to the OS that Webex App is on, Windows OR MacOS aside default). or a self-signed trustworthy security (which must be deployed to the Bone in advance away the enterprise administrator).

Table 4. Phone services error when certificate is untrusted (Webex App for Windows and Mac)

Note	The Tomcat certificate is also used for secure SIP when Webex App is enabled for encrypted calls (SIP Oauth operates happening the default option port 5090). Catch "Configure the Earpiece Security Profile for Encrypted Calls" in this usher for Sir Thomas More inside information.

Certificates issued with a deprecated signature algorithm (such as SHA-1) do not form; you mustiness use a supported secure signature algorithmic rule such as SHA-256 or later, as certified in the Certificates chapter in the Administration Guide for Cisco Integrated Communications Manager.

Note	The certificates that are deployed on Unified CM servers must include the fully qualified arena cite (FQDN) as the host identity preferably than a simple hostname operating theatre IP address (for example, cucm-host-1.example.com rather than cucm-server-1 or 203.0.113.1).

In Cisco Unified CM Presidency > System > Server, the Unified Curium server names must be defined as FQDN.

See Ill-smelling Level View of Certificates and Authorities in CUCM and CUCM Credentials Direction and Vary Notification for entropy about certificate management in Unified CM.

Unified CM certificates (with MRA in deployment)

The Unified CM Tom certificate is significant for Mobile and Remote Access (MRA). This certificate is automatically installed on the Cisco Unified Communications Manager. Past default, information technology is self-signed and has the same common list (CN).

Note	The Tomcat certificate is also used for secure SIP when Webex App is enabled for encrypted calls (SIP Outh operates on the default port 5091 for MRA). See "Configure the Phone Protection Visibility for Encrypted Calls" in this guide for Thomas More details.

We recommend using CA-signed certificates. However, if you act up use self-signed certificates, the two certificates must receive different informal name calling. The Expressway does not allow two soul-signed certificates with the same CN. So if the CallManager and tomcat person-autographed certificates take the duplicate CN in the Expressway's trustworthy CA list, the Expressway can just confidence one of them. This agency that either secure Hypertext transfer protocol or inviolable SIP, 'tween Motorway-C and Cisco Unified Communications Manager, will fail.

Expressway certificates (with MRA in deployment)

Note	For MRA scenarios, certificates solely need to personify validated on the Thruway.

The Pike security signing request (CSR) joyride prompts for and incorporates the relevant Subject Alternative Name (SAN) entries as appropriate for the Unified Communications features that are supported along that Freeway.

The following table shows which CSR alternative name elements use to which Unified Communication theory features.

Table 5. CSR alternative name element and Motile Removed Get at (MRA)

Add these items as Subject Alternative Names (SANs)	When generating a CSR for MRA
Unified Cm registrations domains (despite their name, these have more in uncouth with Robert William Service breakthrough domains than with Unified CM Unified CM SIP registration domains)	Compulsory on Expressway-E only
(Clustered systems only) Thruway cluster diagnose	Required on Expressway-C only

Note	You must restart the Expressway for any new uploaded server credentials to fill effect.

Expressway-E server certificate requirements

The Expressway-E server certificate needs to include the following factor in its list of subject alternative name calling (SAN):

• Unified CM registrations domains: all of the domains which are designed on the Expressway-C for Unified CM registrations. Required for secure communications between endpoint devices and Pike-E.

  The Unified CM registration domains utilised in the Expressway contour and Thruway-E certificate, are used by Mobile River and Remote Access clients to lookup the _collab-edge DNS SRV record during service discovery. They enable MRA registrations along Coordinated CM, and are primarily for service discovery.

  These inspection and repair discovery domains may OR whitethorn non rival the SIP registration domains. It depends on the deployment, and they wear't have to match. One deterrent example is a deployment that uses a .local or similar private domain with Unified CM along the internal network, and state-supported arena names for the Motorway-E FQDN and inspection and repair discovery. Therein case, you need to include the public demesne names in the Thruway-E certificate as SANs. There is zero need to include the reclusive domain name calling used on Unified CM. You only need to list the border domain as a SAN.

  Select the DNS initialize and manually specify the required FQDNs. Separate the FQDNs aside commas if you deman ninefold domains. You may select CollabEdgeDNS format instead, which simply adds the prefix collab-edge to the domain that you enter. This format is recommended if you do non want to include your top level sphere as a SAN (see example in favorable screenshot).

  

Requirements when migrating from Rant to Webex App

In migration scenarios, you may encounter an issue if you're using a private CA with the Certificate Revocation Leaning (CRL) default format (ldap :///) for the Expressway-E certificate.

In that deployment, afterwards migrating from Jabber to the Webex App, Webex App on iOS devices does non cash register to Incorporate CM phone services. The enrollment fails because the iOS node tries to progress to the CRL URL from the Internet, but the CRL format ldap:/// is non supported away iOS clients.

Tippytoe

If you're using a private CA for issuing certificates for Expressway-E, we commend that the Expressway-E is issued by a public CA, and then you can migrate users from Jabber to the Webex App.

If you must use certificates signed by a sequestered CA for your Expressway-E setup (particularly, a CRL with the arrange ldap:///), follow these steps to control a successful migration from Jabber to the Webex App:

• Remove the CRL parametric quantity, if any, from the private Calcium templet.

• Reissue Expressway-E server certificates without the CRL parameter.

• Work sure certificates that the private CA signs support the following requirements for iOS:

  • Minimum describe sized of 2048

  • SHA-2 signature

  • Server DNS name as SAN

  • Lengthy key usage prolongation containing the id-kp-serverAuth OID

  • Validity period of 398 or fewer days

• Install the root CA file on mobile devices

Headset requirements

Unified Cm calling in Webex App supports the following Coregonus artedi serial headsets. Cluck the links for more information connected each model:

• 520 Serial publication

• 530 Series

• 560 Series

• 730 Series (Bluetooth)

Some Jabra headsets are supported. Understand Details around headset reenforcement for more information.

Tone	When using a substantiated headset in Webex App, the headset firmware toilet get updated mechanically. Users get a message that pops up letting them know that an update is available, and and so they'll get confirmation after information technology's updated.

License requirements

You involve a Cisco Webex organization (managed in Control Hub) with a paid subscription. User accounts must be managed in your constitution but they don't require a specific license grant to use Vocation in Webex App (Unified CM).

Additionally, for softphone functionality, each Webex App registers to Unified CM as a softphone client. Equivalent Cisco Jabber, this enrolment uses the Lake herring Unified Client Services Framework (CSF) client for screen background and a BOT, TCT, operating theatre Tabloid gimmick for wandering, and counts A a device toward Unified Centimeter licensing. Users with three or more apps and/surgery devices require CUWL perpetual licensing or for the organization to get on a Flex Calling subscription.

Tip	We recommend Flex Calling as the subscription channel for Calling in Webex App (Interconnected CM).

Webex App requirements

To ensure that Calling in Webex App (Integrated Centimetre) functions correctly and the latest features, functionality, and other fixes are continuously delivered, users mustiness constitute on the latest spillage of the Webex App for desktop or mobile, or the latest VDI thin client.

Note	The Web app (network.webex.com) does not allow users to call phone numbers.

• For installation and upgrade instructions, examine Installation and automatic pistol upgrade.

• For managing the frequency of Webex App updates for users in your organization, see Production update controls for Webex App.

• Chromebooks on both ARM and x86 architecture are supported for Calling in Webex App (Unified CM). Users can also live signed into phone service on both a Chromebook and Android phone at the same time.

• For VDI deployment steps, see the Deployment guide for Practical Desktop Infrastructure (VDI).

• For release information, see the Release notes and What's new documentation for the Webex App and the VDI going notes for Webex App for VDI.

Advisable configuration

Idiosyncratic signal-happening (SSO) and IdP integration

• For Calling in Webex App (Unified CM), SSO is supported with Unified Centimetre and Expressway. You mustiness either enable or disable SSO on some. For a consistent user experience with SSO, we recommend that you extend your Identicalness Provider (IdP) integration to Webex App so that users can check in with the same certificate. With Single Sign-On (SSO) integration between your IdP, your premises environment, and the Webex cloud, users can sign in across applications with one set of credentials.

  

• For premises Unified CM configuration, catch the SAML SSO Deployment Scout for Coregonus artedi Incorporate Communication theory Applications for your turn. We recommend applying this configuration to Unified CM and any Ace Connection voicemail servers in your deployment.

• For Expressway configuration, see the Mobile and Unaccessible Access via Cisco Throughway Deployment Guide for your turn.

• For cloud up (Webex App) configuration, see Individualist Sign on-Happening Integration with Webex Verify Hub

See the tailing table for supported authentication types:

Table 6. Supported certification types

Type	Windows	Mac	iOS	Android
IWA Auth with NTLM	✓	✓	✓ See the SSO Redirect URI requirements	✓
IWA Auth with Kerberos	✓
Form-based Auth	✓	✓	✓	✓
Cert-based Auth	✓	✓	✓ See the SSO Redirect URI requirements	✓

SSO redirect URI

The Webex App supports SSO redirect URI, an enhancement to the app's integrated browser support.

This feature provides the following enhancements:

• Provides protection against "Potency Code Interception Attack" using RFC7636.

• Allows Webex App running on an Operative Systems other than iOS to use the Embedded Web browser (For example: Humanoid).

• Allows Webex App to usance the Embedded browser for Unified Communications Managing director (and MRA) OAuth flow. This support prevents multiple login when SSO is enabled.

Requirements

This feature requires the following token versions:

• Coordinated Centimeter 12.5(x) releases—12.5(1) SU4 and later (Interconnected CM 14 is not supported)

• Expressway X14 and later

• Webex App 41.4 and later

For more data, see the following documentation:

• Expressway Release Notes

• Unified Atomic number 96 Release Notes

Contour

For Unified CM—No configuration is required.

For Expressway—Connected the Expressway-C, you must set the parameter Webex Client Embedded Browser Back to Yes to enable this feature. For more information, see Configure MRA Access Control in the Mobile and Far Access Through Cisco Expressway Deployment Guide (X14.0) .

Directory synchronization and contact card game

We recommend victimisation the Lake herring Directory Connector for user synchronization from your Active Directory into Control Hub.

You can also synchronize user sound numbers. Their Numbers come along in contact cards in the Webex App for Windows and Mac:

Note	For iOS and Android, users can accession soul's contact posting from a infinite by antitrust tapping a profile picture. See Verify Who You're Contacting for more information.

For the numbers to appear, you must deploy Cisco Directory Connector to synchronize the numbers from an existing Active Directory attribute into the cloud. See the attribute mapping information in the Deployment Head for Cisco Directory Connective at https://WWW.cisco.com/go/hybrid-services-directory.

Overview of Auto-Provisioning of Webex App

The auto-provisioning feature in Control Hub allows the users to self-supplying the devices for Calling in Webex (Unified Centimeter) with zero operating theater stripped intervention. This feature avoids over-provisioning of multiple devices in Unified CM that helps to minimize the impact on cluster scaling and licensing utilisation. Devices are auto created in Unified CM, when a user provisioned for Calling in Webex (Integrated Curium) signs in with their registered electronic mail address OR User ID to Webex App.

Administrators don't need to go to Unified CM to pre-provision any of the Webex App devices for users in their organization. When the drug user signs in to the Webex App with whatsoever device for the first time, and if the device isn't already ready in the Unified CM waiter, the new device type is auto created for the user.

This feature allows auto-provisioning of following devices types in Unified CM for the users when they sign into Webex App from several device platforms:

• Android Device (BOT)

• Chromebook/iPad Devices (TAB)

• Windows/MAC Devices (CSF)

• iPhone Device (TCT)

Note	After the deletion of a device, it is recommended that you waitress for 5-10 minutes before you motorcar-provision a device of the same type. Also, you can reset the device from Webex App before you auto-provision it again (Go to Assist > Health Checker and fall into place the Reset button.)

Note	Auto cleanup and omission of auto-provisioned devices is not supported currently.

Prerequisite

Before you plan to allow automobile-purvey of Webex App for the users, make sure that you satisfy the following requirements:

• Trigger Cloud-Connected UC and set rising the on-premises devices in your governing body to communicate with the Control Hub. For more information, see Set Up Overcast-Abutting UC for On-Premises Devices.

• For the user account in Control Hub, sum either a Basic or Professional Webex Calling license.

• Cisco United Communication theory Manager clusters should follow version 11.5 or above. Attend the based Incorporated Atomic number 96 version for Calling in Webex (Unified CM) at Deployment Guide on for Calling in Webex (Unified Centimetre).

• The minimum gimbaled Webex App version is 41.12 and higher.

• The tokenish based Cisco Expressway Bring out version is X14.0.2. If the State highway interlingual rendition is below the recommended version, Thruway should add the following URLs manually to the Admit List to allow external clients (Lake herring Jabber or Webex App) to access the Co-ordinated Communication theory nodes discovered having MRA configuration:

  • POST: https://{{cucmip}}:8443/devicemanagement/v1/clientAutoProv/createDevice

  • Find: https://{{cucmip}}:8443/ucmservices/v1/supportedServices

• Ensure that the Drug user ID or electronic mail ID of Unified CM users matches with the User I.D. of the user records entity in Webex Identity Service. Besides, the users configured in the Unified CM server should be available in the organizations' Webex Identity Service.

Additional configuration

We recommend the following additive configuration to furnish further benefits for your Career in Webex App (United CM) deployment:

• Quality of Service (QoS), covered in the Vermiform appendix in this guide. QoS helps manage packet deprivation, delay and jitter on your network infrastructure.

• Margin call Admission Control (CAC) on Unified Curium, covered in the Organisation Configuration Guide for Cisco Unified Communications Managing director. CAC enables you to control the audio quality and video quality of calls over a wide-area (IP Weak) connexion by restrictive the number of calls that are allowed on that tie-in at the same time.

free calling app for chromebook

Source: https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cloudCollaboration/wbxt/ucmcalling/unified-cm-wbx-teams-deployment-guide/unified-cm-wbx-teams-deployment-guide_chapter_011.html

Berbagi :