• No results found

BroadWorks Release 21. Jim McGonigle Director of Product Management, BroadWorks

N/A
N/A
Protected

Academic year: 2021

Share "BroadWorks Release 21. Jim McGonigle Director of Product Management, BroadWorks"

Copied!
22
0
0

Loading.... (view fulltext now)

Full text

(1)

BroadWorks Release 21

Jim McGonigle

(2)

Mobility

Persona Management Concept

Subscriber – userid@domain

Devices…

Persona / Identities

User Profile

Business Personal

(3)

Mobility

Persona Management Characteristics

• A User can have several identities

• Each identity may require different behavior or personality (persona)

• A User has a single profile with the set of BWKS features:

• The User’s profile includes multiple identities such as Mobile numbers, BWA

Locations, Alternate numbers.

• Some features need to behave differently based on the persona being

utilized.

• Each person can be configured with:

• Incoming call specific alerting rules

• Outgoing calling line ID delivery options

• Incoming call Selective Call Forwarding rules

(4)

Mobility

Persona Management Characteristics

• A User has a single telephony Presence

• based on the aggregation of the user’s Personas • If one Persona is busy, the user is busy

• A User has single set of credentials for configuration and

management of his/her personas

(5)

Mobility

Recommended Deployment

Subscriber – userid@domain

Devices…

Fixed – Primary Address

BC – SCA Address

Mobile – BroadWorks Mobility BYOD – BroadWorks Anywhere A single subscriber has many devices, from a

fixed IP Phone, to soft clients like BC Desktop or Mobile, Mobile phones in the offer or other

BYOD.

All devices are known to BroadWorks and presents telephony presence accordingly.

(6)

Mobility

Identity based call controls (CLID Control)

• Why?

• Users want to control the

number presented on

outgoing calls

• What?

• Outgoing call from Fixed

Device

• Outgoing call from Mobile

• CLI Options (Persistent) • Per call presentation Subscriber – userid@domain

Mobile 1: Present Profile ID

Dial FAC to present Mobile ID

Mobile 2: Present Mobile ID Dial FAC to present Profile ID

(7)

Mobility

Identity based call controls (Alerting Policies)

Why?

• Users want to control what devices ring based on the number they are being contacted at

What?

• Rules based on the User’s assigned numbers (identities)

• For each identity the options include: • Ring all devices

• Mobile identities to include/exclude • Ring fixed devices

• HG/CC Restrictions per device Subscriber – userid@domain

Primary ID

Mobile1 ID Ring All

(8)

Mobility

Multi-Sim Support

• Why?

• Users have multiple devices

• What?

• Multiple Mobile Numbers per user • For each mobile number the Options

Include

• Alerting enabled/disabled • Identity Alerting Policy

• Deny originations/terminations • Prevent/allow calls between

identities

• Option to exclude alerting for some services

Car SIM National

Mobile

Subscriber – userid@domain

International

(9)

Mobility

Selective Criteria Enhancements for Called Number

• Why?

• Users want to provide different call treatment based on the number they are being contacted at.

• What?

• Existing Selective service configuration to include a “Calls To” number in the criteria

• May be the user’s primary, Alternate(s), or BW Mobility Number(s).

• Supported services

• Call Forwarding Selective

• Selective Call Rejection/Acceptance • BroadWorks Anywhere

• Custom Ringback User

• Executive/Executive-Assistant • Priority Alert

• Call Notify

• Pre-alerting Announcement

(10)

Mobility

Selectable SCF Call Anchoring

• Why?

• MNO or User only wants business

calls on Broadworks.

• What?

• Allow a user to dial a FAC code to

enable/disable call anchoring and

allow the call to continue in the

mobile network as a personal call.

• Allow user to set call anchoring on or

off permanently.

• Allow user to disable call anchoring

based on TOD

• Configurable on each Mobile Identity

PSTN Mobile

Network PSTN

Mobile Network

(11)

Mobility

Multi-Country Enhancements

• Why?

• Allow multi-county/multi-MNO deployments

• What?

• SCF in each country/MNO

• Per-Country Number normalization • Per Mobile identity association with

specific SCF

• IMRN pool association with specific SCF MGC/F SIP SS 7 2G/3G CS core MSC 2G/3G Mobile SCF 1 HLR MGC/F SS 7 2G/3G CS core MSC 2G/3G Mobile SCF 2 HLR I P SI P I P I P HQ

(12)

Personal Assistant

Personal Assistant

“Jim McGonigle is in a meeting until today at 2PM. To be transferred to an attendant press 2. Otherwise press 3 or

stay on the line to leave a message.”

Colleague Calls my business # Jim (In a Meeting) Spouse Personal Assistant Calls my business # Jim (In a Meeting)

x

Call is blocked and caller gets choice to leave VM or transfer

to my attendant.

Personal assistant is bypassed for select

calling numbers Friend Personal Assistant Calls my personal # Jim (In a Meeting) Personal assistant is bypassed for select

called numbers

(13)

Personal Assistant

User Service

• User Service assignable to all real users

• Provides an “enhanced Do Not Disturb” functionality

• Personal Assistant provides a number of selections for

user configuration in addition to None (Off)

• Each selection allows

• An announcement that will be played to the caller including the personal name and the end time if configured

