BroadWorks Functional Summary - CommPartners Connect

More documents

Recommendations

Info

2.6.1.3 Pickup A pickup is triggered by the DPUBI service when the picked-up user is alerted for a single, terminating call. When a pickup occurs, the DPUBI user and the other party are connected to one another, and the picked-up user is released. The DPUBI service pickup functionality is identical to the DPU service. 2.6.1.4 Barge-in A barge-in is triggered by the DPUBI service when the picked-up user has a single, answered call. The barge-in occurs regardless of whether the picked-up user’s call was originating or terminating, and regardless of its current state (for example, active, held, and so on). When a barge-in occurs and the user’s warning tone option is enabled, the picked-up user is given the barge-in warning tone (one second of 440 Hz followed by 50 ms of silence). The other party is put on hold while the picked-up user is receiving the warning tone. Note that the picked-up user is not given the warning tone if they have put the call on hold. Once the warning tone has finished (or immediately if the user’s warning tone option is disabled), a three-way call is established with the DPUBI user as the controller. The DPUBI user now has a call with the picked-up user and with the other party. The pickedup user and the other party now have a call with the DPUBI user instead of with each other. If the DPUBI user has the Flash Three-Way Call service assigned and flashes while the three-way call for the barge-in is present, then the other party is dropped from the threeway call. If the DPUBI user does not have the Flash Three-Way Call service and flashes, then the flash is ignored according to the existing flash service rules. If the DPUBI user has the Flash Transfer service assigned and hangs up (goes on-hook) while the three-way call for the barge-in is present, then the picked-up user and the other party are transferred together. If the DPUBI user does not have the Flash Transfer service assigned and hangs up, the picked-up user and the other party are released. 2.6.1.5 Barge-in Exempt When a user has the Barge-in Exempt service enabled, the user’s calls cannot be barged in on by another user using the DPUBI service. If a user attempts to use DPUBI to bargein, then the barge-in is rejected and the user receives the reorder tone. If the Barge-in Exempt service is disabled, then DPUBI barge-in attempts are allowed as usual. If a user has the Barge-in Exempt service enabled but has a single incoming, alerting call then the call can be picked up by another user using the DPUBI service. Barge-in Exempt does not block pickup attempts. BROADWORKS FUNCTIONAL SUMMARY 2O-BD5013-00 PAGE 14 OF 93
2.7 Auto Callback Feature ID(s): 10714 The Automatic Callback (ACB) service allows users to monitor a busy party and automatically establish a call when the busy party becomes idle. Upon reaching a valid ACB busy condition, the user hears an announcement asking if they would like to monitor the line and be called back when it is idle. To activate ACB the subscriber enters the digit when prompted then goes on hook. As soon as the called party becomes idle again, ACB attempts to re-establish the call between the subscriber and the previous busy party. The ACB service can only be activated against a destination within the same group. ACB is authorized and provisioned as a subscriber service, and can be enabled and disabled by the subscriber. 2.7.1 Description Automatic Callback is an outgoing call feature that allows a subscriber to place a call to another subscriber in the same group. If the called subscriber is busy, the call originator can activate Automatic Callback to be notified when the called subscriber is idle. When notified, a new call setup attempt to the idle subscriber is initiated automatically and the originating subscriber is not required to redial the phone number. The new call attempt is treated as an originating call attempt; it could receive busy treatment or be redirected. For the new call setup to be attempted both parties must be available. A terminating subscriber is considered busy, or unavailable if they cannot receive a call at their primary location. This means that if a terminating feature redirects the call and the new location is busy, ACB is not activated. ACB is also disabled if the call is handled by any of the following terminating services, Selective Call Rejection and Selective Call Acceptance, but is not limited to these service interactions. When a subscriber originates a call to another subscriber in the group, if the called party is unable to receive the call because of a valid ACB busy condition, a prompt is played giving the originator the opportunity to activate ACB (for example, callers hear the message: The line you are calling is busy. Press 1 if you would like to be notified when the line is available). After activating ACB, the subscriber goes on hook and is notified with special ringing when both parties are idle. If the user answers special ringing, call setup is automatically initiated toward the other party. A subscriber that has activated ACB can also deactivate all outstanding ACB requests. Entering the ACB deactivation Feature Access Code cancels all outstanding requests by that subscriber. ACB has several operating parameters that are configured at the system: � Monitor minutes: The amount of time to camp-out on the busy line, waiting for it to become idle. (The default is 30 minutes and the range is 5 to 120 minutes.) � Retry originator minutes: The amount of time to wait before re-trying a busy Automatic Callback originator (the owner of the ACB session). (The default is 5 minutes and the range is 1 to 15 minutes.) � Maximum sessions: The total number of outstanding ACB sessions for one subscriber. (The default is 5 and the range is from 1 to 30 sessions.) BROADWORKS FUNCTIONAL SUMMARY 2O-BD5013-00 PAGE 15 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 and 12: • Figure 5 Auto Attendant Add Pag
Page 13: 2.6 Directed Call Pickup with Barge
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

Create successful ePaper yourself

Delete template?

Save as template?