Would have probably been more appropriate to at least announce that
iax was going to disappear at some specific date, as opposed to folks
randomly discoverying it and chasing problems. (Kind of related to why
there isn't a marketing plan.)
Sorry, it was something of a side effect of
Good, glad to hear things are better. Without getting into too much techie
detail, what was the root problem?
There was just race that I introduced a while back. If calls came in
while a reload was taking place in IAX2, bad things would happen. Now
it's fixed. Originally I was thinking it
On Sunday 07 of December 2003 21:14, Mark Spencer wrote:
Good, glad to hear things are better. Without getting into too much
techie detail, what was the root problem?
There was just race that I introduced a while back. If calls came in
while a reload was taking place in IAX2, bad things
Is anyone other than me having trouble dialing out via IAXTEL? I havn't
changed my config files in weeks but seems that IAXTel calls (800 and FWD)
stopped working in the past week sometime.
Robert
___
Asterisk-Users mailing list
[EMAIL PROTECTED]
Is anyone other than me having trouble dialing out via IAXTEL? I havn't
changed my config files in weeks but seems that IAXTel calls (800 and FWD)
stopped working in the past week sometime.
Yes, I've been having problems as well but had not taken the time to diagnose
the problem. Just did
Yes, I've been having problems as well but had not taken the time to
diagnose
the problem. Just did some looking and it appears iaxtel.com has removed
the iax v1 support. iax2 seems to be working fine.
Rich,
That solved the outbound problem.. Thanks for the hint... 800 numbers are
accessable
To add to this problem, we have been fighting a denial of service
attack on the toll-free gateways. We have installed new code to deal
with this problem hopefully. I will never understand why someone would
attack a free service.
John Lodden
Telesthetic
On Sat, 2003-12-06 at 07:45, rnc Info
John,
Did you shut down iax v1 (udp/5036) on purpose, or are we all suppose to
change to iax2 (udp/4569) forever?
Rich
To add to this problem, we have been fighting a denial of service
attack on the toll-free gateways. We have installed new code to deal
with this
Rich Adamson wrote:
On Sat, 2003-12-06 at 07:45, rnc Info Lists wrote:
Is anyone other than me having trouble dialing out via IAXTEL? I havn't
changed my config files in weeks but seems that IAXTel calls (800 and FWD)
stopped working in the past week sometime.
To add to this problem, we
On Sat, 2003-12-06 at 12:36, Olle E. Johansson wrote:
I seem to get a G729 codec on calling 1800 numbers on IAXTEL...
Temporary fault or do we have to buy a license?
/O
The toll-free gateways allows the use of G729, if you don't have that
CODEC don't show you can use it. The gateways can
) 857-3287
IAXTEL (700) 857-3287
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John Lodden
Sent: Saturday, December 06, 2003 12:18 PM
To: [EMAIL PROTECTED]
Subject: Re: [Asterisk-Users] IaxTel seems down
On Sat, 2003-12-06 at 12:36
The FWD bridge is currently down, as I am looking to try to find someone
else to host the IAX2 to SIP gateway so that iaxtel can remain strictly
IAX2.
Mark
___
Asterisk-Users mailing list
[EMAIL PROTECTED]
Mark,
I cannot connect to IAX1 either
We are phasing out support for IAX1. Are the people who still *need*
IAX1?
Given that iax2 has been around and stable for a rather lengthy period,
I would doubt there is any real need for it other then to coordinate production
systems that can't be
Would have probably been more appropriate to at least announce that
iax was going to disappear at some specific date, as opposed to folks
randomly discoverying it and chasing problems. (Kind of related to why
there isn't a marketing plan.)
Sorry, it was something of a side effect of some
14 matches
Mail list logo
