Their routers are all statically set with the old domain name and user
authentication details.
On Sat, 23 Jun 2012 16:36:38 -0400, Tony Graziano wrote:
> That will work but not the "best" way to do it (MWI may have an issue,
> etc.).
>
> Is the customer auto provisioned (devices) via sipx?
>
I'd love to know more about this, as I see that this issue has been "fixed" (
http://track.sipfoundry.org/browse/XX-8692 ) but I haven't run across any
documentation to dive deep into it. I've played with 4.6 beta (when is the
expected stable release btw?) a month or so ago before deploying 4.4.
Looking to get some sipxecs users to hang out with the developers.
Moderator List (topics we'll cover)
http://www.google.com/moderator/#15/e=1fbcb9&t=1fbcb9.42
IRC (live discussion for those not able to join hangout)
freenode.net, #sipx channel
Join G+ Hangout with +Douglas Hubler found on my
That will work but not the "best" way to do it (MWI may have an issue,
etc.).
Is the customer auto provisioned (devices) via sipx?
On Sat, Jun 23, 2012 at 3:00 PM, m...@grounded.net wrote:
> On Sat, 23 Jun 2012 11:52:35 -0700, m...@mattkeys.net wrote:
> > The domain alias setting comes to mind.
You really need to understand how sipx works with projecting and managing
configuration files. There is a way to do this via the .vm files but you
will need to take care to understand how to deal with the upgrade/update
process as well.
On Sat, Jun 23, 2012 at 1:27 PM, m...@mattkeys.net wrote:
>
On Sat, 23 Jun 2012 11:52:35 -0700, m...@mattkeys.net wrote:
> The domain alias setting comes to mind. Maybe worth a shot? In
> sipXsupervisor -> System -> Domain -> and down at the bottom "Add Alias".
Sounds like that could work. Only thing is, this is a live system so I only
have one shot at th
The domain alias setting comes to mind. Maybe worth a shot? In sipXsupervisor
-> System -> Domain -> and down at the bottom "Add Alias".
-Original Message-
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of m...@grounded.net
Sent: S
Well, wasn't really sure how to word that in the subject but here's the issue.
I have some remotes that need to be migrated over to a new sipx server. I can't
get at their routers to change the old domain name and the new sipx box is on a
new domain name.
I was wondering if I could simply poin
So I've noticed! On a reboot it blew away the freeswitch modifications I had
entered. I'm curious what would happen if I make them immutable?
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Tony Graziano
Sent: Saturday, June 23, 2012 12:
Thanks Douglas.
-Original Message-
From: sipx-users-boun...@list.sipfoundry.org
[mailto:sipx-users-boun...@list.sipfoundry.org] On Behalf Of Douglas Hubler
Sent: Saturday, June 23, 2012 1:46 AM
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] Wiki seems to be dow
Therein lies your problem. At no time has multiple NIC's ever been
supported or recommended.
I would suggest you drop back down to one NIC. The issue you are having
WILL reintroduce iteself as the system runs, I guarantee it.
On Sat, Jun 23, 2012 at 10:20 AM, m...@mattkeys.net wrote:
> Tony / Al
Tony / All,
I've started over completely from scratch as you suggested, but I was still
having this issue. I eventually found the problem, so I'll share in case
anybody runs into this. I ran (as root)
$ service sipxecs stop
$ sipxconfig.sh --database drop
$ sipxconfig.sh --database create
$ sip
a restart seemed to have straightened things, thanks
On Fri, Jun 22, 2012 at 11:27 PM, Todd Hodgen wrote:
> Anyone able to reach it?
>
> Sent from my twiddling thumbs.
>
> Joegen Baclor wrote:
>
> On 06/21/2012 10:34 PM, andrewpitman wrote:
>
> Okay, I ran two versions of the Perl script against
13 matches
Mail list logo
