Legacy Paging Interface™ 1.1.1 - Amazon S3 · For testing purposes, a workstation running a...

Corporate Headquarters:

Singlewire Software 2601 West Beltline Highway #510 Madison, WI 53713© 2013 Singlewire. All rights reserved.

Legacy Paging Interface™ 1.1.1.a

Installation and User Guide for a Cisco® Unified Communications Manager Telephony Environment

Advanced Notification

Table of ContentsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

A Note on Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Where to Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Configure Communications Manager to Work with the LPI/InformaCast 7

Configure InformaCast to Work with the LPI . . . . . . . . . . . . . . . . . . 24

Using the Legacy Paging Interface . . . . . . . . . . . . . . . . . . . . . . . 29

Manage the LPI’s Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Configure the LPI’s Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Configure Paging Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Add the LPI to InformaCast as an IP Speaker . . . . . . . . . . . . . . . . . 52

Send a Broadcast . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Upgrade the LPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Start/Stop/Restart the LPI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Resolve Call Routing Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Determine SLP vs Static URL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Resolve SIP Client Call Connection . . . . . . . . . . . . . . . . . . . . . . . . . 69

Set Singlewire Traffic Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Change the IP Address of the LPI Server . . . . . . . . . . . . . . . . . . . . 70

Further Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Legacy Paging Interface Installation and User GuideIntroduction

IntroductionSinglewire’s Legacy Paging Interface (LPI) acts as a liaison between your existing paging system and our InformaCast™ application. When you configure your speakers with the LPI, they can be integrated with InformaCast, and you can add them to recipient groups, create paging zones modeled after your existing zones, and send audio broadcasts out to any combination of speakers/zones.

With the LPI, you create a definition of your existing paging system, which is stored in the LPI’s database. Each definition may have one or more paging zones (i.e. group of speakers) associated with it, and each paging zone can be accessed via a single or multiple dual-tone multi-frequency (DTMF) tone(s). Once your definition is complete, the LPI creates a software “model” of your speaker for each defined paging zone and assigns to it a specified MAC address within the LPI. The speakers register with the InformaCast server and play the broadcasts they send out.

Intended AudienceThis user guide is written for the installers and administrators of the LPI.

RequirementsThe LPI has the following system requirements:

• InformaCast version 8.5

• A Cisco Unified Communications Manager version 6.x to 10.0

A Note on UsageSpecific fonts are used to represent specific kinds of information in this user guide. The fonts and their meaning are listed here:

• Bold Fonts indicate the name of a button, text field, or other element with which you interact and any text that you must enter.

• Angled brackets enclose text that varies with your specific environment, i.e. http:\\<Your IP Address> means that you would enter your specific IP address instead of the brackets and what they enclose.

• Blue, underlined text indicates a hyperlink.

There are two kinds of notification boxes used in this guide.

• Tip. These offer advice or “best practices.”

• Note. These contain additional information, usually relevant in special cases.

4 - 4Cisco Unified Communications Manager Environment

Version 1.1.1.a Advanced Notification


Where to StartIf you have a specific task in mind, peruse the “Table of Contents” to locate the instructions for that task.

Web Interface

All of your Singlewire applications’ user interfaces along with application- and system-level management tools are accessible through the Singlewire Start page, which is accessible through a web browser addressed with the IP address of your InformaCast Virtual Appliance server.

From this page, you can access all of your necessary Singlewire functionality. Click the Detect Emergency Calls with CallAware link to open CallAware’s user interface.




The webpages you’ll use to administer the LPI have two main components: a left navigation menu whose contents are static, and an administration pane whose contents change with what you’re doing.

LPI Definitions

Before working with the LPI, it is helpful to understand a few terms:

• A paging device is a physical unit that allows broadcasts via one or several groups of loudspeakers.

• Paging zones are groups of loudspeakers to which a paging device provides access. InformaCast recognizes paging zones as regular IP speakers.

• A DTMF tone (or code) is assigned to each paging zone. When InformaCast sends a broadcast to one or more of the LPI’s paging zones, the LPI will dial the DTMF code for those zones (after placing a call with the paging device) in order to broadcast to that paging zone. Some types of paging devices allow combining paging zones so that a single DTMF tone can be used for accessing several zones at once.

TroubleshootingIf you’ve followed the instructions in this guide and are still having trouble getting the LPI to work, “Troubleshooting” on page 53 may help you figure out what’s wrong.

Getting HelpYour first line of support is the Help link, which opens this documentation. If you have consulted the documentation, but still can’t answer your question or resolve your issue, you can submit an online support request to Singlewire.

Administration Pane

Navigation Pane



http://www.singlewire.com/online-support-request.html


Legacy Paging Interface Installation and User GuideConfiguration

ConfigurationBefore you can install the LPI, you will need to ensure that your Cisco Unified Communications Manager is properly configured to work with the LPI.

Configure Communications Manager to Work with the LPI/InformaCast

Note This section is for people who have a thorough understanding of Communications Manager and Cisco Voice over IP. Advanced knowledge of dial plan design, call routing, media resources, and SIP trunking are a must before starting this integration.

The LPI needs to be configured to work with Communications Manager to allow it to place calls to the existing analog paging equipment for use by InformaCast. The following diagram is an example of the topology of an external paging system connected to a voice network.

The diagram shows an analog connection from a paging amplifier to a Cisco voice gateway. The voice gateway then connects to Communications Manager via MGCP, H323, SIP, or SCCP. This allows Cisco IP phones to dial into the external paging system.

The LPI may reside on the same server or a different server than InformaCast; in this example, they are coresident. The LPI uses a Session Initiation Protocol (SIP) trunk built between itself and Communications Manager for call setup signaling.

For testing purposes, a workstation running a third-party SIP endpoint can be used to dial into the Communications Manager SIP trunk (which is shown as an example in the diagram). The end result is that a telephone call using SIP is established from the LPI and/or the test workstation to the analog paging system.




Prerequisites

The following requirements must be completed before beginning this integration:

• Installed and functional InformaCast deployment

• Installed and functional Communications Manager environment

• Analog paging equipment connected to Communications Manager environment

• Ability to dial analog paging equipment and use Dual-Tone Multi-Frequency (DTMF) signaling to select zone(s) from IP phones

• LPI license key

Note Contact [email protected] if you need a license key.

Communications Manager Planning

Before beginning your integration, you should take the following points into consideration.

