BW SAApplicationServerModule6 R120

BroadWorks System Administration
Module 6: Application Server Release 12 Version 1
May 2005
142
Module 6: Agenda
BroadWorks Application Server
Brief review of Application Server
Redundancy
Overview and implementation
Application Server Configuration

CLI configuration commands
Web Interface Configuration

Service provider configuration Enterprise configuration Group configuration User configuration
143
2005 BroadSoft, Inc. Proprietary and Confidential; Do Not Copy, Duplicate, or Distribute
143
Module Objectives
At the end of this module, you will be able to:
Explain the roles of the system provider, provisioning administrator, service provider, group administrator, and end user As system provider, configure Application Server system parameters Create and manage service providers Create and manage groups Add users to groups
144
144
Application Server
Network Devices
SIP
CLI
Telnet/SSH
POP/SMTP
Mail Servers
Web Browser
HTTP/SSL
SIP
Media Servers
M GC P
SIP
145
Call and Service Control

Line-side softswitch Call-half based Back-to-back SIP user agent MGCP call agent
Database
Subscriber database, service database, system configuration
File System
System announcements, service prompts and greetings, accounting information
Inter-Networking
SIP used as an IMT Complete PSTN service transparency Connectivity to gateways, proxies, softswitches, Network Servers
External Services
POP, IMAP4, and SMTP support. POP/IMAP servers store voice messages SIP to BroadWorks Media Servers and external media servers
Management
Integrated web server User, group, reseller web portal for self-service management Command line interface
P SI
145
Application Server Features
rsync DB ttRep DB
AS1
AS2
146
Redundancy
Application Servers are deployed in an primary/secondary node configuration. Application Server provides IP interface redundancy (Solaris multipathing).
Data Replication
Application Server is delivered with the commercial database, TimesTen. When a change occurs in either primary or secondary Application Server, data is automatically replicated to the other Application Server database.
File Replication
Relevant files (voice mail prompts, greetings) are synchronized across primary and secondary Application Servers using RSYNC.
146
End-User Active Application Server Tracking

NS Cluster
Node 1 Node 1
AS Cluster 2
Node 0
Node 2
Node 3
Primary
Secondary
N+1
AS Cluster 1
Node 0 Node 1
Primary
Secondary
User A: - Primary: node 0 - Hosting: node 0
User B (rolled over): - Primary: node 0 - Hosting: node 1
147
End-User Active Application Server Tracking

The Application Server cluster tracks where a user is active at any point in time. The Network Server cluster tracks the Application Server node on which end user is active. Each endpoint in an Application Server cluster has an associated node indicator. ActiveNode The active node indicator is changed whenever a rollover or rollback action occurs; it is used to track which node in the cluster can terminate a call. The active node indicator is synchronized with the Network Server so that incoming calls can terminate on the node hosting an endpoint. The Network Server tracks the active node for all users. The Network Server tracks active nodes on a per DN and URL basis. The Application Server Redundancy (ASR) protocol is used to push active node information between Application Servers and the Network Server. When the primary Application Server is not reachable, calls to and from an endpoint are processed by the secondary node in the cluster. This condition triggers a rollover of an endpoint to the secondary Application Server. Subsequent calls are processed by the secondary node until: 1. The primary node becomes available. 2. There are no active calls being processed on the secondary node. 3. These combined conditions trigger a rollback of an endpoint to the primary Application Server.
147
Example: PSTN Originated Rollover

Primary AS - AS1 Network Server NS1
ASR
2 3 4 6a 5a 5b 1
TTREP
6b
NGW NGW
Call
Voic e path
5c
AS2
User A
5d
AD User B
148
Example: PSTN Originated Rollover

1. A (a PSTN user) calls B (a BroadWorks user currently hosted on the primary Application Server). 2. The call goes from the NGW to the Network Server. 3. The Network Server returns the addresses of the primary and secondary. 4. The NGW INVITEs the primary Application Server but times out. 5. The NGW INVITEs the secondary Application Server which accepts the call. 6. The secondary Application Server migrates the user via ASR/TTRep and becomes the active node.
148
Example: Intra-Group Call For Rolled Over Endpoint

NS1
AS1
2 3
AS2
4
Call
1
Call
5
149
Example: Intra-Group Call for Rolled Over Endpoint

1. A and B are in the same group. Following a rollover, B is active on the secondary Application Server. A calls B. 2. The primary Application Server sees that B is not active and asks the Network Server to locate it. 3. The Network Server returns the addresses of the secondary Application Server in the 302 contact list (with proprietary group information). 4. The primary Application Server INVITEs B off the secondary Application Server. 5. The secondary Application Server terminates the call to B.
149
Example: Call Waiting For Rolled Over Endpoint

NS1
AS1
2 3
AS2
4
NGW NGW
CWT
5b 5a
Call
Voice path C User A

1
User B
150
Example: Call Waiting for Rolled Over Endpoint

1. A is on the phone with B, A is hosted on the secondary Application Server. 2. C from the PSTN calls A, the call goes from the NGW to the Network Server. 3. Network Server returns the addresses of the secondary and primary. 4. NGW INVITEs the secondary Application Server, which accepts the call. 5. Call waiting tone provided to A (a), ringback provided to C (b).
150
Example: Rollback - MGCP

AS1
5
NS1
A hosted on: AS1, AS2
Rollover
ASR
A active on: AS2
migration
AS2
2
4
A hosted on: AS1, AS2
IAD
A active on: AS1
User A
Rollback
1
151
Example: Rollback - MGCP

1. The rollback timer expires on the secondary node. 2. The secondary node identifies A to be rolled back and informs the primary node using ASR (RequestMigration). 3. The primary node requests the control of the endpoint from the IAD. 4. IAD accepts the rollover since the endpoint is not already involved on a call. The Application Server updates the active node in the database and notifies the Network Server using ASR of the users new active node. 5. Network Server changes the active node in its database to the primary node. 6. Network Server acknowledges the migration. For MGCP, the rollback is confirmed with the IAD by the primary Application Server sending a RQNT to the endpoint. For SIP, the rollback is confirmed by sending a SIP OPTIONS message to the endpoint.
151
Example: DNS Returns Secondary First

AS1
DNS DNS
1 2 9 10
Log in
Ping
7 5
AS2
3,4 8
Log in
Portal
6
NS1
152
Example: DNS Returns Secondary First

