Home

LanScape VOIP Media Proxy™ - User's Reference

LanScape VOIP Media Proxy®

Tile Page

Part Number

Software License Agreement

Preface

Getting Started

Overview

Prerequisites

The LanScape VOIP Media Proxy®

General Description

Media Proxy Configuration

Performing Configuration

Configuration Dialogs

Basic Settings

Network Configuration

SIP Proxy Configuration

Wan IP/NAT Detection

Event Logging

Authentication

Backing up and restoring configuration information

Backing up the proxy configuration

Restoring the proxy configuration

Running Multiple Instances

Running more than one proxy on the same machine

Running the proxy server as a service

Running the proxy server as a service

Deployment Scenarios

Deploying in the global IP address space

Deploying in your private IP address space

Help File Version

Help File Version

Event Logging

The LanScape VOIP Media Proxy® has the ability to log certain events to the graphical user interface and to an associated event log file. It can also send event log data to a remote event log server.

The VOIP Media Proxy® comes with a simple event log server application you can use for remote monitoring of your media proxies. The event log server is a Windows console application called EventLogD.exe. This server application is installed on your machine when you install the LanScape VOIP Media Proxy® server software. For further information, please see the documentation for the EventLogD server application.

The following dialog is used to specify which logging activity is enabled for your media proxy:

Remote Event Logging

Enable remote event logging::

The proxy server has the ability to log all event information to a remote event log server. You must check this item if you want to enable remote event logging.

When enabled, event log information will be sent to the specified remote event log server using the UDP protocol. Figure 1 below shows an example of event information that could be sent to the remote server.

Figure 1: Example remote event log data.

Source Proxy Event Type Time Date Event log information.

_________________________________________________________________________________________________________________________________________

MediaProxy:mproxy1.lanscapecorp.com Info: 16:19:33 09/19/06 *************** VOIP Media Proxy Session Start ***************

MediaProxy:mproxy1.lanscapecorp.com Info: 16:19:33 09/19/06 VOIP Media Proxy® Starting...

MediaProxy:mproxy1.lanscapecorp.com Info: 16:19:33 09/19/06 Initializing control Port 16000...

MediaProxy:mproxy1.lanscapecorp.com Info: 16:19:33 09/19/06 Initializing Media Ports 16001-16064...

MediaProxy:mproxy1.lanscapecorp.com Info: 16:19:33 09/19/06 Initializing Media Ports 16065-16128...

MediaProxy:mproxy1.lanscapecorp.com Info: 16:19:33 09/19/06 Initializing Media Ports 16129-16192...

MediaProxy:mproxy1.lanscapecorp.com Info: 16:19:33 09/19/06 Initializing Media Ports 16193-16200...

MediaProxy:mproxy1.lanscapecorp.com Info: 16:19:33 09/19/06 Initializing address information for SIP Proxy "ps", (192.168.1.2:9000).

MediaProxy:mproxy1.lanscapecorp.com Info: 16:19:34 09/19/06 Communications with SIP Proxy ps (192.168.1.2:9000) has been established.

MediaProxy:mproxy1.lanscapecorp.com Info: 16:19:34 09/19/06 Media session monitor started.

MediaProxy:mproxy1.lanscapecorp.com Info: 16:19:34 09/19/06 VOIP Media Proxy® Ready

MediaProxy:mproxy1.lanscapecorp.com Session Start: 16:20:08 09/19/06 Media session created (audio). Media Port: 16001, Call Id: 00000ebc@192.168.1.80

MediaProxy:mproxy1.lanscapecorp.com Session Active: 16:20:09 09/19/06 Media stream active (audio). Media Port: 16001, Call Id: 00000ebc@192.168.1.80

MediaProxy:mproxy1.lanscapecorp.com Info: 16:20:09 09/19/06 ---------- Media Port Allocated -----------------------(16001)

MediaProxy:mproxy1.lanscapecorp.com Info: 16:20:09 09/19/06 Src UA(192.168.1.80:8528) <===> MediaProxy(192.168.1.2:16001) <===> Dest UA(192.168.1.2:20000)

