Avaya Solution & Interoperability Test Lab Application Notes for Telesoft PMSI-Desk 4.10 with Avaya IP Office 7.0 Issue 1.0 Abstract These Application Notes describe the configuration steps required for Telesoft PMSI-Desk 4.10 to interoperate with Avaya IP Office 7.0. PMSI-Desk is used to integrate Avaya IP Office with Property Management Systems (PMS), working as a bridge between the two entities. On one side, it establishes communication with PMS and on other side it establishes communication with Avaya IP Office. In the compliance testing, PMSI-Desk used the analog, TAPI and Configuration Web Service interfaces from Avaya IP Office to provide voicemail, name and user profile template change, wake-up call, room status and mini-bar posting features. Information in these Application Notes has been obtained through DevConnect compliance testing and additional technical discussions. Testing was conducted via the DevConnect Program at the Avaya Solution and Interoperability Test Lab. 1 of 21
1. Introduction These Application Notes describe the configuration steps required for Telesoft PMSI-Desk 4.10 to interoperate with Avaya IP Office 7.0. PMSI-Desk is used to integrate Avaya IP Office with Property Management Systems (PMS), working as a bridge between the two entities. On one side, it establishes communication with PMS and on other side it establishes communication with Avaya IP Office. In the compliance testing, PMSI-Desk used the analog, TAPI and Configuration Web Service interfaces from Avaya IP Office to provide voicemail, name and user profile template change, wake-up call, room status and mini-bar posting features. The analog and TAPI interfaces were used by PMSI-Desk to provide hospitality features such as voicemail, wake-up call, do not disturb, room status and mini-bar posting. The analog lines are provisioned via a Synway SHT-8B analog voice processing card, which connects to analog extension ports on Avaya IP Office. The analog lines were configured as members of a hospitality hunt group. PMSI-Desk used the TAPI interface to set the divert setting for Do Not Disturb for guest room phones when requested manually by the guests. For the voicemail coverage scenarios, voicemail messages were recorded and saved on PMSI- Desk. The TAPI linedevspecific capability was used to activate/deactivate the Message Waiting Indicator (MWI). TAPI was also used to capture the calling and called party information when the call is covered to voicemail. PMSI-Desk also has a Property Management System (PMS) interface to integrate with popular PMS solutions. However, for compliance testing, the built-in PMSI-Desk user interface was used to initiate the room check-in and check-out on PMSI-Desk and IP Office. In the compliance testing, two user rights templates were set up on Avaya IP Office for use with check-in and check-out guests. PMSI-Desk used the Configuration Web Service to send updates to Avaya IP Office on the guest name and user rights template as part of the check-in and check-out process. 2 of 21
2. General Test Approach and Test Results The feature test cases were performed manually. Calls were made from the PSTN, and from local users, to the hospitality hunt group by dialing the different extensions for voice message recording/retrieval, mini-bar and room status posting, and wake-up call schedule. PMSI-Desk user interface was used to manually initiate check-in and check-out requests, to activate/deactivate the MWI and to set Do Not Disturb for room phones. The serviceability test cases were performed manually by disconnecting and reconnecting the Ethernet cable to Avaya IP Office, and rebooting the Avaya IP Office and PMSI-Desk PC. 2.1. Interoperability Compliance Testing The interoperability compliance test included feature and serviceability testing. The feature testing focused on verifying the following on PMSI-Desk: Voicemail recording and retrieval, with proper message waiting lamp activation/deactivation for users with digital and IP telephone types. Scheduling and delivering of wake-up call requests, including retried attempts. Setting of MWI and do not disturb divert parameters using the TAPI interface. Posting of room status and mini-bar usage from the room phones. Use of Configuration Web Services to update guest name and user rights template associated with check-in and check-out requests from the PMSI-Desk user interface. 2.2. Test Results All test cases were executed and passed. 2.3. Support Technical support for PMSI-Desk can be obtained by contacting Telesoft s Support Desk at +91 22 26155139, or sending an e-mail to support@telesoft.in. 3 of 21
3. Reference Configuration The configuration used for the compliance testing is shown below. In the compliance testing, Telesoft PMSI-Desk was installed on a PC running Microsoft Windows XP Professional. Figure 1: Test Configuration Table 1 lists the Extensions used for this testing. Extension Note 331 to 338 Analog lines connected to PMSI-Desk analog card. 220 PMSI-Desk Voicemail hunt group extension. 221 Hunt group for wake-up call registration. 321 Guest room digital phone. 301 to 302 Guest room IP phone. 304 Front desk IP phone. Table 1 Extension Setup 4 of 21
4. Equipment and Software Validated The following equipment and software were used for the sample configuration provided: Equipment Avaya IP Office 500 7.0 (12) Avaya 9640 IP Telephones (H.323) 3.1 SP2 Avaya 1608 IP Telephone (H.323) 1.300B Avaya 1408 Digital Telephone - Telesoft PMSI-Desk on Microsoft Windows XP Professional 4.10 Service Pack 3 Avaya TAPI2 Service Provider (tspi2w.tsp) 1.0.0.35 Software 5. Configure Avaya IP Office This section provides the procedures for configuring Avaya IP Office. The procedures include the following areas: Verify IP Office license Configure analog extensions for voicemail Configure hunt group Disable system voicemail Administer voicemail users Administer User Rights Administer Configuration Service Administer Security User and Rights Administer System Password 5 of 21
5.1. Verify IP Office License From a PC running the Avaya IP Office Manager application, select Start > Programs > IP Office > Manager to launch the Manager application. Select the proper IP Office system, and log in with the appropriate credentials. The Avaya IP Office Manager screen is displayed. From the configuration tree in the left pane, select License > CTI Link Pro, to display the CTI Link Pro screen in the right pane. Verify that the License Status is Valid. This license is required for Telesoft PMSI-Desk to use thirdparty TAPI control mode on IP Office. 5.2. Configure Analog Extensions for Voicemail In the Manager window, go to the Configuration Tree and expand Extension. In the list of extensions that appears, select extension 331, i.e. the first extension that will be connected to PMSI-Desk s analog card listed in Table 1. In the Extension window that appears, leave default values for all settings and select Analogue tab. In that tab, select Standard Telephone for Equipment Classification and click OK (not shown). 6 of 21
In the Manager window, go to the Configuration Tree and expand User (not shown) and select the user that corresponds to the previously configured extension 331. In the User window that appears, set Name to a suitable value. Repeat this section for analog extensions that are connected to the PMSI-Desk s analog card. 7 of 21
5.3. Configure Hunt Group In the Manager window, go to the Configuration Tree, right-click Hunt Group and select New in the pop-up menu that appears. In the subsequent Hunt Group window, set Name to a suitable value, set Extension to the extension for the PMSI-Desk Voicemail hunt group listed in Table 1, set Ring Mode to Sequential, and add four of the Voicemail extension numbers (extensions 335 to 338) listed in Table 1 to the Extension List. Select the Queuing tab and uncheck Queuing On. Click OK (not shown). 8 of 21
5.4. Disable System Voicemail In the Manager window, go to the Configuration Tree and double-click System. Select the Voicemail tab. In the Voicemail tab that appears, select None for Voicemail Type and click OK (not shown). 5.5. Administer Voicemail Users From the configuration tree in the left pane, select the first user that will be using PMSI-Desk for voicemail. In this case, the user is 301. Enter a descriptive name for Name and Full Name. Note: The Name and Full Name fields will be used by PMSI-Desk to update the guest name. 9 of 21
Click on the Forwarding tab. Check Forward on Busy, Forward on No Answer, and Forward Internal Calls check boxes. In the Forward Number specify 220 which is the extension of the PMSI-Desk hunt group created in Section 5.3. Click OK. Repeat this section for all users using PMSI-Desk for voicemail, including all guest rooms, front desk, and staff. In the compliance testing, the voicemail users include three guest rooms with extensions 301, 302 and 321, as shown in Figure 1. 10 of 21
5.6. Administer User Rights From the configuration tree in the left pane, right-click on User Rights and select New to create a new user rights template. Enter a desired Name to designate user rights for guests in the check-in state. In the compliance testing, the name was set to checkin as shown below. 11 of 21
Select the Telephony tab and then the Supervisor Settings sub-tab. Uncheck Enable outgoing call bar field towards the bottom, and select Apply User Rights Value from the corresponding drop-down box, as shown below. Repeat this section to create the desired number of user rights templates for guests in various states. In the compliance testing, two user rights templates with names of checkin and checkout were created. The Enable outgoing call bar field was checked for the user right checkout to prevent the guest room phone from making calls to the PSTN when this user right is applied. In the Manager window, select File Save Configuration to push the configuration to IP Office and wait for the system to update. 5.7. Administer Configuration Service From the Avaya IP Office R7 Manager screen, select File > Advanced > Security Settings from the top menu. Select the proper IP Office system, and log in with the appropriate security user credentials (not shown). From the configuration tree in the left pane, select Security > Services > Configuration to display the Service : Configuration screen in the right pane. For Service Security Level, select Unsecure + Secure as shown below. In this compliance testing, Telesoft PMSI-Desk used the Secure level for the Configuration Web Service interface. 12 of 21
5.8. Administer Security User and Rights From the configuration tree in the left pane, right-click Security > Rights Groups and select New in the pop-up menu that appears. Specify the Group Name, e.g. Telesoft, and click OK. From the configuration tree in the left pane, select the new Rights Group created above. In the right pane, select the Configuration tab. Select the IP Office Service Rights to assign to this group as shown below. 13 of 21
From the configuration tree in the left pane, right-click Security > Service Users and select New in the pop-up menu that appears. Specify the New User Name, e.g. Telesoft, and password as shown below and click OK. This user will be used to configured Telesoft PMSI-Desk in Section 6.3 From the configuration tree in the left pane, select the new Service User created above. In the right pane, under Rights Group Membership, select the Rights Group created above. 14 of 21
5.9. Administer System Password Select Security > System from the configuration tree in the left pane to display the System : SGIP500 screen in the right pane, where SGIP500 is the name of the IP Office. In the Unsecured Interfaces tab, click the Change button next to the System Password to configure the IP Office System Password. The System Password is used in Section 6.1 to configure the IP Office TAPI Driver. Click OK. In the Manager window, select File Save Security Settings to push the settings to IP Office and wait for the system to update. This completes configuration of IP Office. 15 of 21
6. Configure Telesoft PMSI-Desk This section provides the procedures for configuring Telesoft PMSI-Desk. The procedures include the following areas: Administer TAPI driver Obtaining IP Office Configuration Web Service SDK Configure PMSI-Desk Settings 6.1. Administer TAPI Driver From the Telesoft PMSI-Desk PC shown in Figure 1, select Start > Control Panel, and click on the Phone and Modem Options icon (not shown). In the Phone and Modem Options window, select the Advanced tab. Select the Avaya IP Office TAPI2 Service Provider entry, and click Configure. 16 of 21
The Avaya TAPI2 configuration screen is displayed. For Switch IP Address, enter the IP address of Avaya IP Office. Select the radio button for Third Party, and enter the IP Office System Password configured in Section 5.9 into the Switch Password field. Reboot the PMSI- Desk PC. 6.2. Obtaining Avaya IP Office Configuration Web Service SDK Avaya provides the IP Office Configuration Web Service SDK for DevConnect members to incorporate IP Office configuration changes in their solutions. The Configuration Web Service SDK must match the release of the IP Office that is deployed, in this case Release 7.0. To obtain the IP Office Configuration Web Service SDK, browse to https://devconnect.avaya.com/ using a web browser and login using a valid DevConnect member account. Then click Products & SDKs > IP Office > IP Office Release 7.0 Contents to locate and download the Configuration Web Service SDK. Telesoft implementation engineer will then deploy the files from the Configuration Web Service SDK onto the Telesoft PMSI-Desk PC. 17 of 21
6.3. Configure PMSI-Desk Settings From the PMSI-Desk PC, open the file CHKINOUT.INI located in the C:\PMSIDESK\pmsi\ folder using a text editor. Configure the following settings: Field Values Section CONN Userver IP Address of the Avaya IP Office, in this case is 10.1.30.10. UName IP Office Security User created in Section 5.8. Upwd IP Office Security User password created in Section 5.8. Uport IP Office Configuration Service TCP Port, i.e. 50805. Section CSSCONF DefCheckInCSS Set to the User Rights created in Section 5.6 for Check-In. DefCheckOutCSS Set to the User Rights created in Section 5.6 for Check-Out. 18 of 21
From the PMSI-Desk PC, open the DIALER.INI file located in the folder C:\PMSIDESK\ipoffvm\ using a text editor. In the section extntochmap, configure the analog extensions configured in Section 5.2 to match the port number on the PMSI-Desk s analog card as shown below: 7. Verification Steps This section provides the tests that can be performed to verify proper configuration of Avaya IP Office and Telesoft PMSI-Desk. 7.1. Verify TAPI Integration Place a call to a guest room and leave a voice message. Verify that the MWI is turned on for the guest room. Place a call from the guest room to the PMSI-Desk voicemail pilot number. Verify that PMSI-Desk recognizes the calling party as a voicemail user. Verify that the voice message can be retrieved, and that the MWI is turned off. Using the PMSI-Desk user interface, activate Do Not Disturb for a guest room and verify using IP Office System Status application or by calling the guest room. 7.2. Verify Configuration Web Service Integration Use the PMSI-Desk user interface to perform a guest check-in request. Verify that the guest name and user rights template are updated correctly on Avaya IP Office as part of the check-in process. 19 of 21
8. Conclusion These Application Notes describe the configuration steps required for Telesoft PMSI-Desk 4.10 to successfully interoperate with Avaya IP Office 7.0. All feature and serviceability test cases were completed successfully. 9. Additional References This section references the product documentation relevant to these Application Notes. [1] IP Office 7.0 Documentation Library CD, May 2011, available at http://support.avaya.com. 20 of 21
Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by and are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice. The configurations, technical data, and recommendations provided in these Application Notes are believed to be accurate and dependable, but are presented without express or implied warranty. Users are responsible for their application of any products specified in these Application Notes. Please e-mail any questions or comments pertaining to these Application Notes along with the full title name and filename, located in the lower right corner, directly to the Avaya DevConnect Program at devconnect@avaya.com. 21 of 21