1. 2. 3. 4. 5. End user posts Application Server cluster FQDN (DNS A record). The DNS returns the secondary node address first. The browser posts an HTTP request on the secondary node and gets the Login page. The end user enters user ID/password which is processed by the secondary server. The secondary server recognizes that the end user is not hosted on itself and queries the Network Server Portal API. 6. The Network Server returns the addresses of the primary and secondary. 7. The secondary finds the primary is alive, retrieves the prepared login cookie from primary. 8. The secondary http redirects the browser to the primary and includes the cookie. 9. The browser sends the HTTP request to the primary with the login cookie. 10. The primary returns the end-user Home page.
End-User Login
1. 2. 3. 4. 5. Always logged in at its hosting node. At login time, the Application Server validates that it is the hosting node for a user. If not, and the primary is available, an http redirect is returned. If not, and the primary is NOT available, the user is rolled over to the login node. The address of the primary node in the cluster is obtained from the Network Server using the Portal API. 6. The Call Manager and Personal CommPilot sessions are invalidated when the endpoint associated with a user is rolled over to an alternate node. 7. User must log in again.
152
Example: Admin Login - Primary Not Responding

AS1
DNS DNS
1 2
Ping
AS2
3,4 8 7 5
Login
Portal
6
NS1
153
Example: Admin Login Primary Not Responding

1. Admin posts Application Server cluster FQDN (DNS A record). 2. The DNS returns the secondary node address first. 3. The browser posts an HTTP request on the secondary node and gets the Login page. 4. The admin types in a user ID/password which is processed by the secondary server. 5. The secondary server recognizes that this is an administrator and verifies that the primary Application Server is not available. 6. The secondary Application Server queries the Network Server Portal API to get the primary server public addresses. 7. The Network Server returns the addresses of the primary node. 8. The secondary finds that the primary is not alive. 9. The secondary returns the administrators home page with a warning that the administrator will be kicked out as soon as the primary becomes available.
153
Application Server Configuration Steps

Using the CLI, perform initial system configuration
Before using the web portal to configure groups and users, certain basic configuration steps must be completed on the Application Server
1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. Application Server aliases Network Server identity Enable Media Server Selection or static MS Enable Application Server/Network Server Sync API Enable accounting Configure SNMP Intra-group/PSTN routing Voice messaging SMTP/POP3 setup MGCP notified entity (redundant systems) System domain Access and network-side devices SIP realm
154
154
Initial Application Server Configuration

AS_CLI/System/Alias> add as.lab.broadsoft.com AS_CLI/System/Alias> get Alias ==================== 192.168.5.180 as.lab.broadsoft.com
AS_CLI/System/Device/NetServ> add 192.168.5.193 both port 5060 poll false AS_CLI/System/Device/NetServ> get Address Port Poll OpState Description Type ================================================= 192.168.5.193 5060 false enabled both
155
Application Server Aliases

Set all names that identify the Application Server as a proxy/call agent (for a redundant system, should each have an alias to the cluster FQDN). The add command and the following field is used to add a system alias. Address: The IP address of the network device from which calls are permitted. Valid values are IP address, host, or domain.
Network Server Identity

Set the Network Server address. When type = both this indicates that the Network Server supports both SYNCAPI updates and SIP redirect lookups. The add command and the following fields are used to add a Network Server IP address. ipAddress: The corresponding IP address, or host name, or domain for the Network Server. Type: One of the following values: lookup - The Network Server is being used for routing purposes. update - Group information is propagated whenever the Application Server talks to the Network Server. both - The Network Server is used for both update and lookup purposes. Attribute: Attributes and their values are: port - The port on the Network Server used by the Application Server to talk to the Network Server. poll - Enables Network Server polling. Valid values are true or false. description - The description of the Network Server.
155

AS_CLI/System/CallP/Routing/MediaServerSelection> get mediaServerTimerLength = 15000 mssRouteTimerLength = 800 useStaticMediaServerDevice = false
AS_CLI/System/CallP/Routing/MediaServerSelection/MediaServerDevice>add 192.168.5.102 port 5060 ...Done AS_CLI/System/CallP/Routing/MediaServerSelection/MediaServerDevice>get IP Address Port Description ================================ 192.168.5.102 5060
156
Enable Media Server Selection (Optional)

Media Server Selection (MSS) is enabled by default. The set command and the following fields are used to set the Media Server Selection. MediaServer TimerLength: The time (in milliseconds) the Application Server waits before declaring that the Media Server has ceased responding. MssRoute TimerLength: The time (in milliseconds) the Application Server waits before advancing to the next Network Server during Media Server selection, or before advancing to the next Media Server when processing an initial connection message. UseStatic MediaServerDevice: When set to false the Application Server will query the Network Server for a Media Server. When set to true the Application Server will use a static list of Media Server on the Application Server. Static Media Servers (optional) If MSS is not used, then Media Servers must be statically defined on the Application Server. The add command and the following fields are used to add Media Servers. ipAddress: The IP address, host name, or domain name of the Media Server. port: The port of the Media Server. attribute: Attributes and their values are: description - The description of the Media Server. poll - Enables server polling (or pinging). Valid values are true or false.
156

AS_CLI/Interface/NetServSync> set syncFlag true AS_CLI/Interface/NetServSync> get syncFlag = true
AS_CLI/Interface/Accounting/BroadWorksCDRInterface> set enabled true AS_CLI/Interface/Accounting/BroadWorksCDRInterface> get enabled = true enableCDRLongDuration = true enableCDRStartEnd = true enableFailoverInfo = true enableIntraGroupCDR = true enableModuleCentrex = true enableModuleIP = true enableTerminatingCDR = true
157

Enable Application Server/Network Server Sync API Sync API ensures all Application Server group/phone number additions/deletions are propagated automatically to the Network Server. The set command and the following fields are used to set the Network Server synchronization. syncFlag: Enables Network Server synchronization. Valid values are true or false. Enable Accounting (Optional) Event billing and call detail record (CDR) generation are disabled by default. However, once enabled records are sent to the /var/broadworks/billing directory. The set command and the following fields are used to set Accounting attributes. Valid values for all of these attributes are true or false. enabled: Enables the Accounting interface. enableCDRLongDuration: Enables long duration CDRs. enableCDRStartEnd: Enables CDR start and end. enableFailoverInfo: Enables failover CDR generation. enableIntraGroupCDR: Enables intra-group CDRs. enableModuleIP: Enables the IP module. enableModuleCentrex: Enables the Centrex module. enableTerminatingCDR: Enables terminating CDR.
157

AS_CLI/Interface/Accounting/BroadWorksCDRInterface/File> set outputFormat csv AS_CLI/Interface/Accounting/BroadWorksCDRInterface/File> get billingHoldTime = 14 billingRotationHour = 14 billingRotationMinutes = 5 billingRotationsPerDay = 1 enabled = true outputFormat = csv bufferSize = 1
158

The outputFormat and cdrBufferSize parameters are added at the AS_CLI/Interface/ Accounting/BroadWorksCDRInterface/File> level.
158

AS_CLI/Interface/Accounting/BroadWorksCDRInterface/Radius> get radiusServer1Address 192.168.12.34 enabled = true sendCallStartCDR = true sendCallAnswerCDR = true radiusServer1Address = 192.168.12.34 radiusServer1Port = 1813 radiusServer2Address = 192.168.56.78 radiusServer2Port = 1813 sharedSecret = 12XpkkY2vVVb28..pZWW8m retransmissionDelay = 1000 retransmissionsMax = 3
159
Application Server Radius Accounting Configuration

