Adrian, In general, is it acceptable to have a slight mismatch between versions of the dispatcher and relay? I ask because my dispatcher is on CentOS, which is a pain to update compared to the relative ease of updating my Debian relay.
Specifically, how about a 2.3.6 dispatcher and a 2.3.7 relay? The changelog seems to reflect updates mostly if not all to the relay anyway. - Jeff On 9/4/09 7:34 AM, "Adrian Georgescu" <[email protected]> wrote: > Hello, > > There is a new release of MediaProxy available, it contains several bug fixes. > > To upgrade your debian unstable installation: > > sudo apt-get update > sudo apt-get install mediaproxy-dispatcher mediaproxy-relay > mediaproxy-web-sessions > > Or download the tar file from: > > http://download.ag-projects.com/MediaProxy/ > > The changelog follows: > > mediaproxy (2.3.7) unstable; urgency=low > > * Fixed typo in debian changelog > * Improved some error messages > * Do not try to send media to port 0 in tests > * Fixed handling of streams that are disabled when their port is set to 0 > * Added 2 more tests for sessions with disabled streams > * Automatically restore the media_sessions table if gone during runtime > * Allow the to_tag field in the media_sessions table to be NULL > * Fixed issue in radius accounting when to_tag is None > > > Kind regards, > Adrian Georgescu > > > > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
