Louis-David Mitterrand wrote:
On Thu, May 04, 2006 at 12:51:52PM -0700, Tom Engleward wrote:
--- Vahan Yerkanian <[EMAIL PROTECTED]> wrote:
Andrew Kohlsmith wrote:
On Thursday 04 May 2006 11:31, Louis-David
Mitterrand wrote:
I've got this low-ping 100%-up dsl connection
between two asterisk
1.2.7.1 servers. And oftentimes one of them would
declare its opposite
UNREACHABLE.
Same, here, two asterisk 1.2.7.1 boxes connected to
the same switch... Over a week I see at least one case of one of the
boxes becoming unavailable for the other... simple iax2 reload
fixes the problem.
Been like this for ages.
<rant>
>From this thread today I've learned that the problems
I've been having the entire time I've been using
asterisk (about two weeks) stem not from NAT, as I
originally thought, but from asterisk itself, so that
if I were to move my asterisk box to a public IP
address, my iax2 connection to my PSTN originator
(which also runs asterisk) would _still_ be
unreliable.
This makes iax2 on asterisk useless for receiving
calls. No matter how many spiffy features asterisk
has, there is one simple nonnegotiable requirement: it
must always answer incoming calls. If it can't do
that, then it can't be relied on. And over iax2, it
can't do that.
Right now I have:
CLI> iax2 show peers
tmm1 192.168.0.1 (S) 255.255.255.255 4569 (T) UNREACHABLE
CLI> sip show peers
tmm1 192.168.0.1 A 5060 OK (40 ms)
And it has been so for 15 minutes.
Why is IAX2 so flaky?
If I did not resort to SIP for inter-asterisk communications I would be
out of a job at this time.
I dropped IAX2 on Friday in favor of SIP and my problems have gotten
much much better.
_______________________________________________
--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