This command is used to modify the Radius Accounting attributes in the system. The set command and the following fields are used to set Radius Accounting attributes: enabled: Enables or disables the sending of CDRs in real time. sendCallStartCDR: Controls whether or not a CDR is to be sent upon originations or terminations. sendCallAnswerCDR: Controls whether or not a CDR is to be sent upon answer. radiusServer1Address: Address (IP or FQDN) of a Radius Server where to send accounting requests. radiusServer1Port: Destination port where accounting requests for RadiusServer1 are sent. Defaults to 1813. radiusServer2Address/radiusServer2Port: Alternate destination for accounting requests. sharedSecret: The shared secret used for computing or validating the Authenticator in accounting request/responses. This field is case sensitive. It MUST match the configuration of the Radius Servers. If two Radius Servers are used, both servers MUST use the same sharedSecret with respect to this Application Server. retransmissionDelayMilliseconds: Time to wait for an accounting response after sending an accounting request, before re-sending. maxTransmissions: Maximum number of transmissions of the same accounting request to a given Radius Server, before trying the other server, or dropping the request should the other server had been tried already.
159

AS_CLI/System/CallP/Routing/RoutingXLA> add * Network Server AS_CLI/System/CallP/Routing/RoutingXLA> get NPA-NXX Route ======================= * Network Server
160
Inter-Group/PSTN Routing
Calls not destined for another user in the same group must be routed to a network device for handling. The Application Server supports originator-based routing (where * means all users). The Application Server should have one route for all users pointing to the Network Server. The add command and the following fields is used to add the PSTN routing: Digits: The NPA-NXX number. Route: The route name. An asterisk (*) is used as a wildcard.
160

AS_CLI/Interface/Mail> get primarySMTPServer = 192.168.5.181 secondarySMTPServer = defaultFromAddress = mailer@broadsoft.com defaultSubject = Default Email AS_CLI/Service/VoiceMsg> set mailServerProtocolForSystemVM POP3 AS_CLI/Service/VoiceMsg> set mailServerForSystemVM 192.168.5.181
161
Voice Messaging SMTP/POP3 Set Up

Voice Messaging and Call Notify services require the presence of a SMTP and POP3/IMAP server. Primary and secondary SMTP server are set up via the CLI. POP3/IAMP server settings can be configured via the CLI or web portal. The set command and the following fields are used to set up the SMTP/POP3 server: primarySMTPServer: The primary SMTP server address to provide e-mail to users. secondarySMTPServer: The secondary SMTP server address to provide e-mail to users. defaultFromAddress: The default From address to be used when the senders address is not available. defaultSubject: The default Subject heading to be used when the senders e-mail subject is not available, for example, Subject Not Available. The set command and the following fields are used to set the mail server: mailServerForSystemVM: The host name of the server to which voice mails will be sent and then retrieved by the user. mailServerProtocolForSystemVM: Valid values are as follows: POP3 - Use the POP3 protocol to connect to mail server. IMAP - Use the IMAP protocol to connect to mail server.
161

MGCP Notified Entity
AS_CLI/Interface/MGCP> set notifiedEntity as.lab.broadsoft.com
Default System Domain

AS_CLI/System/Domain> set lab.broadsoft.com
Access and Network-Side Devices

set bw.sip.accessinterfaceviahost accessSideAS1.broadsoft.com set bw.sip.networkinterfaceviahost networkSideAS1.broadsoft.com
162
MGCP Notified Entity

For Application Server redundancy to work with MGCP devices, the MGCP Notified Entity must be set to the Application Server cluster FQDN. The set command and the following field is used to set the MGCP Notified Entity. notifiedEntity: The hostname portion of the NotifiedEntity parameter sent within MGCP requests when sendNotifyEntity is true.
Default System Domain

A default system domain can be configured. All users belonging to the default domain can log in with their user name only. The set command and the following field is used to set the domain name. domainName: The system-wide domain name. WARNING: This parameter should be set with caution. Every time this parameter is changed, it invalidates the authentication password for all subscribers in the system with the authentication service. Changing this parameter requires every BroadWorks subscriber with the Authentication service to re-enter their authentication password.
Access and Network-Side Devices

bw.sip.accessinterfaceviahost is an ipAddress or hostname indicating the location on this BroadWorks Application Server where access-side devices should send responses. bw.sip.accessinterfaceviahost is included within Via sent-by of SIP requests sent towards access side devices. If the value is empty, system property publicIPAddress shall be used. If it is not set, the ipAddress from resolving localhost is used. bw.sip.networkinterfaceviahost is an ipAddress or hostname indicating the location on this BroadWorks Application Server where network-side devices should send responses. bw.sip.networkinterfaceviahost is included within Via sent-by of SIP requests sent towards network side devices. If the value is empty and privateIPAddress and publicIPAddress are set, privateIPAddress shall be used. If only publicIPAddress is set, it is used. Otherwise the ipAddress from resolving localhost is used. Modifications do not become active until after a restart.
162

SIP Realm
AS_CLI/Interface/SIP> set useDomainForRealm true
AS_CLI /Interfaces/SIP> set supportTcp true
AS_CLI /Interfaces/SIP> set supportDnsNaptr true
AS_CLI/Interface/SIP/ContentType> add application/x-foo-ftp access
163
SIP Realm
Configure authentication challenges to send use domain for realm. The set command and the following fields are used to configure the authentication. useDomainForRealm: False - The SIP authentication realm defaults to BroadWorks for all users. True - The users domain is used for the SIP authentication realm for all users. set supportTcp: false/true -The system either supports or does not support TCP. supportDnsNaptr: false/true The system looks up the appropriate NAPTR and/or SRV records on the DNS. Content Type This command allows a user to add a content type entry to the list of BroadWorks Application Server supported content types. When adding a content type entry, an attribute identifying whether this content type entry should be allowed from the access, network, or both access and network-side interfaces must be specified. The set command and the following fields are used to add a content type entry: contentTypeEntry: Identifies the content type entry. supportedInterface: Identifies whether this content type entry should be allowed from the access, network, or both access and network-side interfaces. Valid values are access, network, or both.
163
Application Server User Hierarchy
System Provider
Service Provider
Enterprise
Group
Dept
Group
Dept
Group
Dept
Group
Dept
Users
Users
Users
Users Virtual System
Virtual System
164
Application Server User Hierarchy

Service provider = Reseller Group or department = Small enterprise User = End user Enterprise = Large company Group or department = Company site User = End user
164
Using BroadWorks Web Portal
165
To log in:
1. In the User ID field, enter the login name assigned to you. 2. Press the Tab key or click in the Password box. 3. Enter your password. 4. Press the Enter key or click the Login button.
To log out:
1. On any page in the system, click Logout. 2. Once you log out, to log in again you can log in with your existing user ID and password or log in with a different user ID and password.
165
CommPilot System Provider Home Page
166
CommPilot System Provider Home Page