• Provides an optional ability to allow caller to transfer to attendant • A date/time for the selection to expire

• VIP List

• Each Personal Assistant has a VIP list that will allow callers on that list to bypass the Personal Assistant

• An entry may be a phone number, extension and can include the use of wildcards

(14)

Personal Assistant

User Experience

• BTBC used to control selection for personal assistant

(Xsi)

• Voice Portal used to select also

• Web Portal or other portals (OCI)

• Receptionist should show Personal Assistant Status

• Predefined Presence

• In a Meeting

• Out for Lunch

• On Vacation

• Out of the Office

• Temporarily Out

• Gone for the day

• On a Business trip

(15)

Business Trunking

Large PBX Support

• The feature simplifies the provisioning requirements on

BroadWorks for supporting Large PBXs.

• Allows BroadWorks to support PBX with one enterprise trunk user instance

• The feature provides a new user service (Route List)

that is functional when assigned to enterprise trunk

users.

• The service allows DN ranges to be assigned.

• All requests to/from the PBX that map to the enterprise

trunk user DN or any DN within the route list service will

use the enterprise trunk user instance to process

originating/terminating services.

(16)

Business Trunking

Enterprise Capacity Management

• Allows the Enterprise Admin to control the number of

calls that are routed through an enterprise trunk.

• The Enterprise Admin can now enable or disable

capacity management on the enterprise trunk.

• At system upgrade the capacity management is disabled.

• When enabled, a capacity can be assigned to the

enterprise trunk up to the maximum capacity for the

enterprise. Once this capacity is reached, no further

calls can be originated or terminated to the enterprise

trunk.

• An alarm is issued when a call is blocked due to ET capacity. • The CDR is updated when a call is blocked due to ET capacity

(17)

WRS

WebRTC

• Enhanced to support registrations from WebRTC client

• Allows WebRTC clients to receive calls

• Enables WebRTC to WebRTC calls

(18)

Network Function Manager (NFM)

Capabilities

• The NFM provides a generic platform that provides a

number of capabilities to enhance BroadWorks

management and orchestration

• NFM-based capabilities are seen to include

• Node License Management (Release 21)

• Automated Node Orchestration • Elasticity Manager

• Fault/Alarm Management and Performance Metrics • Centralized Configuration Management

• Centralized Patch Management • Centralized User Management • Centralized Troubleshooting

(19)

Network Function Manager (NFM)

Node License Management (NLM)

• A centralized NLM function which distributes and controls licenses to

nodes without tying them to a physical machine

• BroadWorks provided licenses are loaded on the NFM NLM function

• BroadWorks nodes are mapped to licenses

• Licenses are automatically pushed to BroadWorks nodes

Node License Manager inventory MS1 license signature license store license signature license signature license signature license signature MS1 ... ... AS1 ... ... Xsp1 ... ... NS1 .. ... AS1 Xsp1 NS1 license signature license signature license signature

(20)

Service Enhancements

Terminate Alerting when Rejected

• Allows alerting to be terminated when a user rejects a

call from a Primary or SCA endpoint

• Why?

• Users typically have multiple devices at the same location (desk phone, BC, mobile)

• Today, all the devices ring and individually need to be told to stop ringing

• What?

• Enhancement allows the user to reject a call on their phone and all the other endpoints will stop alerting

(21)

Service Enhancements

Miscellaneous

• Allow FAC Codes to be disabled on a per user/per group

• MP3 Support for Voice Messaging

• Recorded voice messages can be in the mp3 format

• Query Find-me/Follow-me numbers at system level

• Call Center marking data from external systems

• AoC – Manage tariff changes from the OCS

• MRF – Redundancy for Call Recording/N-Way

• COLP information support for PBX users on Business

Trunking

(22)

24 Month Major Release Cycle

Fewer major releases – Better quality – Better support

• Next Major Release will be in Q4-2016

• Aligns with current frequency of upgrades in the field

• Does not change N-2 maintenance and support model

• Release 21 will now have 6 years of support

Release

Original EOM

New EOM

19/19sp1

12/31/2015

12/31/2016

20/20sp1

12/31/2016

12/31/2018

References

Related documents

Log into Call Center Configuration Settings ……… Page 3 Change Your Password .... • To delete a report, click the Delete button in the row for

Enterprise Service Provisioning Portal page.. 1) The default monitoring style in Receptionist uses dynamic monitoring; however if you wish to constantly monitor the status of

The test plan exercises the SIP interface between the device and BroadWorks with the intent to ensure interoperability sufficient to support the BroadWorks feature set.. NOTE: DUT

The BroadWorks Device Management feature provides the capability to automate generation of device configuration files to support mass deployment of devices. This section

 The BroadWorks® SIP Trunking solution allows communication service providers to deliver cost effective, feature-rich SIP trunks to businesses while enhancing the PSTN voice

redundancy failover capabilities and the unsurpassed scalability of PaaS application technology, VoIP Logic’s deployment of the BroadWorks Hosted PBX application server

granted and person’s representative appointed G) Authorisation implemented by managing authority E) Best interests assessor recommends person to be appointed as

reimbursement policy... Moreover, there is affirmative evidence that the same manager had recently fired another, non-disabled employee for a similarly trivial violation of