• Dial plan considerations. Each paging amplifier must have a unique extension with Communications Manager. The LPI will attempt a call with the paging equipment, and Communications Manager will set up this call. When the LPI sends the call setup SIP invite to Communications Manager, it will send a telephone number. The calling search space applied to the SIP trunk will need access to all partitions where the paging directory numbers reside.

• Media Termination Point (MTP) considerations. Because the LPI uses SIP for call setup with Communications Manager, RFC2833 DTMF will be used. More than likely the far side, i.e. a Cisco gateway, will be using either MGCP or H323 as its signaling protocol. To get DTMF to pass from the LPI to the gateway, an MTP must be used.

By starting the IP Voice Media Streaming Application service on Communications Manager, software MTP will be available. Hardware MTP can be used on a Cisco IOS device, and transcoders will also act as MTP.

• Codec considerations. The LPI will use G.711 µlaw for its audio payload. The MTP resources will need to be in a device pool where the codec negotiation will be G.711 µlaw. The gateways to which the analog paging equipment is connected must also have a device pool where the codec negotiation will be G.711 µlaw.

If another codec needs to be used—for instance, across a WAN connection—transcoders will have to be invoked. This configuration is outside the scope of this guide.

Create a Media Resource Group

The first step in configuring Communications Manager is to add a media resource group.

Note The pictures in the following sections illustrate Cisco Unified Communications Manager v6.x; however, the steps are consistent between versions of Communications Manager. Discrepancies are noted where they occur.



mailto:[email protected]