After you have successfully logged in, the System - Profile page appears. It contains the Options list and the Profile menu items, which are Service Providers, Enterprises, Groups, Users, Administrators. System Links (Available on Every Page) Help: Click Help for online assistance. It takes you to the Help page associated with the current page. Home: Home takes you to the System Provider-Profile page. You can also use your browsers Back button. Logout: Logout exits the system.
166
Resources - Add Domain
167
Resources Add Domain

1.Select Domains from the System Resources menu to add or edit domains. 2.Click Add and enter the domain and click OK. The management of domains has been moved to the system level so that service providers can share domains. These domains are created at the system level. Domains can then be assigned to new or existing service providers.
167
Services Voice Messaging
168
System Voice Mail

Voice Portal Scope: Select one of the following options: System - Users can call any group voice portal rather than only the voice portal of their own group in order to initiate the login process. Users are redirected to their own voice portal, and will thus have access to their full feature set. Group - Users can only initiate the login process by calling the voice portal of their own group. MWI Sending Delay: If there are delays (due to SMTP relaying) for the voice mail to reach the users mailbox, the users phone message waiting indicator (MWI) light can start flashing before the message actually reaches the users mailbox. Set a delay time (in seconds).
168
Utilities Password Rules
169
Password Rules
You can specify to which users the password rules apply. If you want the password rules to apply only to administrative users, select System, Provisioning, Service Provider, Enterprise Administrators Only. To apply the password rules to all users in the system, select All Administrators and Users. When administrators and users are maintained outside of the system, select System and Provisioning Administrators; all other Administrators and Users use external authentication.
169
Add a Service Provider

To create a new service provider, you use a wizard that walks you through the steps to enter the information required for a service provider to operate The steps are:
1. 2. 3. 4. Assign domains Add a service provider administrator Authorize services Authorize phone numbers
170
170
171

1. From the Profile menu, click Service Providers. 2. To use the wizard to add a service provider, click Add Service Provider Wizard. 3. To edit a service provider, click Edit for the service provider you are editing.
171
Service Provider Setup: Step 1 of 5
172
Service Provider Setup

Wizard step 1 Specify information for the following fields: Service Provider ID: An identification or login name for the new service provider administrator. An e- mail address is a valid user ID. Default Domain: The default domain for the service provider. Click Next to continue.
172
173

Wizard step 2 Select the domains you are assigning to the service provider and then click Add or to select all domains, click Add All. Click Next continue.
173
174

Wizard step 3 Add the Administrator ID. This is an identification or login name for the new service provider administrator. An e-mail address is a valid user ID. Click Add for each administrator you wish to add. Click Next to continue.
174
175

Wizard step 4 Check the Select All box or check individual services to permit the use of services by the service provider for groups and users. Check the Limited To box to the right of the service name, and type the service instances limit number for this service provider (for assigning to groups and users). Based on the number of licenses purchased by a service provider, this field can be used to track and limit the number of instances of a service used by a service provider. Click Next to continue. NOTE: When unauthorizing services, you cannot remove those services that have already been assigned by the service provider.
175
176

Wizard step 5 Type up to four single phone numbers. Type complete phone numbers (including a plus sign [+] and the country code), without spaces or dashes. These numbers are purchased by and assigned for use by this service provider. Type up to four phone number ranges to be allocated by the service provider. Type ranges of complete phone numbers (including a plus sign [+] and the country code), without spaces or dashes (only the last four digits can be a range; type lowest number first). These numbers are purchased by and re-allocated for use by this service provider. To add the number(s) to the list of usable phone numbers by this service provider, click Finish.
176
Resources Devices
177
177
Shared Devices
VoIP Network
48-port IAD
Company A
Company B
Company D
Company C
178
178
Hands-On Training
Lab 1 Service Provider Configuration
179
Lab 1: Service Provider Configuration

Your instructor has completed the following basic Application Server configuration steps: 1. Set Application Server aliases. 2. Configured the Network Server and set RoutingXLA to send all network calls to the Network Server. 3. Enabled Media Server Selection and Network Server SyncAPI. 4. Configured Voice Messaging SMTP and POP3 servers.
179
System Domains
A service provider can assign domains to groups and user IDs. 1. On the System Resources menu page, click Domains. 2. Click Add. The System Domains Add page displays. 3. Add new domains as follows:
TEAM Service Provider TEAM 1 SP1 TEAM 2 SP2 TEAM 3 SP3 TEAM 4 SP4 TEAM 5 SP5 TEAM 6 SP6 TEAM 7 SP7 TEAM 8 SP8 TEAM 9 SP9 Domains grp11.com grp12.com grp21.com grp22.com grp31.com grp32.com grp41.com grp42.com grp51.com grp52.com grp61.com grp62.com grp71.com grp72.com grp81.com grp82.com grp91.com grp92.com
4. To save your changes, click OK.
180
Create a Service Provider

A system administrator can create multiple service providers to support group administration segregation. 1. On the System Profile menu page, click Service Providers. The System Service Providers page displays. 2. Click Add Service Provider Wizard. The System - Service Provider Setup: Step 1 of 5 Add a Service Provider page displays. 3. Create a new service provider with the following attributes:
Team Service Provider ID SP1 Domains Administrator Password Language Authorized Services Select All Phone Numbers 2403645111 2403645216 2403649171 Team 2 SP2 grp21.com grp22.com Team 3 SP3 grp31.com grp32.com Team 4 SP4 grp41.com grp42.com Team 5 SP5 grp51.com grp52.com Team 6 SP6 grp61.com grp62.com Team 7 SP7 grp71.com grp72.com Team 8 SP8 grp81.com grp82.com Team 9 SP9 grp91.com grp92.com sp9_admin 123456 English Select All sp8_admin 123456 English Select All sp7_admin 123456 English Select All sp6_admin 123456 English Select All sp5_admin 123456 English Select All sp4_admin 123456 English Select All sp3_admin 123456 English Select All sp2_admin 123456 English Select All 2403645112 2403645242 2403649177 2403645115 2403645248 2403649251 2403645141 2403645252 2403649253 2403645193 2403645255 2403649257 2403645195 2403645264 2403649259 2403645177 2403645230 2403649248 2403645136 2403645148 2403649249 2403645387 2403649225 2403649226
Team 1
grp11.com grp12.com
sp1_admin
123456
English
4. To save your changes, click Finish.
181
Create Service Provider Service Pack

