Shared lines and virtual lines across locations provide several benefits for Webex Calling, including:
-
Improved call handling: Shared lines and virtual lines cross locations can ensure that incoming calls are answered promptly
even during busy hours. This reduces call wait time and improves call answer rates.
-
Increased scalability: Shared lines and virtual lines across locations can allow businesses to easily add or remove lines
as needed to accommodate changes in call volume or staffing levels.
-
Greater cost effectiveness: Shared lines and virtual lines across locations can help businesses reduce the cost of long-distance
calls.
Supported devices
The following table shows the devices that can be configured with shared lines and virtual lines across locations.
|
Devices
|
Shared Line
|
Virtual Line
|
|
MPP devices assigned to users
|
✓
|
✓
|
|
Webex App
|
✓
|
✓
|
|
Wireless phones 840/860
|
✓
|
✓
|
|
Guest Profiles for Hot desking
|
✓
|
✓
|
|
DECT handsets
|
✓
|
✓
|
|
MPP devices assigned to workspace
|
✓
|
NA
|
|
ATA devices
|
✓
|
NA
|
|
Impact on call routing
When the end user selects a line for an outbound call or when the end user receives a call on a line, the calling dial plan,
calling services and policies of that specific line are invoked. For an outbound call, the routing profile of the line’s location
is used, hence the PSTN calls are routed based on that location’s assigned PSTN option.
Emergency calling considerations
Routing of emergency calls is determined by the location settings of the line that is selected to place an emergency call.
For RedSky enabled locations, emergency calls are routed directly to RedSky via the dedicated peering connection. For other
locations, emergency calls are routed via the PSTN provider in that location.
HELD/HELD+ is a device function that is independent of the lines configured on the device. In case of an emergency call, the
device provides location information, but the routing of the call to RedSky depends on the line location settings. It should
be noted that including location information for a call from a line that is defined in a location without RedSky enablement
doesn't trigger routing through RedSky.
Emergency Call Back Number (ECBN) selection for emergency calls is determined by the line that is selected to place an emergency
call. Specifically, the line ECBN settings will determine the phone number sent to emergency responders. This will be one
of three possible values:
For more information on emergency calling and ECBN, see: Enhanced Emergency Calling for Webex Calling and Emergency Callback Number in Control Hub.
Survivability considerations
In survivability mode, shared lines and virtual lines from a different Webex Calling location do not register to the Survivability Gateway (SGW). The device displays the line as unregistered. Users can't make
outbound calls or receive inbound calls on those lines. If that line is assigned to a device in a different Webex Calling location that is in active mode, then those users can make and receive calls using that line.
In survivability mode, shared lines and virtual lines from the same Webex Calling location will register to the SGW. Users can make calls from the device in survivability mode and from the device in active
mode. Calls made to the line will alert devices that are in active mode. Internal calls from devices in survivability mode
will alert devices in the same survivability location. LGW-PSTN calls received in the location that is in survivability mode
are handed off to the SGW and alert the devices in the same survivability location. Other devices in active mode that share
that line are not alerted.
When that Webex Calling location is back in active mode, all lines in that location successfully register to Webex Calling.
Limitations
-
A line from a Webex Calling location in India can’t be assigned to a device in a different Webex Calling location.
-
A device in Webex Calling location in India can’t be assigned a line from a different Webex Calling location.