MediaProxy:mproxy1.lanscapecorp.com Info: 16:20:09 09/19/06 Local RTP media synchronization applied.

MediaProxy:mproxy1.lanscapecorp.com Session End: 16:20:34 09/19/06 Media session closed normally (audio). Media Port: 16001, Call Id: 00000ebc@192.168.1.80

MediaProxy:mproxy1.lanscapecorp.com Info: 16:20:43 09/19/06 Terminating Media session monitor.

MediaProxy:mproxy1.lanscapecorp.com Info: 16:20:43 09/19/06 Terminated communications with SIP Proxy ps (192.168.1.2:9000).

MediaProxy:mproxy1.lanscapecorp.com Info: 16:20:43 09/19/06 Terminating control Port 16000...

MediaProxy:mproxy1.lanscapecorp.com Info: 16:20:44 09/19/06 Terminating Media Ports 16001-16064...

MediaProxy:mproxy1.lanscapecorp.com Info: 16:20:44 09/19/06 Terminating Media Ports 16065-16128...

MediaProxy:mproxy1.lanscapecorp.com Info: 16:20:45 09/19/06 Terminating Media Ports 16129-16192...

MediaProxy:mproxy1.lanscapecorp.com Info: 16:20:45 09/19/06 Terminating Media Ports 16193-16200...

MediaProxy:mproxy1.lanscapecorp.com Info: 16:20:45 09/19/06 VOIP Media Proxy® Terminated.

MediaProxy:mproxy1.lanscapecorp.com Info: 16:20:45 09/19/06 *************** VOIP Media Proxy Session End ***************

Each line is sent to the remote event log server individually. The fields of the even log data are separated by white space characters. The fields of the event log information are as follows:

Source Proxy:
This field is used to identify the source of the event log data. In figure 1, this fields has the value "MediaProxy:mproxy1.lanscapecorp.com". Note that a colon character is used to separate the server product name from the server host name.

Event Type:
This field identifies the disposition or "type" of the event log entry. The following event log types are currently defined:

Error	A proxy error was detected.
Warning	A proxy warning was detected.
Info	General information
Session Start	A VOIP phone call is starting. Media session(s) have been reserved.
Session Active	A VOIP phone call is connected and media session(s) are actively exchanging media.
Session End	A VOIP phone call has ended. Media exchange is terminated and any media session(s) used for the call are recovered

Time:
The time the event occurred at the proxy.

Date:
The date the event occurred at the proxy.

Event Log Information:
The "man readable" text data for the event.

Remote server:

This setting specifies the host name of the IP address of the event log server that will receive the event log data.

Remote port:

This setting specifies the UDP server port of the event log server.

Local Event Logging

Enable Event Logging:

If you check this option, then the local event log functions will be enabled. Local event logging is useful when you are initially setting up your VOIP network and when you require indications that VOIP call media processing is progressing properly. The overhead associated with event logging is small so you may want to always keep local logging enabled. The events that are logged are displayed in the log area of the graphical user interface and to the ASCII text file "VoipMediaProxy.log"

Max log entries:

The maximum number of log file entries maintained.

Log sounds enabled:

If checked, a tone will be played whenever an error is detected by the LanScape VOIP Media Proxy®. Error messages are the only events that cause an error tone to be sounded.

Ask for confirmation when clearing the log:

If checked, the media proxy will always ask for confirmation whenever you attempt to clear the log. If un-checked, the event log will be cleared immediately.

Event log auto save enabled:

If checked, the events will periodically be saved to a log file for later viewing. If un-checked, logged events are displayed only and not written to a log file until the server software terminates.

Event log save interval (Seconds):

When event log "auto save" is enabled, this is the time interval that events are written to the log file.

Event to log Group:

Check all event type you want to log. If you are particularly interested which VOIP calls get assigned to media sessions, make sure you check the "Media Related Events" check box. That way you will see "Session Start", "Session Active" and "Session End" events being logged.