[cid:imagea237cf.GIF@0003fca9.4ba8ddee]
Hi All,
I hope someone can help as I seem unable to solve this.
Running sipx 4.6 on CentOS 6.3 – last night I ran a YUM UPDATE
Upon completion sipxsaa and sipxrls show as shut down in the services list.
I have rebooted the server, disabled and
On Thu, Sep 13, 2012 at 1:12 PM, Ben Goodfellow b...@btg-computers.co.ukwrote:
** **
Upon completion sipxsaa and sipxrls show as shut down in the services list.
** **
I have rebooted the server, disabled and reenabled the relevant services
but to no avail.
** **
Has anyone
do
yum info js
if it is not installed, install it.
then if mongo is not running, see this:
*
All,
If you have 4.6 installed from RPMs / ISO and yum upgrade please mind
that it will upgrade MongoDB as well (from 2.0.2 within sipxecs repo
to 2.0.7 published in epel-release). While mongo 2.0.2
Since there is no wiki page for it yet. I think it would probably help a
few people to know what the proper update procedures need to be when
updating sipx packages via yum.
This is what I do, though I am looking for input on this in order to put
together a basic how to for the website.
1. Stop
It looks like I'm a little late to this party. I've been
able to successfully restore my 4.4 configuration to a fresh
4.6 system, but for some reason the voicemail restore
doesn't seem to be working.
Is the restore in 4.6's sipxconfig able to take a 4.4
tarball with the flat files from
try doing a local backup then replace the voicemail.tar.gz file onboard
with the one you need to restore, then do a restore.
On Thu, Sep 13, 2012 at 1:57 PM, andrewpitman andrewpit...@comcast.netwrote:
It looks like I'm a little late to this party. I've been
able to successfully restore my
Nope, still no dice.
- Original Message -
From: Tony Graziano tgrazi...@myitdepartment.net
To: Discussion list for users of sipXecs software
sipx-users@list.sipfoundry.org
Sent: Thursday, September 13, 2012 2:07:59 PM
Subject: Re: [sipx-users] 4.4.0 to 4.4.6
try doing a local
can you detail a few things?
/var/sipxdata/backup/local/directory is sipx:sipx 0755 and files in it
are sipx:sipx 0644
correct?
once you confirm that, make do a restore and garb the sipxconfig log from
that attempt and inspect it. if you figure it out and solve it, share what
was wrong. If not,
On Thu, Sep 13, 2012 at 9:23 PM, andrewpit...@comcast.net wrote:
Nope, still no dice.
Can you manually run /usr/bin/sipxivr-archive --restore
{path_to_backup} and see the output?
George
___
sipx-users mailing list
sipx-users@list.sipfoundry.org
List
Yes, indeed. /var/sipxdata/backup/local/201209131417 is pwned by sipx:sipx and
mode 0755 and voicemail.tar.gz is sipx:sipx and mode 0644.
Here's the sipxconfig.log entry from when I ran the local restore:
Just got a test trunk to add to SipX, as a secondary gateway, but running into
some problems. I'm able to receive phone calls to the new DID from the second
ITSP, but making outbound does not go through it. It is going out through the
primary. Trying to follow this setup here:
On Thu, Sep 13, 2012 at 1:57 PM, andrewpitman andrewpit...@comcast.net wrote:
It looks like I'm a little late to this party. I've been
able to successfully restore my 4.4 configuration to a fresh
4.6 system, but for some reason the voicemail restore
doesn't seem to be working.
Is the
I'm not sure how well that translates in 4.4 and also 4.6 (branches).
A couple of things you can do: dial only 10 digits at the phone. Let the
trunk take care of adding anything one provider requires beyond that. You
can also have only one gateway per rule but ceate duplicate rules for
testing
so let us know what happends when you:
/usr/bin/sipx-archive --restore /var/sipxdata/backup/local/
201209131417/voicemail.tar.gz
On Thu, Sep 13, 2012 at 4:01 PM, Douglas Hubler dhub...@ezuce.com wrote:
On Thu, Sep 13, 2012 at 1:57 PM, andrewpitman andrewpit...@comcast.net
wrote:
It
Right, it uploaded fine and didn't give me any errors. I guess what I needed to
know is can I restore sipxecs 4.4.0 voicemail to an openuc 4.6.0 system?
If I run openucivr-archive...
[root@sipx01 ~]# /usr/bin/openucivr-archive --restore
On Thu, Sep 13, 2012 at 11:22 PM, andrewpit...@comcast.net wrote:
Right, it uploaded fine and didn't give me any errors. I guess what I
needed to know is can I restore sipxecs 4.4.0 voicemail to an openuc 4.6.0
system?
If I run openucivr-archive...
[root@sipx01 ~]#
since there are very different procedures with openuc, i'll let ezuce
handle this.
I imagine you have the system all updated and have made sure servies are
running and mongo is too first, right?
On Thu, Sep 13, 2012 at 4:22 PM, andrewpit...@comcast.net wrote:
Right, it uploaded fine and
Thanks George. I had assumed that voicemail storage would be the same between
sipxecs and openuc 4.6, but you know what they say about assumptions. ;)
I'll leave this in your capable hands.
In the meantime I will verify that I can restore sipxecs 4.4 to sipxecs 4.6
(which I'm sure won't be a
Also, 4.2.1 Is end of support. Please consider upgrading to 4.4.0 or later.
Grandstream phones are not generally used with sipXecs due to their SIP
stack deficiencies. Among the things that weren't working last time I
tested:
- Phones would use a second line and put the first line on hold
On Thu, Sep 13, 2012 at 4:07 PM, Tony Graziano tgrazi...@myitdepartment.net
wrote:
so let us know what happends when you:
/usr/bin/sipx-archive --restore /var/sipxdata/backup/local/
201209131417/voicemail.tar.gz
that's not the command actual, each subsystem has a different archive
command.
(before I knew he was using openuc)
On Thu, Sep 13, 2012 at 5:26 PM, Douglas Hubler dhub...@ezuce.com wrote:
On Thu, Sep 13, 2012 at 4:07 PM, Tony Graziano
tgrazi...@myitdepartment.net wrote:
so let us know what happends when you:
/usr/bin/sipx-archive --restore
Just thought I'd give an update on updating the jain-sip
I've put this latest jain-sip in production on 3 system for several weeks now.
One 4.2.1 and the other 2 are 4.4
They are working fine and there is no useability issues. However the sipxrest
java process pegs at 100%.
Our systems are
On Thu, Sep 13, 2012 at 7:56 PM, Matt White mwh...@thesummit-grp.com wrote:
Just thought I'd give an update on updating the jain-sip
I've put this latest jain-sip in production on 3 system for several weeks
now. One 4.2.1 and the other 2 are 4.4
They are working fine and there is no
23 matches
Mail list logo
