Jan,
One thing you might check is your channel selection order. Outbound you
should be selecting channels from 30 (or 23 in the US) down. Inbound your
service provider should be ringing in 1 and up.
This helps to avoid the old telcom problem called glare. Glare occurs when
a device picks up a
On Tue, Oct 23, 2012 at 12:37 PM, Aaron Pursell aar...@esgw.org wrote:
At least I'm not crazySo assuming this is an issue beyond something we
can do.
1.) Is it possible the numeric id of second server is not 2? Can you
send me screen shot of the list of servers?
2.) Can you run
date
I uploaded all the stuff to the dropbox you shared with me.
Server 2 gave the following error during sipx-snapshot.
[root@gfgwph ~]# sipx-snapshot
pg_dump: [archiver (db)] connection to database SIPXCONFIG failed:
could not connect to server: No such file or directory
Is the server
Mike,
We have ACL's, Views, and split the zone into an internal AND external zone
already. We are returning internal IP's to the RFC 1918's defined in our
internal ACL and view for external carries any and has a modified zone that
includes the A record for the public entry instead of the
Tony,
Wouldn't the same be said for an unmanaged firewall then? Moving firewall to
unmanaged and manually creating your own tables and rules has been suggested
more than once as how to control iptables, no suggestion that the system at
some point would add/remove or reset the rules was
On Thu, Oct 25, 2012 at 9:38 AM, Aaron Pursell aar...@esgw.org wrote:
I uploaded all the stuff to the dropbox you shared with me.
thanks, this was useful in that it proved we need to add more info to
snapshot script. We need to be able to diagnose 4.6 more easily. Then
I may ask you to yum
All,
Thanks for help. This has been resolved by BroadVox after they worked with the
provider that the toll free numbers are on, to increase the Max Forwards to 67.
From: Brian Buckles itnc...@yahoo.com
To: Brian Buckles itnc...@yahoo.com; Discussion list
Not a problem, just let me know. I just updated to the latest release
out on the repo.
Aaron Pursell
Network Security Administrator
Easter Seals-Goodwill Northern Rocky Mountain, Inc.
4400 Central Ave
Great Falls, Montana 59405
(406) 771-3721
aar...@esgw.org
Douglas Hubler
Sent wirelessly from my BlackBerry
-Original Message-
From: Aaron Pursell aar...@esgw.org
Sender: sipx-users-boun...@list.sipfoundry.org
Date: Thu, 25 Oct 2012 11:32:25
To: Discussion list for users of sipXecs
softwaresipx-users@list.sipfoundry.org
Reply-To: Discussion list for users
On Thu, Oct 25, 2012 at 6:15 PM, Alan Worstell
aworst...@a-1networks.com wrote:
Hello,
As Trevor mentioned, replacing /etc/named.conf.unmanaged with our changed
conf resolved this. I had noticed in sipxagent.log entries about fulfilling
promises from that file.
Attached is the log file in
Hello,
My earlier reply to the list is currently held in moderation (I believe
because I attached another log which was slightly larger) but named.conf
is still actually being overwritten. /etc/named.conf.unmanaged still has
our changes, but /etc/named.conf keeps going back to the default.
Here
On Fri, Oct 26, 2012 at 2:11 AM, Alan Worstell
aworst...@a-1networks.com wrote:
Hello,
My earlier reply to the list is currently held in moderation (I believe
because I attached another log which was slightly larger) but named.conf
is still actually being overwritten. /etc/named.conf.unmanaged
On Fri, Oct 26, 2012 at 2:19 AM, George Niculae geo...@ezuce.com wrote:
On Fri, Oct 26, 2012 at 2:11 AM, Alan Worstell
aworst...@a-1networks.com wrote:
Hello,
My earlier reply to the list is currently held in moderation (I believe
because I attached another log which was slightly larger) but
Yes, this is correct, it was set to managed in the gui again. I know
that it *was* set to unmanaged, because I had to create the cfengine
script to allow udp 53 through the local firewall.
I've set it to unmanaged again.
Alan Worstell
A1 Networks - Systems Administrator
VTSP, dCAA, LPIC-1,
14 matches
Mail list logo