A service pack is a collection of user services. A service provider can create service packs that can be authorized for assignment to users in groups. 1. On the System Profile menu page, click Service Providers and then click on the service provider you just created. 2. Click Resources. The Service Provider Resources menu page displays. 3. Click Service Packs. The Service Provider Service Packs page displays. 4. Click Add. The Service Provider Service Packs Add page displays. 5. Create a Service Pack called Call Forwarding with only the services: Call Forwarding Always, Call Forwarding Busy, Call Forwarding No Answer, and Call Forwarding Selective. 6. Create another Service Pack called Premium DO NOT assign Authentication assign all services except those found in the Call Forwarding service pack. Type the name and description for each new service pack. 7. Check the Available For Use box to make the service pack available for authorization for all groups. 8. Click Unlimited quantity to assign an unlimited number of instances to the service pack. 9. On the Available Services column, select the services to add to the service pack. To select several services listed in consecutive order, click the first service name you want and, while holding down the SHIFT key on the keyboard, click the last service name you want to select. To select more than one service, but not in a particular order, use your mouse to click the service names while holding down the CTRL key on the keyboard. Click Add> to transfer services to the Services in Pack column. Or, to move all services, click Add All>>. 10. To save your changes, click OK.
182
Add a Group
To create a new group, you use a wizard that walks you through the steps to enter information to provision a new group The steps are:
1. 2. 3. 4. 5. 6. Add a new group Add domains Add a group administrator Authorize services Authorize phone numbers Authorize access devices
183
183
Add a Group
184
Add a Group
1. Click Groups from the Profile menu page. 2. From the Service Provider - Groups page, click Add Group Wizard. 3. The system automatically walks you through with a wizard that prompts you to complete each step.
184
Group Setup: Step 1 of 6
185
Group Setup
Wizard step 1 Specify the following information for the group: Group ID: The unique identification code for this group, to be used when adding group members, and configuring group services. Do not use spaces. Default Domain: The domain to be used by this group. The default domain is at the beginning of the list.
185
186
Group Setup
Wizard step 2 To move only selected domains from one box to the other, click Add >. To move all the domains from one box to the other, click Add All >>.
186
187
Group Setup
Wizard step 3 Specify information for the following fields: Administrator ID: The unique login ID for the group administrator. Type this ID without using spaces. An e-mail address is a valid user ID. Domain name drop-down menu: The name of the domain. Initial Password: The initial password for the group administrator. (For security, asterisks display on the page instead of the characters typed.) Click Add. The new administrator displays in the list at the bottom of the Group Setup: Step 3 of 6 Add a Group Administrator page.
187
188
Group Setup
Wizard step 4 You use this page to authorize the use of the service packs and services. Click Select All or check individual services to permit the use of services by the group. Authorized Service Packs and Services are indicated by a check mark. Checked services are available for authorization to a group. Check the Limited To: box to the right of the service name (where available), and type a number of services available for assignment for this group. Based on the number of licenses purchased, this field can be used to track and limit the number of services assigned. NOTE: You cannot unauthorize a service if it has been assigned.
188
+15146922320 +15146922321 +15146922322 +15146922323 +15146922324 +15146922327 +15146922328 +15146922333
+15146922310 +15146922311 +15146922312 +15146922313 +15146922314 +15146922317 +15146922325 +15146922326
189
Group Setup
Wizard step 5 Click the range to add in the Available Range(s) box and then click Add >. Click the phone number or several numbers to assign in the Available Phone Number(s) box and click Add>. To move all the phone numbers from one box to the other, click Add All >>.
189
190
Group Setup
Wizard step 6 Specify information for the following fields: Device Name: The device name, for example, NetGraphics Main Hub. Device Type: The type of device. When the names are similar, the number of ports is listed after the dash at the end of the name, for example, Cisco 242116. Software Load: The selected software load, for example, CiscoLoad1. Protocol: The protocol of the device, for example, MGCP 0.1. Host Name/IP Address: The device name or IP number. This is optional for some devices, for example, for an IP phone. Examples are hostdevice@broadsoft.com or 111.1.11.1.
190
Resources - Assign Group Services
191
Assign Services for a Group

