On 10 Jul 2007, at 17:02, Stanisław Pitucha wrote: > 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.
I am finding it hard to read your log because you don't indicate the actual frame type, Which of those full frames are ProtocolControl frames and which Control ? If you could snoop the traffic with etherreal and post the log from that, it would be easier (for me at least) to see what is going on. (Asterisk iax debug logs wouldn't hurt either....) Tim Panton www.mexuar.net www.westhawk.co.uk/ _______________________________________________ --Bandwidth and Colocation Provided by http://www.api-digital.com-- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
