asterisk users - May 2006 - Forcing Marker bit

Ever since upgrading to 1.2.8 I've been getting occasional WARNINGS that
say:

WARNING[4356]: rtp.c:500 ast_rtp_read: Forcing Marker bit, because 
SSRC has changed.

Is there something I need to fix or is this a benign message?

Ira


-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.1.394 / Virus Database: 268.8.0/352 - Release Date: 5/30/2006

Ira wrote:
> WARNING[4356]: rtp.c:500 ast_rtp_read: Forcing Marker bit, because SSRC
> has changed.
> 
> Is there something I need to fix or is this a benign message?
Nope, it's normal. It should be happening after a SIP transfer has
completed. Probably shouldn't be a WARNING, though.

In article <68be8a270606010218n3753255bi7795a5c15c02c78a@mail.gmail.com>,
Andrew Furey <andrew.furey@gmail.com> wrote:
> On 6/1/06, Tony Mountifield <tony@softins.clara.co.uk> wrote:
> > # script /tmp/output.txt
> > Script started, file is /tmp/output.txt
> > # exec asterisk -rvvvvv
> > ... do asterisky stuff ...
> > host*CLI> exit
> > Script done, file is /tmp/output.txt
> > #
> 
> Actually you need another exit in there:
> 
> # script /tmp/output.txt
> Script started, file is /tmp/output.txt
> # exec asterisk -rvvvvv
> ... do asterisky stuff ...
> host*CLI> exit
> Executing last minute cleanups
> # exit
> Script done, file is /tmp/output.txt
> #
Not if you do "exec asterisk -r" as I did, instead of just
"asterisk -r".
Using "exec" makes asterisk replace the shell that was started by
"script",
and therefore auto-exits when you exit asterisk. That is why I use exec
in that way - it saves me forgetting the second exit and filling up the
script file with rubbish, or even worse, trying to edit it while it is
still active!

Cheers
Tony
-- 
Tony Mountifield
Work: tony@softins.co.uk - http://www.softins.co.uk
Play: tony@mountifield.org - http://tony.mountifield.org