1. Click Assign Group Services from the Resources menu page. The services available, but not currently assigned to the group are listed on the left side. The services assigned to the group are listed on the right side. 2. To assign or unassign a service for the group, highlight the service and use the Add, Remove, Add All or Remove All buttons to move the service from column to column. 3. Click OK or Apply.
191
Hands-On Training
Lab 2 Group Configuration
192
192
Create a Group
Groups belong to a service provider. 1. On the System Profile menu page, click Service Providers and then click on the service provider you just created. 2. On the Service Provider Profile menu page, click Groups. The Service Provider Groups page displays. 3. Click Add Group Wizard. The Group Setup: Step 1 of 6 Add a Group page displays. 4. Create a new group for your team with the attributes shown in the following table. NOTE: Use the default system domain and do not add any devices.
Team
Group ID
Domain
Group Administrator ID grp1_1_admin grp1_2_admin grp2_1_admin grp2_2_admin grp3_1_admin grp3_2_admin grp4_1_admin grp4_2_admin grp5_1_admin grp5_2_admin grp6_1_admin grp6_2_admin grp7_1_admin grp7_2_admin grp8_1_admin grp8_2_admin grp9_1_admin grp9_2_admin
Group Administrator Password 123456 123456 123456 123456 123456 123456 123456 123456 123456 123456 123456 123456 123456 123456 123456 123456 123456 123456
Authorized Services Select All Select All Select All Select All Select All Select All Select All Select All Select All Select All Select All Select All Select All Select All Select All Select All Select All Select All
Phone Numbers
Team 1 Team 1 Team 2 Team 2 Team 3 Team 3 Team 4 Team 4 Team 5 Team 5 Team 6 Team 6 Team 7 Team 7 Team 8 Team 8 Team 9 Team 9
GRP1_1 GRP1_2 GRP2_1 GRP2_2 GRP3_1 GRP3_2 GRP4_1 GRP4_2 GRP5_1 GRP5_2 GRP6_1 GRP6_2 GRP7_1 GRP7_2 GRP8_1 GRP8_2 GRP9_1 GRP9_2
grp11.com grp12.com grp21.com grp22.com grp31.com grp32.com grp41.com grp42.com grp51.com grp52.com grp61.com grp62.com grp71.com grp72.com grp81.com grp82.com grp91.com grp92.com
2403645111, 2403645216 2403649171 2403645112 2403645242 2403649177 2403645115 2403645248 2403649251 2403645141 2403645252 2403649253 2403645193 2403645255 2403649257 2403645195 2403645264 2403649259 2403645177 2403645230 2403649248 2403645136 2403645148 2403649249 2403645387 2403649226 2403649225
5. Click Finish.
193
Create Group Access Devices Users must be associated with a device. MGCP devices must be created before they can be assigned to a user. SIP phone devices can be created dynamically when a user is created. 1. On the Service Provider Profile menu page, click Groups. The Service Provider Groups page displays. 2. Click on the group belonging to your team shown in the table below.
Team Team 1 Team 2 Team 3 Team 4 Team 5 Team 6 Team 7 Team 8 Team 9 Group ID GRP1_1 GRP2_1 GRP3_1 GRP4_1 GRP5_1 GRP6_1 GRP7_1 GRP8_1 GRP9_1 Device Name Polycom1 Polycom2 Polycom3 Polycom4 Polycom5 Polycom6 Polycom7 Polycom8 Polycom9 Device Type Verilink NetEngine 6x08 MGCP1.0 Verilink NetEngine 6x08 MGCP1.0 Verilink NetEngine 6x08 MGCP1.0 Verilink NetEngine 6x08 MGCP1.0 Verilink NetEngine 6x08 MGCP1.0 Verilink NetEngine 6x08 MGCP1.0 Verilink NetEngine 6x08 MGCP1.0 Verilink NetEngine 6x08 MGCP1.0 Verilink NetEngine 6x08 MGCP1.0 Address 192.168.5.111 192.168.5.112 192.168.5.113 192.168.5.114 192.168.5.115 192.168.5.116 192.168.5.125 192.168.5.126 192.168.5.130
3. Click Resources. The Group Resources menu page displays. 4. Click Devices. The Group Assign Domains page displays. 5. Click Add. Create a new access device for your group with the attributes shown in the table from Step 2. Assign Services Once authorized, services need to be assigned. Assigned users services are automatically assigned to existing and newly created users. 1. Click Resources. The Group Resources menu page displays. 2. Click Assign Group Services. The Assign Group Services page displays. 3. Assign all group services to each of your groups. 4. Click New User Services Template and then assign the Premium Service Pack to each of your groups. Extension Dialing Group extensions can range from two to six digits (the default is four digits). Group extension lengths can be increased. However, once users have been added, the group extension length cannot be reduced. From the group level and the Utilities menu page, click on Extension Dialing. Verify that the group extension length has been set to 4.
194
Group Calling Line ID BroadWorks supports phantom users (extension-only users). In order for extension-only users to originate calls, the group calling line ID must be set. For each of your teams groups, from the group level and the Utilities menu page, click on Calling Line ID, then select one of the assigned directory numbers to be the Group Calling Line ID. Voice Portal Activation A group can have a Voice Portal. Once active, the Voice Portal supports functions like voice mail retrieval, greetings changes, Remote Call Forwarding activation. 1. Under the group Group->Voice Portal menu, enable Voice Portal by clicking On and setting the extension field to 2000. 2. Click Save. 3. Repeat for each of your groups. Group Departments A user can be associated with a specific department. Departments can be used to specify calling plans for a subset of users and allows user searches based on departments. From your groups Profile page, click on Departments and then click Add. Create a new department called Testing. Group Auto Attendant A group can support multiple auto attendants. Each auto attendant can be configured to different DTMF key prompts for transfer to different numbers. 1. Under the GRP <Team#>_1 group level, click Services then Auto Attendant. Click Add to create a new auto attendant. 2. Set the Auto Attendant Name to Auto_Attendant. 3. Set the Auto Attendant phone number for your team according to the following table.
Team 1 2403645216 Team 6 2403645264 Team 2 2403645242 Team 7 2403645230 Team 3 2403645248 Team 8 2403645148 Team 4 2403645252 Team 9 2403649226 Team 5 2403645255
3. Under the Business Hours Menu, set Key 0, transfer to operator number to the Auto Attendant number (transfer on zero re-triggers the auto attendant). 4. Under the After Hours Menu, set Key 0, transfer to operator number to the Auto Attendant number and make sure Saturday and Sunday are not selected as Business days.
195
Group Calling Plans The Application Server supports a system-level incoming and outgoing call plan that can be applied to all groups. Different pre-defined digit pattern matches can be enabled or disabled per group, department, or user basis. The Application Server also supports the creation of customized group-level digit patterns that can be applied to group, department, or user to enable or disable specific user dialing patterns. 1. Under the GRP <Team#>_1 group level, click Calling Plan and then Outgoing Plan. Enable Casual dialing for the entire group. 2. Under the GRP <Team#>_1 group level, click Calling Plan and then Digit Strings. Click Add and then create a digit string named 01161_block with string value 01161* that will be applied to a group to block international calls to country code 61. 3. Under the GRP<Team#>_1 group level, click Calling Plan and then Outgoing Digit Plan. Disable group international calls to country code 61.
196
Add and Manage Users

Once a group has been set up, the group administrator can:
Add users to a group Assign or un-assign services to individual users Customize a users calling plan
197
197
Add a User
198
Add a User
Specify information for the following fields: User ID: The login ID (with no spaces, dashes or the symbols * and +). An e-mail address is a valid user ID. @: The domain name. The drop-down list displays all domains configured for the group. The group default domain name displays first. Last Name: A character-based name. First Name: A character-based name. Phone Number: The phone number. The drop-down list displays all phone numbers for the group. Extension: When a phone number is selected, the last X digits of the number populate the Extension text box automatically. Calling Line ID Last Name: The last name of the user for the calling line ID (CLID). Calling Line ID First Name: The first name of the user for the CLID. Calling Line ID Phone Number: The phone number to appear as the CLID for all calls, all but emergency calls, or only emergency calls. Aliases: One to three valid aliases for the user, to be used for URL dialling and other services. Some examples are as follows: sip:192.168.5.2:40070 sip:2403645125@12.39.208.204:23590 sip:2403645286@12.39.208.207:40036;user=phone;transport=udp
198
Add User Device Category
199
Set Up IAD/Gateway
IAD/Gateway Name: The model of the IAD or gateway for access. Certified IADs/Gateways set up by an administrator for use by this group display. Line/Port: The port or line.
Set Up IP Phone
IP Phone: The IP phone. The drop-down list contains all phones already registered by an administrator. New IP Phone Name: Name of a new IP phone. IP Phone Type: For a new IP phone, the type of model. The drop-down list contains the phone types certified for use by this group. Line/Port: The line or port number. @: The domain for a line/port. Contact: sip: The SIP URL for third-party call center queue users. MAC Address: The Media Access Control address of the phone.
Set Up Shared Device

Shared (name): The shared device set up by the service provider. Line/Port: The line or port number. Contact: sip: The SIP URL for devices with static registration.
199
Add a User Device
200
200
SIP Phone Key Components

(FTP Client) (File Server Machine) Configuration files are automatically transmitted to the file server BroadWorks Server TFTP Server FTP Server
reques ts c (T)FTP onfig files via server Phone
Web Interface
Upl oad defa ult c o
nfig fi
les
IP Phone
201
System deployment consists of configuring the FTP Client that is integrated into BroadWorks and installing an FTP server on a remote machine. The remote FTP server is used to upload the device configuration files to the file server machine. The phone downloads its configuration files from the file server machine. Typically the phone uses a TFTP server to download its file, although some devices support FTP. The TFTP server should also be installed on the remote machine. Each device type can configure its own file server, for example Cisco 7960 and Mitel 5055 phones can each have their own file server on different machines.
201
SIP Phone Configuration Process

