[asterisk-users] 1.6rc4 chan_iax2 messages

[MFH]

I was on the call at the time and was not experiencing any apparent 
problems. 

As I was responding I did some further investigation and saw the 
messages even when there wasn't an active call (so I thought).  I looked 
at the active IAX channels:

[Sep  4 14:27:14] WARNING[2956]: chan_iax2.c:1200 __send_lagrq: I was 
supposed to send a LAGRQ with callno 6467, but no such call exists (and 
I cannot remove lagid, either).
[Sep  4 14:35:14] WARNING[2958]: chan_iax2.c:1200 __send_lagrq: I was 
supposed to send a LAGRQ with callno 5345, but no such call exists (and 
I cannot remove lagid, either).

asterisk*CLI> iax2 show channels
Channel               Peer             Username    ID (Lo/Rem)  Seq 
(Tx/Rx)  Lag      Jitter  JitBuf  Format
(None)                67.202.54.166    (None)      02713/00000  
00001/00000  00000ms  -0001ms  0000ms  unknow
1 active IAX channel

and determined that this is a connection to an Amazon EC2 image that I 
was using for testing but recently deactivated:

asterisk*CLI> iax2 show peers
Name/Username    Host                 Mask             Port          Status
asterisk2/aster  67.202.54.166   (S)  255.255.255.255  4569          
UNREACHABLE


[asterisk2]
   type=friend
   username=asterisk2
   secret=pass
   auth=md5
   host=asterisk2.myhost.com
   context=frompeer
   peercontext=frompeer
   qualify=yes
   trunk=yes

I'm going to remove this definition and see if the messages go away.

MARK.

Tilghman Lesher wrote:
> 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.
>
>