[asterisk-dev] IAX inval packet

[Stanisław Pitucha]

Hi
I've been writing a tool for routing IAX packets lately and hit some
strange asterisk behaviour - it doesn't happen on the first call.
Probably only when source call number is reused after some other
connection.

It's my internal log, but effect should be obvious:

IAX - incoming - full 1 - added 169.254.1.1 ---
IAX - outgoing - full 7 established: c1-s1 - existing 169.254.1.1 ---
IAX - incoming - full 4 - existing 169.254.1.1 ---
IAX - outgoing - full 4 - existing 169.254.1.1 ---
IAX - outgoing - full 2 - existing 169.254.1.1 ---
IAX - incoming - full 4 - existing 169.254.1.1 ---
IAX - incoming - full 4 - existing 169.254.1.1 ---
IAX - incoming - full 5 - existing 169.254.1.1 - hangup ---
IAX - outgoing - mini - existing ---
IAX - outgoing - full 4 - existing 169.254.1.1 - hangup ack ---
IAX - outgoing - full 10 - no connections: ignoring ---

It's a very short connection - basically what you see is type 10
(INVAL) packet after hangup ack. After it happened once, it happens
after every connection. It is sent by host that sent hangup ack before
and that's the same host that sent the only voice mini frame in that
call - why shoud it send INVAL after that?
INVAL packet got seqno==0 of course, so I can't tell what packet it
tried to respond to.

Should I report a bug?