Administering Avaya Aura ® Session Manager Issue 1.1 03-603324 Release 6.
© 2010 Avaya Inc. All Rights Reserved. Notice While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes.
Downloading Documentation For the most current versions of Documentation, see the Avaya Support Web site: http://support.avaya.com. Contact Avaya Support Avaya provides a telephone number for you to use to report problems or to ask questions about your Product. The support telephone number is 1-800-242-2121 in the United States. For additional support telephone numbers, see the Avaya Web site: http://support.avaya.com.
Administering Avaya Aura ® Session Manager Comments? infodev@avaya.
Contents Chapter 1: Getting started.................................................................................................. 13 Introduction............................................................................................................................................... 13 Overview of System Manager................................................................................................................... 13 Log on to System Manager...............................................
Adding trusted certificates......................................................................................................................... 45 Exporting the Session Manager Certificate............................................................................................... 46 Removing trusted certificates.................................................................................................................... 47 Refreshing CA Certificate List.........................................
Aborting a user import job on first error............................................................................................ 114 Canceling a user import job.............................................................................................................. 114 Deleting an importing job.................................................................................................................. 115 Viewing a user importing job in Scheduler...............................................
Creating Adaptations........................................................................................................................ 261 Adaptation example.......................................................................................................................... 263 Modifying Adaptations...................................................................................................................... 265 Deleting Adaptations..........................................................
Deleting Routing Policies................................................................................................................. 302 Delete Confirmation field descriptions.............................................................................................. 302 Routing Policies field descriptions.................................................................................................... 302 Routing Policy Details field descriptions...................................................
Delete Confirmation page field descriptions..................................................................................... 341 Session Manager Administration page field descriptions................................................................. 341 Session Manager page field descriptions......................................................................................... 344 Saving Global Session Manager Settings....................................................................................
Changing status of an alarm............................................................................................................ 460 Exporting alarms.............................................................................................................................. 460 Filtering alarms................................................................................................................................. 460 Searching for alarms.......................................................
Replica Nodes field descriptions...................................................................................................... 492 Data Replication field descriptions................................................................................................... 494 Managing scheduled jobs......................................................................................................................... 495 Scheduler............................................................................
Chapter 1: Getting started Introduction This book provides information on administration, ongoing management of Avaya Aura ™ Session Manager and includes procedures for • Using System Manager Common Console • Creating user accounts • Administering routing for Session Manager and various SIP entities • Configuring, and monitoring Session Manager instances Required skills and knowledge The audience is expected to have some experience installing Avaya products and be able to perform administration procedures
Getting started Manage groups, roles and assign roles to users. - Synchronize and Import Synchronize users with the enterprise directory, import users from file. - User Management Manage users, public contact lists, shared user resources, system level presence access control lists. • Under Elements - Application Management Manage application instances and application certificates - Communication Manager Manage Communication Manager objects such as Call Center, Call Coverage, Endpoints and others.
Log on to System Manager - Events Manage alarms, view and harvest logs generated by System Manager and other components of System Manager. - Licenses View and configure licenses for individual components of Avaya Aura Unified Communication System. - Replication Track data replication nodes, repair replication nodes. - Scheduler Schedule, track, cancel, update and delete jobs. - Security Manage Security Certificates. - Templates Manage Templates for Communication Manager and Messaging System objects.
Getting started 3. In the Password field, enter the password. 4. Click Log On. If your user name and password: • Match an authorized System Manager user account, the System Manager home page appears with the System Manager version_number. The System Manager home page displays a navigation menu. This menu provides access to shared services with which you can perform various operations supported by System Manager. The tasks you can perform depends on your user role.
Password and security policies for users with username admin Password and security policies for users with username admin Password aging policy enforcement Note: All password policies are applicable ONLY for users with the log-on name “admin”.
Getting started • Passwords must have a total character length from 6 to 25. Default is eight. • Passwords are not required to have a minimum character type; however, the default is one lower- and upper case character, one numeric character, and one special character, such as exclamation mark (!). The sum cannot exceed the minimum total length.
Password and security policies for users with username admin Editing password policies About this task Administrators can edit the password settings through this procedure. Procedure 1. On the System Manager console, under Services, click UCM Services. 2. Click Security > Policies in the left navigation pane. 3. In the Password Policy section, click Edit. 4. Edit the required fields on the Password Policy page. 5. Click Save. Click Cancel to undo your changes and return to the previous page.
Getting started 5. Click Save. Related topics: Session Properties field descriptions on page 22 Security settings System Manager provides a customizable logon banner that appears when a user logs on to the system. The customizable banner is intended for use by customers with security policies that require network equipment to display a specific message to users when they log on. Editing the login warning banner Procedure 1. On the System Manager console, under Services, click UCM Services. 2.
Password and security policies for users with username admin Name Description Enable expired password change Select this check box if you want to allow users to change password after it expires. Expiration period Specifies the maximum allowable days to maintain the password. Default value is 90. You can enter values from 1 to 365. Expiration warning Sends a warning to the user if the password is about to expire. You can type in any value from 1 to 15. The default value is 7.
Getting started Name Description Minimum by character Type: Special case Minimum number of special characters required in the password. Default value is 1. Lockout section Name Description Lockout Select this check box if you want to enforce lockout after failed login attempts. Consecutive Invalid Login Attempts Number of failed attempts before lockout. You can set values from 1 to 20 attempts. Default value is 3.
SIP Application Server Button Description Save Saves your entries in the Session Properties page. Cancel Cancels your entries and takes you to the previous page. SIP Application Server Overview of SIP Application Server The SIP Application Server (SIP A/S) is a scalable, highly available and high-performance server for the development and deployment of real-time, multimedia, presence-enabled IP communications applications.
Getting started SIP A/S Connection Details field descriptions Name Description Primary Hostname The name of the machine hosting the primary Management Server of the SIP Application Server cluster to which you are connecting. This is mandatory. Primary Port The administration port of the primary Management Server. This is mandatory. Backup Hostname The name of the machine hosting the backup Management Server of the SIP Application Server cluster to which you are connecting.
SIP Application Server Viewing Service Director Statistics Procedure 1. On the SIP Application Server Management Console, click Monitoring > Statistics > Service Directors. The Statistics: Service Directors page opens showing details of the listed Service Director. 2. Select the Service Director instance and click View. The Service Director Statistics page opens where you can view statistics for the selected Service Director instance.
Getting started Name Description • TESTING: The Service Director is in testing mode. • HALTED: The Service Director is stopped. • HALTING: The Service Director is stopping. • DISABLED: The Service Director is disabled but can still receive configuration. • BOOTERROR: The Service Director has encountered an error during start-up. Restart Req? Indicates whether the Service Director requires a restart.
SIP Application Server Viewing Service Host Instance Statistics Procedure 1. On the SIP Application Server Management Console, click Monitoring > Statistics > Service Hosts. The Statistics: Service Hosts page opens showing the list of Service Hosts. 2. In the section Service Host Instance Statistics, select a Service Host instance and click View. The Service Host Statistics page opens where you can view statistics for the selected Service Host instance. 3.
Getting started Name Description • RESTARTING: The Service Host is rebooting from a previously up state and will soon become available. • STARTING: The Service Host is starting up from a down state and will soon become available. • TESTING: The Service Host is in testing mode. • HALTED: The Service Host is stopped. • HALTING: The Service Host is stopping. • DISABLED: The Service Host is disabled but can still receive configuration. • BOOTERROR: The Service Host has encountered an error during start-up.
SIP Application Server Free Physical Memory (Mb) The amount of free physical memory available on the Service Host hardware platform. Container Sip Application Sessions The number of SIP application sessions currently being processed by the Service Host. This equals the sum of the number of sessions which represent subscriptions from endpoints and the number of currently active calls handled by the Session Manager.
Getting started 30 Name Description Total Responses In The total number of SIP responses received by the Service Host. Total Responses Out The total number of SIP responses sent by the Service Host. Transaction Quantity The total number of transactions that have taken place through the Service Host. Administering Avaya Aura ® Session Manager Comments? infodev@avaya.
Chapter 2: Synchronizing Communication Manager and messaging data with System Manager Introduction This chapter explains how to use Communication System Manager feature to synchronize Communication Manager station data to the System Manager database. The system automatically connects to System Manager and Communication Manager in the core and synchronizes provisioning data in the System Manager database with each managed Communication Manager system.
Synchronizing Communication Manager and messaging data with System Manager 5. Click Commit . When you add an application entity through RTS (Runtime Topology Service), it in turn starts a synchronization job in the background to bring all the relevant data from the application instances to the Communication System Management database.
Initializing Synchronization console by accessing Scheduler under Services in the System Manager console or the log files on the Communication System Management server. Initializing Synchronization Procedure 1. On the System Manager console, under Elements, click Inventory. 2. Click Synchronization > Communication System in the left navigation pane. 3. Select the Communication Managers you want to synchronize. 4. Select Initialize data for selected devices. 5.
Synchronizing Communication Manager and messaging data with System Manager 34 Name Description Name Displays the name of the application instance. Node Displays the node on which the application runs. Type Displays the type of the application to which the instance belongs. You can view this field only if you access the Manage Elements page through the Inventory menu. Version Displays the version of the application instance.
Application Details field descriptions Button Description Filter: Disable Hides the column filter fields. This is a toggle button. Filter: Apply Filters application instances based on the filter criteria. Select: All Selects all the application instances in the table. Select: None Clears the selection for the users that you have selected. Refresh Refreshes the application instance information in the table.
Synchronizing Communication Manager and messaging data with System Manager Name Description Protocol Displays the protocol associated with the corresponding port. Description Displays a brief description about the port. Button Description New Displays fields in the Port section that you can use to add a port. Edit Displays fields in the Port section with port information. You can modify the port details in the port mode. Delete Deletes the selected configured port.
Application Details field descriptions Name Description Host Displays the name of the host on which the application instance is running. Port Displays the port on which the application instance is running. Order Displays the order in which the access points are accessed. Button Description New Displays fields in the Access Point section that you can use to add port details. Edit Displays fields in the Access Point section that allows you to modify the selected port details.
Synchronizing Communication Manager and messaging data with System Manager Button Description Note: This button is visible only when you click Add and Edit in the Access Point section. Cancel Cancels the operation of creating or editing an access point and hides the fields that you use to enter or modify the access point information. Note: This button is available only when you click Add and Edit in the Access Point section.
Application Details field descriptions Name Description Port The port on which the service provided by the application instance is running. The default SSH port is 5022. Alternate IP Address Alternate IP address of the application instance. This is the IP address of the standby server in case of duplex servers. RSA SSH Fingerprint (Primary IP) The RSA SSH key of the Communication Manager Server. In case of Duplex servers, RSA SSH Key is the key of the Active server.
Synchronizing Communication Manager and messaging data with System Manager Name Description Secured LDAP Connection Use this check box to specify whether Secure LDAP connection is to be used. Select this check box to use secure LDAP connection, else LDAP will be used. Port Displays the port on which the LDAP or secure LDAP service provided by the application instance is running. For LDAP the port is 389 and for secure LDAP the port is 636. Location Displays the location of the application instance.
Application Details field descriptions Button Description Assign Applications Opens the Assign Applications page. Use the page to assign an application instance to another application instance. Unassign Applications Removes an assigned application. Button Description Commit Creates or modifies an instance by saving the instance information to the database. Note: This button is visible only when you click New and Edit on the Application Management page.
Synchronizing Communication Manager and messaging data with System Manager 42 Administering Avaya Aura ® Session Manager Comments? infodev@avaya.
Chapter 3: Managing Security Introduction Trust Management provisions certificates to applications enabling them to have a secure interelement communication. It provides Identity and Trusted (root) certificates with which mutually authenticated TLS sessions can be established. For administering third-party trusted certificates for Session Manager, a "Session Manager" application needs to be added for a specific Session Manager or Branch Session Manager instance.
Managing Security 4. Click Generate. The password field displays the generated password. 5. Click Commit. Note: When you click Commit, the time displayed next to the Time remaining label is updated by the value selected in the Password expires in field. Adding a Session Manager application Procedure 1. On the System Manager console, under Elements, click Inventory. 2. Click Inventory > Manage Elements in the left navigation pane. 3.
Adding trusted certificates Procedure 1. On the System Manager console, under Elements, click Inventory. 2. Click Inventory > Manage Elements in the left navigation pane. 3. On the Manage Elements page , select a Session Manager instance and click More Actions > Configure Trusted Certificates. 4. On the Trusted Certificates page, click View. Result The View Trust Certificate page displays the details of the selected certificate.
Managing Security iii. Click Commit. • To import certificates from a file (in .cer format): i. Click Import from file . ii. Enter the name of the file. You can also click Browse to select a file. iii. Click Retrieve Certificate. iv. Click Commit. • To import certificates in the PEM format: i. Locate the PEM certificate. ii. Open the certificate in the Notepad application. iii. Select all the contents in the file. iv. Perform a copy operation. v. Click Import as PEM Certificate . vi.
Removing trusted certificates 3. On the Manage Elements page , select a Session Manager instance and click More Actions > Configure Trusted Certificates. 4. Select SM_SECURITY_MODULE and click Export to save it. Removing trusted certificates Procedure 1. On the System Manager console, under Elements, click Inventory. 2. Click Inventory > Manage Elements in the left navigation pane. 3. On the Manage Elements page , select a Session Manager instance and click More Actions > Configure Trusted Certificates.
Managing Security Viewing identity certificates Procedure 1. On the System Manager console, under Elements, click Inventory. 2. Click Inventory > Manage Elements in the left navigation pane. 3. On the Manage Elements page , select a Session Manager instance and click More Actions > Configure Identity Certificates. 4. On the Identity Certificates page, click View. Result The Identity Certificate page displays the identity certificates.
Manage Elements field descriptions Manage Elements field descriptions Use this page to view the create, edit, view, and delete instances of the application. Name Description Name Displays the name of the application instance. Node Displays the node on which the application runs. Type Displays the type of the application to which the instance belongs. You can view this field only if you access the Manage Elements page through the Inventory menu.
Managing Security Button Description More Actions > Import Opens the Import Applications page. Use this page to bulk import application data from a valid xml file. Filter: Enable Displays fields under select columns that you can use to set filter criteria. This is a toggle button. Filter: Disable Hides the column filter fields. This is a toggle button. Filter: Apply Filters application instances based on the filter criteria. Select: All Selects all the application instances in the table.
Application Details field descriptions Port Name Description Name Displays the name of the port. Port Displays the port on which the application instance is running. Protocol Displays the protocol associated with the corresponding port. Description Displays a brief description about the port. Button Description New Displays fields in the Port section that you can use to add a port. Edit Displays fields in the Port section with port information.
Managing Security Name Description • GUI: Use this option to create any GUI access point. • Other Protocol Displays the protocol that the application instance supports to communicate with other communication devices. Host Displays the name of the host on which the application instance is running. Port Displays the port on which the application instance is running. Order Displays the order in which the access points are accessed.
Application Details field descriptions Name Description Port Displays the port on which the application instance is running. Order Displays the order in which the access points are accessed. Button Description Save Saves the access point details. Note: This button is visible only when you click Add and Edit in the Access Point section. Cancel Cancels the operation of creating or editing an access point and hides the fields that you use to enter or modify the access point information.
Managing Security Name Description instance. This field is not required for ASG login. Is SSH Connection Use this check box to specify whether the SSH connection should be used to connect to the application instance. By default this is selected. If you clear the check box, the connection with the application instance is made using Telnet. Port The port on which the service provided by the application instance is running. The default SSH port is 5022.
Application Details field descriptions Name Description Messaging Type Displays the type of the Messaging box. The following are the types of messaging: • MM: for Modular Messaging systems • CMM: for Communication Manager Embedded Messaging systems Version Displays the version of the Messaging Box. Supported versions are 5.0 and above. Secured LDAP Connection Use this check box to specify whether Secure LDAP connection is to be used.
Managing Security Assign Applications Name Description Name Displays the name of the application instance. Type Displays the type of application. Description Displays a brief description about the application instance. Button Description Assign Applications Opens the Assign Applications page. Use the page to assign an application instance to another application instance. Unassign Applications Removes an assigned application.
Add Trusted Certificate field descriptions Button Description View Opens the View Trust Certificate page. Use this page to view the certificate details. Add Opens the Adds Trusted Certificate page. use this page to import certificates from the selected resource. Remove Removes the selected certificate from the list of trusted certificates. Exports Exports the selected certificate from the list of trusted certificates.
Managing Security The page displays the following fields when you select the Import from existing option. Name Description Certificate Name Specifies the fully qualified domain name of the certificate. Subject Name Specifies the fully qualified domain name of the certificate holder. Valid To Specifies the date until which the certificate is valid. Filter: Enable Displays fields under select columns that you can use to set filter criteria. This is a toggle button.
View Trust Certificate field descriptions Name Description Valid To Specifies the date and time until which the certificate is valid. Key Size Specifies the size of the key in bits for encryption. Issuer Name Specifies the name of the issuer of the certificate. Finger Print Specifies the finger print that authenticates the certificate. The page displays these fields when you select the Import using TLS option.
Managing Security Name Description Issuer Name Specifies the name of the issuer of the certificate. Finger Print Specifies the finger print that authenticates the certificate. Button Description Done Closes the page and takes you back to the Trusted Certificates page. Related topics: Viewing trusted certificates Delete Trusted Certificate Confirmation field descriptions Use this page to delete a trusted certificate from the list of trusted certificate maintained by the application instance.
Identity Certificates field descriptions Name Description Service Name Specifies the name of the service that uses the identity certificate. Common Name Specifies the common name to identify the service. Valid To Specifies the date until which the certificate is valid. Service Description A brief description about the service. Button Description Replace Opens the Replace Identity Certificate page. Use this page to replace a selected identity certificate with a new certificate.
Managing Security 62 Administering Avaya Aura ® Session Manager Comments? infodev@avaya.
Chapter 4: Managing Users Introduction This chapter explains adding a user profile for accessing enhanced enterprise call handling facilities using: • application sequencing (with Communication Manager Feature Server and other applications) • modular messaging mailbox • telephone set Following are the pre-administration steps required for adding the Session Manager Profile of a user: 1.
Managing Users See the topic Creating a Communication Manager instance on page 31 for details. • Add the Communication Manager Feature Server as an Application. See the topic Creating an application on page 405 for details. b. Similarly add other Applications to be added in the Application Sequence. 5. Create Application Sequence from existing Applications for specifying “Origination Application Sequence” and “Termination Application Sequence”.
Adding users A user may have more than one Communication Profile. For more information regarding the fields, see the on-line help. Procedure 1. On the System Manager console, under Users, click User Management. 2. In the User Management page, click New. 3. Under Identity tab, enter the user's last name and first name. 4. Enter a description in the Description field. This field is optional. 5. Enter a Login Name name. This is the unique system login name given to the user.
Managing Users The box must be checked in order to associate the user with the selected Communication Manager station settings. Otherwise, leave the box unchecked to create a station automatically . d. Enter the extension that is administered on Communication Manager for the existing or new station in the Extension field. Click Endpoint Editor to modify the CM station data. e. Select a phone template for the use's phone in the Template field.
Managing communication profiles Managing communication profiles Creating a new communication profile Procedure 1. On the System Manager console, under Users, click User Management. 2. Click Manage Users in the left navigation pane. 3. On the User Management page, perform one of the following steps: • If you are creating a new user account, click New. • If you want to add a communication profile to an existing user, select a user and click Edit. 4.
Managing Users • On the User Management page, select a user and click Edit. • On the User Management page, select a user and click View > Edit. 4. On the User Profile Edit page, click the Communication Profile tab. 5. In the Communication Profile section, click a profile. 6. Click Delete. 7. Click Commit. Result When you delete a communication profile, System Manager deletes all the communication addresses associated with the communication profile.
Managing communication profiles Related topics: New User Profile field descriptions on page 82 User Profile Edit field descriptions on page 92 Modifying a communication address of a communication profile Procedure 1. On the System Manager console, under Users, click User Management. 2. Click Manage Users in the left navigation pane. 3. Perform one of the following steps: • On the User Management page, select a user and click Edit. • On the User Management page, select a user and click View > Edit. 4.
Managing Users 4. On the User Profile Edit page, click the Communication Profile tab. 5. In the Communication Profile section, click a communication profile. 6. In the Communication Address section, select a communication address from the table. 7. Click Delete. 8. Click Commit.
Managing communication profiles • Station Profile: to create an association between a station and a user • Messaging Profile: to create an association between a subscriber mailbox and a user You can add, view, modify, and delete station and messaging profiles. You can go to Station or Subscriber Management to modify any of the station or subscriber fields that are not available through User Profile Management.
Managing Users Note: Select the Delete Messaging on Unassign of Subscriber from User or Delete User check box if you want to delete the subscriber mailbox from the communication management device after removing the association between the subscriber and the user. 7. Click Commit to add the messaging profile or, click Cancel to return to return to the previous page. The field names that are marked with an asterisk (*) are mandatory fields.
Managing communication profiles Removing association between a subscriber mailbox and a user Before you begin The Delete Subscriber on Unassign of Subscriber from User or Delete User check box is clear while associating a mailbox with a user. Procedure 1. On the System Manager console, under Users, click User Management. 2. Click Manage Users in the left navigation pane. 3. On the User Management page, select a user and perform one of the following steps: • Click Edit. • Click View > Edit. 4.
Managing Users 2. Click Manage Users in the left navigation pane. 3. On the User Management page, select a user and perform one of the following steps: • Click Edit. • Click View > Edit. 4. On the User Profile Edit page, click the Communication Profile tab. 5. In the Messaging Profile tab, clear the check box next to the Messaging Profile label. 6. Click Commit . Note: You can delete only those subscribers that are associated with a user through User Management.
Managing communication profiles 7. Click Commit to add the endpoint profile. The field names that are marked with asterisk (*) are mandatory fields. You must enter valid information in these fields for the successful creation of the endpoint profile. If you want to cancel the action and return to the previous page, click Cancel. Through User Management, you can create or add endpoint.
Managing Users Removing association between an endpoint and a user Before you begin Ensure that you have not selected the Delete Endpoint on Unassign of Endpoint from User or Delete User check box while associating a station with a user. Procedure 1. On the System Manager console, under Users, click User Management. 2. Click Manage Users in the left navigation pane. 3. On the User Management page, select a user and perform one of the following steps: • Click Edit. • Click View > Edit. 4.
Modifying user accounts • Click Edit. • Click View > Edit. 4. On the User Profile Edit page, click the Communication Profile tab. 5. In the Endpoint Profile , clear the check box next to the Endpoint Profile label. 6. Click Commit . Note: You can delete only those endpoints that are associated with a user through User Management. You can delete non-user associated endpoints through endpoint management.
Managing Users Related topics: User Profile Edit field descriptions on page 92 Viewing details of a user Before you begin The permission to view the details of the selected user. Procedure 1. On the System Manager console, under Users, click User Management. 2. Click Manage Users in the left navigation pane. 3. On the User Management page, select a user. 4. Click View to view details of the selected user account. You can view details of only one user account at a time.
Creating duplicate users Note: This operation marks the deleted users as deleted and stores them in the database in a list of deleted users. However, the deleted users can be permanently deleted. You cannot delete users with the login name “admin” through user management. Creating duplicate users Use this capability to create a new user account by copying information from an existing user account.
Managing Users You may apply one or more filters to view users that match the filter criteria. Procedure 1. On the System Manager console, under Users, click User Management. 2. Click Manage Users in the left navigation pane. 3. On the User Management page, click Filter: Enable. You can find the button at the upper-right corner of the table displaying users. 4.
Viewing deleted users 4. In the Criteria section, do the following: a. Select the search criterion from the first field. b. Select the operator from the second field. c. Enter the search value in the third field. If you want to add another search condition, click + and repeat substeps a through c listed in Step 3. If you want to delete a search condition, click - next to the search condition. This button is available only if there is more than one search condition. 5. Click Search.
Managing Users Procedure 1. On the System Manager console, under Users, click User Management. 2. Click Manage Users in the left navigation pane. 3. On the User Management page, click More Actions > Show Deleted Users. 4. On the Deleted Users page, select the user you want to restore, and click Restore. 5. On the User Restore Confirmation page, click Restore. 6. On the User Profile Edit page, enter a new password in the Password field. 7.
New User Profile field descriptions Name Description takes the form of username@domain. It is used to create the user's primary handle. You cannot edit this field for users with the login name “admin”. Authentication Type Displays the authentication type that defines how the system performs user's authentication. The options are: • Enterprise: User's login is authenticated by the enterprise. • Basic: User's login is authenticated by an Avaya Authentication Service.
Managing Users Name Description Postal Code Displays the postal code used by postal services to route mail to a destination. In United States this is Zip code. Province Displays the full name of the province. Country Displays the name of the country. Button Description New Opens the Add Address page. Use the page to add the address details. Edit Allows you to modify the address. Delete Deletes the selected address.
New User Profile field descriptions Name Description Name Displays the name of the communication profile for the user. Default Displays the profile that is made default is the active profile. There can be only one active profile at a time. Communication Profile tab — Communication Address section Use this section to create, modify and delete one or more communication addresses for the user. Name Description Type Displays the type of the handle. Handle A unique communication address of the user.
Managing Users Name Description • Microsoft Exchange: Signifies that the handle is an e-mail address and supports communication with Microsoft SMTP server. • Lotus Notes: Indicates that the handle is for Lotus Notes and domino calender. • IBM Sametime: Indicates that the handle is for IBM Sametime. • Jabber: Indicates that the handle supports Extensible Messaging and Presence Protocol (XMPP)-based communication with the Jabber service.
New User Profile field descriptions Name Description Primary Session Manager Select the Session Manager instance that should be used as the home server for the currently displayed Communication Profile. As a home server, the selected primary Session Manager instance will be used as the default access point for connecting devices associated with the Communication Profile to the Aura network. A selection is required.
Managing Users Name Description LSP that is resident with the Branch Session Manager. Home Location A Home Location can be specified to support mobility for the currently displayed user. This is used by Session Manager specially in cases when the ip-address of the calling phone does not match any IP Address Pattern of any of the location. Communication Profile tab — Endpoint Profile Note: You may see these fields only if an endpoint profile can be configured for the user .
New User Profile field descriptions Name/Button Description Voice Mail Number The voice mail number of the endpoint you want to associate. Delete Endpoint on Unassign of Endpoint Use this check box to specify whether you from User or Delete User want to delete the endpoint from the Communication Manager device when you remove the association between the endpoint and the user or when you delete the user.
Managing Users Name Description header row to select all the roles assigned to the user account. Name The name of the role. Description A brief description about the role. Button Description Assign Roles Opens the Assign Role page that you can use to assign the roles to the user account. Unassign Roles Removes the selected role from the list of roles associated with the user account. Membership tab — Group Membership section Name Description check box Use this check box to select the group.
New User Profile field descriptions Name Description Speed Dial The value specifies whether the speed dial is set for the contact or not. Speed Dial Entry The reduced number that represents the speed dial number. Presence Buddy The value specifies whether you can monitor the presence information of the contact or not. A false value indicates that you can not track the presence of the contact. Button Description Edit Opens the Edit Contact List Member page.
Managing Users Button Description New Opens the New Private Contact page. Use this page to add a new private contact. Delete Deletes the selected contacts. Filter: Disable Hides the column filter fields without resetting the filter criteria. This is a toggle button. Filter: Enable Displays text fields under the columns that you can use to set the filter criteria. This is a toggle button. Filter: Apply Filters contacts based on the filter criteria.
User Profile Edit field descriptions The User Profile Edit page has the following four tabs: • Identity • Communication Profile • Membership • Contacts Identity tab — Identity section Name Description Last Name Displays the last name of the user. First Name Displays the first name of the user. Middle Name Displays the middle name of the user, if any. Description Displays a brief description about the user.
Managing Users Name Description that cannot handle localized text, for example, some endpoints. Honorific Displays the personal title for address a user. This is typically a social title and not the work title. Language Preference Displays the user's preferred written or spoken language. Time Zone Displays the preferred time zone of the user. Identity tab — Address section Name Description Select check box Use this check box to select the address.
User Profile Edit field descriptions Communication Profile tab — Communication Profile section Use this section to create, modify and delete a communication profile for the user. Each communication profile may contain one or more communication addresses for a user. Name Description Communication Profile Password Specifies the password for the communication profile. Option button Use this button to view the details of the selected communication profile.
Managing Users Button Description New Displays the fields for adding a new communication address. Edit Use this button to edit the information of a selected communication address. Delete Deletes the selected communication address. The page displays the following fields when you click New or Edit in the Communication Address section. Name Description Type Displays the type of the handle. The different types of handles are: • Avaya SIP: Indicates that the handle supports SIP-based communication.
User Profile Edit field descriptions Name Description • Other SIP: Indicates that the handle supports other SIP-based communication than the ones mentioned above. • Other XMPP: Indicates that the handle supports other XMPP-based communication than the ones mentioned above. Fully Qualified Address Displays the fully qualified domain name or uniform resource identifier. The address can be an e-mail address, IM user, or of a communication device using which user can send or receive messages.
Managing Users Name Description Origination Application Sequence Select an Application Sequence that will be invoked when calls are routed from this user. A selection is optional. Note: If both an origination and a termination application sequence are specified and each contains a Communication Manager application, the Communication Manager should be the same in both sequences. Termination Application Sequence Select an Application Sequence that will be invoked when calls are routed to this user.
User Profile Edit field descriptions Name Description phone does not match any IP Address Pattern of any of the location. Communication Profile tab — Endpoint Profile Note: The page displays the following fields if an endpoint profile exists for the user. Name/Button Description System Displays the Communication Manager on which you need to add the endpoint. Use Existing Endpoints Select this check box if you want to use an existing endpoint extension to associate with this profile.
Managing Users Communication Profile tab — Messaging Profile section Note: The page displays the following fields if a messaging profile exists for the user. Name Description System Displays the Messaging System on which you need to add the subscriber. Template Displays the system-defined or user-defined template you want to associate with the subscriber.
User Profile Edit field descriptions Membership tab — Group Membership section Name Description Select check box Use this check box to select the group. Name Displays the name of the group. Type Displays the group type based on the resources. Hierarchy Displays the position of the group in the hierarchy. Description Displays a brief description about the group. Button Description Add To group Opens the Assign Groups page that you can use to add the user to a group.
Managing Users Button Description Edit Opens the Edit Contact List Member page. Use this page to modify the information of the selected contact. Add Opens the Attach Contacts page. Use this page to select one or more contacts from the list of contacts. Remove Removes one or more contacts from the list of the associated contacts. Filter: Disable Hides the column filter fields without resetting the filter criteria. This is a toggle button.
User Profile View field descriptions Button Description Filter: Enable Displays text fields under the columns that you can use to set the filter criteria. This is a toggle button. Filter: Apply Filters contacts based on the filter criteria. Common buttons Button Description Commit Modifies the user account. Note: While restoring a deleted user, use this button to restore a deleted user.
Managing Users Name Description Middle Name Displays the middle name of the user. Description A brief description of the user. Status Displays the login status of the user. Update Time Displays the time when the user details were last modified. Login Name Displays the unique system login name given to the user. It takes the form of username@domain. You can use the login name to create the user's primary handle. You cannot edit the login name for users with the login name “admin”.
User Profile View field descriptions Identity tab — Address section Name Description Name Displays the unique label that identifies the address. Address Type Displays the type of the address. Types of addresses are: • Office • Home Street Displays the name of the street. Locality Name Displays the name of the city or town. Postal Code Displays the postal code used by postal services to route mail to a destination. In United States this is Zip code.
Managing Users Communication Profile tab — Session Manager section Note: The page displays the following fields if a communication profile of the user exists for the product. Name Description Primary Session Manager Select the Session Manager instance that you want to use as home server for the currently displayed Communication Profile.
User Profile View field descriptions Name Description Manager instances in the Aura Core is lost. If a Branch Session Manager is selected, and the termination and origination application sequences contain a Communication Manager application, sequencing to this application will continue, locally, to the Communication Manager LSP resident with the Branch Session Manager. A selection is optional.
Managing Users Name/Button Description Security Code Displays the security code for authorized access to the endpoint. Port Displays the relevant port for the set type you select. Voice Mail Number Displays the voice mail number of the endpoint you want to associate.
User Profile View field descriptions Membership tab — Group Membership section Name Description Name Displays the name of the group. Type Displays the group type based on the resources. Hierarchy Displays the position of the group in the hierarchy. Description Displays a brief description about the group. Contacts tab — Default Contact List section Name Description Description Displays a brief description of the contact list.
Managing Users Button Description Filter: Apply Filters contacts based on the filter criteria. Contacts tab — Private Contacts section Use this section to add new private contacts, modify and deletes existing contacts. Name Description Last Name Displays the last name of the private contact. First Name Displays the first name of the private contact. Display Name Display name of the private contact. Contact Address Displays the address of the private contact.
User Delete Confirmation field descriptions User Delete Confirmation field descriptions Use this page to delete an user account. Name Description Login Name Displays the login name of the user you want to delete. Status Indicates whether the user status is currently online or offline. Name Displays the localized display name of a user. It is typically the localized full name. Last login Displays the date and time of last successful login on to System Manager.
Managing Users • Update and merge the user attributes data from the imported file to the existing data. • Delete the user records from the database that match the records in the input XML file. See the “XML Schema Definition for bulk importing users” and “Sample XML for bulk importing users” sections in the “List of XML Schema Definitions and Sample XMLs for bulk Import” topic for details on the user imported attributes.
Managing bulk importing and exporting Communication Manager Synchronization is started, the current records being processed will fail. After the synchronization is complete, the remaining bulk import records will be processed successfully. You have to re-import the records that have failed during synchronization. Scheduling a user import job Procedure 1. On the System Manager console, under Services, click Bulk Import and Export. 2. Click Import > User Management > Users. 3.
Managing Users Aborting a user import job on first error About this task The user import process may encounter errors at the time of importing users. Use this feature to abort the user import process on encountering the first error. Procedure 1. On the System Manager console, under Services, click Bulk Import and Export. 2. Click Import > User Management > Users. 3. On the Import Users page, enter the complete path of the file in the Select File field. You can also use the Browse button to select a file.
Managing bulk importing and exporting Deleting an importing job Before you begin You can delete only successful jobs. Procedure 1. On the System Manager console, under Services, click Bulk Import and Export. 2. Click Import > User Management > Users. 3. On the Import Users page, select the job you want to delete from the table in the Manage Job section. 4. Click Delete Job. Viewing a user importing job in Scheduler Procedure 1. On the System Manager console, under Services, click Bulk Import and Export.
Managing Users 4. Click View Job. The Job Detail page displays the details of the selected job.
Managing bulk importing and exporting xs:element name="user" type="tns:xmlUser" minOccurs="0" maxOccurs="unbounded"/> PAGE 118Managing Users minOccurs="0" maxOccurs="unbounded" /> PAGE 119Managing bulk importing and exporting PAGE 120Managing Users
PAGE 121Managing bulk importing and exporting minOccurs="0" maxOccurs="unbounded"/>
Managing Users
Managing bulk importing and exporting enterprise directory entry. If it does not exist, synchronization rules can be used to populate it for other fields e.g. Surname, GivenName, or LoginName. displayNameAscii:The full text name of the user represented in ASCII. It is used to support display (e.g. endpoints) that cannot handle localized text. dn:The distinguished name of the user. The DN is a sequence of relative distinguished names (RDN) connected by commas.
Managing Users userPassword:The encrypted password for this users account.A null password is used when the user is authenticated by the enterprise such as with a separate source such as the enterprise LDAP. commPassword:The encrypted subscriber or communication password with which the user logs can use to authentication with on to any CommProfile SIP and non SIP. This attribute is meant to be a shared across different communication profiles and thus different communication services.
Managing bulk importing and exporting mycommPassword ADMINISTRATOR End-User XML Schema Definition for bulk deleting users
Managing bulk importing and exporting soft jmiller@avaya.com XML Schema Definition for bulk importing elements 5555555 sip username domain.
Managing Users XML Schema Definition for bulk importing endpoint profiles PAGE 139Managing bulk importing and exporting set types, but you can enter for a DCP set with softphone permissions. This changes to the s00000 type when the set registers. --> PAGE 141Managing bulk importing and exporting
Managing Users
Managing bulk importing and exporting
Managing Users
Managing bulk importing and exporting maxOccurs="24" minOccurs="0" /> PAGE 156Managing Users PAGE 157Managing bulk importing and exporting minOccurs="0" /> <
Managing Users >
Managing bulk importing and exporting
Managing Users
Managing bulk importing and exporting PAGE 162Managing Users Sample XML for bulk importing endpoint profiles PAGE 163Managing bulk importing and exporting IP 1 1 10 4 false 1-way english false internal true false
Managing Users none false false true PAGE 167Managing bulk importing and exporting
Managing Users
Managing bulk importing and exporting and call-answer messages from other subscribers. You can choose one of the following: - yes: to allow the subscriber to create, forward, and receive messages. - no: to prevent the subscriber from receiving call-answer messages and to hide the subscriber from the telephone user interface (TUI). The subscriber cannot use the TUI to access the mailbox, and other TUI users cannot address messages to the subscriber.
Managing Users
Managing bulk importing and exporting -->
Managing Users ADMINISTRATOR commProfileSetName00 true PAGE 173Managing bulk importing and exporting Attribute Attribute Description Mandatory/ Optional Validation Constraints when displaying. It will typically be the localized full name. This value may be provisioned from the user’s enterprise directory entry. If it does not exist, synchronization rules can be used to populate it for other fields. For example: Surname, GivenName, or LoginName. displayNameAsci This is the full text name of Optional i the user represented in ASCII. It is used to support display (e.
Managing Users Attribute Attribute Description Mandatory/ Optional Validation Constraints to disable access between login attempts. A running session’s login will not be revocable. Alternatively, the administrator can always modify the password to disable the user from logging in. A true stipulates this is an active user, a false used for a disabled user.
Managing bulk importing and exporting Attribute Attribute Description Mandatory/ Optional loginName This is the unique system Mandatory login name given to the user. It can take the form of username@domain or just username. This may vary across customers. It can be used to help provision default user handles in the CSHandle table. The username is an alphanumeric value that must comply with the userinfo related portion of a URI as described in rfc2396.
Managing Users Attribute 176 Attribute Description Mandatory/ Optional Validation Constraints source Free format text field that Optional identifies the entity that created this user record. The format of this field will be either a IP Address/Port or a name representing an enterprise LDAP or Avaya. User Management will populate the source field with the name of the file. sourceUserKey This is the key of the user Optional from the source system.
Managing bulk importing and exporting Attribute Attribute Description Note: You need to consider Daylight saving time (DST) and summer time adjustments while using the suggested values for timeZone. Typically you have to add one hour to the offset. Note: The following characters cannot be used as is in the xml.
Managing Users Attribute Attribute Description Mandatory/ Optional Validation Constraints (+3:0)Moscow, St.
Managing bulk importing and exporting Attribute Attribute Description Mandatory/ Optional Validation Constraints (+12:0)Fiji, Kamchatka, Marshall Is. (+13:0)Nuku'alofa title This is the job function of a Optional person in their organizational context. userName This is the username Mandatory portion of the loginName field. It is an alphanumeric value that must comply with the userinfo related portion of a URI as described in rfc2396.
Managing Users Attribute Attribute Description Mandatory/ Optional Validation Constraints resident_expert, service_technician, lobby_phone roles This is the text name of a role. This value needs to pre-exist in SMGR DB. Optional address This is the address of the user.
Managing bulk importing and exporting Attribute Attribute Description Mandatory/ Optional Validation Constraints themselves on who can monitor their presence information. There may be several entries in the list for a given presentity, each entry corresponding to one watcher. presenceUserCL Default This is a personal rule that Optional is set by presentities to define how much presence information can be shown to watchers that belong to the user’s contact list.
Managing Users Attribute Attribute description Mandatory/Optional selects “soft”, the user record is not permanently deleted and the user record can be recovered. If the user selects “delete”, all attributes associated with the user and the links to public contacts and shared addresses is permanently deleted. 182 Validation constraints • soft • delete loginName This is the unique system login name assigned to the user in the format of username@domain or username.
Managing bulk importing and exporting Attribute details defined in the Endpoint profile XSD Attribute details defined in the Endpoint profile XSD Attribute Attribute Description Mandator y/ Optional CM Name cmName CM Name as it appears under 'Applications/ Application Management/ Entities Use Existing Extension useExistingExtensio n 'true' if already Optional created extension is to be used. 'false' if available extension is to be used.
Managing Users Attribute Attribute Description Mandator y/ Optional Validation Constraints have a non-IP set. Or, the extension had a non-IP set, and it dissociated. Use x for Administered WithOut Hardware (AWOH) and Computer Telephony (CTI) stations, as well as for SBS Extensions. IP Indicates that there is no hardware associated with the port assignment since the switch was set up, and the administrator expects that the extension would have an IP set.
Managing bulk importing and exporting Attribute Attribute Description Mandator y/ Optional of extensions to which your voice system will route an unanswered call. Validation Constraints 1-2000, time of day table, t1-t999, or blank. Hunt To Station huntToStation The extension the Optional system should hunt to for this telephone when the telephone is busy. A station hunting chain can be created by assigning a hunt-to station to a series of telephones.
Managing Users Attribute Attribute Description Mandator y/ Optional Validation Constraints format (00:00 23:59) for all languages except English, which is displayed in 12-hour format (12:00 a.m. to 11:59 p.m.). unicode: Displays English messages in a 24hour format . If no Unicode file is installed, displays messages in English by default. Personalized Ringing Pattern personalizedRinging Pattern Defines the personalized ringing pattern for the station.
Managing bulk importing and exporting Attribute Attribute Description Mandator y/ Optional either a voice or a data call, and voice conversion, coverage, and forwarding apply as if the call were made to the 1-number. H.323 station extension For 4600 series IP Telephones, enter the corresponding H.323 station. For IP Softphone, enter the corresponding H.323 station. If you enter a value in this field, you can register this station for either a road-warrior or elecommuter/Avaya IP Agent application.
Managing Users Attribute Attribute Description Mandator y/ Optional Validation Constraints stations register with Communication Manager, this list is sent down in the registration confirm message. This allows the IP station to use the IP address of this Survivable Gatekeeper as the call controller of last resort to register with. Available only if the station type is an H.323 station (46xxor 96xx models).
Managing bulk importing and exporting Attribute Attribute Description Mandator y/ Optional Validation Constraints for all analog and IP station types. routing tables. Those strings marked as deny are also denied to these users. Survivable Trunk Destination survivableTrunkDest Optional Designates certain telephones as not being allowed to receive incoming trunk calls when the Media Gateway is in survivable mode.
Managing Users Attribute Attribute Description Mandator y/ Optional Validation Constraints building with the system. • dataOption If a second line on the Optional telephone is administered on the I-2 channel, enter analog. Otherwise, enter data module if applicable or none. Valid entries analog, none. Message Waiting Indicator messageWaitingIndi cator If led or neon, then messageLampExt should be enable otherwise its blank. Valid entries: led, neon, none.
Managing bulk importing and exporting Attribute Attribute Description Mandator y/ Optional Validation Constraints messages that indicate the wakeup calls failed. Enter true if LWC Reception is audix. activeStationRinging Active station Ringing Optional Valid entries: • single • continuous • if-busy-single • silent idleActiveRinging Defines how call rings to the telephone when it is on-hook.
Managing Users Attribute 192 Attribute Description Mandator y/ Optional Validation Constraints switchhookFlash Must be set to true Optional when the Type field is set to H.323 Boolean ignoreRotaryDigits If this field is true, the Optional short switch-hook flash (50 to 150) from a 2500-type set is ignored. Boolean h320Conversion H.320 Conversion — Optional Valid entries are true and false (default).
Managing bulk importing and exporting Attribute Attribute Description Mandator y/ Optional Validation Constraints link is never used by a Basic mode complex H.320 DVC system. Connecting a service link will take several seconds. When the service link is connected, it uses MMI, VC and system timeslot resources. When the service link is disconnected it does not tie up any resources.
Managing Users Attribute Attribute Description Mandator y/ Optional Validation Constraints without having to wait for the service link to disconnect and reestablish. Permanent – Multimedia call center agents and other users who are constantly making or receiving multimedia calls might want to be administered with this service link mode.
Managing bulk importing and exporting Attribute Attribute Description Mandator y/ Optional Validation Constraints telephone set. Enhanced - An Enhanced multimedia complex consists of a BRIconnected multimediaequipped PC and a nonBRIconnected multifunction telephone. mwiServedUserType Controls the auditing Optional or interrogation of a served user’s message waiting indicator (MWI). Valid entries: 1. fp-mwi - Use if the station is a served user of an fp-mwi message center. 2.
Managing Users Attribute Attribute Description Mandator y/ Optional unplugged from one location and moved to a new location without additional Communication Manager administration. Communication Manager automatically associates the extension to the new port. Validation Constraints DCP telephone can be moved anytime without additional administration by unplugging from one location and plugging into a new location. 2.
Managing bulk importing and exporting Attribute Attribute Description Mandator y/ Optional Validation Constraints Communication Manager sets the field to done after the telephone is moved and routine maintenance runs on the DCP telephone. 5. Error - Error is a display-only value. Communication Manager sets the field to error, after routine maintenance runs on the DCP telephone, when a non-serialized telephone is set as a movable telephone.
Managing Users Attribute Attribute Description Mandator y/ Optional Validation Constraints Manager to send the CESID information supplied by the IP Softphone to the PSAP. 4. Option - Enter option to allow the user to select the option (extension, block, or cesid) that the user selected during registration and the IP Softphone reported. emergencyLocation Ext 198 This field allows the Optional system to properly identify the location of a caller who dials a 911 emergency call from this station.
Managing bulk importing and exporting Attribute Attribute Description Mandator y/ Optional Validation Constraints Station screen is the same as the Emergency Location Extension field in the IP Address Mapping screen, the feature sends the extension to the Public Safety Answering Point (PSAP).
Managing Users Attribute Attribute Description Mandator y/ Optional Validation Constraints LoginID for ISDN Display . Does not apply to SCCAN wireless telephones, or to extensions administered as type h.323. precedenceCallWaiti Activates or ng deactivates Precedence Call Waiting for this station. 200 Optional autoSelectAnyIdleAp Enables or disables Optional pearance automatic selection of any idle appearance for transferred or conferenced calls.
Managing bulk importing and exporting Attribute autoAnswer Attribute Description Mandator y/ Optional In EAS Optional environments, the auto answer setting for the Agent LoginID can override a station’s setting when an agent logs in. Validation Constraints Valid entries: 1. all: All ACD and non-ACD calls terminated to an idle station cut through immediately. Does not allow automatic hands-free answer for intercom calls. With non-ACD calls, the set is also rung while the call is cut through.
Managing Users Attribute Attribute Description Mandator y/ Optional Validation Constraints station is active on an ACD call and a non-ACD call arrives, the Agent receives call-waiting tone. 3. none: All calls terminated to this station receive an audible ringing treatment. 4. icom: Allows a telephone user to answer an intercom call from the same intercom group without pressing the intercom button.
Managing bulk importing and exporting Attribute Attribute Description Mandator y/ Optional and there is an incoming call. callWaitingIndication enable/disable call waiting for this station Validation Constraints false - The Alerting Appearance Preference is set and the user connects to the ringing call appearance.
Managing Users Attribute Attribute Description Mandator y/ Optional Validation Constraints is used for incoming priority calls and outgoing call originations. adjunctSupervision Enable / Disable adjunct Supervision. Optional Valid entries: 1. true: Analog disconnect signal is sent automatically to the port after a call terminates. Analog devices (such as answering machines and speakerphones) use this signal to turn the devices off after a call terminates. 2.
Managing bulk importing and exporting Attribute Attribute Description Mandator y/ Optional Validation Constraints "Presentation Allowed." 2. n: No CPN information is sent for the call 3. r: Outgoing nonDCS network calls from the station will deliver the Calling Party Number information as "Presentation Restricted.
Managing Users Attribute Attribute Description Mandator y/ Optional Validation Constraints (Optional Features) screen. This field affects the telephone display on calls that originated from a station with Client Room Class of Service. Note: For stations with an audix station type, AUDIX Voice Power ports, or ports for any other type of messaging that needs display information, Display Client Redirection must be enabled.
Managing bulk importing and exporting Attribute Attribute Description Mandator y/ Optional Validation Constraints remains on the button last used for a call. 2. false: The line selection on an on-hook station with no alerting calls can be moved to a different line button, which might be serving a different extension. coverageAfterForwa rding Whether an unanswered forwarded call is provided coverage treatment.
Managing Users Attribute 208 Attribute Description Mandator y/ Optional Validation Constraints building This is field of Site Data Optional headset This is field of Site Data Optional speaker This is field of Site Data Optional mounting This is field of Site Data Optional Valid values d, w. cordLength This is field of Site Data Optional Valid range from 0 to 99. setColor This is field of Site Data Optional abbrList This is complex type for Station Abbreviated Dialing Data fields.
Managing bulk importing and exporting Attribute Attribute Description Mandator y/ Optional Validation Constraints data6 This is field of button Optional data. stationDataModule This is complex type for Station Data module. dataExtension This is field of Station Mandatory Data module. name This is field of Station Optional Data module. Max length 29 Class of restriction cor This is field of Station Mandatory Data module. Valid range from 0 to 995.
Managing Users Attribute Attribute Description Mandator y/ Optional nativeName This is complex type of Native Name Data. locale This is field of Native Mandatory Name Data. Name This is field of Native Mandatory Name Data.
Managing bulk importing and exporting Attribute Attribute Description Mandator y/ Optional Validation Constraints Community ID communityID Specifies the default Optional community ID for the subscriber. Community IDs are used to control message sending and receiving among groups of subscribers. Email Handle emailHandle Specifies the name that appears before the machine name and domain in the subscriber's e-mail address.
Managing Users Attribute 212 Attribute Description Mandator y/ Optional mmSpecific This is complex type for Messaging specific fields data. numericAddress This is field of Optional Messaging specific data. Specifies a unique address in the voice mail network. The numeric address can be from 1 to 50 digits and can contain the Mailbox Number. pbxExtension This is field of Messaging specific data. The primary telephone extension of the subscriber.
Managing bulk importing and exporting Attribute expirePassword mailBoxLocked Attribute Description This is field of Messaging specific data. Specifies whether your password expires or not. Mandator y/ Optional Optional Validation Constraints You can choose one of the following: • yes: for password to expire • no: if you do not want your password to expire This is field of Optional Messaging specific data. Specifies whether you want your mailbox to be locked.
Managing Users Attribute tuiMessageOrder Attribute Description Mandator y/ Optional This is field of Optional Messaging specific data. Specifies the order in which the subscriber hears the voice messages. Validation Constraints You can choose one of the following: • urgent first then newest: to direct the system to play any messages marked as urgent prior to playing non-urgent messages. Both the urgent and nonurgent messages are played in the reverse order of how they were received.
Managing bulk importing and exporting Attribute Attribute Description Mandator y/ Optional Specifies the intercom paging settings for a subscriber. Validation Constraints paging for this subscriber. • paging is manual: if the subscriber can modify, with Subscriber Options or the TUI, the setting that allows callers to page the subscriber. • paging is automatic: if the TUI automatically allows callers to page the subscriber. voiceMailEnabled Optional This is field of Messaging specific data.
Managing Users Attribute 216 Attribute Description Mandator y/ Optional Validation Constraints miscellaneous1 This is field of Messaging specific data. Specifies additional, useful information about a subscriber. Entries in this field are for convenience and are not used by the messaging system. Max length 51 miscellaneous2 This is field of Messaging specific data. Specifies additional, useful information about a subscriber.
Managing bulk importing and exporting Attribute cmmSpecific Attribute Description Mandator y/ Optional This is field of Optional Messaging specific data. Specifies the number of the switch on which this subscriber's extension is administered. accountCode This is field of CMM Optional data. Specifies the Subscriber Account Code. The Subscriber Account Code is used to create Call Detail Records on the switch for calls placed by the voice ports.
Managing Users Attribute Attribute Description Mandator y/ Optional of Messaging feature. 218 Validation Constraints or leave this field blank. miscellaneous1 This is field of CMM data. Specifies additional, useful information about a subscriber. Entries in this field are for convenience and are not used by the messaging system. Optional Max length 11 Miscellaneous2 This is field of CMM data. Specifies additional, useful information about a subscriber.
Managing bulk importing and exporting Attribute details defined in the Session Manager communication profile XSD Attribute Attribute Description Mandator y/ Optional Primary Session Manager primarySM Specify the name of Mandatory the Session Manager instance that should be used as the home server for a Communication Profile.
Managing Users Attribute Attribute Description Mandator y/ Optional Validation Constraints are specified and each contains a CM application, the CM should be the same in both sequences. 220 Termination Application Sequence terminationAppSequ ence Specify an Optional Application Sequence that will be invoked when calls are routed to this user. A selection is optional.
Managing bulk importing and exporting Attribute Attribute Description Mandator y/ Optional Validation Constraints Session Manager. A selection is optional. Note: if a termination or origination application sequence contains a CM application, the CM associated with the application must be the main CM for the CM LSP that is resident with the Branch Session Manager.
Managing Users File Selection Name Description Select File The path and name of the XML file from which you want to import the users. Button Description Browse Opens a dialog box that you can use to select the file from which you want to import the users. General Name Description Select Error Configuration The options are: • Abort on first error: Aborts importing the user records when the import user operation encounters the first error in the import file containing the user records.
Managing bulk importing and exporting Name Description lists, contact lists, and so on. With this option, you can replace a user and the associated data of the user. • Merge: Imports the user data at an even greater degree of granularity. Using this option you can simultaneously perform both add and update operation of users. For example, add a contact to a contact list and update a last name. • Delete: Deletes the user records from the database that match the records in the input XML file.
Managing Users Button Description Import Imports or schedules the import operation based on the option you selected. Manage Job Name Description Select check box Use this check box to select a job. Scheduled Time The time and date of scheduling the job. Status The current status of the job. The following are the different status of a job: 1. PENDING EXECUTION: The job is in queue. 2. RUNNING: The job execution is in progress. 3. SUCCESSFUL: The job execution is completed. 4.
Managing bulk importing and exporting Button Description scheduled jobs are spanning multiple pages, select All to view all the jobs on a single page. Select: All Selects all the jobs in the table. Select: None Clears the check box selections. Previous Displays jobs in the previous page. Next Displays jobs in the next page. Done Takes you back to the User Management page. Import Users – Job Details field descriptions The Import Users-Job Details page displays the details of the selected job.
Managing Users Name Description Success Displays the total number of user records that are successfully imported. Fail Displays the total number of user records that failed to import. Message Displays a message that indicates whether the import is successful or failure. Completed Displays the percentage completion of the import. Name Description Line Number Displays the line number in the file where the error occurred.
Managing bulk importing and exporting Name Description Scheduled by Name of the user who initiated or scheduled the import job. Scheduled at Start time of the scheduled job. End End date and time of the job. Status Status of the job. File Name of the file that is used to import the global user settings records. Count Total number of global user settings records in the input file. Success Total number of global user settings records that are successfully imported.
Managing Users XML for user with core attributes Following are the minimal elements for mapping the user import XML with user interface fields: Table 1: Minimal elements UI field Authentication Type Description XML tag Specifies the type of authentication. Possible value Basic or Enterprise ... > First Name Specifies the first name of the user. ... First name of the user.
Managing bulk importing and exporting Miller mypassword The highlighted XML tag in the user profile XML represents the data for a single user tag that starts and ends with . To create multiple users in the same XML, repeat the highlighted content multiple times with different user values. For example, the following sample XML contains two users, John Miller and Roger Philip.
Managing Users To assign communication address, the mapping of Communication Profile for a new SIP user is as follows: Table 2: Mapping of Communication Profile for a new SIP user UI field Description XML tag Possible value this communication profile. profile. ... Name Default Indicates whether this is a default profile. True or False. ...
Managing bulk importing and exporting UI fField Origination Application Sequence Termination Application Sequence Home Location Description XML tag instance that is used as the home server for a communication profile. ... Specifies the Application Sequence that is invoked when calls are routed from this user. Specifies the Application Sequence that is invoked when calls are routed to this user. Specifies the routing home location.
Managing Users UI field Description for creating the station. Set Type XML tag Possible value ... Specifies the set type of the station. ... Port Specifies the port number from the list for the template you select. ... Related topics: Bulk importing users on page 111 Sample XML file for a user with SIP Communication Profile Here is the sample XML of a user profile with basic fields.
Managing bulk importing and exporting PAGE 234Managing Users 234 Administering Avaya Aura ® Session Manager Comments? infodev@avaya.
Chapter 5: Managing Session Manager routing Overview of Session Manager routing This section details the procedures that are required to set up Session Manager enterprise routing. To complete the administrative procedures, you must use the Routing selection from the System Manager Common Console navigation pane. Once the initial setup is completed, administrators can use the same screens and procedures for administering and modifying the various routing entities as well as Session Manager instances.
Managing Session Manager routing Prerequisites for Routing Setup This section assumes that the following requirements are met: • The System Manager server is installed. • All Session Manager instances are installed. Refer to the section Session Manager installation for details. Routing Routing Routing tells the system which SIP Entity should receive a call that matches the configured dial pattern or regular expression.
Routing Routing of a call using routing policy data 1. Session Manager tries to match the domain to one of the authoritative domains. 2. If Session Manager is authoritative for the domain, then the Session Manager tries to match the digit pattern. 3. If a digit pattern match is not found, it tries to use the regular expression table. 4. If no regular expression match is found, it sends the request to a Session Managerprovisioned outbound proxy. 5.
Managing Session Manager routing 8. Create routing policies. 9. Create dial patterns and assign them to routing policies and locations. 10. Create regular expressions and assign them to routing policies. 11. Create Session Manager instances using the Session Manager menus on the System Manager navigation pane. Routing import and export Overview Overview of exporting and importing routing element data The Routing screens allow administering of the Avaya Aura Session Manager SIP routing rules.
Routing System Manager Routing Import/Export supports: • Routing related data: - Domains - Locations - Adaptations - SIP Entities - Entity Links - Time Ranges - Routing Policies - Dial Patterns - Regular Expressions • Each element can be imported separately as a single XML file containing many entries. • It is possible to compress the XMLs using ZIP compression in order to decrease the size of the files that need to be uploaded to the System Manager server.
Managing Session Manager routing g. Routing Policies h. Dial Patterns i. Regular Expressions The order is decided by analyzing the files internal structure (it must be a well formed XML as described in this guide). Any file name can be used as long as its extension is “xml”. • The Import operation does not halt if one of the elements fails validation. The failed element will not be added to the database, and the operation will continue to the next one.
Routing For example, to export adaptations, select Routing > Adaptations. From the Adaptations screen, select More Actions > Export Adaptations. To export regular expressions, select Routing > Regular Expressions. From the Regular Expressions screen, click More Actions > Export Regular Expressions. 4. Select a check box for the entity to be exported from the list of entities on the screen. 5. To export multiple routing elements, from the routing element screen, click More Actions > Export all data. 6.
Managing Session Manager routing Saving, Committing, and Synchronizing configuration changes About this task Session Manager allows you to save the domain data to the System Manager database and distribute the changes to all the Session Manager instances. To save the data to System Manager and distribute it to the Session Managers, click Commit. When you click Commit , System Manager saves the data to the System Manager database.
Domains • Domain name can be , for example, avaya.com or abc.org. • Sub-domain can be named based on the geographical location or any other corporate requirements such as office location, for example, us.avaya.com and fr.avaya.com can be sub-domains for Avaya offices in the US and in France, or dr.avaya.com and br.avaya.com can be sub-domains for Avaya offices in Denver and in Basking Ridge.
Managing Session Manager routing 6. Click Commit. Deleting domains Procedure 1. On the System Manager console, under Elements, click Routing. 2. Click Routing > Domains. 3. To delete an existing domain or domains, select the check boxes for the domains that you want to edit and click Delete. 4. Click Delete on the confirmation page.
Domains Button Description Duplicate Creates a duplicate of the selected domain. Delete Opens the Delete Confirmation page on which you can confirm or cancel the deletion of the domain. More Actions > Refresh all data Refreshes all data. Any unsaved modifications are lost. More Actions > Import Opens the Import data page that allows you to import from XML files or zip file containing one or more XML files.
Managing Session Manager routing Bulk import for Domains Please follow these rules when creating an XML bulk import file: • The domain name must be unique, and is referred to by other elements. • It is not possible to create a domain with of type “sip” that have containing the value “true”. • The values in must appear exactly same (being case sensitive) as they appear in the System Manager user interface. Example:
Locations offices to data centers in the network core. The Overall Managed Bandwidth and Per-Call Bandwidth Parameters sections in the Location Details page allow you to specify the CAC related details. Note: Session Manager logs the result of each rejected multimedia CAC request which enables the determination of the root cause when multimedia calls fail.
Managing Session Manager routing 12. Click Commit. Related topics: Location Details field descriptions on page 254 Modifying Locations Procedure 1. On the System Manager console, under Elements, click Routing. 2. Click Routing > Locations. 3. To edit a location name or location matching pattern, select a check box for the required location and click Edit and make the required changes to the location or location pattern for that location. 4.
Locations Delete Confirmation field descriptions Use this page to confirm or cancel the deletion of locations. Button Description Delete Deletes the selected location. Cancel Cancels the deletion of the location. Related topics: Deleting Locations on page 248 CAC Overview Audio and multimedia calls require high bandwidth and low latency for best user experience.
Managing Session Manager routing prevents such calls from consuming too large a percentage of the available bandwidth of a location (Total Bandwidth). 3. If the Total Bandwidth is left “BLANK” then Session Manager does not perform CAC for calls in the Location. 4. Allows audio and multimedia bandwidth sharing at a location by selecting the option Audio Calls Can Take Video Bandwidth. • If selected, then Session Manager considers only the Total Bandwidth when deciding whether a new audio call can proceed.
Locations Provisioning Session Manager and Communication Manager CAC together For simultaneous use of Session Manager and Communication Manager CAC, following configurations should be done: 1. Create 1-to-1 mapping of Session Manager Locations to Communication Manager Network Regions, because Communication Manager uses Network Regions for CAC. This is limited by the fact that Communication Manager supports no more than 250 Network Regions, while Session Manager supports thousands of Locations. 2.
Managing Session Manager routing environment, Y is likely to be 83, because Avaya endpoints (as well as many others) use G.711Mu as their primary audio codec. For multimedia (video) users, a more complex analysis is required as suggested below. Example: Given A = percentage of calls that are audio (ex: 80%) B = percentage of calls that are multimedia (ex: 20%) C = average bandwidth used by an audio call (kbps) (ex: 83) D = average bandwidth used by a multimedia call (kbps) (ex: 768).
Locations video locations to the audio location and ensure that none of the SIP Entities are assigned to the video location. 2. Change the Total Bandwidth value for the audio location to be the sum of the previous audio location value and the reassigned video location value. 3. Add the IP address pattern values from the video location under the audio location, combining them with existing patterns to create patterns with broader ranges if possible.
Managing Session Manager routing Button Description Edit Opens the Location Details page that you can use to modify the location details. New Opens the Location Details page that you can use to create new locations. Duplicate Creates a duplicate of the selected location and assigns a new state to it. Delete Opens the Delete Confirmation page on which you can confirm or cancel the deletion of the location. More Actions > Refresh all data Refreshes all data. Any unsaved modifications are lost.
Locations Overall Managed Bandwidth section Name Description Managed Bandwidth Units Specifies the bandwidth unit for Overall Managed Bandwidth values. Total Bandwidth The total bandwidth available for use by any calls between this location and other locations. Any attempt to exceed this limit results in calls being alternate routed or denied. If no value is specified, the bandwidth limit is infinite.
Managing Session Manager routing Name Description Manager uses while reducing the bandwidth request for a call to or from this location to enforce any bandwidth restriction. If a bandwidth restriction requires Session Manager to reduce a media stream below this level, the stream is removed from the call, possibly resulting in the entire call being blocked. Media requests for bandwidth beneath this minimum will not be blocked; this is solely a restriction on Session Manager’s ability to modify requests.
Locations Button Description Commit Modifications made to the Location are saved. Cancel Modifications made to the Location are not saved. Related topics: Creating Locations on page 247 Bulk import for Locations Please follow these rules when creating an XML bulk import file: • Locations are referred to as routing origination in the import XML. • The name of a location is unique and is referred to by other elements.
Managing Session Manager routing true 384 384 64 40 900000 Kbit/sec
Adaptations • From (see note 1 below) • P-Asserted-Identity • History-Info (calling portion) • Contact (in 3xx response) The destination type URIs are: • Request-URI • To (see note 1 below) • Message Account (in NOTIFY/message-summary body) • Refer-To (in REFER message, see note 2 below) Note: 1. The From and To headers are only modified by adaptation if the “fromto” module parameter is present and has the value of “true”. See “Adaptation Module Administration” below. 2.
Managing Session Manager routing Refer to the section “Installed vendor adapters” for details. • Module Parameter : Note: The list is separated by spaces and not by commas. Supported adaptation module parameters are: • fromto: if set to “true”, then adaptation will modify From and To headers of the message. If omitted or set to any other value, From and To headers will not be modified.
Adaptations CiscoAdapter overrideSourceDomain=dr.avaya.com overrideDestinationDomain=ny.avaya.com All adaptation modules have the ability to replace the domain (also known as host name) portion of the URI with a specified value for source and destination type URIs on outgoing calls (egress) and to append parameters to the Request URI on for outgoing calls (egress). This adaptation functionality is expandable to adapt additional deployments needing further flexibility.
Managing Session Manager routing Note: c. The list is separated by spaces and not by commas Enter a list of URI parameters to append to the Request-URI on egress in the Egress URI Parameters field. URI parameters can be added to the Request-URI. For example, the parameter “user=phone” can be appended for all INVITEs routing to a particular SIP entity. The egress Request-URI parameters are administered from the Adaptation Details using the Egress URI Parameters field.
Adaptations 15. Enter the matching pattern and other required fields. The Matching Pattern field can have 1 to 36 characters. Mouse over the input field to view a tool tip describing valid input. 16. Enter the number of minimum and maximum digits to be matched in the Min and Max fields respectively. The minimum value can be 1 or more. The maximum value can be 36. 17. Add Phone Context as an optional parameter for the egress adaptation rules. 18.
Managing Session Manager routing • Insert Digits = + • Address to modify = both For outgoing calls to AT&T, Session Manager must convert the E.164 form to a format that AT&T supports, either 1+10 digits for North America calls, or 011+country code + number for international calls.
Adaptations • Phone-Context = site1 • Delete Digits = 3 • Insert Digits = • Address to modify = both Input (String prior to the adaptation processing) Adaptation Processing Output (String after the adaptation processing) 5335; phone-context = site1@avaya.com; user = phone Ingress adaptation 9085335@avaya.com 9085335@avaya.com Egress adaptation 5335; phone-context = site1@avaya.com; user = phone Modifying Adaptations Procedure 1. On the System Manager console, under Elements, click Routing. 2.
Managing Session Manager routing URI in RFC3261. A leading ';' is optional. Entry “;user=phone;custApp=1” is equivalent to “user=phone;custApp=1”. d. Enter description about the adaptation module in the Notes field. 5. Click Add under Digit Conversion for Incoming Calls if you need to configure ingress digit conversion. Ingress adaptation is used to administer digit manipulation for calls coming into the Session Manager instance. 6. Enter the matching pattern and other required fields.
Adaptations 19. Enter the digits that you want inserted before the number in the Insert Digits field. 20. From the drop-down list, select the value for Address to modify. A setting of both will look for adaptations on both origination and destination type headers. The digit conversion applied to a header will be taken from the entry with the longest matching pattern. 21. Continue clicking the Egress Adaptation Add button until all the required egress matching patterns have been configured. 22.
Managing Session Manager routing Related topics: Deleting Adaptations on page 267 Installed vendor adapters Cisco Adapter (CiscoAdapter) The Cisco Adapter provides two basic header manipulations: converting between Diversion and History-Info headers and converting between P-Asserted-Id and Remote-Party-Id headers. The Diversion and Remote-Party-Id headers have not been accepted by the IETF. They are replaced by History-Info and P-Asserted-Identity respectively, but are still used in the Cisco products.
Adaptations Reason=SIP%3Bcause%3D486%3Btext%3D%22Busy%20Here%22 &Reason=Redirection%3Bcause%3DNORMAL%3Bavaya-cm-reason%3D%22 cover-busy%22%3Bavaya-cm-vm-address-digits%3D81080000%3Bavaya-cm-vm-addresshandle%3Dsip:80000%40avaya.com>;index=1.1 History-Info: "MM" ;index=1.2 Remote-Party-Id to P-Asserted-Identity Header Adaptation Cisco requires information in the P-Asserted-Identity (PAI) header to be received in the Remote-Party-Id (RPI) header.
Managing Session Manager routing CS1000 Adapter (CS1000Adapter) The CS1000 Adapter provides two services between formats used by the CS1000 and the format used by other Avaya equipment: • translation between History-Info header formats • Support for CS1000 origination based routing History-Info header adaptation Since the CS1000 adapter uses some different formatting for the History-Info header than other Avaya products, it is necessary to adapt the History-Info header values.
Adaptations CS1000 History-Info: History-Info: ; index=1, ;index=2 gets converted to: Avaya History-Info: History-Info:;index=1 History-Info:
Managing Session Manager routing Name Description Module name The module name contains only the name. Egress URI Parameters The terminating trunk group parameters. Notes Other details that you wish to add. Adaptation Details field descriptions Use this page to specify the adaptation details. General section Name Description Adaptation Name Name of the adaptation. Must be unique and be between 3 and 64 characters in length. Module name The module name contains only the name.
Adaptations Name Description Request-URI, To header (if administered), Refer-To header, and Notify/messagesummary body with the given value for egress only. • overrideSourceDomain ( may be abbreviated to osrcd): replaces the domain in the From header (if administered), P-Asserted-Identity header and calling part of the History-Info header with the given value for egress only.
Managing Session Manager routing Name Description Insert Digits Number of digits to be added before the dialed number Address to Modify A setting of both will look for adaptations on both origination and destination type headers. The digit conversion applied to a header will be taken from the entry with the longest matching pattern. Notes Any other details that you wish to add.
Adaptations Button Description Commit Saves the adaptation details and distributes them to the Session Manager instances in the enterprise. Cancel Cancels changes to the adaptation details and returns to the Adaptations page. Related topics: Creating Adaptations on page 261 Bulk import for Adaptations Follow these rules when creating an XML bulk import file: • The name of an adaptation is unique and is referred to by other elements.
Managing Session Manager routing test 1 3 810 21 3 destination test 1 3 811 22 3 both
SIP Entities Authentication of trusted SIP entities Routing uses the following information for the authentication of SIP entities by performing validation on IP/Transport Layer and TLS Layer: • FQDN or IP Address of the SIP entity • Credential name of the SIP entity • Protocol of the Entity Links.
Managing Session Manager routing • If the Credential Name string is not empty, the Credential Name and the IP address of the far-end is searched for in the following fields in the identity certificate provided by the SIP entity: - CN value from the subject - subjectAltName.dNSName - subjectAltName.uniformResourceIdentifier (For IP address comparison, IP address string is converted to SIP:W.X.Y.Z before comparison. W.X.Y.Z is the remote socket IPV4 address.
SIP Entities 9. If the SIP entity Type is “Session Manager” and you need to specify an Outbound Proxy for the SIP entity, click the drop-down selector for the Outbound Proxy field. In cases when Session Manager cannot associate any administered routing policies, then the request is sent to the SIP entity administered as an outbound proxy. If no outbound proxy is provisioned, then Session Manager will proxy the request on its own. 10. Enter a regular expression string in the Credential name field.
Managing Session Manager routing The default port for TCP and UDP is 5060. The default port for TLS is 5061. 15. Enter the SIP entity 2 by selecting the required non-Session Manager SIP entity from the drop-down list and provide the required port. The port is the port on which you have configured the remote entity to receive requests for the specified transport protocol. 16. If the SIP entity is trusted, select the Trusted check box.
SIP Entities 8. Enter or modify a regular expression string in the Credential name field. Credential name is used for TLS connection validation by searching this string in the SIP entity identity certificate. • If you do not want to perform the additional validation on SIP entity identity certificate or are not using SIP TLS for connecting to the SIP entity, leave this field empty.
Managing Session Manager routing 15. Select the protocol you require for the link using the Protocol drop-down list. 16. If you need to specify the Port parameters, click Add under Port. When Session Manager receives a request where the host-part of the request-URI is the IP address of the Session Manager, it associates one of the administered domains with the port on which the request was received. 17. Enter the necessary Port and Protocol parameters. 18.
SIP Entities Button Description Edit Opens the SIP Entity Details page that you can use to modify the SIP entity. New Opens the SIP Entity Details page that you can use to create new SIP entities. Duplicate Creates a duplicate of the selected SIP entity and assigns a new state to it. Delete Opens the Delete Confirmation page on which you can confirm or cancel the deletion of the SIP entity. More Actions > Refresh all data Refreshes all data. Any unsaved modifications are lost.
Managing Session Manager routing Name Description emergency call. The SIP Entity selected as the ELIN server should be resolved through local host name resolution to use either the primary or secondary IP address. Notes Additional notes about the SIP entity. SIP Entity Details field descriptions Use this page to specify SIP entity details. General Name Description Name SIP entity name. This name must be unique and can have between 3 and 64 characters.
SIP Entities Name Description Credential name Enter a regular expression string in the Credential name. Credential name is used for TLS connection validation by searching this string in the SIP entity identity certificate. SIP Link Monitoring Name Description SIP Link Monitoring Select the process for SIP Link monitoring. Entity Links Name Description SIP Entity 1 Select a SIP entity from the drop-down list. This entity must always be a Session Manager instance.
Managing Session Manager routing Button Description Add Adds the selected entity. Remove Removes the selected entity. Commit Saves the SIP entity and distributes it to the Session Managers in the enterprise. Cancel Cancels the creation or modification of the SIP entity. Related topics: Creating SIP Entities on page 278 SIP Entity List field descriptions Use this page to select and associate SIP entities to a routing policy.
SIP Entities that exists in the same import operation as the SIP Entity. SIP Entity of type “ASM” cannot contain an adaptation entry. • contains the adaptation module name and parameters separated by spaces . • Listen ports () are only relevant for SIP Entity of type “ASM”. Do not include these entries for any other type of SIP Entity. • Multiple listen ports entries () can be configured for one ASM SIP Entity.
Managing Session Manager routing CM 9.8.7.
SIP Entity References SIP Entity References About SIP Entity References Session Manager enables you to see all references to a SIP entity such as its location, the routing policy that is created for the SIP entity, and adaptations, if any. If a single SIP entity has more than one combination of these references, Session Manager displays each of the combinations on a separate row. Displaying SIP Entity References Procedure 1. On the System Manager console, under Elements, click Routing. 2.
Managing Session Manager routing Name Description Location Name Lists the location associated with the specified SIP entity Routing Policy Name Lists the routing policy associated with the specified SIP entity Adaptation Name Lists the name of the adaptation associated with the SIP entity Button Description Back Returns to the SIP Entities page Related topics: Displaying SIP Entity References on page 289 Entity Links About Entity Links Session Manager enables you to create an entity link betwe
Entity Links Creating Entity Links Procedure 1. On the System Manager console, under Elements, click Routing. 2. Click Routing > Entity Links. 3. Click New. 4. Enter the name in the Name field. 5. Enter the SIP entity 1 by selecting the required Session Manager SIP entity from the drop-down list and provide the required port. SIP entity 1 must always be an Session Manager instance. The default port for TCP and UDP is 5060. The default port for TLS is 5061. 6.
Managing Session Manager routing 8. Select the transport protocol you require for the link using the Protocol drop-down list. 9. Click Commit. Deleting Entity Links Procedure 1. On the System Manager console, under Elements, click Routing. 2. Click Routing > Entity Links. 3. To delete an existing link or links, select the respective check boxes and click Delete. 4. Click Delete on the confirmation page.
Entity Links Button Description Duplicate Creates a duplicate of the selected entity link and assigns a new state to it. Delete Opens the Delete Confirmation page on which you can confirm or cancel the deletion of the entity link. More Actions > Refresh all data Refreshes all data. Any unsaved modifications are lost. More Actions > Import Opens the Import data page that allows you to import from XML files or zip file containing one or more XML files.
Managing Session Manager routing Bulk import for Entity Links Please follow these rules when creating an XML bulk import file: • The name of an Entity Link must be unique. • , must refer to an existing SIP Entity with the exact same name. It must either appear in the System Manager database or in an import file that exists in the same import operation as the Entity Link.
Time Ranges For example, routing policy A can be in effect on all weekdays from 9:00 a.m. to 5:59 p.m., routing policy B can be in effect on all weekdays from 6:00 pm. to 9 a.m., and routing policy C time ranges can be in effect on weekends. These three time ranges together cover how calls should be routed throughout the week. Creating Time Ranges About this task You can use the Time Ranges screen to administer time ranges with start and end times. Procedure 1.
Managing Session Manager routing Deleting Time Ranges Procedure 1. On the System Manager console, under Elements, click Routing. 2. Click Routing > Time Ranges. 3. To delete an existing time range or ranges, select the respective check boxes and click Delete. 4. Click Delete on the confirmation page. Related topics: Delete Confirmation field descriptions on page 296 Delete Confirmation field descriptions Use this page to confirm or cancel the deletion of time ranges.
Time Ranges Field Description Days (Mo to Su) Select the days of the week for which the time range should be used. Start Time Start time for the time range. Use 24–hour time format. End Time End time for the time range. Use 24–hour time format. Notes Additional notes. Button Description Edit Opens the Time Ranges page that you can use to modify the time range details. New Opens the Time Ranges page that you can use to create new time ranges.
Managing Session Manager routing Name Description Mon Selected check box indicates that the time range is used for Mondays. Similarly, other days of the week for which the time range to be used are selected. Start Time Start time for the time range. For a 24–hour time range, the start time is 0.00. End Time End time for the time range. For a 24–hour time range, the end time is 23:59. Notes Additional notes about the time range.
Routing Policies weekend 00:00:00 23:59:00 Time Range 24/7 true true true true true true true 24/7 00:00:00 2
Managing Session Manager routing The second time (if there's no match) only user@host is compared, that is the URI scheme (sip:, sips:, tel:) and any URI parameters appearing after the host-part of the request-URI are stripped. If there's a match, then the Routing Policies are selected as per the administered Regular Expressions. Creating Routing Policies Procedure 1. On the System Manager console, under Elements, click Routing. 2. Click Routing > Policies. 3. Click New. 4.
Routing Policies Related topics: Routing Policy Details field descriptions on page 303 Modifying Routing Policies Procedure 1. On the System Manager console, under Elements, click Routing. 2. Click Routing > Policies. The Routing Policies screen is displayed. 3. Select a routing policy for modification and click Edit. 4. If required, modify the routing policy name and notes in the relevant fields in the General section. Note that the routing policy can be disabled by selecting the Disabled check box. 5.
Managing Session Manager routing Deleting Routing Policies Procedure 1. On the System Manager console, under Elements, click Routing. 2. Click Routing > Policies. 3. To delete an existing routing policy or routing policies, select the respective check boxes and click Delete. 4. Click Delete on the confirmation page. Note: If you delete a routing policy, all dial patterns and regular expressions that are linked only to this routing policy are also deleted.
Routing Policies Button Description Edit Opens the Routing Policy Details page that you can use to modify the routing policy. New Opens the Routing Policy Details page that you can use to create a new routing policy. Duplicate Creates a duplicate of the selected routing policy and assigns a new state to it. Delete Opens the Delete Confirmation page on which you can confirm or cancel the deletion of the routing policy. More Actions > Refresh all data Refreshes all data.
Managing Session Manager routing Name Description Disabled Selecting this check box specifies that the routing policy is to be disabled and should not be used. Notes Additional notes about the routing policy. SIP Entity as Destination section Button Description Select Opens the SIP entity List page. You can use this page to select a SIP entity as a destination and associate it to the selected routing policy. Name Description Name SIP entity name.
Routing Policies Name Description Start Time Start Time of the Time Range. End Time End Time of the Time Range. Notes Additional notes. Dial Patterns section Button Description Add Adds a new dial pattern to the selected routing policy. Remove Removes the selected dial pattern from the selected routing policy. Name Description Pattern Dial pattern to match. The pattern can have between 1 and 36 characters. Roll over the field for the valid pattern.
Managing Session Manager routing Name Description Deny Denies routing for a matched regular expression pattern. Notes Additional Notes. Button Description Commit Saves the routing policy changes and distributes those to the Session Manager instances in the enterprise. Cancel Cancels modifications to the routing policy.
Dial Patterns Bulk import for Routing Policies Please follow these rules when creating an XML bulk import file: • The name of a routing policy is unique and is referred to by other elements. • must refer to an existing SIP element with the exact same name. It must either appear in the System Manager database or in an import file that exists in the same import operation as the Routing Policy.
Managing Session Manager routing call gets routed. The dial pattern look up method as per the Global Setting option is explained below: 1. When the Global Settings option is not selected: Session Manager compares the user-part of the Request-URI with all dial patterns valid for the originating location where the domain matches the domain in the Request-URI.
Dial Patterns Location Specific Pattern “ALL” Locations Pattern Chosen Pattern 1303538 130353 Location-Specific 130353x 1303538 ALL Locations 1303538 130353x Location-Specific 1x 1303538 ALL Locations 13035xx 130xxxx Location-Specific 1303xxxxx 1303538xx Location-Specific The pattern matching algorithm works as follows: • Valid digits are 0-9 • Valid characters for the leading position are,+, *, and #. Any other characters are not matched.
Managing Session Manager routing 7. Click Select to indicate that you have completed your selections. 8. If you need to specify that calls from the specified locations will be denied, click Add under the Denied Locations section. 9. Select all the Locations that are to be denied and click Select to indicate that you have completed your selections. 10. Click Commit. Note: You cannot save a dial pattern unless you add at least a routing policy or a denied location.
Dial Patterns Note: You cannot save a dial pattern unless it has at least one routing policy or a denied location associated to it. Deleting Dial Patterns Procedure 1. On the System Manager console, under Elements, click Routing. 2. Click Routing > Dial Patterns. 3. To delete an existing dial pattern or patterns, select the respective check boxes and click Delete. 4. Click Delete on the confirmation page.
Managing Session Manager routing 312 Button Description Edit Opens the Dial Pattern Details page that you can use to modify the dial pattern details. New Opens the Dial Pattern Details page that you can use to create new dial patterns. Duplicate Creates a duplicate of the selected dial pattern and assigns a new state to it. Delete Opens the Delete Confirmation page on which you can confirm or cancel the deletion of the dial pattern. More Actions > Refresh all data Refreshes all data.
Dial Patterns Name Description SIP Domain Domain for which you want to restrict the dial pattern. Notes Other details that you wish to add. Dial Pattern Details field descriptions Use this page to specify the dial pattern details. General section Name Description Pattern Dial pattern to match. The pattern can have between 1 and 36 characters. Roll over the field for the valid pattern. Min Minimum number of digits to be matched. Max Maximum number of digits to be matched.
Managing Session Manager routing Name Description Originating Location Name Name of the location to be associated to the dial pattern. Originating Location Notes Notes about the selected location. Routing Policy Name Name of the routing policy to be associated to the dial pattern. Rank Rank order. Routing Policy Disabled Name of the routing policy that should not be used for the dial pattern. Routing Policy Destination Destination of the routing policy.
Dial Patterns Name Description Pattern Dial pattern to match. The pattern can have between 1 and 36 characters. Roll over the field for the valid pattern. Min Minimum number of digits to be matched. Max Maximum number of digits to be matched. Emergency Call Indicate if it is an emergency call. Note: Some of the important constraints on the use of this feature are as follows • Each location should be assigned to only one emergency dial number.
Managing Session Manager routing Bulk Import for Dial Patterns Please follow these rules when creating an XML bulk import file: • A dial pattern is identified by a combination of 5 elements below. This combination must be unique for each dial pattern. - - - - - • must refer to an existing domain with the exact same name.
Regular Expressions Regular Expressions About Regular Expressions You can configure routing in Session Manager by creating regular expressions and associating them with a routing policy. Regular expression syntax is based on Java syntax. The asterisk character "*" matches any character string. The dot character "." matches one character. The backslash character "\ " makes a character lose its special meaning, if any Some examples are: • For “www.sipentity.domain.com”, use the string “www\.sipentity\.
Managing Session Manager routing 5. Specify a rank order for the regular expression. A lower rank order indicates a higher priority. 6. To deny routing for a matched regular expression pattern, select the Deny check box. 7. To associate a routing policy for the matched pattern, click Add under the Routing Policy section. 8. Select the required routing policies that you want associated with the Regular Expression by selecting the respective check boxes. 9.
Regular Expressions 10. To remove an associated routing policy, select the routing policy and click Remove. 11. Click Commit. Note: You cannot save a regular expression unless it has a routing policy associated to it. Deleting Regular Expressions About this task Deleting a regular expression deletes it from all of the routing policies that it is associated with. Procedure 1. On the System Manager console, under Elements, click Routing. 2. Click Routing > Regular Expressions. 3.
Managing Session Manager routing Regular Expressions field descriptions Use this page to create, modify, delete, and manage regular expressions. 320 Button Description Edit Opens the Regular Expression Details page that you can use to modify the regular expressions. New Opens the Regular Expression Details page that you can use to create new regular expressions. Duplicate Creates a duplicate of the selected regular expression and assigns a new state to it.
Regular Expressions Regular Expression Details field descriptions Use this page to specify the regular expression details. General Name Description Pattern Regular expression pattern that Session Manager tries to match. Refer to the “Appendix B: Regular Expression constructs” for details. Rank Order Priority of the pattern. A lower rank order means higher priority. Deny Denies routing for a matched regular expression pattern. Notes Additional notes about the regular expression pattern.
Managing Session Manager routing Regular Expression List field descriptions Use this page to view the regular expression associated with the selected routing policy. Name Description Regular Expression Displays the regular expression to be used for the selected routing policy. Rank Order Priority of the regular expression. Lower rank order means a higher priority. Deny Denies routing for a matched regular expression. Notes Additional notes for the regular expression.
Defaults Defaults Modifying the default settings You can use the Defaults screen to change the default values or ranges for parameters that are used by the other Routing menu options About this task These values are used as defaults values of admin personal settings when creating new Routing entities. Modifying these values does not change the values of already created entities . Procedure 1. On the System Manager console, under Elements, click Routing. 2. Click Routing > Defaults.
Managing Session Manager routing • If the FQDN is not in the local table and DNS is consulted, if you have not selected the check box, only an A-Record lookup is done in DNS to resolve the host name to an IP address. Transport and port specified in the entity link are used. If you selected the check box, a full DNS lookup (as described in RFC 3263) is done, and the transport and port specified in the entity link could be overridden. 8.
Defaults Entity Links Name Description Listen Port Number of the port to be used for entity links. The default port is 5060. Default Transport Protocol for Entity Links The default transport protocol that the entity links use, such as TLS, TCP, or UDP. The default is TLS. Domain Management Name Description Suffix The default suffix to be used for the domain name. SIP Entities Name Description Type Type of the SIP entity, such as ASM, CM, Trunk, Gateway, and so on. The default is ASM.
Managing Session Manager routing Button Description Restore Defaults Restores vendor defaults. Revert Reverts to settings before the last applied settings. Apply Saves and applies the modified default settings. Related topics: Modifying the default settings on page 323 326 Administering Avaya Aura ® Session Manager Comments? infodev@avaya.
Chapter 6: Configuring and monitoring Session Manager instances Dashboard About Session Manager Dashboard Session Manager Dashboard provides a snapshot view of the health and summary of all the administered Session Manager instances. It also enables some of the following maintenance operations: Before you start a maintenance operation or an upgrade of a Session Manager, you must: • Set the Session Manager to block new incoming calls (set the Deny New Service state) and wait for active calls to terminate.
Configuring and monitoring Session Manager instances Button Description which were previously blocked using a Deny New Service request. Shutdown System > Shutdown Shuts down the selected Session Manager server or servers. Shutdown System > Reboot Reboots the selected Session Manager server or servers. Name Description Session Manager Name of administered Session Manager instance. You can click on the link to go to the Session Manager Administration page. Type Type of Session Manager instance.
Dashboard Name Description Active Call Count The current active call counts for this session manager instance. Registrations The registration summary. You can click on the link to display the Registration Summary page. Version Version of the Session Manager software installed and has the following format: .....
Configuring and monitoring Session Manager instances Name Description Active Call Count The current active call counts for this session manager instance. Registrations The registration summary. You can click on the link to go to the Registration Summary page. Confirm Deny New Service for Session Managers page field descriptions Button Description Cancel Cancels the blocking of new calls for processing. Processing of new calls continues. Confirm Blocks new calls from being processed.
Dashboard Confirm Shutdown for Session Managers page field descriptions Button Description Cancel Cancels the shutdown of the selected Session Manager instances. Confirm Confirms the shutdown of the selected Session Manager instances. Name Description Session Manager Name of administered Session Manager instance. You can click on the link to go to the Session Manager Administration page. Type The type of Session Manager instance, either as Core or Branch Session Manager.
Configuring and monitoring Session Manager instances Name Description Session Manager Name of administered Session Manager instance. You can click on the link to go to the Session Manager Administration page. Type The type of Session Manager instance, either as Core or Branch Session Manager. Service State Current service and management state of the selected Session Manager instance.
Session Manager Administration About E911 Services The E911 service enables identification of the physical location of a registered user in the event of an emergency call. The location is determined through the IP address and port level discovery as per E911 administration. Session Manager interacts with E911 service upon user registrations to obtain an Emergency Location Identification Number (ELIN).
Configuring and monitoring Session Manager instances Adding a SIP entity as a Session Manager instance Before you begin Before starting this procedure, make sure that the SIP entity that you want to add was created. For a Session Manager SIP Entity type, you must administer the listen ports on the SIP entity form. These listen ports are used by endpoints to connect to Session Manager and can be used to map different ports to different domains. Procedure 1.
Session Manager Administration 8. If you selected ARP Monitoring for Device Monitoring Mode, enter the following information: a. ARP Interval (msecs) — Specifies the ARP link monitoring frequency. The range is 50 to 1000. The default value is 100. b. ARP Target IP — Specifies the IP target of the ARP request which is sent to determine the health of the link to the targets. You can configure up to 3 IP addresses for ARP monitoring.
Configuring and monitoring Session Manager instances a. Select the Limited PPM Client Connection check box to enable the Maximum Connection per PPM client field. The default value is enabled. b. Specify the value of Maximum Connection per PPM client. Valid values are integers between 1 and 10. The default value is 3. c. Select the PPM Packet Rate Limiting check box to enable the PPM Packet Rate Limiting Threshold field. The default value is enabled. d.
Session Manager Administration Procedure 1. On the System Manager console, under Elements, click Session Manager. 2. Click Session Manager Administration in the left navigation pane. 3. Select a Session Manager instance from the list and click Edit. 4. Under the General section, change the following information, if required: • Add a comment in the Description field for the Session Manager SIP entity.
Configuring and monitoring Session Manager instances • Modify the value for VLAN ID. This is the VLAN that the Session Manager is to be associated with. Call traffic segregation could be based on the VLAN that the Session Manager is associated with. 6. Under NIC Bonding section, change the following information if required: • To enable or disable NIC bonding, select or clear the Enable Bonding check box. NIC bonding slaves interfaces eth2 and eth3 in a bond of interfaces.
Session Manager Administration • Type a required value in seconds for Proactive cycle time (secs). The default is 900 seconds. • Session Manager uses this value for monitoring and polling an administered SIP entity at this interval till that entity is reachable. • Type a required value in seconds for Reactive cycle time (secs). The default is 120 seconds. This value is used when proactive monitoring detects that an administered SIP entity is not reachable and changes to a reactive mode.
Configuring and monitoring Session Manager instances 10. Event Server section specifies the option to clear Subscription on Notification Failure. 11. Click Commit. Related topics: Session Manager Administration page field descriptions on page 341 Session Manager page field descriptions on page 344 Deleting a Session Manager instance Procedure 1. On the System Manager console, under Elements, click Session Manager. 2. Click Session Manager Administration in the left navigation pane. 3.
Session Manager Administration 3. In the Session Manager Administration page under Global Settings section, select the administered ELIN Server for “ELIN SIP Entity” field. 4. Create the Entity Links from ELIN Server to all Session Manager SIP Entities. 5. Import certificates using TLS link between Session Manager and ELIN server. This is required only if the entity link is of “TLS” type. Note: OPTIONS monitoring is enabled between Session Manager and ELIN Server.
Configuring and monitoring Session Manager instances Name Description ELIN SIP Entity Used by third party E911 services, which determines a user’s location based on IP address, to send the new ELIN to Session Manager in case of emergency call. The SIP Entity selected as the ELIN server should be resolved through local host name resolution to use either the primary or secondary IP address.
Session Manager Administration Name Description Profile(s) if a single other Session Manager fails.
Configuring and monitoring Session Manager instances Session Manager page field descriptions General Name Description SIP Entity Name Select a name of the SIP entity that you wish to add as a Session Manager instance. The entity must be of type Session Manager and it must be in Sync state. Description Description of the entity added. Optional.
Session Manager Administration Name Description uses a default DSCP value of 46 which indicates forwarding with the highest priority. QOS Priority This value specifies the ability to provide different priority to different applications, users, or data flows, or to guarantee a certain level of performance for a call on a local area network. The higher the priority, lower the QOS priority number. This is the value of 802.
Configuring and monitoring Session Manager instances Name Description Down Delay (msecs) Specifies the wait time for disabling of a slave in case of detection of a link failure. The value is a multiple of link monitoring frequency value and range is from 50 to 1000 (default value is 200). Up Delay (msecs) Specifies the wait time for enabling of a slave in case of detection of a link recovery.
Session Manager Administration Button Description a SIP entity before it is deemed unreachable. The default is 1. Session Manager uses these default values for each administered SIP entity unless overridden by the Monitoring options that you specified on the SIP Entities page for a specific entity. CDR Name Description Enable CDR This controls whether CDR is enabled at the system level for that Session Manager instance.
Configuring and monitoring Session Manager instances Event Server Name Description Clear Subscription on Notification Failure Specifies the option to clear Subscription on Notification Failure. Button Description Cancel Cancels the Session Manager addition operation. Commit Saves the added SIP entity as a Session Manager instance with the selected configuration options.
Branch Session Manager Administration Branch Session Manager Administration About Branch Session Manager The Branch Session Manager provides a SIP-enabled branch survivability solution. It allows a customer who has deployed SIP phones in a branch to receive LSP-style survivability. For example, when the core Session Manager is unreachable, the SIP phones receive their Communication Manager features from the LSP.
Configuring and monitoring Session Manager instances Communication Manager. When Communication Manager is detected in the sequence, the request is sent after substituting the LSP's IP address for the core Communication Manager. So the LSP is automatically used as the Survivable Feature Server. It is recommended that the Branch Session Manager be configured to support no more than 2 core session managers. Either of the Session Managers can be configured as a primary or secondary server for a branch user.
Branch Session Manager Administration 4. If required, create a sequence of applications (application sequence) and specify call handling by CM-FS/ES which should be the same one as specified on the BSM Instance form. 5. Administer users using the BSM as the Survivability Server. Adding a SIP entity as a Branch Session Manager instance Before you begin Before starting this procedure, make sure that the SIP entity that you want to add was created.
Configuring and monitoring Session Manager instances Manager entity. The adaptation is applied either to calls that are routed through the gateway to the LSP and also to calls that are application sequenced. Note: To be a part of the Branch Session Manager instances network of an enterprise, a Branch Session Manager instance must first be administered as a management access point. This is the network mask of the domain name of the server that hosts the Branch Session Manager application.
Branch Session Manager Administration SIP Entity IP Address field is populated as per the IP address of the SIP entity. 6. Under the Monitoring section, enter the following information to configure how this Branch Session Manager instance should monitor SIP entities: • To enable or disable monitoring of the SIP entities by this Branch Session Manage instance, select or clear the Enable Monitoring check box. • Type a required value in seconds for Proactive cycle time (secs). The default is 900 seconds.
Configuring and monitoring Session Manager instances Related topics: Session Manager Administration page field descriptions on page 341 Branch Session Manager page field descriptions on page 358 Viewing the Branch Session Manager administration settings Procedure 1. On the System Manager console, under Elements, click Session Manager. 2. Click Session Manager Administration in the left navigation pane. 3.
Branch Session Manager Administration Manager application. Branch Session Manager passes the address to the security module to allow the agent to query the server for the required information. To be a part of the Branch Session Manager instances network of an enterprise, a Branch Session Manager instance must first be administered as a management access point. • Select the Main CM for LSP from the drop-down list. Click the View / Add CM Entities link to add new CM applications.
Configuring and monitoring Session Manager instances The default is 6. Range of this value is 0-7. This value specifies the ability to provide different priority to different applications, users, or data flows, or to guarantee a certain level of performance for a call on a local area network. The higher the priority, the lower the QOS priority number. • Modify the value for VLAN ID. This is the VLAN that the Branch Session Manager is to be associated with.
Branch Session Manager Administration During normal operation, Branch Session Manager receives data from a Communication Manager feature server for synchronization to Avaya SIP endpoints. 8. Event Server section specifies the option to clear Subscription on Notification Failure. 9. Click Commit. Related topics: Session Manager Administration page field descriptions on page 341 Branch Session Manager page field descriptions on page 358 Deleting a Branch Session Manager instance Procedure 1.
Configuring and monitoring Session Manager instances Button Description Cancel Cancels the deletion of the selected Branch Session Manager instance. Related topics: Deleting a Branch Session Manager instance on page 357 Branch Session Manager page field descriptions General Name Description SIP Entity Name Select a name of the SIP entity that you wish to add as a Branch Session Manager instance. The entity must be of type Session Manager and it must be in Sync state.
Branch Session Manager Administration Name Description Call Control PHB The Call Control PHB (per hop behavior) specifies the type of service and priority SIP traffic from SM100 may expect as it travels through the IP network. All packets containing SIP signaling which leave the SM100 have the specified value in the DSCP (differentiated service code point) field of the IP header.
Configuring and monitoring Session Manager instances Button Description Proactive cycle time (secs) Enter a value in seconds for polling the administered SIP entities by the added Branch Session Manager. Monitoring ensures that the entities are still reachable. Proactive monitoring occurs as long as no outages are detected. The default is 900 seconds.
Communication Profile Editor Name Description PPM Packet Rate Limiting Threshold This value is applied per PPM client. Value Range: 1-500, default value: 25. Event Server Name Description Clear Subscription on Notification Failure Specifies the option to clear Subscription on Notification Failure. Button Description Cancel Cancels the Branch Session Manager addition operation. Commit Saves the added SIP entity as a Branch Session Manager instance with the selected configuration options.
Configuring and monitoring Session Manager instances Important: A user's SIP phone is added to the Aura Network by assigning the user a Communication Profile containing a Communication Manager endpoint profile and a Session Manager profile. The Communication Manager profile associates the user with a station on a Communication Manager that is in the core network. The Session Manager profile assigns the user's primary and secondary Session Managers, application sequences and survivability server.
Communication Profile Editor 4. In the New Communication Profile Values section, all fields initially have the default value as “Use existing values”. Modify the field values to be set as property values for the selected list of Communication Profiles. You cannot set the value for Primary Session Manager and Home Location fields as “None”. For adding a new value for the Home Location field, you need to add location using Routing > Locations menu selection. 5. Click Commit Changes to save the changes.
Configuring and monitoring Session Manager instances 5. Click Return to View All Profiles for returning to the original Communication Profile Editor screen. Communication Profile Editor field descriptions Session Manager Communication Profiles Name Description Login Name Full login name of the user and is a unique name that gives access to the system. Address: Handle Handle part of the Communication Address. Note: The displayed address can be either the “E.164 ” or the “Avaya E.
Communication Profile Editor Name Description will continue, locally, to the CM LSP resident with the Branch Session Manager. Note: If a termination or origination application sequence contains a CM application, the CM associated with the application must be the main CM for the CM LSP that is resident with the Branch Session Manager. Home Location A Home Location can be specified to support mobility for the currently displayed user.
Configuring and monitoring Session Manager instances Name Description Failed Edits Number of failed background edits during the job run. Last Updated Finish time of the background edit job run. Job Name Name of the background edit job. Button Description View Profile Edit Failures Shows the details of all Communication Profiles which could not be modified in the selected job run. It also states the reason for such editing failures.
Communication Profile Editor Name Description Profile in the event that the primary Session Manager is not available. Origination Application Sequence Defines application sequences for calls from this user. Termination Application Sequence Defines application sequences for calls to this user.
Configuring and monitoring Session Manager instances Button Description Commit Saves the changes to the selected Session Manager Communication Profiles. Cancel Cancels the changes to the selected Session Manager Communication Profiles. Network Configuration Local Host Name Resolution About Local Host Name Resolution Session Manager can locally resolve hostnames into an ordered set of (IP address, port, and transport) tuples and can assign priority and weights to each tuple.
Network Configuration 5. Enter host name information on the New Local Host Name Entries screen as follows. You can enter a maximum of ten host names. • Host Name (FQDN): Enter Fully Qualified Domain Name or IP address of the host. The host name entries override the information provided by DNS. • IP Address: IP address that the host name is mapped to. A host can be mapped to more than one IP addresses and each of these mappings are a separate entry.
Configuring and monitoring Session Manager instances their original versions by Avaya Inc. The modifications are Copyright Avaya Inc., All Rights Reserved.
Network Configuration Example A sample XML Schema file is provided below for reference purpose: www.domain1.com 192.168.1.100 1024 900 50 TLS www.domain2.com 192.168.
Configuring and monitoring Session Manager instances Button Description More Actions > Get Local Host Name Schema Allows you to get/retrieve the XML Schema for the current version of the Session Manager release. This enables you to understand the XML schema format for a creating new XML schema instance file for import purpose. Name Description Host Name (FQDN) Enter Fully Qualified Domain Name or IP address of the host. The host name entries override the information provided by DNS.
Network Configuration Name Description Port Port number that the host should use for routing using the particular IP address Priority If there are multiple IP address entries for a given host, Session Manager tries the administered IP addresses in the order of the priority. Weight If there are multiple IP address entries for a given host, and if some entries have the same priority, then for each priority level, Session Manager picks a host according to the specified weights.
Configuring and monitoring Session Manager instances Name Description Session Manager picks a host according to the specified weights. Transport The transport protocol that should be used for routing, such as TLS, TCP, or UDP. The default is TLS.
Network Configuration Configuring the SIP Firewall Procedure 1. On the System Manager console, under Elements, click Session Manager. 2. Click Network Configuration > SIP Firewall. 3. Click the Session Manager Instances button to display the list of Session Manager instances. 4. Select a Session Manager instance from the list. 5. Select More Actions to retrieve current, default, or backup configuration or to save a configuration as a backup configuration.
Configuring and monitoring Session Manager instances jdoe@avaya.com for a specific user, or @avaya.com for a domain of users. - FROM — String to look for in the “From” SIP Header in the SIP message. This string need not be an exact match with the “From” SIP header content and can be a subset of the string present in the “From” SIP Header. Its value can be a complete or partial SIP URI, for example, jdoe@avaya.com for a specific user, or @avaya.com for a domain of users.
Network Configuration from Session Manager SIP Server and are only applied to the incoming SIP traffic from Network. • 19.2.11.13.2 (added as a part of default rules) • Session Manager Management IP address 11. Click Save to save the SIP Firewall configuration. After saving, you can review the results of the configuration changes to the SIP Firewall using Monitoring > Logging from the System Manager navigation pane.
Configuring and monitoring Session Manager instances Name Description More Action > Save Configuration as backup Allows you to back up the configuration for the selected Session Manager instance. Rules Button Description New Opens the Rules page which enables you to define a new SIP firewall rule. Edit Opens the Rules page which enables you to edit the selected SIP firewall rule. Delete Allows you to delete a selected rule or rules. Up Allows you to move a selected rule up in the list.
Network Configuration Name Description drop the additional matching SIP packets for the duration of remaining period (as defined by the Threshold parameters). Log Type Allows you to specify if a log is to be generated or not, and if an alarm should be sent. You must specify Log Type when the Action Type is None.
Configuring and monitoring Session Manager instances Name Description need not be an exact match with the “From” SIP header content and can be a subset of the string present in the “From” SIP Header. Its value can be a complete or partial SIP URI, for example, jdoe@avaya.com for a specific user, or @avaya.com for a domain of users. Mask Specify the Subnet mask only when you have used the Remote IP address in the Key. This can be used to Blacklist an entire IP subnet.
Network Configuration Name Description the string present in the “From” SIP Header. Its value can be a complete or partial SIP URI, for example, jdoe@avaya.com for a specific user, or @avaya.com for a domain of users. Mask Subnet mask used for the whitelist operation. Button Description Save Saves the changed SIP firewall configuration settings. Related topics: Configuring the SIP Firewall on page 375 Blacklist SIP Blacklist enables you to block any known bad SIP elements.
Configuring and monitoring Session Manager instances Related topics: Specifying a new SIP Firewall rule on page 382 Rule page field descriptions on page 385 Deep inspection filtering on page 389 Denial of Service protection on page 389 SIP Firewall default rule set on page 390 Specifying a new SIP Firewall rule Procedure 1. On the System Manager console, under Elements, click Session Manager. 2. Click Network Configuration > SIP Firewall. 3. On the Firewall Configuration screen, under Rules, click New. 4.
Network Configuration • Remote IP Address—For any incoming SIP message, select Any to use the rule for all IP addresses, or select Specify to use the rule for a specific IP address. • IP Address—Type the IP address if you selected Specify for Remote IP Address. • Mask—Network mask for the specific IP address. • Remote Port—For any incoming SIP message, select Any to use the rule for all ports, select Specify to use a single port, or select Specify Range for a range of ports.
Configuring and monitoring Session Manager instances Firewall. Refer to the SIP Firewall Configuration Section in the Avaya Aura Security Guide for details and examples on using IP/SIP Layer Track • None—No tracking used. • Remote IP address—Track messages for a specific IP address of the remote host. • Local Port—Track messages for a specific local port. • From—Track messages for a specific sender. • To—Track messages sent to a particular receiver. • Contact—Track messages for a specific contact.
Network Configuration 10. Click Commit to save the rule or Cancel to cancel the changes. This does not save the SIP Firewall configuration to the Session Manager. To save the configuration to the Session Manager after creating or editing the configuration, return to the SIP Firewall Configuration screen and click Save.
Configuring and monitoring Session Manager instances Name Description sent. You must specify Log Type when the Action Type is None. • No — Do not save the rule to a log file • Yes — Save the rule to a log file • Alarm — If it is possible, generate an alarm when the rule conditions are met Log Message The message that should be logged when the log type is “Yes” or “Alarm” IP Layer Match Options: 386 Name Description Protocol Allows you to select the protocol for which the rule is to be used.
Network Configuration SIP Layer Match Options: Button Description New Allows you to create up to five SIP layer match options Delete Deletes the selected SIP layer match options Name Description KeyType Allows you to select the key type that the rule should match from the list. You can add up to five key type match options. If more than one match options are defined, then logically, AND of the options is used to create a search pattern.
Configuring and monitoring Session Manager instances Name Description Configuration Section in the Avaya Aura Security Guide for details and examples on using IP/SIP Layer Track. • None — No tracking required • Remote IP address — Track messages for a specific IP address of the remote host. • Local Port — Track messages for a specific local port • From — Sender of the message • To — Receiver of the message • Contact ——Track messages for a specific contact.
Network Configuration Name Description option is suitable for creating SIP Firewall filtering rules for SIP telephones that are directly connected to Session Manager. • NRP Trusted SIP Entity: If this option is selected, SIP Firewall rule is matched against the incoming SIP traffic from entities that are marked as Trusted SIP Entity in the Routing Policy.
Configuring and monitoring Session Manager instances then blocked until the configured timeout expires. Refer to the section Specifying a new SIP Firewall rule for details on how to configure the Rate Block rules. • Signature Detection—A rule may be configured to perform signature detection and drop those packets matching signature. Both simple and regular-expression string searching is supported across the entire SIP header region of the message or across the full message (headers and body).
Device and Location Configuration the terminal is set up for the first time, it is set up with a pre-provisioned group called Default Group which provides the global settings across locations and terminals. A terminal can be individually associated with a set of Device Settings which are downloaded and set as per the following criteria.
Configuring and monitoring Session Manager instances 2. Click Device and Location Configuration > Device Settings Groups to open Device Settings Groups page. The Device Settings Groups page displays the list of Device Settings Groups. 3. Click New > Location Group to open the Device Settings Group screen. 4. On the Device Settings Group screen, enter the appropriate information about the Location Group. 5. Click Save to create a Location Group. 6.
Device and Location Configuration Removing Device Settings Groups - Location Groups About this task You cannot delete the default Location Device Settings Group. Procedure 1. On the System Manager console, under Elements, click Session Manager. 2. Click Device and Location Configuration > Device Settings Groups to open Device Settings Groups page. The Device Settings Groups page displays the list of Device Settings Groups. 3.
Configuring and monitoring Session Manager instances Modifying a Device Settings Group - Terminal Group About this task You can modify only one Terminal Device Settings Group at a time. Procedure 1. On the System Manager console, under Elements, click Session Manager. 2. Click Device and Location Configuration > Device Settings Groups to open Device Settings Groups page. The Device Settings Groups page displays the list of Device Settings Groups. 3.
Device and Location Configuration Purpose and usage of SIP subscriptions SIP Subscription and Notification requests update connected SIP endpoints on state changes related to services that the endpoints consume. For example, when a new voice message arrives in a mailbox, Session Manager sends a SIP notification request to notify the related endpoints about the arrival of a new voice mail message. For an endpoint to receive SIP notifications, it first needs to subscribe to the relevant subscription package.
Configuring and monitoring Session Manager instances Name Description Description Shows the details of Terminal Device Settings Group. Button Description Edit Opens the Device Settings Group page that allows you to modify the selected Terminal Device Settings Group. New Opens the Device Settings Group page that allows you to create a new Terminal Device Settings Group. Delete Allows you to delete the selected Terminal Device Settings Group.
Device and Location Configuration Device Settings Group - Default Group field descriptions General section Name Description Name Specifies a non—editable field as Default Group. Description Specifies a non—editable field as Default Group. Group Type Specifies a non—editable field as Location Group Terminal Group Number Specifies a non—editable field.
Configuring and monitoring Session Manager instances Name Description proceeds to another proxy. The range is 0 to 32 seconds. (0 disables this feature.) The default value is 2. Maintenance Settings section Name Description IP Address For SNMP Queries Specifies the IP address of a server that can query the phone for SNMP messages. This server must have the correct community string. If this field is blank, any server can query the phone. SNMP Community Specifies the SNMP community name.
Device and Location Configuration Volume Settings section Name Description Receiver Volume Sets the volume in the handset rather than the speaker. This is a required field and range is 0-10. The default value is 5. Ringer Cadence Sets the cadence of the ring tone. This is a required field and range is 1-8. The default value is 3. Ringer Volume Sets the ringer setting for the stations bridged appearance buttons. This is a required field and range is 1-10. The default value is 5.
Configuring and monitoring Session Manager instances Name Description Registration Expiration Timer (secs) Specifies the maximum duration as 3600 and minimum duration as 60 seconds for a SIP server to keep a SIP client as registered. Assigned Location section Name Description Name Is the name of the location to which the Device Group Settings is associated. Button Description Restore Restores the earlier device settings. Cancel Cancels the modified device settings.
Device and Location Configuration Name Description appearance can be reserved for. If no value is entered, the default value is 30 seconds. Reactive Monitoring Interval (secs) Specifies the duration after which (in seconds) the phone attempts to REGISTER with a proxy server when it is not reachable/ available. Range is 10 to 3600 seconds. The default is 60 seconds.
Configuring and monitoring Session Manager instances VoIP Monitoring Manager section Name Description IP Address Specifies the IP address of the Avaya Voice over IP Monitoring Manager server. Port Specifies the port used by the Avaya Voice over IP Monitoring Manager server. The range is 1 through 65,535. The default is 5005. Reporting Period Specifies how often an endpoint should send its RTCP packets to the Avaya Voice over IP Monitoring Manager server. The range is 5 through 30 seconds.
Device and Location Configuration Location Settings Location Settings Location Settings module enables you to assign a Device Setting Group to a Location. Viewing location settings Procedure 1. On the System Manager console, under Elements, click Session Manager. 2. Click Device and Location Configuration > Location Settings to open Location Settings page. The Location Settings page displays the list of location settings.
Configuring and monitoring Session Manager instances Name Description Device Setting Group Name of the Device Setting Group. Button Description Save Saves the Location Settings. Related topics: Viewing location settings on page 403 Modifying Location Settings on page 403 Application Configuration Applications About Applications Application entries allow you to define and manage single applications with application attributes for inclusion into one or more application sequence.
Application Configuration Creating an application Before you begin Creating a new application entry requires that a non-Session Manager SIP entity first be administered. Refer to the topic “Creating SIP entities” to create the SIP entity. Procedure 1. On the System Manager console, under Elements, click Session Manager. 2. Click Application Configuration > Applications to open the Applications page. 3. Click New. The Application Editor page appears. 4.
Configuring and monitoring Session Manager instances Removing applications About this task You cannot delete an application if it is a member of an Application Sequence. If you try to delete it, a warning appears, and the application entry remains. Procedure 1. From the navigation pane on the System Manager Common Console, click Elements > Session Manager > Application Configuration > Applications to open the Applications screen. 2. Select one or more applications and click Delete .
Application Configuration Modifying an application on page 405 Removing applications on page 406 Application Editor field descriptions Application Editor section Name Description Name Name of the application entries. This is a mandatory field. SIP Entity List of previously provisioned SIP entities. This is a mandatory field. CM System for SIP Entity List of previously provisioned CM systems. This is a mandatory field.
Configuring and monitoring Session Manager instances Related topics: Creating an application on page 405 Modifying an application on page 405 Application Sequences Application Sequences Application Sequence enables defining and managing an ordered set of applications used in call sequencing.
Application Configuration 2. Click Application Configuration > Application Sequences to open the Application Sequences page. The Application Sequences page displays the list of Application Sequences. 3. Click New. The Application Sequence Editor page appears. 4. Enter the appropriate information. 5. Click Commit to create the Application Sequence.
Configuring and monitoring Session Manager instances Procedure 1. On the System Manager console, under Elements, click Session Manager. 2. Click Application Configuration > Application Sequences to open the Application Sequences page. The Application Sequences page displays the list of Application Sequences. 3. Select one or more application sequence and click Delete . Delete Confirmation page appears. 4. Click Delete to remove the selected application sequences.
Application Configuration Adding Applications in an existing Application Sequence Procedure 1. On the System Manager console, under Elements, click Session Manager. 2. Click Application Configuration > Application Sequences to open the Application Sequences page. 3. Select an application sequence and click Edit to open the Application Sequence Editor page. 4. In the section Available Applications, click the + button to add the application to the application sequence at the end.
Configuring and monitoring Session Manager instances Rearranging Applications in an Application Sequence on page 410 Adding Applications in an existing Application Sequence on page 411 Application Sequence Editor field descriptions Sequence Name section Name Description Name Name of the application sequence. This is a mandatory field. Description Shows the details about the application sequence .
Application Configuration Name Description Description Shows the description of the application Button Description Cancel Cancels the changes made to the application sequence. Commit Saves the changes made to the application sequence.
Configuring and monitoring Session Manager instances Creating an Implicit User Rule Procedure 1. On the System Manager console, under Elements, click Session Manager. 2. Click Application Configuration > Implicit Users to open Implicit Users page. 3. Click New. The Implicit User Rule Editor page appears. 4. On the Implicit User Rule Editor page, enter the appropriate information. 5. Click Commit to create a new Implicit User rule.
Application Configuration 3. Select one or more Implicit User rules and click Delete to delete one or more Implicit User rules respectively . Delete Confirmation screen appears. 4. On the Delete Confirmation screen, click Delete to remove the selected Implicit User rules. Related topics: Implicit User Rules field descriptions on page 415 Implicit User Rules field descriptions Name Description Pattern Shows the dial pattern with the same pattern format as the Routing Policy Dial pattern.
Configuring and monitoring Session Manager instances Implicit User Rule Editor field descriptions The Implicit User Rule Editor screen enables you to define a new pattern rule or to modify an existing pattern rule. Name Description Pattern Shows a dial pattern with the same pattern format as the Routing Policy Dial pattern. This is a mandatory field. Min Shows the minimum value of the dial pattern matching. Valid values are 1-36. This is mandatory field.
Application Configuration provided by Nortel Network Routing Service (NRS). The NRS provides following three services: • SIP Proxy Server (SPS): SPS performs two roles in CS1000-based configuration. These roles are SIP routing proxy and SIP registrar. • Network Connect Server (NCS): NCS supports the centralized CS1000 solution for IP clients, that is, IP phones. • H.323 Gatekeeper (GK): GK provides typical H.323 gatekeeper functions to H.323 endpoints in the solution.
Configuring and monitoring Session Manager instances 5. Create an NRS Proxy User Rule. Creating Terminal Proxy Server instance Procedure 1. On the System Manager console, in Elements, click Inventory. 2. From the left navigation pane, click Inventory > Manage Elements. 3. On the Manage Elements page, click New and select a “CS 1000 Terminal Proxy Server” entity instance. 4.
Application Configuration Modifying NRS Proxy User Rule Procedure 1. On the System Manager console, in Elements, click Session Manager. 2. To open the NRS Proxy Users page, click Application Configuration > NRS Proxy Users. 3. Select the NRS Proxy User Rule to be modified and click Edit. 4. On the NRS Proxy User Rule Editor page, modify the information and click Commit to save the changes. Note: Terminal Proxy Server must be administered using Elements > Inventory > Manage Elements.
Configuring and monitoring Session Manager instances NRS Proxy Users field descriptions Name Description Pattern User Pattern type. Primary Terminal Proxy Server The administered Terminal Proxy Server. This field is a required field. Secondary Terminal Proxy Server The administered Terminal Proxy Server. Survivable Terminal Proxy Server The administered Terminal Proxy Server. Button Description New Adds a new entry. Edit Saves the changes of the modified entry.
System Status Name Description force a specific length match. For example, 5703360#. • Wild card: The wild card digit character "?" can be appended to a basic digit entry. Multiple wild cards may be appended, but each wild card character matches only one digit. For example, 57033??. Primary Terminal Proxy Server Select an administered Terminal Proxy Server. This field is a required field. Secondary Terminal Proxy Server Select an administered Terminal Proxy Server.
Configuring and monitoring Session Manager instances up. An entity is down if all of its addresses are down. An entity is partially up if some, but not all, of its addresses are up.
System Status SIP Entity Link Monitoring Status Summary page field descriptions Button Description Entity Link Status for All Session Manager Instances: Run Monitor Starts asynchronous demand monitor test for the selected Session Manager instances. Refresh link refreshes the status of the entity links for all administered Session Manager instances.
Configuring and monitoring Session Manager instances Button Description entity links from all Session Manager instances to a single SIP entity. SIP Entity, Entity Link Connection Status page field descriptions Link Description Refresh Refreshes and displays the detailed connection status for all entity links from the selected Session Manager instance to a single SIP entity.
System Status Session Manager Entity Link Connection Status page field descriptions Link Description Refresh Refreshes and displays all entity links for a connection that is down for the selected Session Manager. The status displays the following details: • Name of the SIP entity. Clicking the name field for a SIP entity opens the SIP Entity, Entity Link Connection Status page for that SIP entity.
Configuring and monitoring Session Manager instances Managed Bandwidth Usage About Managed Bandwidth The Managed Bandwidth Usage displays Managed Bandwidth (Call Admission Control) realtime data. Measurement of bandwidth usage helps administrators to manage networks with multimedia calls. It displays a read-only table containing one row for each administered location and provides details on actual call counts and bandwidth usage for audio and video calls respectively.
System Status Button Description Details to show or hide the detailed usage for that location. • Location : Locations that you have administered in Routing Policy. • Audio Call Count : Sum of audio calls of Session Manager in a given location. • Audio BW Used : Sum of bandwidth used for audio calls of Session Managers in a given location. • Multimedia Call Count : Sum of multimedia calls of Session Managers in a given location.
Configuring and monitoring Session Manager instances Button Description • Audio BW Used : Sum of bandwidth used by audio calls terminated by the selected Session Manager for the given location. • Multimedia Call Count : Number of multimedia calls terminated by the selected Session Manager for the given location. • Multimedia BW Used : Sum of bandwidth used by multimedia calls terminated by the selected Session Manager for the given location.
System Status • Synchronize – verifies that the administered configuration matches the actual configuration stored on the security module. This action should be performed anytime the values in the security module statistics table do not match the administered data. • Update Installed Certificates – provides the capability of switching the active certificate being used by the security module to the default certificate.
Configuring and monitoring Session Manager instances b. Click the Synchronize button. c. Click the Refresh button to see the latest status. 6. If the status is still Down, reset the security module: a. Select the appropriate Session Manager instance in the Session Manager list. b. Select the Reset button. Warning: The Session Manager cannot process calls while the security module is being reset . 7. Select the Refresh button to see the latest status.
System Status Button Description • NIC Bonding—Shows whether NIC bonding is “enabled” or “disabled”. • Entity Links (expected / actual)—The expected value is the number of SIP Entities configured in Routing Policy which have Entity Links to the Session Manager. The actual value is the number of Entity Links currently configured on the security module. If these values do not match, then the Synchronize action should be performed. Reset Opens the Security Module Reset Confirmation page.
Configuring and monitoring Session Manager instances • identification of whether Session Manager is required to be taken out of service • determination of whether links are secured or not • viewing of link details and statistics Monitoring Connection Links Procedure 1. On the System Manager console, under Elements, click Session Manager. 2. Click System Status > Security Module Status to open the Security Module Status page. 3.
System Status Connection List section This section shows basic information of all the active connections. Name Description Details Shows detailed information about the selected connection link in the Connection Details section. Type Link type. Local IP Local IP address. Local Port Local SM100 port. Remote IP Remote IP address. Remote Port Remote port. Remote FQDN Remote FQDN. Transport Transport protocol (UDP, TCP, TLS). Policy Security Policy.
Configuring and monitoring Session Manager instances Registration Summary Registration Summary This module enables you to view the registration status for all AST devices registered to the selected Session Manager Instance.
System Status Rebooting of selected AST devices Procedure 1. On the System Manager console, under Elements, click Session Manager. 2. Click System Status > Registration Summary to open Registration Summary page. The Registration Summary page displays the list of registered devices. 3. Select the AST Device and click Reboot. The Confirm Reboot Notification page appears. 4. On the Confirm Reboot Notification page, click Confirm. 5.
Configuring and monitoring Session Manager instances After user confirmation a status page appears showing the detailed information regarding the current state of scheduled and running endpoint actions. Related topics: Registration Summary on page 434 Failback of selected AST devices Procedure 1. On the System Manager console, under Elements, click Session Manager. 2. Click System Status > Registration Summary to open Registration Summary page.
System Status Registration Summary field descriptions Button Description Reboot Reboots selected AST devices. Reload Complete Forces complete reload of selected AST devices. Reload Config Reloads only configurations of selected AST devices. Reload Contacts Reloads only contacts of selected AST devices. Failback Enable devices to failback to Primary Session Manager. Name Description Session Manager Shows the name of the Session Manager Instance.
Configuring and monitoring Session Manager instances Name Description Total Registered Show the total count of registrations for this Session Manager or for Branch Session Manager. Total AST Show the total count of registrations which are “Active Controller” registrations for this Session Manager or for Branch Session Manager. Total Admin Show the total count of Communication Profiles what are administered to this Session Manager or for Branch Session Manager.
System Status 4. Click Refresh to retrieve the latest user registration summary results.
Configuring and monitoring Session Manager instances Rebooting of selected AST devices Procedure 1. On the System Manager console, under Elements, click Session Manager. 2. Click System Status > User Registrations to open User Registrations page. The User Registrations page displays the list of registered users. 3. Click to select the AST Devices and click Reboot. The Confirm Reboot Notification page appears. 4. On the Confirm Reboot Notification page, click Confirm. 5.
System Status After user confirmation a status page appears showing the detailed information regarding the current state of scheduled and running endpoint actions. Related topics: User Registrations field descriptions on page 442 Failback of selected AST devices Procedure 1. On the System Manager console, under Elements, click Session Manager. 2. Click System Status > User Registrations to open User Registrations screen. The User Registrations screen displays the list of registered users. 3.
Configuring and monitoring Session Manager instances User Registrations field descriptions Customize Column Display section 442 List Description Available Columns Shows list of available columns. Display Columns Shows list of selected columns. Link Description Customize Expands Customize Column Display section. Move Moves selected items from Available Columns list to the Display Columns list. Move All Moves all items from Available Columns list to the Display Columns list.
System Status AST Device Notifications: section The label As of (time) indicates the time of the last update of information for the AST Device Notifications section. Button Description Reboot Reboots selected AST devices. Reload Complete Forces complete reload of selected AST devices. Reload Config Reloads only configurations of selected AST devices. Reload Contacts Reloads only contacts of selected AST devices. Failback Enable devices to failback to Primary Session Manager.
Configuring and monitoring Session Manager instances Name Description Registration Address The Communication Address/handle user logged in with. All Addresses All of the SIP Communication Addresses the user has administered. Primary SM Indicates administered primary Session Manager in the user's Communication Profile. Secondary SM Indicates administered secondary Session Manager in the user's Communication Profile.
System Tools System Tools Maintenance Tests About Maintenance Tests The Maintenance Tests page allows you to perform maintenance tests on the System Manager server and administered Session Manager instances. These maintenance tests test functionality of the System Manager and Session Manager servers.
Configuring and monitoring Session Manager instances Button Description You can run the following maintenance tests for a Session Manager: • Test replication to System Manager Status • Test Call Processing status • Test Service Hosts status • Test Service Director Status • Test Management Server • Test sanity of Secure Access Link (SAL) agent • Test management link functionality • Test Security Module Status • Test postgres database sanity Execute All Tests Runs all the maintenance tests on the selected
System Tools 1. An upgrade or install is in progress. 2. The server could be down. Check the log, then check Log Event Codesfor the appropriate troubleshooting action. 3. There is a network outage. Run a ping test between the System Manager and the failing Session Manager to verify network connectivity. Test data distribution and redundancy link This test only runs on the Session Manager.
Configuring and monitoring Session Manager instances Test sanity of Secure Access Link (SAL) agent This test can run on either System Manager or Session Manager. It checks if the Security Access Link agent is running or not on the server. If the link is up and running, the test passes. If the test fails, run the statapp command and other corrective actions for associated alarms on the Session Manager before escalating to Avaya Technical Support.
System Tools SIP Tracer Configuration About Tracer Configuration You can use the Tracer Configuration page to configure the tracing of SIP messages incoming through the security module, SIP messages outgoing from the security module, and also messages dropped by ASSET proxy or by the SIP firewall. You can also filter these messages based on the user or the call. Session Manager logs all the traced messages to a file based on the configuration.
Configuring and monitoring Session Manager instances Name Description Manager uses Syslog protocol for sending the SIP traffic (as used currently for SIP Tracing). Remote Server FQDN or IP Address FQDN or IP address of the remote syslog server.
System Tools Name Description Source Filter SIP messages based on the source address. Destination Filter SIP messages based on the destination address. Max Message Count Value for maximum number of messages matching the filter that Session Manager should trace. Default is 25 messages. Call Filter Button Description New Create a new filter for filtering all SIP messages that start a new call. You can define a maximum of three call filters. Delete Delete a selected call filter or filters.
Configuring and monitoring Session Manager instances Name Description Request URI Filter calls based on the called party (URI address). A valid Request URI format, for example, is .@192.111.11.111. Session Manager Instances Name Description Name Select one or more configured Session Managers for which the specific filters should be used. Note: If you select only one Session Manager from this list, the Read button is activated.
System Tools For details, refer to the section Tracing in Maintaining and Troubleshooting Avaya Aura®™ Session Manager (03-603325) Trace Viewer page field descriptions Use the From and To fields to specify a range of days or time as follows: Filter Name Description From: Date Date from which you want to filter the trace logs From: Time Time from which you want to filter the trace logs From: Time Zone Time Zone for the From date that you want to use for filtering trace logs To: Date Date up to wh
Configuring and monitoring Session Manager instances 454 Button Description Show dropped messages Displays dropped message in the trace log entries More Actions > Export Trace Viewer Overview Creates a tabulator-separated plain text file with all of the overview columns of the Trace Viewer page. You can open this file with editors such as Wordpad and Excel. The More Actions button is active only if trace records are listed. The retrieved Trace Viewer list can be saved into a file at the client side.
System Tools Button Description Session Manager list for the selected date range. This output displays the following details: Note: Number of retrieved records shows the number of records that matched the filter criteria. If Session Manager displays fewer records than this number, it means that not all the matching records are displayed. Usually this is done to avoid problems caused by running out of memory.
Configuring and monitoring Session Manager instances Name Description address of a SIP Entity. You can enter any IP address that you require, but make sure that it is recognized by Session Manager. If it is not, Session Manager considers it to have come from a non-trusted host and rejects it. Called Party URI The SIP URI of the called party. You must specify a handle and a domain, for example, sip:5551000@companydomain.com. You can also specify a full URI such as sip: 5555555@domain.
System Tools Button Description Each line displays not only where the INVITE would be routed, but also what the adapted digits and domain would be. The Routing Decision Process box contains details about how Session Manager made the routing decisions. This gives you a tool to check your routing algorithms.
Configuring and monitoring Session Manager instances 458 Administering Avaya Aura ® Session Manager Comments? infodev@avaya.
Chapter 7: Managing events Managing alarms Alarming The Alarming service provides an interface for monitoring alarms generated by System Manager and other components. You can: • View an alarm. • Change the status of an alarm. • Export alarms to a Comma Separated Values (.csv) file through the Alarming service. System Manager generates alarms to notify users of system events. Alarms are classified by their effect on system operation and they identify the system component which generated the alarm.
Managing events Changing status of an alarm The status of an alarm can be: • Acknowledged: Maintenance support must manually set the alarm to this state, indicating the alarm is under investigation. • Cleared: Maintenance support must manually set the alarm to this state, indicating that the error condition has been resolved. Procedure 1. On the System Manager console, under Services, click Events. 2. Click Alarms in the left navigation pane. 3.
Managing alarms Procedure 1. On the System Manager console, under Services, click Events. 2. On the Alarming page, select the alarms you want to filter. 3. Click Filter: Enable at the top right corner of the Alarm List table. 4. Select the filter criteria you want to apply to the selected alarms. The Status and Severity fields have drop-down menus. You can enter the alarm code in the Message field to find all alarms which contain a particular alarm code. 5. Click Filter: Apply.
Managing events 6. Click Search to find alarms for the given search conditions. Alarming field descriptions The Alarming page displays a list of alarms. Use this page to view the alarms in the AutoRefresh mode. In this mode, the page updates the alarm information automatically. Field Description Time Stamp Specifies the date and time when the alarm is generated. Severity Specifies the severity of the alarm. Status Specifies the current status of the alarms.
Managing alarms Field Description Severity Specifies the severity of the alarm. Status Specifies the current status of the alarms. Host Name / SysName Specifies the name of the host server that generated the alarm. In case of trap listener, this column specifies the system name. Source IP Address Specifies the IP address of the system that generated the alarm. Message A short description of the problem that generated the alarm.
Managing events Button Description Refresh Refreshes the log information in the table. Filter: Enable Displays fields under select columns that you can use to set filter criteria. This is a toggle button. Filter: Disable Hides the column filter fields without resetting the filter criteria. This is a toggle button. Filter: Clear Clears the filter criteria. Filter: Apply Filters alarms based on the filter criteria. All Selects all the alarms in the table. None Clears the check box selections.
Managing alarms Name Description • Identifier: Searches all of the alarms that match the specified identifier. • Message: Searches all of the alarms that match the specified message. • M/E Ref Number: Searches all of the alarms that match the specified M/E Ref Number. The operators available are based on the search criterion that you select in the first drop-down field.
Managing events Button Description Search Searches the alarms based on the search conditions. Close/Advanced Search Hides the search fields. + Adds a search condition. - Deletes a search condition. Managing logs Logging The logging service provides an interface for viewing logs and their details generated by System Manager or other components. The System Manager console allows you to monitor log messages. The log viewer displays a list of logs.
Managing logs Debug.Station Debug Station loggers gather debug information for station management related operations. Debug.Template Template Debug loggers gather debug information for template management related operations. Debug.CM CM debug loggers gather debug information for communication between Communication Manager and the Communication System Management server. Debug.NCM NCM debug logger gathers debug information related to Element Cut Through. Debug.
Managing events 2. Click Logs > Log Viewer in the left navigation pane. 3. On the Logging page, click Advanced Search. 4. In the Criteria section, from the first and second drop-down fields, select the search criterion and the operator. 5. Select or enter the search value in the third field. 6. If you want to add another search condition, click + and repeat the steps 4 through 6. Click - to delete a search condition. You can delete a search condition only if you have more than one search condition. 7.
Managing logs Logging field descriptions The Logging page has two sections. The upper section contains buttons that allow you to view the details of the selected logs, search for logs, and set filters. The lower section displays logs in a table. The table provides information about the logs. You can click the title of the column to sort the data of the column in ascending or descending order. Name Description Select check box Use this check box to select a log.
Managing events Name Description the log. For a log with severity level debug, the message contains information about debugging an error. Process Name Process on the device that has generated the message. This is usually the process name and process ID. Facility The operating system, processes, and applications quantify messages into one of the several categories. These categories generally consist of the facility that generated them, along with the severity of the message.
Managing logs Button Description Previous Displays logs in the previous page. This button is not available if you are on the first page. Next Displays logs in the next page. This button is not available if you are on the last page. Criteria section This section appears when you click Advanced Search on the top right corner. Name Description Criteria Use this section to specify search conditions. Select the search criteria from the first dropdown field.
Managing events Name Description selected criterion are displayed in the second drop-down field. The following are the list of operators: • Equals • Not Equals • Starts With • Ends With • Contains The operators for Time Stamp are: =, >, <, >=, <=, and !=. When you select Time Stamp from the first drop-down field, the page provides date and time fields for entering the date and time in the respective fields. Enter the date in MM/ DD/YYYY format . You can select the date from the calender.
Managing logs Name Description Log ID Unique identification number that identifies the log. Time Stamp Date and time of the log generation. Host Name Name of the system from which the log is generated. Product Type A code which uniquely identifies the component which generated the log. For example, product, device, application, service and so on. GW600, which is a product type code identifier is an example of the log product type. Severity Severity level of the log.
Managing events Name Description them, along with the severity of the message. The following are the types of supported facilities: • User-Level Messages • Security/authorization • Log Audit 474 Button Description Logging Landing Page Switches the mode from Auto-Refresh to manual refresh and displays the Logging Home page. This is a toggle button. Administering Avaya Aura ® Session Manager Comments? infodev@avaya.
Chapter 8: Managing system data Administering backup and restore Backup and Restore The backup and restore functions are executed through System Manager. With these functions, you can back up and restore configuration data for System Manager and all of the Session Manager instances. All of the configuration data for the entire system is kept centrally on System Manager. This means that individual backups of the Session Manager instances are not needed.
Managing system data Scheduling a data backup on a local server Procedure 1. On the System Manager console, under Services, click Backup and Restore. 2. On the Backup and Restore page, click Backup. 3. On the Backup page, Click Local option. 4. In the File name field, enter the name of the backup file that you want to create. 5. Click Schedule. 6. Click Commit. Restoring a data backup from a local server Procedure 1. On the System Manager console, under Services, click Backup and Restore. 2.
Administering backup and restore Modifying data retention rules Procedure 1. On the System Manager console, under Services, click Configurations. 2. Click Data Retention in the left navigation pane. The system displays the Data Retention page with the Rule list. 3. Select a rule from the Rule list. 4. Click Edit. 5. Modify the value in the Retention Interval (Days) field. 6. Click Update to save the value. Accessing the Data Retention Rules service Procedure 1.
Managing system data Assigning an appender to a logger About this task The appender where logger logs the log messages. Procedure 1. On the System Manager console, under Events, click Logs. 2. Click Log Settings in the left navigation pane. 3. On the Log Settings page, select a log file from the Select Log File field. 4. Click a logger in the Logger List section. 5. Click Edit. 6. On the Edit logger page, click Attach in the Attached Appenders section. 7.
Administering backup and restore Modifying an appender Procedure 1. On the System Manager console, under Events, click Logs. 2. Click Log Settings in the left navigation pane. 3. On the Logging Configuration page, click a log file from the Select Log File field. 4. Click a logger in the Logger List section. 5. Click Edit. 6. On the Edit logger page, click an appender in the Attached Appenderssection. 7. Click Edit. 8. On the Edit Appender page modify the appender information.
Managing system data Name Description File Name Specifies the name of the backup file. Path Specifies the path of the backup file. Status Indicates the status of the backup. The values are: • SUCCESS • FAILED Backup Time Specifies the time of backup. Backup Mode The mode defines whether the backup is manual or automatic. Backup Type The type defines whether the backup is a local or remote backup. User The user who has performed the backup. Button Description Backup Opens the Backup page.
Administering backup and restore Name Description File Name Specifies the name of the file that identifies the backup. If you specify only the file name, System Manager creates a backup file in the home directory of the specified user. If you want to create the backup file in a directory other than the home directory, specify a complete path including the file name. The page displays the following fields when you choose to create a backup of System Manager data on a remote computer.
Managing system data Job Details Name Description Job Name Specifies the name of the job. Job Frequency Name Description Task Time Specifies the date and time of running the job. Recurrence The settings define whether the execution of the jobs is a recurring activity or a one time activity. In case of a recurring job, the field also displays the time interval of recurrence. The options are: • Execute task one time only. • Task are repeated.
Administering backup and restore Name Description Type Specifies the type of computer from which you want to restore the application data. The options are: • Local: The data is restored from a local machine. • Remote: The data is restored from a remote machine. The page displays the following fields, when you select Local as Type. Name Description File Name Specifies the name of the backup file that you want to restore. Select File Name Lists the name of the backup file that you want to restore.
Managing system data Name Description Option button Provides the option to select a data retention rule. Rule Name Specifies the name of the rule. Rule Description A brief description about the data retention rule. Retention Interval (Days) Specifies the number of days the data is retained. Button Description Edit Modifies the selected rule. Update Updates the rule with changes made to the rule. Cancel Cancels the editing operation. Apply Applies the selected rule.
Administering backup and restore Name Description Attached Appenders > host The name of the syslog host where the log output is stored. Show All Provides you an option to select the maximum number of logger records that you can view at a time. Button Description Edit Opens the Edit Logger page that you can use to edit loggers. Edit Logger field descriptions Use this page to edit logger and appender information. You can also add and remove appenders from the loggers.
Managing system data Name Description Facility The process running on the machine for which log messages are created. Host The name of the syslog host that stores the log output. Header The header part of the syslog packet. The header part contains timestamp and host name information. Facility Printing The printed message includes the facility name of the application. Button Description Edit Opens the Edit Appender page. Use this page to modify the appender information.
Administering backup and restore Name Description File Path The path of the file where the appender logs the information. Max File Size The maximum KB, MB, and GB reserved for the appender file. # Backup Files The number of log files that an appender can use to store log information if one log file becomes full. If all the backup files are full, the appender overwrites the previous backup files in the order the files are created. Button Description Commit Saves the changes to the database.
Managing system data Data Replication Service Data Replication Service The Data Replication Service replicates data from the master database residing on the server. The Data Replication Service supports the following two modes of replication: • Replication in Repair mode: In repair mode, the Data Replication Service replicates all of the requested data from the master database to the database of the replica node.
Data Replication Service Viewing replica nodes in a replica group You can view the replica nodes in a group. Procedure 1. On the System Manager console, under Services, click Replication. The system displays the Replica Groups page. 2. Select a replica group and click View Replica Nodes. Alternatively, you can click a replica group name displayed under the Replica Group column to view the replica nodes for that replica group. The Replica Nodes page displays the replica nodes for the select group.
Managing system data Repairing all replica nodes in a replica group You can replicate data for all the replica nodes that are in a group. You can perform this operation if replica nodes in a group are not synchronized with the System Manager database. Procedure 1. On the System Manager console, under Services, click Replication. The system displays the Replica Groups page. 2. Select a replica group for which you want repair the replica nodes from the table displaying replica groups. 3. Click Repair.
Data Replication Service Removing a replica node Procedure 1. On the System Manager console, under Services, click Replication. The system displays the Replica Groups page. 2. Select a replica group in which you want to remove a node. 3. On the Replica Node page, click Remove. Removing a replica node from queue Procedure 1. On the System Manager console, under Services, click Replication. The system displays the Replica Groups page. 2.
Managing system data Name Description Synchronization Status Replication status of the replica group. The system displays the out of sync status if any one of the group replica databases is not synchronized with the master database. Button Description View Replica Nodes Opens the Replica Nodes page. You can use this page to view replica nodes for a selected group. Repair Replicates data for a selected replica node that is not synchronized with the master nodes.
Data Replication Service Name Description • Repairing: This status indicates that the data replication process is in progress. The color code of the status is yellow. • Synchronized: This status indicates that the data requested by the replica node is successfully replicated from the master database to the database of the replica node. The color code of the status is green. • Synchronization Failure: This status indicates an error in data replication for the initial load.
Managing system data Data Replication field descriptions General Name Description Replica Node Group Name of the group of the replica server. Replica Node Host Name The IP address of the replica server. Last Synchronization Time The last time and date when the data synchronization or replication happened for the replica node. Synchronization Status The synchronization status of the replica server.
Managing scheduled jobs Managing scheduled jobs Scheduler Scheduler is a schedule management service that provides the ability to monitor the tasks that are scheduled for execution. The scheduled tasks are of three types: • System scheduled: The job scheduled for the normal operation of the application. The system administrator can reschedule and stop a system schedule job, but cannot delete the job. • Admin scheduled job: The job that the administrator schedules for administering the application.
Managing system data Viewing pending jobs Procedure 1. On the System Manager console, under Services, click Scheduler. 2. Click Pending Jobs in the left navigation pane. Related topics: Pending Jobs field descriptions on page 502 Viewing completed jobs Procedure 1. On the System Manager console, under Services, click Scheduler. 2. Click Completed Jobs in the left navigation pane. The Completed Jobs page displays completed jobs.
Managing scheduled jobs Viewing details of a completed job Procedure 1. On the System Manager console, under Services, click Scheduler. 2. Click Completed Jobs in the left navigation pane. 3. On the Completed Jobs page, select a completed job and click View. The Job Scheduling-View Job page displays the details of the selected job. Viewing details of a pending job Procedure 1. On the System Manager console, under Services, click Scheduler. 2. Click Pending Jobs in the left navigation pane. 3.
Managing system data ii. On the Completed Jobs page, select a completed job and click More Actions > View Log. Result The log viewer displays the log details for the selected job. Viewing completed jobs Procedure 1. On the System Manager console, under Services, click Scheduler. 2. Click Completed Jobs in the left navigation pane. The Completed Jobs page displays completed jobs. Related topics: Completed Jobs field descriptions on page 505 Filtering Jobs Procedure 1.
Managing scheduled jobs Note: The system displays this field only for the completed jobs. 9. Click Apply. The system displays jobs that match the filter criteria. Result Editing a job Procedure 1. On the System Manager console, under Services, click Scheduler. 2. Perform one of the following steps: • To edit a pending job, perform the following steps: i. Click Pending Jobs in the left navigation pane. ii. On the Pending Jobs page, select a pending job and click Edit.
Managing system data Deleting a job Before you begin You must log in as an administrator to delete an administrator scheduled job. About this task Use this functionality to delete an obsolete job. You can delete an On demand and an administrator scheduled job. Note: You can remove only jobs that are of type Schedule On Demand. Procedure 1. On the System Manager console, under Services, click Scheduler. 2. Perform one of the following steps: • To remove a pending job, perform the following steps: i.
Managing scheduled jobs Disabling a job About this task Use this functionality to make a job inactive. Procedure 1. On the System Manager console, under Services, click Scheduler. 2. Perform one of the following steps: • To disable a pending job, perform the following steps: i. Click Pending Jobs in the left navigation pane. ii. On the Pending Jobs page, select a pending job and click More Actions > Disable. • To disable a competed job, perform the following steps: i.
Managing system data ii. On the Completed Jobs page, select a completed job and click More Actions > Enable. The State of the selected job is changed to Enabled. Result Stopping a Job Procedure 1. On the System Manager console, under Services, click Scheduler. 2. Click Pending Jobs in the left navigation pane. 3. On the Pending Jobs page, select a pending job in the running state and click More Actions > Stop. 4. Click Continue on the Stop Confirmation page. Scheduler stops the selected job.
Managing scheduled jobs Name Description Job Name The name of the scheduled job. Job Status The current status of the pending job. The options are: 1. Pending Execution 2. Running State The state of a job indicates if the job is an active job. The options are: • Enabled • Disabled Frequency The time interval between two consecutive executions of the job. Scheduled By The scheduler of the job.
Managing system data Button Description Filter: Enable Displays fields under select columns that you can use to set filter criteria. This is a toggle button. Filter: Disable Hides the column filter fields without resetting the filter criteria. This is a toggle button. Filter: Apply Filters pending jobs based on the filter criteria. Select: All Selects all the pending jobs in the table displayed in the Job List section.
Managing scheduled jobs Completed Jobs field descriptions Use this page to view and edit the completed jobs. In addition, you can also perform the following operations: • Disable or Enable a job • View a log • Schedule and delete an on demand job Name Description Job Type The type of job represented by an icon that corresponds to its type. The application uses different icons to represent the job types. Following are the job types: 1.
Managing system data Name Description Frequency The time interval between two consecutive executions of the job. Scheduled By The scheduler of the job. Button Description View Opens the Job Scheduling-View Job page that displays the details and of the selected completed job. Edit Opens the Job Scheduling-Edit Job page that you can use to modify the information of a selected completed job. Delete Opens the Delete Confirmation page that prompts you to confirm the deletion of the selected Jobs.
Managing scheduled jobs Criteria section Click Advanced Search to view this section. You can find the Advanced Search link at the at the upper-right corner of the page. Name Description Criteria Displays the following three fields: • Drop-down 1 - The list of criteria that you can use to search the completed jobs. • Drop-down 2 – The operators for evaluating the expression. The operators displayed depends on the type of criterion that you have selected in the first dropdown field.
Managing system data Name Description the application. The System Administrator can reschedule and stop a system schedule job, but can not delete the job. 2. Admin scheduled job — The job that the administrator schedules for administering the application. 3. On-demand job — The periodic jobs that the administrator may schedule to perform non-routine tasks. Job Status The current status of the job. The options are: 1. Running 2. Pending 3. Status Unknown 4. Interrupted 5. Failed 6. Successful 7.
Managing scheduled jobs Button Description Edit Opens the Job Scheduling-Edit Job page that you can use to edit the pending job information. Cancel Closes the Job Scheduling-View Job page and returns to the Pending or Completed Jobs page. Job Scheduling-Edit Job field descriptions Use this page to modify job details and frequency related information of a selected job. Job Details Name Description Job Name The name of the job.
Managing system data Name Description 5. Failed 6. Successful 7. Not Authorized Note: You can only view the information in this field. Job State The state of a job indicates whether the job is an active job or not. The options are: • Enabled • Disabled Scheduled By The scheduler of the job. Note: You can only view the information in this field. Job Frequency 510 Name Description Task Time The date and time of running the job. Use the calendar icon to select a date.
Managing scheduled jobs Job Scheduling-On Demand Job field descriptions Use this page to schedule an on demand job. Job Details Name Description Job Name The name of the job. Job Frequency Name Description Task Time The date and time of running the job. Recurrence The settings define whether the execution of the jobs is a recurring activity or a one time activity. In case of a recurring job, the field also display the time interval of recurrence. The options are: • Execute task one time only.
Managing system data Name Description Job Type The type of job represented by an icon that corresponds to its type. The application uses different icons to represent the Job types. Following are the job types: 1. System scheduled Job — The job scheduled for the normal operation of the application. The System Administrator can reschedule and stop a system schedule job, but can not delete the job. 2. Admin scheduled job — The job that the administrator schedules for administering the application. 3.
Managing scheduled jobs Button Description Continue Disables the job and cancels the next executions that are scheduled for the job. Cancel Cancels the operation of disabling a job and takes you back to the Pending or completed Jobs page. Stop Confirmation field descriptions Use this page to stop a running job. Name Description Job Type The type of job represented by an icon that corresponds to its type. The application uses different icons to represent the Job types.
Managing system data Name Description Frequency The time interval between two consecutive executions of the job. Scheduled By The scheduler of the job. Button Description Continue Stops the job. Cancel Cancels the operation of stopping a job and takes you back to the Pending Jobs page. Delete Confirmation field descriptions Name Description Job Type The type of job represented by an icon that corresponds to its type. The application uses different icons to represent the Job types.
Managing scheduled jobs Name Description Frequency The time interval between two consecutive executions of the job. Scheduled By The scheduler of the job. Button Description Continue Deletes the selected job. Cancel Cancels the operation of deleting a job and takes you back to the Pending or completed Jobs page.
Managing system data 516 Administering Avaya Aura ® Session Manager Comments? infodev@avaya.
Appendix A: Default certificates used for SIP-TLS The Trusted/CA certificate of the issuer that follows is used to generate the default Identity Certificate for SIP-TLS. Certificate: Data: Version: 3 (0x2) Serial Number: 0 (0x0) Signature Algorithm: sha1WithRSAEncryption Issuer: C=US, O=Avaya Inc., OU=SIP Product Certificate Authority, CN=SIP Product Certificate Authority Validity Not Before: Jul 25 00:33:17 2003 GMT Not After : Aug 17 05:19:39 2027 GMT Subject: C=US, O=Avaya Inc.
Default certificates used for SIP-TLS Certificate Authority serial:00 Signature Algorithm: sha1WithRSAEncryption 60:3e:b6:92:b6:8f:be:f8:a0:05:32:d5:12:19:59:b8:8e:c6: e4:9d:6c:1a:cd:1e:72:17:19:6d:5a:b8:28:a2:c3:0d:fb:5b: 77:e7:50:04:25:e7:75:0c:2b:d4:5a:26:db:7d:2c:a5:87:5d: cf:37:36:0b:85:22:25:98:a3:d1:f7:c2:d5:43:83:f9:97:6e: 82:da:cb:89:3d:ac:9e:11:45:fc:ef:00:c2:1d:ef:1e:34:d1: bd:de:f9:79:e1:4e:1a:40:3b:a6:f7:c1:52:4d:19:58:8d:d4: a2:2f:d4:77:b6:b2:8b:3a:28:98:94:b0:44:d6:82:47:04:63: e2:17:34:57:8
dBW9uKQkImd8KU= -----END CERTIFICATE---------BEGIN CERTIFICATE----- MIIE3zCCA8egAwIBAgIBWzANBgkqhkiG9w0BAQUFADBeMQswCQYDVQQGEwJVUzET MBEGA1UEChMKQXZheWEgSW5jLjEaMBgGA1UECxMRQXZheWEgUHJvZHVjdCBQS0kx HjAcBgNVBAMTF UF2YXlhIFByb2R1Y3QgUm9vdCBDQTAeFw0wNzEyMjExMTU0NDBa Fw0yNzEyMDIxMTU0NDBaMGsxCzAJBgNVBAYTAlVTMRMwEQYDVQQKEwpBdmF5YSBJ bmMuMRowGAYDVQQLExFBdmF5YSBQcm9kdWN0IFBLSTErMCkGA1UEAx MiQXZheWEg TWFudWZhY3R1cmluZyBTdWJvcmRpbmF0ZSBDQTCCASAwDQYJKoZIhvcNAQEBBQAD ggENADCCAQgCggEBAMNFdBihMGWSsTAx24rWE5sbjMVkHe0ybSAo
Default certificates used for SIP-TLS hvcNAQEBBQADggEPADCCAQoCggEBAN HrAz5BUuNXL3cH9eAodevZY+5C1IaBtmxe K7+TweCWSljAeX/ e2EKMQatNIOFHO3cXqV7ERBUp0ymmrnnmLeqVfbS9anWOzoGr MCZ3grohkFWh41uBzxlgYhDoGhGc1H8RZJBEE3Rmo5djZrTzAutSuOi7iAO7S9IC a9RBZF /db3Z8jkc0ucSi3pDTolIJvjVx5ccztRd133uUyvHSAoXAwyFVx/9trZHp rQr76xUC/ 8nOAhXlUlt8Vnp5C30X5WywCOXWelIUaLldH55fxDVcGL5h7Yu8SLb9 iynrlJ6XeDKp +fDtWCVySIZBCLx0Ho29f8hOmLpg5/vb691 Q6mUCAwEAAaM/MD0w DwYDVR0TAQH/BAUwAwEB/zAdBgNVHQ4EFgQUc50Q0MwSbfz43CTFP6gsFsrWv+Uw CwYDVR0PBAQD
LtNd36MZl/KavEn6wCChR5IM1GAPwCIvZV pG907FRxPoxdZOAZZRqgWzG7L9mC30NxBiBwA3DO9GbFqOdeW8zupf5SBZqpQ7k/ DZO7oAuYZE8GFhNkUVECAwEAAaOBzDCByTAdBgNVHQ4EFgQUixd7HNzpgfqPlLcc uhqhDY ZUX6QwgZkGA1UdIwSBkTCBjoAUixd7HNzpgfqPlLccuhqhDYZUX6Shc6Rx MG8xCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJNQTEQMA4GA1UEBxMHQW5kb3ZlcjEO MAwGA1UEChMFQVZBWUExDTALBgNVBAsTBEVNTUMxIjAgBgk qhkiG9w0BCQEWE2ln b256YWxlc0BhdmF5YS5jb22CAQAwDAYDVR0TBAUwAwEB/zANBgkqhkiG9w0BAQQF AAOBgQCLiZfxwyTbfC5C5KRnz9tbDLLEzCHoHqZASlUtIK/cY6fzmEtkNb/k6pdM 0CwYeY5u7rBMhj9Umnhv
Default certificates used for SIP-TLS 522 Administering Avaya Aura ® Session Manager Comments? infodev@avaya.
Appendix B: Regular Expression constructs Construct Matches Characters x The character x \\ The backslash character Character classes [abc] a, b, or c (simple class) [^abc] Any character except a, b, or c (negation) [a-zA-Z] a through z or A through Z, inclusive (range) [a-d[m-p]] a through d, or m through p: [a-dm-p] (union) [a-z&&[def]] d, e, or f (intersection) [a-z&&[^bc]] a through z, except for b and c: [ad-z] (subtraction) [a-z&&[^m-p]] a through z, and not m through p: [a-lq-z](s
Regular Expression constructs \p{Lu} An uppercase letter (simple category) \p{Sc} A currency symbol \P{InGreek} Any character except one in the Greek block (negation) [\p{L}&&[^\p{Lu}]] Any letter except an uppercase letter (subtraction) Boundary matchers ^ The beginning of a line $ The end of a line Greedy quantifiers X? X, once or not at all X* X, zero or more times X+ X, one or more times X{n} X, exactly n times X{n,} X, at least n times X{n,m} X, at least n but not more than m ti
Index A aborting a user import job .........................................114 about Adaptations .....................................................258 about Administering Certificates for Session Manager Instances .......................................................43 about Applications ....................................................404 about Branch Session Manager ...............................349 about CAC Administration ........................................249 about CAC Overview .........
Backup Hostname ......................................................24 Backup page .............................................................480 Backup Port ................................................................24 Bounced Requests Count ..........................................26 Branch Session Manager ..........................351, 354, 357 adding SIP entities as Branch Session Manager 351 deleting a Branch Session Manager ..................357 modifying administration settings ............
deleting Locations .....................................................248 deleting pending jobs ................................................500 deleting regular expressions .....................................319 deleting routing policies ............................................302 deleting SIP entities ..................................................282 deleting time ranges .................................................296 Denial of Service protection ......................................
L legal notice ...................................................................2 list of XML Schema Definitions and Sample XMLs for bulk Import ...................................................116 Local Host Name Resolution page field descriptions 371 location .....................................................................254 location deletion ........................................................249 location details ..........................................................
pattern list .................................................................315 Peak (Cross-Cluster Total) .........................................27 Peak (Individual) .........................................................27 pending jobs ......................................................496, 502 Pending Jobs page ...................................................502 Primary Hostname ......................................................24 Primary Port .............................................
searching for alarms .................................................461 searching for logs .....................................................467 searching logs ..........................................................467 searching users ..........................................................80 security module page actions ...................................428 Security Module Reset Confirmation page field descriptions .................................................
viewing applications ..................................................404 viewing background edit job status ...........................363 viewing Communication Profile edit failures .............363 viewing Communication Profiles ...............................362 viewing completed jobs .....................................496, 498 viewing data retention rules ......................................476 viewing deleted users .................................................81 view deleted users ...........