1
Administrator creates system and group default configuration file Administrator sets the system file (Via CLI Interface, file must reside on the Broadworks file system)
proxy: Second proxy: TOS: Firmware:
Administrator saves the default files to a local disk
(File)
Computer
System default file is stored on the TFTP Server
TFTP Server
Administrator uploads the group file (Web or CLI interface)
Computer
Group default parameters are stored on the BroadWorks Server
BroadWorks Server
User or device is add to the system
Computer
Subscriber parameters are added to create a device configuration BroadWorks Server file
TFTP Server
202
202
Assign User Services
203
203
CommPilot Call Manager

System Buttons Indicators Your Name and Number
CommPilot Express Profile in Use
Enter Phone Number
Scott Smith, BroadSoft
Talking
3015550987
Call Control Buttons
Tabs
204
CommPilot Call Manager

You use to your CommPilot Call Manager to: Initiate a call Answer a second call End a call Place a call on hold Remove a call from hold Set Do Not Disturb (DND) Set Call Forwarding Always (CFA) Set Remote Office (RO) Start a Three-Way Conference call Blind Transfer a call Transfer with consultation System buttons allow you send an e-mail to technical support, get online help, or configure your CommPilot Call Manager.
204
Outlook Integration
Enter Phone Number text box Click card icon for v-card
Scott Smith, BroadSoft Talking 3015550987
Tabs Folder to Search for Contacts Search Criteria text boxes Refresh button Search button
Click name for v-card
205
Outlook Integration
1. Click the Outlook tab to display Outlook Contacts; click again to close. 2. Click phone number to populate the Enter Phone Number text box. 3. Click a name in the list or Card Icon in Call Control Area to show v-card of contact. Called or calling parties with a v-card have a Card Icon to the left of the name in Call Control Area. 4. Click Refresh to expose newly entered contacts. 5. Use scroll bar to view up to 25 contacts. Contacts not displayed must be searched for, or use the FIRST PAGE, PREVIOUS, NEXT, and LAST PAGE buttons (not shown). Search 1. Select the Name or Company from the drop-down menu. 2. Enter the search criteria in the text box. 3. Click Search. Up to 25 contacts meeting the criteria are displayed. 4. To search again with more specific criteria, use the paging buttons to view additional search results. Contacts newly entered in Microsoft Outlook display when Refresh is clicked.
205
Questions
206
206
Hands-On Training
LAB 3 User Configuration User Operations
207
207
User Configuration
Create Users A group administrator can create users and associate them with an access device type. A user can be associated with a MGCP device, a SIP device, or no device at all. The Application Server provides a list of supported access devices to select from. MGCP User Under your GRP<Team#>_1, click Profile and then Users. Click on Add and create a new user with the following attributes.
Team Team 1 Team 2 Team 3 Team 4 Team 5 Team 6 Team 7 Team 8 Team 9 User ID GRP1_1@grp11.com GRP2_1@grp21.com GRP3_1@grp31.com GRP4_1@grp41.com GRP5_1@grp51.com GRP6_1@grp61.com GRP7_1@grp71.com GRP8_1@grp81.com GRP9_1@grp91.com First and Last Names grp_1 Test grp_2 Test grp_3 Test grp_4 Test grp_5 Test grp_6 Test grp_7 Test grp_8 Test grp_9 Test Password 123456 123456 123456 123456 123456 123456 123456 123456 123456 Phone 2403645111 2403645112 2403645115 2403645141 2403645193 2403645195 2403645177 2403645136 2403645387 Device Category/Name/Port IAD/Gateway / Polycom1 / 1 IAD/Gateway / Polycom2 / 1 IAD/Gateway / Polycom3 / 1 IAD/Gateway / Polycom4 / 1 IAD/Gateway / Polycom5 / 1 IAD/Gateway / Polycom6 / 1 IAD/Gateway / Polycom7 / 1 IAD/Gateway / Polycom8 / 1 IAD/Gateway / Polycom9 / 1
SIP Phone User Under your GRP<Team#>_2, click Profile and then Users. Click on Add and create a new SIP phone user with the following attributes. (A new SIP phone can be created dynamically.)
Team Team 1 Team 2 Team 3 Team 4 Team 5 Team 6 Team 7 Team 8 Team 9
User ID GRP1_2 GRP2_2 GRP3_2 GRP4_2 GRP5_2 GRP6_2 GRP7_2 GRP8_2 GRP9_2
First & Last Names grp_1 Test2 grp_2 Test2 grp_3 Test2 grp_4 Test2 grp_5 Test2 grp_6 Test2 grp_7 Test2 grp_8 Test2 grp_9 Test2
Password 123456 123456 123456 123456 123456 123456 123456 123456 123456
Phone 2403649171 2403649177 2403649251 2403649253 2403649257 2403649259 2403649248 2403649249 2403649225
Device Category/Name/Type/ Port New IP Phone / IP1/ Siemens/ 2403649171 New IP Phone / IP2/ Siemens/ 2403649177 New IP Phone / IP3/ Siemens/ 2403649251 New IP Phone / IP4/ Mitel 5055/ 2403649253 New IP Phone / IP5/ 7960/ 2403649257 New IP Phone / IP6/ SoundPoint/ 2403649259 New IP Phone / IP7/ Mitel 5055/ 2403649248 New IP Phone / IP8/ Mitel 5055/ 2403649249 New IP Phone / IP9/ Mitel 5055/ 2403649225
208
Phantom (Extension Only) MGCP User Under your GRP <Team#>_1, click Profile and then Users. Click Add to create a new user with the following attributes. NOTE: The Phone Number should be set to none.
Team Team 1 Team 2 Team 3 Team 4 Team 5 Team 6 Team 7 Team 8 Team 9
User ID
GRP1_3@grp1_1.com GRP2_3@grp2_1.com GRP3_3@grp3_1.com GRP4_3@grp4_1.com GRP5_3@grp5_1.com GRP6_3@grp6_1.com GRP7_3@grp7_1.com GRP8_3@grp8_1.com GRP9_3@grp9_1.com
First and Last Names grp_1 Test3 grp_2 Test3 grp_3 Test3 grp_4 Test3 grp_5 Test3 grp_6 Test3 grp_7 Test3 grp_8 Test3 grp_9 Test3
Password 123456 123456 123456 123456 123456 123456 123456 123456 123456
Phone Ext 2001 2001 2001 2001 2001 2001 2001 2001 2001
Device Category/Name/Port IAD/Gateway / Polycom1 / 2 IAD/Gateway / Polycom2 / 2 IAD/Gateway / Polycom3 / 2 IAD/Gateway / Polycom4 / 2 IAD/Gateway / Polycom5 / 2 IAD/Gateway / Polycom6 / 2 IAD/Gateway / Polycom7/ 2 IAD/Gateway / Polycom8 / 2 IAD/Gateway / Polycom9 / 2
Voice Messaging Configuration Voice Messaging must be configured for each user. A user can be associated with a POP3/IMAP standard mail server or have voice messages delivered as .WAV files to a private e-mail address. Perform the following steps for each of your users. 1. Under the group level, click Profile and then Users. Click on your user. 2. Under the user level, click Messaging and then Voice Management. Messaging to on. Set Voice
3. Click on Advanced Settings next to Use unified messaging to enter POP3 information. 4. POP3 accounts have been pre-configured for each user. Server set the following parameters for each user:
E-mail address: user<group#>_<user#>@192.168.5.102 User ID: user<group#>_<user#> Password: 123456
Under the Group's Mail
209
BroadWorks User Experience

