Date: Mon, 13 Oct 2008 23:58:44 +0200 (CEST) From: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> To: "Zane C.B." <v.velox@vvelox.net> Cc: freebsd-questions@freebsd.org Subject: Re: IAX2 (or SIP) softphone for FreeBSD Message-ID: <20081013235425.B83595@wojtek.tensor.gdynia.pl> In-Reply-To: <20081013070444.56c4dad6@vixen42> References: <20081012162321.V39974@wojtek.tensor.gdynia.pl> <20081012175941.4d675ad0@vixen42> <20081013122726.X56368@wojtek.tensor.gdynia.pl> <20081013070444.56c4dad6@vixen42>
next in thread | previous in thread | raw e-mail | index | archive | help
> Jagermiester so this may not make to sense. > > The problem I originally ran into is that behind goat fraging NAT I > would run into issues receiving calls. The problem I ran into is that this is not kiax problem. this may be your NAT problem. what is doing NAT? IAX has configurable "ping" time, kiax tries 300 seconds by default, while asterisk PBX (or whatever IP PBX) could force it lower. every that time IAX client "pings" (but throught IAX not ICMP) the PBX. if NAT removes entries from translation table faster than this, you.. yes.. won't be able to accept calls, because you'll not be reachable. minregexpire and maxregexpire options in iax.conf control this. unfortunately no options in kiax for this. there is already another problem. kiax just ignore lots of "out-of-band" IAX commands. when you make a call to other softphone, there is no "buu buu" before answering, just plain silence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081013235425.B83595>