Version History File For LanScape VOIP Media ProxyServer

Version 2.72


“Allow your customers to do what they do best, communicate.” ™



This file will briefly outline the product changes, enhancements and bug fixes that have been performed on the LanScape VOIP Media ProxyServer.

Version History:



New Features and Capabilities

Product distribution now includes the LanScape Service Manager Suite.

The VOIP Media Proxy Server now comes bundled with the LanScape Service Manager Suite. With the LanScape Service Manager Suite, you can now run the SIP proxy server as a windows service. The Service Manager Suite can also be used to run any other user supplied GUI or console application, batch file or script as a Windows service..

VOIP Media Proxy Server can now execute as a service using the Service Manager Suite.

The VOIP Media Proxy server can be executed on the server host machine as an NT service or a Windows service. The primary advantage of running the proxy server as a service is that the VOIP Media Proxy® server will be started when the host machine is started. It does not matter if a user logs into the server machine or not. The VOIP Media Proxy® server will also automatically shutdown gracefully when the server host machine shuts down.

Benefits of running as a service:

Automatically start and stop the proxy server when the host machine starts/stops.

Monitor the proxy server for fault situation.

Automatically restart the proxy server if faults occur.

Periodically restart the proxy server software if need be to help preserver long term overall server stability.

Create log file data that reflects the fault monitoring activity of the proxy server.

Running VOIP server software as a service is generally required in secure network environments.

Added remote event logging capabilities.

Remote event logging capabilities have been added to this latest release of the VOIP Media Proxy Server. Remote event logging allows other third party server monitoring tools to be used with the VOIP Media Proxy Server. This capability is primarily use when deploying multiple VOIP Media Proxy Servers that are running as a service on the server host machine.

However, remote event log monitoring can also be used for single server deployments if required.

Added proxy configuration backup and restore support.

The VOIP Media Proxy server now supports media proxy configuration backup and restore support. This capability is useful when administering multiple media proxy servers or when debugging multiple media proxy configurations.

Enable or disable system tray balloon tips.

Added support for enabling or disabling system tray balloon tips. When disabled, the media proxy will not display system tray "informational balloons" during media proxy operation.

Proxy now reports an error if UDP port are in use.

The VOIP Media Proxy Server now reports an appropriate error if any of the required UDP ports are in use by other applications. If other applications are using the configured SIP port, an error will be logged to the event log area of the GUI.


Bug fixes

Main application window position problem.

Under certain conditions, the main application window of the proxy may not be visible or is displayed off screen when the proxy server starts up. When this occurs, the main application window cannot be viewed. This problem has been fixed.

Main application windows not being displayed.

Under certain situations the main VOIP Media Proxy application window may not be displayed if the operating system was shut down and the proxy server was still running.

When this condition occurred, the only way to get the main window to display properly would be to delete registry entries associated with the last main window position.

This problem is related to the proxy server’s ability to keep track of the last main window position. In some shut down scenarios, the proxy would get all negative screen coordinates for the main window. Then next time the proxy is started, the main window would be moved “off screen” thus making it look as if the main window is never displayed even though an icon can be seen in the system tray and the proxy server is present in the task bar.

This problem has been fixed.

Main proxy event log file not saved to default directory.

Under certain situations, the log file used for proxy event logging may not be saved to the desired working directory of the proxy. This problem has been fixed.

Modified the installer so that when upgrading, multiple entries are not shown in Add/Remove Programs.

The product installation image has been updated so that when upgrading to future version, you can install over the top of your existing installation and not have multiple entries being shown in Add/Remove Programs of control panel.

If you are upgrading from an earlier version of this software to this latest version, you can still install this version over your existing installed image. However, you will see two product entries in Add/Remove Programs. If you do not want to see multiple entries for this product in Add/Remove Programs, uninstall your current version and install this latest version.

Note: Be sure to make a backup of the current install directory to ensure that critical license or other files do not mistakenly get deleted.

Fix media session terminate race condition.

Under certain call situation and system loading, the media proxy may experience a race condition that might not allow a media session to be terminated synchronously with session call termination. This issue has been fixed.



New Features and Capabilities

Media Proxy now passes version information to Centrex Proxy Servers.

The VOIP Media Proxy now passes version information to configured Centrex Proxy Servers. This allows configured Centrex Proxy Servers to detect VOIP Media Proxies that are unsupported.

Relate sibling media channels on a per call basis.

The "Relate Sibling Media Sessions" configuration feature has been added to the VOIP Media Proxy.

Normally, when a call is established that contains more than one media session, the individual media sessions would separately be evaluated periodically for media session timeouts (not receiving media) and other similar media states. In some deployment situation, this could cause some of the media streams of calls to be terminated due to inactivity in a subset of the media channels while other media channels of the call remained active.

To solve this problem, the VOIP Media Proxy can perform media session evaluation of individual media channels in addition to evaluating all sibling media channels.

Stated another way: Enabling this feature allows the media proxy to manage multiple call media streams as a single media stream block. What this means is that for calls that require multiple media streams, no single media stream will be destroyed due to media timeouts unless all of the other "sibling" media channels also timeout.

Supports up to 128 Media streams per call session.

The LanScape VOIP Media Proxy now supported up to 128 Media streams per call session. The media sessions can be any data rate and format the call endpoints require.

Added the ability to perform dynamic IP address monitoring.

The VOIP Media Proxy can now be deployed on a host machine using a dynamic IP address. The VOIP Media Proxy can be configured to monitor its dynamic IP address and inform all Centrex Proxy Servers when an IP change is detected.

This feature is especially useful for SOHO (small office - home office) deployments where a static IP address for the proxy server is not available or possible.

Note: LanScape still recommends that you deploy our session and media proxies using static IP addresses. However, this capability allows the deployment where static IP addresses are not available.

Improved the throughput capabilities of the media handling logic

The media handling logic has been optimized to a fuller degree to allow a higher level of calls per minute to be media proxied.


Bug fixes


There were no bug fixes in this version.






Initial version 2.x product offering. Replaces all legacy versions of LanScape VOIP Media proxies.










January 2009,

LanScape Corporation