The following steps allow you to become familiar with the CommPilot web portal, basic calling, and BroadWorks services. User Login Users logging into the Application Server CommPilot web portal have access to the BroadWorks Call Manager to manage calls and the CommPilot web portal (IE window) to manage user services. All service changes are automatically updated in the Application Server database. 1. In the Call Manager window, click the Help link. 2. Can you find information on the help page for the Call Manager?_______________ 3. In the Call Manager window, click on the Support icon 4. What is the To address on the e-mail message and which menu option was used to set it?_______________________________________________________________ 5. In the Call Manager window, click the Configure link. 6. What happened? ____________________________________________________ 7. What happens if the CommPilot Personal web page is closed?_______________ 8. In the Call Manager window, click on the Group tab. 9. What information is provided? __________________________________________ 10. Close the CommPilot Personal window and click on the Call Manager window DND button. 11. What happens?_____________________________________________________ 12. In the CommPilot Personal window, click on the Home link. 13. What three pieces of information is provided? _____________________________ 14. Which Personal level menu would you go to change your CommPilot web access password? ____________________________________________________ 15. Which level would you go to in order to set the Call Forward No Answer Phone Number? __________________________________________________________________
210
Call Manager Basic Calling Call Manager provides basic information related to active calls (for example, calling party identity, and call state). 1. Have user<Team#>_1 call the four-digit extension of user<Team#>_2, let the phone ring. 2. What do you see in each users Call Manager window? _____________________ 3. What happens when user<Team#>_1 clicks the Call Manager Hang Up button? _________________________________________________________________ 4. Have User<Team#>_1 the call the four-digit extension for User<Team#>_2, answer the call. 5. What state is the call in according to Call Manager? _______________________ 6. Populate User<Team#>_1s Call Manager dialing box with the four-digit extension of User<Team#>_2, and click Dial. 7. Whose phone rings first? ______________________________________________ 8. What happens after user<Team#>_1 answers the call? ______________________ 9. What happens after user<Team#>_2 answers the call? _______________________ 10. Have User<Team#>_1 call the voice portal extension 2000, and enter the voice portal default password 0000. 11. Which key is entered to retrieve voice messages? __________________________ 12. Have User<Team#>_1 call the four-digit extension of the groups Auto Attendant and select key 1, dial by extension. Enter 2001. 13. To which user are you transferred? ______________________________________
211
Call Manager Basic Services Call Manager supports basic call management and service invocation (for example, call transfer, three-way calling, and pre-answer transfer to voice mail). Voice Messaging: 1. Have User<Team#>_1 call the 10-digit DN of user<Team#>_2. Do not answer the call. When the call rolls to voice messaging, leave a message for user<Team#>_2. How many rings did it take to roll over to voice messaging? ____________________ Where would you go to change the number of rings that occur before roll over to voice messaging? ________________________________________________________ What service would you invoke to send a call directly to voice mail? _____________ What happens to the call if user<Team#>_2 clicks the Call Manager Send to VM button while the call is still ringing? _______________________________________ What happens to the call if user<Team#>_2 populates the Call Manager dialing box with 2001, then clicks the Call Manager Send To VM button while the call is still ringing? Who gets the message? ________________________________________ 2. Under user<Team#>_2 Voice Messaging-> Message Management menu, enable E-mail a carbon copy of the voice message to: and set the address to your e-mail address (if accessible). What type of file is attached to the e-mail? ________________________________ Call Transfer and Conferencing: 1. Have User<Team#>_1 call the 10-digit DN of the user<Team#>_2. Answer the call. On User<Team#>_1s Call Manager, click the Hold button. Populate the Call Manager dialing box with 2001 and then click the Call Manager Transfer button to transfer the call. Which users end up connected? ________________________________________ The above scenario corresponds to a blind transfer, what would you do to invoke a consultative transfer to 2001? ___________________________________________ 2. Have User<Team#>_1 call the 10-digit DN of user<Team#>_2. Answer the call. On User<Team#>_1 Call Manager, click the Hold button. Populate the Call Manager dialing box with 2001 and then click the Call Manager Conference button to establish a threeway call. What happens if User<Team#>_1 hangs up? _______________________________
212

BW SAApplicationServerModule6 R120

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

BW SAApplicationServerModule6 R120

Uploaded by

Copyright:

Available Formats

BroadWorks System Administration

Module 6: Application Server Release 12 Version 1

Application Server Configuration

Web Interface Configuration

Call and Service Control

Application Server Features

End-User Active Application Server Tracking

User A: - Primary: node 0 - Hosting: node 0

User B (rolled over): - Primary: node 0 - Hosting: node 1

End-User Active Application Server Tracking

Example: PSTN Originated Rollover

Example: PSTN Originated Rollover

Example: Intra-Group Call For Rolled Over Endpoint

Example: Intra-Group Call for Rolled Over Endpoint

Example: Call Waiting For Rolled Over Endpoint

Voice path C User A

Example: Call Waiting for Rolled Over Endpoint

Example: Rollback - MGCP

A active on: AS2

A active on: AS1

Example: Rollback - MGCP

Example: DNS Returns Secondary First

Example: DNS Returns Secondary First

Example: Admin Login - Primary Not Responding

Example: Admin Login Primary Not Responding

Application Server Configuration Steps

Initial Application Server Configuration

Application Server Aliases

Network Server Identity

Initial Application Server Configuration

Enable Media Server Selection (Optional)

Initial Application Server Configuration

Initial Application Server Configuration

Initial Application Server Configuration

Initial Application Server Configuration

Initial Application Server Configuration

Application Server Radius Accounting Configuration

Initial Application Server Configuration

Initial Application Server Configuration

Voice Messaging SMTP/POP3 Set Up

Initial Application Server Configuration

Default System Domain

Access and Network-Side Devices

MGCP Notified Entity

Default System Domain

Access and Network-Side Devices

Initial Application Server Configuration

AS_CLI /Interfaces/SIP> set supportTcp true

AS_CLI /Interfaces/SIP> set supportDnsNaptr true

AS_CLI/Interface/SIP/ContentType> add application/x-foo-ftp access

Application Server User Hierarchy

Users Virtual System

Application Server User Hierarchy

Using BroadWorks Web Portal

CommPilot System Provider Home Page

CommPilot System Provider Home Page

Resources - Add Domain

Resources Add Domain

Services Voice Messaging

System Voice Mail

Utilities Password Rules

Add a Service Provider

Add a Service Provider