[ previous ] [ next ] [ threads ]
 From:  Chris Buechler <cbuechler at gmail dot com>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  Fwd: [m0n0wall] monowall and call droping
 Date:  Tue, 27 Sep 2005 22:20:55 -0400
meant for the list...

---------- Forwarded message ----------
From: Tomas Florian <tomas at florien dot ca>
Date: Sep 27, 2005 2:25 PM
Subject: RE: [m0n0wall] monowall and call droping
To: Chris Buechler <cbuechler at gmail dot com>

If you are using SIP protocol, Asterisk, and NAT my guess would be that you
need to send keep-alives so that monowall doesn't close the inactive port.

In asterisk you can accomplish that with the qualify=yes option

But if you have control over your own monowall then the more robust way is
to look at asterisk documentation and open up all of the required ports


-----Original Message-----
From: Chris Buechler [mailto:cbuechler at gmail dot com]
Sent: Tuesday, September 27, 2005 12:11 PM
Cc: m0n0wall at lists dot m0n0 dot ch
Subject: Re: [m0n0wall] monowall and call droping

On 9/27/05, swiss ipcom <swissipcom at yahoo dot com> wrote:
> i wish to report this problem, i hae the following setting:
> cisco modem >>>monowall>>>astersik
> while making calls i am getting dropp calls which varies during the day,
> is there some port to be opened on the monowall or is there another
adjustment in configuration to do that

shouldn't be, no.  you sure it's actually m0n0wall that's causing the
drops?  I'm not familiar with asterisk, so not sure how you'd go about
troubleshooting to see if it's causing it, or if it knows why it's


To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch