BroadWorks Functional Summary - CommPartners Connect

More documents

Recommendations

Info

5 Operations, Administration, and Maintenance 5.1 Call Capture and Trace Utility Feature ID(s): 10178 The Call Trace Utility is a tool that allows a user to trace specific calls in the debug logs based on a BroadWorks user ID, a directory number, and a specified time frame. This allows customers to provide BroadWorks support using only the necessary sections of the Execution Server logs that pertain to a particular call scenario, which enables BroadWorks support to more easily diagnose problems. 5.1.1 Description Providing the proper logs for support is always a difficult task for customers. The Call Trace Utility addresses this problem by providing a method for customers to specify a time range and a call scenario and extract the precise sections of the Execution Server debug logs. The Call Trace Utility is used via the command line interface. The user is required to specify the following: � Starting time, which should be in the format “YYYY.MM.DD HH:MM”. Hours should be specified using the 24-hour clock. � Ending time, which should be in the format “YYYY.MM.DD HH:MM”. Hours should be specified using the 24-hour clock � One or more directory numbers (DNs) or user IDs to identify either the terminating or originating side of the call. DNs should be in E.164 format. � Inter-group calls should be specified with both originating and terminating user IDs or DNs. � Tracing scenarios that cannot identify the user (for example, a 404 response to a REGISTER) should be searched with “Unknown” as the user. � PSTN call legs must be specified with a DN � A BroadWorks user can be specified with either DN or user ID. Users without a provisioned DN must be searched by user ID. The user can also specify a file name to store the output or dump the output to the screen. Output displayed on screen can be paged so it can be easily viewed. Both sides of the call are included in the call trace output. In addition to the parsed call trace data, configuration information is included in the output, describing the device and configuration for the user. BROADWORKS FUNCTIONAL SUMMARY 2O-BD5013-00 PAGE 40 OF 93
5.2 Conferencing OAM Integration Feature ID(s): 13585, 13584, 13587 5.2.1 Web Portal Integration The purpose of this activity is to make Conferencing Server functionality available in the BroadWorks web application. Specifically, this activity makes available the following call control commands that were not previously fully supported on the Conferencing Server, as follows: � Ad-hoc conferencing (bridge administrator initiates a conference on-the-fly by specifying their own phone number and a participant’s phone number – the bridge dials out to both numbers and establishes the conference). � Bridge administrator or participant can initiate an outgoing call from the conference bridge to a specified number, automatically adding a participant to a specified conference (known as "join a conference" functionality). � Bridge administrator or participant can initiate an outgoing call from the conference bridge to a specified number, automatically starting playback of a conference recording. 5.2.2 Accounting Integration In Release 11, the Application Server integrates more seamlessly with the Conference Server. As part of a larger integration effort, this particular feature integrates accounting information from the server into the BroadWorks call detail records. BroadWorks service providers should find it easier to bill their customers for use of the Conference Server. This feature affects two Application Server interfaces: the Application Server or Conference Server SIP interface, and BroadWorks call detail records. The Application Server or Conference Server SIP interface adds support for SIP NOTIFY messages from the Conference Server to the Application Server. These NOTIFY messages convey relevant accounting information from the Conference Server to the Application Server. The BroadWorks call detail records add new information necessary for more accurate billing for Conference Server usage. 5.2.3 Description 5.2.3.1 Web Portal Integration There are several concepts introduced on the Application Server by this activity, as follows: � Bridge provisioning enhancements (available both in the web and OSS) � Conference scheduling (available both in the web and OSS) � Presentation set up (web only) � Ad-hoc conferencing (web only) � Conference call control and recording (web only) � Presentation viewing and moderating (web only) � Audio recording and slide show playback (web only) BROADWORKS FUNCTIONAL SUMMARY 2O-BD5013-00 PAGE 41 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 and 14: 2.6 Directed Call Pickup with Barge
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: 4.4.1.4 Detection of Escape Sequenc
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?