Step 1 Open a web browser and log into the administration interface of the Communications Manager server (the address will be similar to https://<Communications Manager IP Address>/CCMAdmin). The Cisco Unified CM Administration page appears.

Step 2 Go to Media Resources | Media Resource Group. The Find and List Media Resource Groups page appears.




Step 3 Click the Add New button. The Media Resource Group Configuration page appears.

Step 4 Enter a name for your group in the Name field, e.g. LPI-MTP-MRG.

Step 5 Enter a description for your group in the Description field, e.g. Singlewire LPI MTP for RFC2833 DTMF.

Step 6 Use the down arrow to move MTP from the Available Media Resources area to the Selected Media Resources area.

Step 7 Click the Save button.

Note If a media resource group already exists with MTP, you do not need to create a new group. The MTP resource should be using a device pool with a region that will have the call from LPI use G.711.




Create a Media Resource Group List

Once you’ve created your media resource group, you’ll add it to a media resource group list.

Step 1 Go to Media Resources | Media Resource Group List. The Find and List Media Resource Group Lists page appears.

Step 2 Click the Add New button. The Media Resource Group List Configuration page appears.

Step 3 Enter a name for your list in the Name field, e.g. LPI-MTP-MRGL.

Step 4 Use the down arrow to move the media resource group you just created (see “Create a Media Resource Group” on page 8) from the Available Media Resource Groups area to the Selected Media Resource Groups area.





Create a Region

Once you’ve created media resource groups and group lists, you’ll need to add a region that contains the G.711 audio codec.

Step 1 Go to System | Region. The Find and List Regions page appears.

Step 2 Click the Add New button. The Region Configuration page appears.

Step 3 Enter a name for your region in the Name field, e.g. LPI.




Step 4 Click the Save button. The Region Configuration page refreshes.

Step 5 Select your other regions in the Regions area and select G.711 from the Audio Codec dropdown menu.


Note Because the LPI places a phone call, it is possible to have this call be G.729 to remote sites. The call LPI places will always be G.711. If it is desired to use G.729 across WAN links, transcoders must be invoked. That configuration is beyond the scope of this guide.

Create a Device Pool

Once you’ve added a region with G.711, you’ll add it and the media resource group list you created in “Create a Media Resource Group List” on page 11 to a device pool.

Step 1 Go to System | Device Pool. The Find and List Device Pools page appears.




Step 2 Click the Add New button. The Device Pool Configuration page appears.

Step 3 Enter a name for your device pool in the Device Pool Name field, e.g. LPI.

Step 4 Select a Communications Manager group from the Cisco Unified Communications Manager Group dropdown menu.

Tip Make sure that the Communications Manager group you choose contains the Communications Manager with which the LPI will communicate.

Step 5 Select a date/time group from the Date/Time Group dropdown menu.

Tip Select CMLocal unless you are performing dialing restrictions/re-routing by time of day.

Step 6 Select the region you created in “Create a Region” on page 12 from the Region dropdown menu.

Step 7 Select the media resource group list you created in “Create a Media Resource Group List” on page 11 from the Media Resource Group List dropdown menu.

Step 8 Select Disable from the SRST Reference dropdown menu.





Create a Calling Search Space

You’ll need to create a calling search space to house the directory numbers (DNs) of the phones you will be paging.

Step 1 Go to Call Routing | Class of Control | Calling Search Space. The Find and List Calling Search Spaces page appears.

Step 2 Click the Add New button. The Calling Search Space Configuration page appears.

Step 3 Enter a name for your calling search space in the Name field, e.g. LPI-CSS.

Step 4 Enter a description for your calling search space in the Description field, e.g. Singlewire LPI to Paging DNs.

Step 5 Use the down arrow to move the partition(s) that contain the DNs to which you will be sending broadcasts from the Available Partitions area to the Selected Partitions area.





Note The paging DNs must be unique so Communications Manager can route the calls from the LPI to the proper paging amplifier.

Create a SIP Trunk

Once you have a device pool and a calling search space for the LPI, you’ll create a SIP trunk and assign them to it.

Step 1 Go to Device | Trunk. The Find and List Trunks page appears.

Step 2 Click the Add New button. The Trunk Configuration page appears.

Step 3 Select SIP Trunk from the Trunk Type dropdown menu.




Step 4 Click the Next button. The Trunk Configuration page refreshes.

Step 5 Enter a name for your trunk in the Device Name field, e.g. LPI, in the Device Information area.




Step 6 Enter a description for your trunk in the Description field, e.g. Singlewire LPI on <IP Address>, where <IP Address> is the address of your LPI server.

Step 7 Select the device pool you created in “Create a Device Pool” on page 13 from the Device Pool dropdown menu.

Step 8 Select the calling search space you created in “Create a Calling Search Space” on page 15 from the Calling Search Space dropdown menu in the Inbound Calls area.

Step 9 Enter the IP address of your LPI server in the Destination Address field in the SIP Information area.

Step 10 Select Non Secure SIP Trunk Profile from the SIP Trunk Security Profile dropdown menu.

Step 11 Select Standard SIP Profile from the SIP Profile dropdown menu.


Test Functionality

Once you’ve set up Communications Manager properly, it’s important to test the functionality before relying on the LPI to deliver your important broadcasts.

After you configure Communications Manager and set up the SIP trunk, the LPI should drop in easily to this environment. However, how do you know things are set up properly and LPI will work? Test your environment with a third-party SIP “phone,” like Linphone.

If you can use Linphone to perform the following actions, you have set up your environment properly:

• Can you place a call to the existing paging system?

• Does the existing paging system answer that call?

• Can you use DTMF to select a zone?

• Can you hear your voice over the existing paging system?

By testing your environment before installing and configuring the LPI, you narrow down your troubleshooting options if the LPI doesn’t work upon installation. If your Linphone test fails, your Communications Manager isn’t set up properly and your Cisco representative can assist you with further configuration help. If the Linphone test succeeds and the LPI still doesn’t work, it’s a problem with the LPI and Singlewire Support personnel can assist you.




Modify the SIP Trunk For Client Test

To properly test your Communications Manager environment, you’ll need to modify the SIP trunk you just set up to use your workstation’s IP address.

Step 1 Go to Device | Trunk in Communications Manager. The Find and List Trunks page appears.

Step 2 Click the Find button to list all of your available trunks or use the filter fields to refine your search.




Step 3 Click the Name link of your desired trunk. The Trunk Configuration page appears.

Step 4 Change the Destination Address field in the SIP Information area to InformaCast’s statically configured IP address.





Step 6 Click the Reset button to reset the SIP trunk. The Device Reset window appears.

Step 7 Click the Reset button and close the Reset Device window.

Use Linphone to Place a Test Call

Once you’ve modified your SIP trunk to use your workstation’s IP address, you’ll need to download a SIP client, such as Linphone, to place a test call from your client to the paging system. If this call connects and you get DTMF, the LPI will drop in easily. If this call does not connect, check that your Communications Manager is configured properly. If the problem persists, contact your Cisco representative for further configuration assistance.

Note Any SIP client that is able to place a G.711 µlaw call should work. In this example, we use a free product called Linphone (http://www.linphone.org/index.php/eng/download).

Step 1 Download Linphone from http://www.linphone.org/index.php/eng/download and launch the application. The Linphone window appears.



http://www.linphone.org/index.php/eng/download

http://www.linphone.org/index.php/eng/download


Step 2 Go to Linphone | Preferences. The Preferences window appears.

Step 3 Click the Codecs tab. The Codecs tab appears.

Step 4 Select PCMU 8000 and use the Up button to move it to the top of the list.

Step 5 Select each of the other codecs and click the Disable button. PCMU 8000 should be the only enabled codec.

Step 6 Click the Done button.

Step 7 Enter an extension for a paging amplifier in the SIP address or phone number field. The format for this should be: sip:<Extension>@<CM IP Address>, where <Extension> is the paging amplifier’s extension and <CM IP Address> is the address of the Communications Manager to which you want to send calls.




Step 8 Click the green Start Call button. The Linphone window refreshes showing the call will being placed.

Wait for the amplifier to answer and the call to be connected. The Linphone window refreshes.

Step 9 Click the Keypad tab. The Keypad tab appears.

Step 10 Use the keypad to enter the paging zone.

Step 11 Complete the page.




Step 12 Press the red Terminate Call button to end the call.

Step 13 Follow Steps 1 through 6 in “Modify the SIP Trunk For Client Test” on page 19 to change the Destination Address field back to the LPI’s IP address.

Before Continuing Forward

The test in “Use Linphone to Place a Test Call” on page 21 must complete successfully in order for the LPI to function properly. The LPI will do exactly the same thing as the SIP client software is doing. If you are not able to successfully use the SIP client to place the call and select a zone with DTMF, the LPI will not be able to do so either. If your answer to any of the following questions is ‘No,’ fix your configurations and try again before proceeding.

• Did a call get placed?

• Did the call get connected?

• Was DTMF received at the far end?

• Was the paging zone selected by the DTMF?

• Was your voice heard over the analog paging system?

Assistance With Communications Manager Configurations

All instructions up to this point have included Communications Manager while no Singlewire Software product is running. If this testing is unsuccessful, the LPI will also not work correctly. If you require assistance with Communications Manager configurations, please contact the Cisco TAC or your Cisco Partner. If you would like Singlewire to assist with your Communications Manager configurations, please contact [email protected].

Configure InformaCast to Work with the LPIIn order to properly integrate your legacy paging system with InformaCast through the LPI, you’ll need to make sure that InformaCast is properly configured.

Configure Speaker Registration

If speaker auto-registration is enabled in InformaCast, the paging zones you define in the LPI will automatically register with the InformaCast server as regular IP speakers (see “Configure the Desktop Notification System” in the “InformaCast Installation and User Guide” for steps on enabling speaker auto-registration). If speaker auto-registration is not enabled, you will have to register speakers manually using the InformaCast web interface (see “Manage IP Speakers and Desktop Notification System Machines” in the “InformaCast Installation and User Guide” for steps on manually registering your IP speakers). Either method is acceptable; choose that which works best with your environment.

Tip If you have a lot of speakers, configuring speaker auto-registration would lead to an easier and quicker installation.





Check the InformaCastSpeaker.cfg File

Open your InformaCastSpeaker.cfg file (typically located in /usr/local/singlewire/InformaCast/web/resources) and ensure that your InformaCast server has a valid speaker configuration file. This means that in the following lines of the InformaCast Speaker.cfg file, the IP address and port number of your InformaCast server will appear in place of <Your IP Address:Port #>:

<InformaCastSpeakerConfiguration>

<Servers>

<InformaCast url=“http://<Your IP Address:Port #>/InformaCast/admin?cmd=spkr”/>

</Servers>

</InformaCastSpeakerConfiguration>

Start the LPI

Once you’ve initially performed these steps, the LPI will start whenever this server is booted.

Step 1 Open a web browser, enter the IP address of your InformaCast Virtual Appliance server, and press the Enter key. The Singlewire Start page appears.




Step 2 Click the Access System Management Tools with Webmin link. A separate tab/window opens to the Login to Webmin page.

Note You may have to accept a warning from your web browser about the security of this page’s content.

Step 3 Enter your login credentials and click the Login button. By default, your username is admin and your password is changeMe. The Virtual Appliance server’s homepage appears.




Step 4 Go to System | Bootup and Shutdown. The Bootup and Shutdown page appears.

Step 5 Scroll down the list of actions until you come to singlewireLPI. Click its link. The Edit Action page appears.




Step 6 Click the Start Now button. It will take a minute or so for the LPI to start.



Legacy Paging Interface Installation and User GuideUsing the Legacy Paging Interface

Using the Legacy Paging InterfaceAdministering the LPI includes adding users and paging devices, configuring the LPI’s parameters, and sending broadcasts.

Manage the LPI’s Users

Note You must have a valid license for the LPI to access any of its functionality. If you do not have a license, contact [email protected] to gain access to one and follow the steps in “Upgrade the LPI” on page 53.

The LPI ships with a default administrator role. If you’d like to have more than one user with the ability to administer the LPI, you will need to add that user to the system.

At the very least, you should change the default administrator’s password to enforce tighter security.

Change the Default Administrator’s Password

The LPI ships with a default administrative user so that you can log in and configure the system. In this section, you will change that password so that other people familiar with the LPI won’t have complete access to your configuration.





Step 1 Open a web browser, enter the IP address of your InformaCast Virtual Appliance server, and press the Enter key. The Singlewire Start page appears.

Step 2 Click the Connect to Analog Speakers with the Legacy Paging Interface (LPI) link. A separate tab/window opens to the Legacy Paging Interface Administration page.




Step 3 Enter your credentials in the Logon Name and Password fields. Your default logon credentials are admin and changeMe, respectively. The Legacy Paging Interface Administration page refreshes.

Step 4 Click the Users link. The User Administration page appears.




Step 5 Click the Admin link. The Edit User page appears.

Step 6 Enter a new password in the Password field.

Step 7 Enter that same, new password again in the Confirm Password field.

Step 8 Click the Save button. Your new password will be saved.

Add a User

Use the following steps to add a user to the LPI.





Step 2 Click the Add a New User icon ( ). The Add User page appears.

Step 3 Enter your new user’s name in the First Name and Last Name fields.

Step 4 Enter the new user’s username in the Logon Name field.

Step 5 Enter the new user’s password in the Password and Confirm Password fields.

Step 6 Click the Save and Add Another button to save your new user’s information and add another user or click the Save button if you’re finished adding users.

Note Your LPI user information does not need to match that of InformaCast because the applications are completely unrelated in that manner. However, mirroring the information between the two applications will cut down on possible user confusion with login information.




Edit a User/Change a User’s Password

Once you have added more administration users to the LPI, you may need to change their information.


Step 2 Click the Logon Name link of the user you’d like to edit. The Edit User page appears.

Step 3 Make your desired changes and enter your user’s password in the Password and Confirm Password fields.


Delete a User

After you have added users to the LPI, you may want to delete them.





Step 2 Click the Delete User icon next to the user you want to delete ( ). A dialog box appears.

Step 3 Click the OK button and the user will be deleted.




Configure the LPI’s ParametersThe Configuration Parameters page displays, and allows you to modify, the parameters that affect the behavior of the LPI. Most of the parameters have default values and do not have to be changed after installation.

Step 1 Click the Configuration Parameters link. The Configuration Parameters page appears.

Step 2 Check that the IP address in the Host Address field is the IP address of the computer where the LPI is installed. If it’s not correct, change it to reflect the correct IP address.

Tip The Host Address field is set to 127.0.0.1 by default. This value must be changed to the actual IP address of the computer where the LPI is installed.




Step 3 Modify the rest of the fields on the Configuration Parameters page as you desire to change how the LPI works. An explanation of the fields follows:

• Speaker Configuration URL. Specifies how the paging zones should discover their configuration. If this field is left blank, which is the default setting, the LPI will use the SLP protocol for finding the IP speaker configuration file servers. If you enter a URL in that field, the LPI will assume that the speaker configuration files are located at that URL. See “Determine SLP vs Static URL” on page 68 for more information on SLP versus a static URL.

• Use Custom Test Tone. Allows you to replace the audio file the LPI uses for testing paging zones. Like IP speakers, paging zones can be instructed to play a test tone. The default tone is a clock chime, but you can customize the test tone by clicking the Browse button and navigating to an 8 KHz u-law file. Testing the paging zones can be done through the InformaCast web interface (click the Edit IP Speakers link and click the Test button for your defined paging zone).

• Request Wait Period. Specifies how long the LPI will collect incoming activation requests at the beginning of a broadcast before it starts streaming the audio to the participating paging zones. When a broadcast begins, each of the participating paging zones receives an individual activation request. The LPI collects such requests during the time specified in the Request Wait Period field. Once all such requests have been collected, the LPI determines the DTMF code to use for dialing the participating zones and, if such a code exists, it places a call with the paging device in order to start streaming the broadcast’s audio.

The following example illustrates how the Request Wait Period field is used by the LPI. There is a user-defined paging device, PD, that has three paging zones: A, B, and C. When InformaCast sends a message to zones A and C, it first instructs them to prepare to listen to the audio by sending activation requests to them.

The LPI receives the activation request addressed to zone A and begins to wait for more activation requests for the same broadcast; this is when the request wait period begins. A bit later, the LPI receives the request addressed to zone C. It will wait a little more to make sure the broadcast is not supposed to be delivered to zone B. Once the request wait period expires, the LPI knows that only zones A and C are the intended recipients. The LPI determines the DTMF code it should use to call only those two zones. If such a code exists, it places a phone call to the paging device, PD, and uses that code to dial zones A and C. If there is no such DTMF code that selects only zones A and C but not B, the LPI reports an error to InformaCast and the delivery of the broadcast to zones A and C will fail.

One second is the default value for the Request Wait Period field, which is long enough for most uses. However, it is possible that in some cases, the LPI may fail to detect that a broadcast should be delivered to some of the zones of a multi-zone paging device (which may cause the rest of the zones of the same paging device to fail to play the message, depending on how their DTMF codes are set up). Normally, this would rarely happen, unless there are persistent network problems. If you decide to make the Request Wait Period longer, avoid setting it to large values (such as 5 seconds and above), since that may lead to unnecessary delays in the delivery of broadcasts to the LPI paging zones.

• TCP Connection Timeout. Determines how long the LPI should wait for a response from InformaCast. By default it is set to 0, which means it should wait forever. Paging zones request their configurations from the configuration file server that they discovered via SLP or a static URL. The zones will wait for a response for no longer than the duration specified in the TCP Connection Timeout field. This field also determines how long the paging zones will wait for a response from InformaCast when they send their registration requests, which happens every five minutes.




Warning The following SIP fields are low-level settings used by the SIP stack that you should not normally have to change. You should only make changes to these fields when directed by one of Singlewire’s Support personnel.

• MAC Address Prefix. Supplies a six-digit hexadecimal number that is used for generating unique MAC addresses, which will be used when defining paging zones. InformaCast uses MAC addresses to uniquely identify each paging zone when sending broadcasts to them. Every time you add a new paging zone to a paging device, the LPI will generate a MAC address for that zone using the MAC Address Prefix field. You should never need to change the default setting of this field unless you have two or more LPI's installed on the same network. In that case, to prevent those LPI installations from generating identical MAC addresses, you should set the MAC Address Prefix field in each LPI to a unique value, i.e. 000001, 000002, 000003, etc.

• Port. Defines the port number the LPI uses for SIP messages. The default is 5060. If you change the Port field, you must restart the LPI before changes take effect. Follow the steps in “Start/Stop/Restart the LPI” on page 61 for help on stopping and starting the LPI.

• Transport Protocol (UDP/TCP). Determines the protocol used when sending a SIP message to a peer in order to establish a SIP session. May be UDP or TCP.

• Contact User Name. Defines the username used in the SIP contact header.

Note A SIP message has a contact header that tells the peer how to contact the LPI SIP peer for subsequent requests. It is optional. The values in this field and the Contact Display Name field make it clear that the LPI is being used and they will stand out when looking at packet captures.

• Contact Display Name. Defines the contact display name to use in the SIP contact header.

• Cache TCP Connections. Determines how the SIP stack controls the server socket. A true value means the SIP stack closes the server socket after a server transaction goes to a terminated state, allowing the server to protect against TCP-based denial of service attacks launched by clients. A false value means the SIP stack will keep the socket open so as to maximize performance at the expense of thread and memory resources. The default is false. If you change the Cache TCP Connections field, you must restart the LPI before changes take effect.

• Max Message Forwards. Defines the maximum number of hops that a SIP request can transit on its way to its destination. The default is 70.

Note The default value for the Max Message Forwards fields is large enough that you should never have to worry about changing it.

• Max Incoming Message Size. Sets the maximum size of content that a TCP connection can read. Your value must be at least 4K. The SIP stack defaults to “infinity,” i.e. no limit. The purpose of this property is to prevent denial of service attacks launched by writing to a TCP connection. The default is 1048576. If you change the Max Incoming Message Size field, you must restart the LPI before changes take effect.




• TCP Read Timeout. Defines the timeout (in milliseconds) between successive reads on a TCP connection after the first byte of a SIP message is read by the stack. The SIP stack default is -1, which leaves the stack open to starvation attacks and allows the client to send data as slowly as it wants. The application default is 1,000 milliseconds. If you change the TCP Read Timeout field, you must restart the LPI before changes take effect.

• Debug Log. Defines the name of the SIP stack debug log. The path is relative to the root directory of the LPI. The application default is /logs/pagingDebug.log. If you change the Debug Log field, you must restart the LPI before changes take effect.

• Server Log. Sets the name of the log file where valid incoming SIP requests are written. The path is relative to the root directory of the LPI. The application default is /logs/pagingServer.log. If you change the Server Log field, you must restart the LPI before changes take effect.

Note There is no reason for either the Debug or Server logs to be moved from their default locations.

• Trace Level. Controls the amount of information the SIP stack writes to the Server and Debug logs. When set to zero, no information is written to the Server or Debug logs. When set to 16 or greater, incoming valid messages are logged in the Server log. When set to 32, vast amounts of trace information is written to the Debug log, along with valid messages to the Server log. The application default is zero. If you change the Trace Level field, you must restart the LPI before changes take effect.

Note Zero is the recommended value for the Trace Level field. Larger values are only required when you want to see what the SIP stack is doing. You will never want to run the LPI with anything other than zero in the Trace Level field unless you are troubleshooting something for Singlewire’s Support personnel.

• Socket Min Port. Sets the minimum port number that will be allocated by datagram sockets used to send RTP packets. The value of this field must be an even number.

• Socket Max Port. Sets the maximum port number that will be allocated by datagram sockets used to send RTP packets. The value of this field must be an odd number and less than 65,535.

• Traffic Class. Sets the value in the Differentiated Services field in the IP header of RTP packets sent by the LPI. This value is used to assign a Quality of Service (QoS) ranking to voice and audio traffic on the network. For recommended values, see the Problem on page 69.




Configure Paging DevicesBefore you can send broadcasts to your legacy paging system, you must first add paging devices and paging zones to the LPI.

Add a Paging Device

A paging device is a physical unit that allows broadcasts via one or several groups of loudspeakers. Paging zones are groups of loudspeakers to which a paging device provides access. InformaCast sees paging zones as regular IP speakers.

Step 1 Click the Paging Devices link. The Paging Devices page appears.




Step 2 Click the Add a New Paging Device icon ( ). The Add Paging Device page appears.

Step 3 Enter a name for your paging device in the Device Name field. This field is mandatory and identifies the paging device in the LPI. Each paging device must have a unique name.

Step 4 Enter the IP address of the paging device in the SIP IP Address field. This field is mandatory and used for placing phone calls with the paging device. For InformaCast, this is the IP address of Communications Manager, and it should also be a member of the Communications Manager group you selected in Step 4 on page 14.

Step 5 Enter the network port used by the paging device in the SIP Port field. This field is mandatory and specifies the port at which the paging device accepts requests to start phone calls.

Note The default is 5060. The only reason to change this value would be if its corresponding value on the PBX was changed, or if there is another SIP application already installed on the same server that is using port 5060.

Step 6 Enter the Directory Number (DN) of the analog paging system with which the SIP session is to be established in the SIP User field.

Step 7 Enter 0 in the Max SIP Response Time field. This field is mandatory and determines how long the LPI will wait for the paging device to answer phone calls.

Step 8 Select the RFC2833 radio buttons for DTMF via to specify how DTMF tones are sent to the paging device.




Step 9 Enter a numerical value (in milliseconds) in the DTMF Duration field. This field is mandatory and specifies the duration of each individual digit that comprises a DTMF sequence. The default value of 500 milliseconds is usually acceptable, but some older models of paging devices may require a longer duration.

Step 10 Enter a numerical value (from 0 - 36, with 0 being the loudest) in the DTMF Volume field. This field is only applicable when DTMF tones are sent as part of the RTP stream (i.e. selecting the RFC2833 option with the DTMF via radio buttons).

Step 11 Enter a numerical value (in milliseconds) in the Pause Before First DTMF field if the paging device cannot immediately accept DTMF tones after answering a phone call. This tells the LPI to wait that amount of milliseconds before sending the first DTMF tone.

Step 12 Enter a numerical value (in milliseconds) in the Pause After Last DTMF field if paging zone activation requires a certain amount of time. This tells the LPI to wait that amount of milliseconds after the LPI sends the last DTMF tone before streaming audio.

Note If you’re not sure on the pauses for either the Pause Before First DTMF or Pause After Last DTMF fields, leave these two fields at their default values of 500 milliseconds.




Add a Paging Zone

Once you’ve added a paging device, you can add zones to the device to further configure your broadcasting abilities.

Step 1 Click the Add button. The Paging Zones section expands.

Note The MAC Address field will automatically populate with an unique MAC address, which was generated from the MAC Address Prefix field on the Configuration Parameters page.

Step 2 Enter an unique name for this zone in the Zone Name field.

Step 3 Leave the MAC Address field set as suggested by the LPI or enter your own unique value. Singlewire recommends that you use the generated MAC address.

Step 4 Enter the code(s) for this zone in the DTMF Codes field.

Note Each paging zone may have one or more DTMF tones (or codes), separated by commas. Normally, each paging zone will have an individual DTMF code, i.e. a code that selects only that zone, which is dialed after placing a call with the paging device. If the paging device allows paging zones to be grouped, you may have additional DTMF codes that select multiple zones as members of a zone group.




Step 5 Click Add button to add another zone or click the Save button if you are finished adding zones. In the following picture, you can see a correctly set up paging device with multiple zones.

In the Paging Zones section, DTMF code 0 will reach all zones, DTMF code 1 will only reach the first floor, and DTMF code 2 will only reach the second floor.




Step 6 Click the Status button to open a new window with endpoint and gateway details, the current state of zone, and details on configuration and registration, etc.




Edit a Paging Zone

Once you’ve added paging zones, you may need to edit their information.


Step 2 Click the Device Name link of the paging device whose paging zone you want to modify. The Edit Paging Device page appears.

Step 3 Scroll down to the Paging Zones section and modify your information.





Delete a Paging Zone

As your needs change, you may want to delete unused paging zones from the system.





Step 2 Click the Device Name link of the paging device whose paging zone you want to delete. The Edit Paging Device page appears.

Step 3 Scroll down to the Paging Zones section and click the Delete button next to the paging zone you want to delete.

Step 4 Click the OK button.





Edit a Paging Device

Once you’ve added paging devices, you may need to modify their information.


Step 2 Click the Device Name link of the paging device you want to delete. The Edit Paging Device page appears.

Step 3 Modify your information.





Delete a Paging Device

As your needs change, you may want to delete unused paging devices from the system.


Step 2 Click the Delete Paging Device icon ( ) next to the paging device you want to delete.

Step 3 Click the OK button.




View Current Activities

The Current Activities page displays the broadcasts that the LPI’s paging zones are involved in at any time. It also allows you to stop the delivery of an active broadcast to any participating paging zone. The following picture shows an example of what you will see when a broadcast is being delivered to the LPI’s paging zones.

You see when the broadcast started, the sender’s IP address, the multicast IP address and port of the audio stream sent by InformaCast, and the recipients receiving the broadcast. Clicking the Stop button will stop the device from playing the broadcast.

The Current Activities page also displays any active paging zone tests and allows you to stop them, if necessary. Since InformaCast sees the LPI’s paging zones as regular IP speakers, it is possible to test how they function by sending a test request to any of them from the InformaCast web interface. When the LPI receives a request to perform a test of a paging zone, it places a call with the paging zone’s paging device, dials the zone that is being tested using its individual DTMF code, and streams the test sound to it. The following picture shows what you see on the Current Activities page when the test of a paging zone is in progress.




Clicking the Stop button will stop the paging zone’s test.

Add the LPI to InformaCast as an IP SpeakerBefore InformaCast can send out broadcasts to your analog paging system, the LPI must be added as an IP speaker. Follow the steps in the “InformaCast Installation and User Guide” for defining/adding an IP speaker and adding that IP speaker to a recipient group.

Send a BroadcastOnce everything has been configured, a user holding message sending rights in InformaCast can simply select one or more paging zones from the list of recipients on InformaCast’s Send Message page (Send or Edit Messages link | Send button of a specific message). The LPI will look at the paging device to which the selected zones belong, determine the DTMF tone needed to broadcast to the selected zones, and allow the broadcast to stream to your legacy paging device.

Tip When selecting an InformaCast message, ensure that the value in the Wait Time field (for Synchronized messages only) is set to at least 5. Lowering this value may impede your paging zones from receiving your broadcast.



Legacy Paging Interface Installation and User GuideTroubleshooting

TroubleshootingThis section is intended to help track down and resolve the common problems people face when installing and working with the LPI.

Upgrade the LPI

Problem What are the steps for upgrading the LPI?

Solution If you upgrade your version of the LPI, contact Singlewire for a new Virtual Appliance and license, and follow the steps in the following sections.

Install a Software Package

When you upgrade the LPI, you must upgrade your Virtual Appliance and replace your license from Singlewire Software. Once you have these items, continue with the following steps.

Step 1 Make a backup of your current LPI installation.

Step 2 Log into the InformaCast Virtual Appliance (see Step 1 on page 30).



Tip Leave your Singlewire Start page tab/window open. You will come back to it in the next section.







Step 5 Go to System | Software Packages. The Software Packages page appears.




Step 6 Select the From uploaded file radio button in the Install a New Package area and click its Browse button. The Choose File to Upload dialog box appears.

Step 7 Navigate to where you saved the software package you acquired earlier, select it, and click the Open button.

Step 8 Click the Install button in the Install a New Package area. A pop-up window will appear showing you the transferring of the file.

After transferring the file, the Install Package page appears.

Step 9 Leave the default selections as they are and click the Install button. Your software package is installed.

Note The Install Package page should display a long list of files that were correctly installed. If you see something different, please make a note of what you see and contact Singlewire Support.






Step 11 Click the Reboot System button at the bottom of the page. The Reboot page appears.

Step 12 Click the Reboot System button. The Reboot page refreshes and the Virtual Appliance reboots. This may take a few moments.




Note Leave this window open. You will come back to it in the next section.

Step 13 Clear your web browser’s cache.

Manage your New License

Before you can perform these steps, you must have a license that includes the LPI. If your salesperson has not already provided one to you, contact Singlewire and request that a license be emailed to you.

Step 1 Return to the Singlewire Start page.

Step 2 Click the Access Application Management Tools with the Toolbox link. A separate tab/window opens to the Toolbox homepage.






Step 3 Click the License Manager link. The License Manager Login page appears.

Step 4 Enter your username and password in the Login and Password fields, respectively. By default, your username is admin and your password is changeMe. Click the Login button. The License Status page appears.




The License Manager holds all of your Singlewire licenses. Depending on the software applications you are using, you will see different licenses housed on this page.

Step 5 Click the Browse button. The Choose File to Upload window appears.

Step 6 Navigate to where you saved your new license file, select it, and click the Open button.




Step 7 Click the Upload button on the License Status page. Your page refreshes with a confirmation that the license has been uploaded.

Note If your new license key contains less functionality than your previous key, you will be presented with a warning to that effect, a comparison of your two licenses, and the request to click the Apply button to confirm the change.




Step 8 Return to your Virtual Appliance server’s window and click the Bootup and Shutdown link. The Bootup and Shutdown page appears.

Step 9 Select all of your Singlewire applications that were affected by your new license and click the Restart button. The Restarting Actions page appears.

Start/Stop/Restart the LPI

Problem What are the steps for starting, stopping, and restarting the LPI?

Solution Backing up and restoring the LPI or application malfunction are all reasons you would need to start, stop, and restart the LPI.




Stop the LPI

Follow these steps to stop the LPI.








Step 6 Click the Stop Now button. It will take a minute or so for the LPI to stop.

Start the LPI

Follow these steps to start the LPI.








Step 6 Click the Start Now button. It will take a minute or so for the LPI to start.

Restart the LPI

Follow these steps to restart the LPI.









Step 5 Scroll down the list of actions until you come to singlewireLPI. Select it by placing a checkmark in its Action column and click the Restart button. The Restarting Actions page appears.

It will take a minute for the LPI to restart.

Resolve Call Routing Error

Problem I have my call routing configured properly, but the LPI isn’t sending my broadcasts. Also, the LPI’s log (located at /usr/local/singlewire/LPI/web/logs) is showing the error, “404 Not Found.” Why isn't the LPI sending broadcasts?

Solution Your Communications Manager isn’t routing the calls properly. Use the following steps to remedy the problem. If it’s still not working, you’ll need to contact Cisco to solve the problem.




• Log into your Communications Manager.

• Go to Device | Trunk.

• Click the Find button.

• Locate the LPI’s SIP trunk and make a note of the calling search space being used.

• Log into your Communications Manager’s DNA (typically, this is http://<IP Address of your Communications Manager>/dna, where <IP Address of your Communications Manager> should be replaced by your actual Communications Manager IP address).

• Go to Analysis | Analyzer.

• Enter the DN to which you’re trying to broadcast in the Dialed Digits field.

• Set the calling search space to the same one listed with the SIP trunk.

• Click the Do Analysis button.

• Expand the contents of the output.

• Verify that the Dialed Number Analyzer shows the call routing through to the analog paging system number that was entered. If the DNA tells you it can't route your call, make sure your calling search space, partition, and directory number are configured correctly.

Determine SLP vs Static URL

Problem How do I know if I should use SLP or a static URL for my speakers?

Solution The LPI allows InformaCast to interact with traditional paging systems by making the traditional paging zones “look like” regular IP speakers. That is, each paging zone defined in the LPI behaves just like a usual IP speaker and, as such, it must be able to configure itself. Regular hardware IP speakers can use only one method for discovering their configuration: the SLP protocol. They don’t have a user interface, so the only way to configure a hardware speaker is to plug it into the network and hope it find its configuration somewhere.

Unlike hardware speakers, the LPI’s look-alike software speakers do have a user interface. So, in addition to the SLP protocol, they can be set up to use a static URL for downloading their configuration.

In order to choose whether the LPI should use SLP or a static URL for configuring its software IP speakers, you should see if you are already using regular hardware IP speakers. If you are, it should be safe to make the LPI use the SLP protocol, because the InformaCast server is already set up correctly to advertise itself as a configuration file server (via the advertiseCFS parameter in the web.xml file) and to serve a valid IP speaker configuration file.

If you are not using hardware IP speakers, it is easier to use a static URL. In this case, you should ensure that the contents of the IP speaker configuration file served by InformaCast are correct. On the Configuration Parameters page, enter http://<InformaCast Server IP Address>:8081/InformaCast/resources/ in the Speaker Configuration URL field. Replace <InformaCast Server IP Address> with the address of your InformaCast server.




Resolve SIP Client Call Connection

Problem The SIP client call won’t connect.

Solution The problem could be with the configuration of your calling search space or region in Communications Manager:

• Ensure that the calling search space assigned to the SIP trunk allows a call to the partition in which the paging extension is located

• Use the Dialed Number Analyzer (DNA) to ensure (http://<CM IP Address>/dna)

• Verify that G.711 µlaw is selected in your region’s settings

Problem The SIP client call connects, but there’s no DTMF.

Solution If the call connects, but no DTMF is heard or no zone is selected, there is an issue with the MTP. See the following Cisco article for more help: https://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00808b6ca6.shtml.

Set Singlewire Traffic Class

Problem What are the recommended values for traffic class settings for the LPI?

Solution The values needed by Singlewire applications do not follow RFC 2474. This RFC states that the values used to obtain DSCP values are done on six bits. However, Singlewire applications use all eight bits of the field to obtain the decimal value.

The following table lists common values as they would be recognized using industry standards and the corresponding Singlewire application values.

Note This information is only relevant if DSCP QoS settings are not being done at the network or operating system level, but by a Singlewire application itself.

Code

Industry Standard Singlewire

Binary Decimal Binary Decimal

CS0 000 000 0 000 000 00 0

CS1 001 000 8 001 000 00 32

AF11 001 010 10 001010 00 40

AF12 001 100 12 001 100 00 48

AF13 001 110 14 001 110 00 56

CS2 010 000 16 010 000 00 64

AF21 010 010 18 010 010 00 72

AF22 010 100 20 010 100 00 80

AF23 010 110 22 010 110 00 88

CS3 011 000 24 011 000 00 96



https://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00808b6ca6.shtml

https://www.cisco.com/en/US/products/sw/voicesw/ps556/products_tech_note09186a00808b6ca6.shtml


Change the IP Address of the LPI Server

Problem Is it possible to change the IP address of the LPI server?

Solution Yes. Use the following steps to change the IP address of the LPI server.

Note Performing these steps will set all of your Singlewire applications to start when the server boots.

Step 1 Contact your salesperson at [email protected] to obtain a new license for the new IP address.

Step 2 Stop the LPI (see “Start/Stop/Restart the LPI” on page 61 for steps on starting and stopping the LPI).

Step 3 Install your new Virtual Appliance (see “Install a Software Package” on page 53).

Step 4 Use the vSphere client to access the LPI’s command line interface: select your LPI virtual machine and go to Inventory | Virtual Machine | Open Console.

Note Singlewire supports the Virtual Appliance on the VMware ESX 4.0 and later platform. This platform is managed through the vSphere client.

Step 5 Press Alt + F2 to reach the login prompt.

Step 6 Enter admin at the prompt and press Enter.

Step 7 Enter changeMe at the prompt and press Enter.

Step 8 Enter change-ip-address and press Enter.

Step 9 Enter Y and press Enter.

Step 10 Enter a routable IP address on your network that’s not currently in use and press Enter.

Step 11 Enter a valid netmask for that IP address and press Enter.

Step 12 Enter the default gateway for your specified IP address and press Enter.

Step 13 Enter the IP address(es) of a DNS server(s) on your network and press Enter.

AF31 011 010 26 011 010 00 104

AF32 011 100 28 011 100 00 112

AF33 011 110 30 011 110 00 120

CS4 100 000 32 100 000 00 128

AF41 100 010 34 100 010 00 136

AF42 100 100 36 100 100 00 144

AF43 100 110 38 100 110 00 152

CS5 101 000 40 101 000 00 160

EF 101 110 46 101 110 00 168

Code

Industry Standard Singlewire

Binary Decimal Binary Decimal





Step 14 Enter Y and press Enter.

Step 15 Enter Exit and press Enter.

Step 16 Log into License Manager and apply your new LPI license (see “Manage your New License” on page 57).

Step 17 Log into Communications Manager, go to System | Enterprise Parameters, and change the URL Authentication field to reflect your new IP address. Also, go to Device | Device Settings | Phone Services, and change the IP address for any LPI service URLs you have created.

Note If you are using Communications Manager 8.x, you will need to enter this IP address in the Secured Authentication URL field as well.

Note You need to use the Update Subscriptions button whenever you change service information, so that any subscribed phones are properly updated.

Step 18 Reset all of your phones.

Further InformationFor troubleshooting purposes, you can also look at the logs for InformaCast and the LPI and perform CCM traces or traffic captures.

InformaCast logs (typically located in /usr/local/singlewire/InformaCast/web/logs) will show communication between InformaCast and the LPI. Because InformaCast triggers the LPI to start a telephone call, the InformaCast log will show whether InformaCast was able to successfully trigger the LPI and what the LPI’s response was.

The LPI logs (typically located in /usr/local/singlewire/LPI/web/logs) will show information on the communication between itself and CUCM for setting up a call. Detailed SIP information is not logged, but there will be errors reported.

CCM traces will show the actual SIP content for the call setup. This call signaling allows for any events to be seen from start to finish and tracked for errors in setting up the call. Likewise, you could also see if MTP was properly allocated by the Media Resource Manager. Use Communications Manager Serviceability to turn on detailed traces for the Communications Manager service and use RTMT to pull Communications Manager traces.

By running a Wireshark traffic capture on the LPI server, you could see the actual SIP packet data used for call setup and teardown. With this data, you could see if the call from the LPI to Communications Manager was completed properly and, if not, on what side the error occurred. To set up a traffic capture, install Wireshark on the LPI server or the workstation using the SIP client.

The following real-life examples provide a blueprint for easy troubleshooting:

• If you’ve determined that the call from the LPI and/or Linphone isn’t set up properly, you could run a traffic capture on the server or desktop to see the SIP call setup and look at the CCM traces to see call setup.




• If the call is set up properly, but there is no DTMF to select a zone, troubleshoot MTP by looking at the CCM traces to see that the Media Resource Manager inserted MTP.

• If the LPI does not register with InformaCast, look at the LPI and InformaCast logs to see if there are any errors.

• If InformaCast broadcasts to phones but not the existing paging system, ask yourself:

– Did the call get setup?

– Did DTMF get used for the zone selection?

– Was the LPI registered with InformaCast?

Look in the InformaCast logs to see that the LPI speaker was tried for activation. Look at the LPI logs to see that InformaCast contacted it, and that LPI tried to place a phone call. Run a traffic capture to see the SIP call setup messages. Look at the CCM traces to see the call setup messages and whether the Media Resource Manager allocated MTP.



Legacy Paging Interface Installation and User GuideRelease Notes



Release NotesThe following sections contain the release notes for the LPI from version 1.0.a through the current version.

What’s New in the LPI 1.1.1.a?Newly Supported Communications Manager. Cisco’s Unified Communications Manager 10.0 is now supported by the LPI.

What’s New in the LPI 1.1.1?Resolved Data Issue. Configuration settings are now preserved on upgrades from LPI 1.1.

What’s New in the LPI 1.1? • New Virtual Appliance for the LPI. Previously only available on a Windows platform, the LPI

is now available on the Singlewire Virtual Appliance for virtual environments. A separate user guide has been created to support this new environment.

• New InformaCast EX. InformaCast EX is a new offering from Singlewire Software that bundles InformaCast, CallAware, the LPI, and all of InformaCast’s plugins into one OVA, available for download for InformaCast Virtual Appliance users.

• New License Manager for InformaCast EX. The Singlewire Toolbox houses the License Manager for InformaCast EX. This new management system allows you to manage all of your Singlewire Virtual Appliance licenses from one interface.

What’s New in the LPI 1.0.a?In v1.0.a, the “Configuration” chapter has been expanded to include configuring a proper Cisco Unified Communications Manager environment (if you’re using InformaCast) and testing that environment to ensure the LPI works correctly upon installation. The “Configuration” chapter was also expanded to include configuration of a SIP-enabled PBX or, in the absence of that, a PBX with an attached SIP-enabled device for an InformaCast SE environment.

Legacy Paging Interface™ 1.1.1 - Amazon S3 · For testing purposes, a workstation running a...

Documents

Transcript of Legacy Paging Interface™ 1.1.1 - Amazon S3 · For testing purposes, a workstation running a...