[asterisk-users] 1.6rc4 chan_iax2 messages

Tilghman Lesher tilghman at mail.jeffandtilghman.com
Thu Sep 4 13:42:30 CDT 2008


On Thursday 04 September 2008 12:59:33 MFH wrote:
> As a result of:
> http://lists.digium.com/pipermail/svn-commits/2008-July/036122.html
>
> I am seeing these messages when upgrading for 1.6b9 to 1.6rc4.  Is there
> something I should be doing to address this warning?
>
> [Sep  4 13:31:34] WARNING[2954]: chan_iax2.c:1200 __send_lagrq: I was
> supposed to send a LAGRQ with callno 14670, but no such call exists (and
> I cannot remove lagid, either).
> [Sep  4 13:34:34] WARNING[2949]: chan_iax2.c:1200 __send_lagrq: I was
> supposed to send a LAGRQ with callno 13447, but no such call exists (and
> I cannot remove lagid, either).
> [Sep  4 13:39:14] WARNING[2956]: chan_iax2.c:1200 __send_lagrq: I was
> supposed to send a LAGRQ with callno 14442, but no such call exists (and
> I cannot remove lagid, either).
> [Sep  4 13:40:34] WARNING[2949]: chan_iax2.c:1200 __send_lagrq: I was
> supposed to send a LAGRQ with callno 11096, but no such call exists (and
> I cannot remove lagid, either).
> [Sep  4 13:42:14] WARNING[2951]: chan_iax2.c:1200 __send_lagrq: I was
> supposed to send a LAGRQ with callno 14517, but no such call exists (and
> I cannot remove lagid, either).
> [Sep  4 13:42:54] WARNING[2954]: chan_iax2.c:1200 __send_lagrq: I was
> supposed to send a LAGRQ with callno 2761, but no such call exists (and
> I cannot remove lagid, either).
> [Sep  4 13:43:34] WARNING[2949]: chan_iax2.c:1200 __send_lagrq: I was
> supposed to send a LAGRQ with callno 10117, but no such call exists (and
> I cannot remove lagid, either).
> [Sep  4 13:44:54] WARNING[2951]: chan_iax2.c:1200 __send_lagrq: I was
> supposed to send a LAGRQ with callno 4215, but no such call exists (and
> I cannot remove lagid, either).

They're actually pretty harmless messages.  I may wind up moving them to
DEBUG only.  You'll only get them when a host is unreachable during a call,
though, so you may want to figure out why that host became unreachable.

-- 
Tilghman



More information about the asterisk-users mailing list