[OpenSIPS-Users] New MediaProxy release 2.3.3

[Jeff Pyle]

Hello,

I attempted an upgrade from 2.3.2, recompiling from source.  Everything
seemed to build and install okay.  But, when running media-dispatcher on
2.3.3, I receive the following error:

Traceback (most recent call last):
  File "/usr/bin/media-dispatcher", line 32, in ?
    log.level.current = config_file.get_option("Dispatcher", 'log_level',
default=log.level.DEBUG, type=datatypes.LogLevel)
AttributeError: 'module' object has no attribute 'level'


I reinstalled 2.3.2 and the error went away.


- Jeff



On 4/8/09 5:08 AM, "Adrian Georgescu" <ag at ag-projects.com> wrote:

> Hello,
> 
> There is a new release of MediaProxy available, it contains various bug fixes.
> To upgrade your debian installation:
> 
> apt-get update
> apt-get install mediaproxy-dispatcher mediaproxy-relay mediaproxy-web-sessions
> 
> Or download the tar file from:
> 
> http://download.ag-projects.com/MediaProxy/
> 
> The changelog since 2.3.2 is below:
> 
> mediaproxy (2.3.3) unstable; urgency=low
> 
>   * Re-raise the exception on failing to read RADIUS config file so we get a
>     full traceback
>   * Have dispatcher close TLS connection cleanly when relay has duplicate IP
>   * Added log_level to both Relay and Dispatcher configuration sections
>   * Improved reconnection behaviour in relay to dispatcher
>     When the connection from the relay to the dispatcher is lost, first retry
>     in 1 second, then retry in 10 second on subsequent attempts if it loses
>     the connection again.
>   * Fix bug where relay connects needlessly to previously removed dispatcher
>   * Implemented a keepalive mechanism from relay to dispatcher
>   * On relay reconnect don't have dispatcher query expired sessions
>   * Removed superfluous datatype declaration
>   * Only allow positive integers for time intervals and delays
>   * Updated version dependency for python-application
>   * In dispatcher, replace old connection from relay with new one instead of
>     giving an error
>   * In the dispatcher, check if the reported expired session belongs to the
>     relay that reported it
>   * Improved log messages when a relay reconnects to the dispatcher
>   * In dispatcher, break the connection to a relay if a request times out
>   * In dispatcher check if we know about the session that expired at relay
>   * Use a more robust strategy to disconnect an unresponsive relay
> 
> 
> Kind regards,
> Adrian Georgescu
> 
> 
> 
> 
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/users/attachments/20090408/8477eba9/attachment.htm