BroadWorks Functional Summary - CommPartners Connect

More documents

Recommendations

Info

2.5 Caller ID Restriction Override Feature ID(s): 10560 Calling Line ID Blocking Override (CLIO) allows a user to override the calling line identity presentation restrictions and therefore always receive the calling line identity at their customer premises equipment (CPE), if available. In other words, the user who activates this option always receives the calling line identity if available, regardless of whether or not the calling line identity is blocked. The user never receives a calling line identity indicating “private”. This service is configured via the CommPilot web portal. 2.5.1 Description CLIO is offered as an override to Calling Line ID Delivery Blocking. When activated by the user, this service ignores the presentation indicator and delivers the calling line ID to the user if it is available (both name and number). The user activates and deactivates the service through the CommPilot Personal web interface. It should be noted that the caller information provided to the CLIO user is bound to what <strong>BroadWorks</strong> receives from the calling party and from other peripheral systems. For example, if the caller’s name is blocked in the CNAM database and cannot be obtained by <strong>BroadWorks</strong>, the CLIO user only receives the calling number. Similarly, if the Caller ID Enhancement service is activated and the incoming call is overseas, from a payphone or from an operator, the CLIO user only receives the corresponding indication instead of the caller ID. When this service is active, all Caller ID-based services behave as if the Caller ID was present, regardless of the presentation indicator, unless the call is Anonymous, as follows: � Anonymous Caller Rejection lets private calls through � Screening services apply regardless of the presentation indicator � The Call Manager’s incoming call log shows all incoming Caller IDs This service is only overridden by the CLID Delivery (both External and Internal) service. If the Caller ID Delivery service is not active for a user, then CLIO has no impact. BROADWORKS FUNCTIONAL SUMMARY 2O-BD5013-00 PAGE 12 OF 93
2.6 Directed Call Pickup with Barge-in Feature ID(s): 10562, 13394 Directed Call Pickup with Barge-in (DPUBI) allows users to dial a feature access code (FAC) followed by an extension to pick up (answer) a call directed to another user in the same customer group, or barge-in on the call if the call was already answered. When a barge-in occurs, a three-way call is established between the parties with the DPUBI user as the controller. Note that the pickup portion of this feature is identical to the existing Directed Call Pickup (DPU) feature. DPUBI is a completely separate service from DPU, however, the barge-in capability is added, and it has its own unique FAC. Throughout this section, the following terms are used: � DPUBI user – the user invoking the DPUBI service � Picked-up user – the user whose extension has been selected by the DPUBI user � Other party – the party that is connected with the picked-up user before the DPUBI attempt takes place 2.6.1 Description 2.6.1.1 Provisioning The DPUBI service is a user service. Therefore, it can be authorized to service providers and groups, and can be assigned to users. The only configurable option for the DPUBI user service is the barge-in warning tone. This option controls whether a warning tone is given to the picked up user when a barge-in occurs. The warning tone option is only configurable by administrators. Users can view the current warning tone setting, but cannot change it. At the group level, the DPUBI FAC can be configured by administrators. It defaults to *33, but can be changed to any valid, available FAC. 2.6.1.2 Service Invocation A user invokes the DPUBI service by dialing the DPUBI FAC. If the user does not supply an extension when dialing the DPUBI FAC, then they are given a stutter dial tone so that they can enter the extension to be picked up. If an invalid extension is entered (for example, an extension that does not exist in the group, too few digits, and so on), then the DPUBI user is given reorder tone. If a valid extension is entered, then a pickup or barge-in is attempted as described in the following sections. Note that if the picked-up user has no calls or more than one call, then the DPUBI user is given a reorder tone. A pickup or barge-in can occur only when the picked-up user has exactly one call. BROADWORKS FUNCTIONAL SUMMARY 2O-BD5013-00 PAGE 13 OF 93
Page 1 and 2: BROADWORKS FUNCTIONAL SUMMARY RELEA
Page 3 and 4: Table of Contents 1 Introduction...
Page 5 and 6: 6.7.1 Description .................
Page 7 and 8: 2 User Services 2.1 Auto Attendant
Page 9 and 10: • Figure 2 Calendar Pop-up 2.3.1.
Page 11: • Figure 5 Auto Attendant Add Pag
Page 15 and 16: 2.7 Auto Callback Feature ID(s): 10
Page 17 and 18: 2.9 User Category Service Feature I
Page 19 and 20: 2.12 Configurable Calling Line ID f
Page 21 and 22: 3 Group Services 3.1 Department Mus
Page 23 and 24: • Figure 8 Enterprise Setup Step
Page 25 and 26: 3.2.1.3 Enterprise Private Dialing
Page 27 and 28: � No access to groups. The Enterp
Page 29 and 30: 3.3 Originating Fully Restricted Fe
Page 31 and 32: 3.4 Terminating Fully Restricted Fe
Page 33 and 34: 4 Messaging Services 4.1 Callback R
Page 35 and 36: 4.3.1.2 CommPilot Express Support f
Page 37 and 38: 4.4.1.2 Call Origination BroadWorks
Page 39 and 40: 4.4.1.4 Detection of Escape Sequenc
Page 41 and 42: 5.2 Conferencing OAM Integration Fe
Page 43 and 44: In the current release conferences
Page 45 and 46: 5.2.7 Ad-Hoc Conferencing From the
Page 47 and 48: 5.2.11 Accounting Integration The d
Page 49 and 50: 5.4 Performance Enhancements for Tr
Page 51 and 52: An optional -day argument is added
Page 53 and 54: 6 System 6.1 Call Client Hold Integ
Page 55 and 56: 6.2 Calling Line ID Delivery Enhanc
Page 57 and 58: • Figure 23 Schematic Overview of
Page 59 and 60: NMS SYSTEM NS Customer database SLA
Page 61 and 62: 6.5 G.729 Codec Support Feature ID(
Page 63 and 64:
cList List of string (1 to 32 chara
Page 65 and 66:
According to RFC 2897 (for MGCP), t
Page 67 and 68:
is physically connected to that aud
Page 69 and 70:
6.10 Multiple Country Code Support
Page 71 and 72:
6.11.1.2 Custom Service Announcemen
Page 73 and 74:
A new mouse over text property file
Page 75 and 76:
� Selective Call Rejection The ch
Page 77 and 78:
Open Client Server maintains TCP/IP
Page 79 and 80:
OTG Maps to Site The Network Server
Page 81 and 82:
6.17 Pre-Typing Policy Feature ID(s
Page 83 and 84:
A PreCallTyping dial plan entry is
Page 85 and 86:
formatted directory number for whic
Page 87 and 88:
6.20.1.3 Application Server The App
Page 89 and 90:
AS_CLI/System/Routing/MediaServerSe
Page 91 and 92:
� SMCtcpwr, version 7.6 � SUNWj
Page 93:
6.22 Unregistered Endpoint Announce
show all

BroadWorks Functional Summary - CommPartners Connect

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?