On Tuesday 13 May 2008, Steve Totaro wrote:
Can you describe exactly how you are utilizing it, including LAN/WAN,
switches, ping times, and other network central details. TDMoE adds
the E (ethernet) component to troubleshooting and I think do to this,
it may be very fragile depending on
On Tuesday 13 May 2008, Steve Totaro wrote:
You can be shot several times and not die. I would try
resetinterval=never just to be able to to say Not the problem
rather than Probably not the problem.
I'll do that, although I'm pretty sure that the setting is not the
problem as the yellow alarm
Florian Hackenberger wrote:
On Tuesday 13 May 2008, Steve Totaro wrote:
You can be shot several times and not die. I would try
resetinterval=never just to be able to to say Not the problem
rather than Probably not the problem.
I'll do that, although I'm pretty sure that the setting is not
On Tue, May 13, 2008 at 9:57 AM, Florian Hackenberger
[EMAIL PROTECTED] wrote:
On Tuesday 13 May 2008, Steve Totaro wrote:
You can be shot several times and not die. I would try
resetinterval=never just to be able to to say Not the problem
rather than Probably not the problem.
I'll do
On Friday 09 May 2008, Steve Totaro wrote:
Try resetinterval=never
Thank you very much for your suggestion, I'll try the setting and will
report back whether it solved our problems.
Cheers,
Florian
--
DI Florian Hackenberger
[EMAIL PROTECTED]
www.hackenberger.at
On Friday 09 May 2008, Steve Totaro wrote:
Try resetinterval=never
Hi! I tried setting resetinterval=60 and established a call. The call
survived several channel resets successfully, so this setting is
probably not the problem. Any more ideas?
Cheers,
Florian
--
DI Florian
On Fri, May 9, 2008 at 5:32 PM, Florian Hackenberger
[EMAIL PROTECTED] wrote:
Hi!
We are using a red-fone bridge (connected to an E1 line from the Telekom
Austria) to provide TDMoE connectivity to our asterisk server (ubuntu
7.10, asterisk 1.4.10 from ubuntu, libpri 1.4.0-2, zaptel 1.4.9.2
