There isn't quite enough info in that log to tell what is going on.
What you have above is part of 2 separate conversations.
You have the tail end of a successful registration with 70.87.18.51
and the HANGUP of a call with 64.26.157.230 which your asterisk seems
to be confused about.
Could you try it again, and make sure you include the NEW message that
starts the call
which fails ? (assuming that is that there was a NEW !)
Tim,
There was no NEW. Some IAX2 messages just aren't reaching me, I think.
I think that the real problem is a short timeout (maybe 60 seconds?) in
my hardware firewall (Sonicwall TZ170) for UDP address:port pairs in the
NAT/PAT translation memory. I've hacked the chan_iax2.c code to force a
15 second registration refresh time, instead of 60 seconds, and so far
things have worked much better (i.e., the registration is like a
"keep-alive" for the PAT translation pairs).
I'll keep the list posted ...
- Mike
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
