Thanks Lonnie. Simple!
Add 'service asterisk stop' to any restore or factory reset script and all is
resolved after a reboot.
Regards
Michael Knill
On 5/7/18, 9:24 am, "Lonnie Abelbeck" wrote:
> On Jul 4, 2018, at 5:23 PM, Michael Knill
wrote:
>
> Does anyone know if there
Thanks Lonnie. Good call. That will be my next test.
PS IP Address stays the same.
Regards
Michael Knill
On 5/7/18, 9:14 am, "Lonnie Abelbeck" wrote:
Michael,
My theory has always been your problem is with an upstream firewall.
Stopping asterisk for a period of time may a
> On Jul 4, 2018, at 5:23 PM, Michael Knill
> wrote:
>
> Does anyone know if there is an issue with writing or deleting entries
> directly in the astdb.sqlite3 database rather than via Asterisk?
> It would only be used for backup/restore/factory reset purposes.
I would not do that if Asteris
Michael,
My theory has always been your problem is with an upstream firewall.
Stopping asterisk for a period of time may allow upstream firewall states to
expire.
By rebooting AstLinux you will do the same (stop/start Asterisk) and if you
have PPPoE you may pull a different IP address which wi
I’ve done it and it didn’t seem to hurt though I’d never do it in production.
I’m not sure how much data is cached by asterisk so I end up always handling
the DB through AMI Christopher
On Wednesday, July 4, 2018, 6:23:56 PM EDT, Michael Knill
wrote:
Does anyone know if there is an
Does anyone know if there is an issue with writing or deleting entries directly
in the astdb.sqlite3 database rather than via Asterisk?
It would only be used for backup/restore/factory reset purposes.
Regards
Michael Knill
--
And yes good test. Of course a firewall restart does not clear translations.
Am I able to clear firewall translations without waiting for them to time out
which is what I assume you are doing here?
It would have to be dome from a remote session as well e.g. through the
firewall.
Regards
Michael
Thanks Lonnie. Great info to know.
Its still a bit of a mystery though as I was seeing the outbound packet with
tcpdump so it had passed the firewall, but did not see the return packet!
Regards
Michael Knill
On 4/7/18, 10:41 pm, "Lonnie Abelbeck" wrote:
> So my questions are:
> • Is t
> So my questions are:
> • Is tcpdump BEFORE the firewall?
For incoming packets tcpdump is before the firewall, for outgoing packets
tcpdump is after the firewall, ie.
--
wire -> NIC -> tcpdump -> netfilter/firewall
netfilter/firewall -> tcpdump -> NIC -> wire
--
so tcpdump does not see outbound
