Hi there,
I'm considering migration of my voicemail system from Cisco Unity to
sipXecs. It has to be able to work with Cisco Callmanager 4.
Fortunately, CCM 4 seems to provide a few simple hooks for that, as
outlined in [
http://www.voip-info.org/wiki/view/Asterisk+Cisco+CallManager+Voice
On Sun, Jan 31, 2010 at 6:59 PM, Tony Graziano
wrote:
> Er... unless the net-install uses the 2.6.32 kernel I fail to see how that
> will help his situation. He would still need to manually edit the local file
> to properly initialize the nic, which is the issue.
>
You are right...5.4 net-install
-- Forwarded message --
From: Charles Chalekson
Date: Sun, Jan 31, 2010 at 5:13 PM
Subject: Re: [sipx-users] iso install issues
To: Tony Graziano
Agreed, however, I would think the wiki would better explain what things we
should check for to make sure we aren't going to have iss
Refer to the redhat bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=525966
On Sun, Jan 31, 2010 at 7:59 PM, Tony Graziano wrote:
> Er... unless the net-install uses the 2.6.32 kernel I fail to see how that
> will help his situation. He would still need to manually edit the local file
> to
Er... unless the net-install uses the 2.6.32 kernel I fail to see how that
will help his situation. He would still need to manually edit the local file
to properly initialize the nic, which is the issue.
On Sun, Jan 31, 2010 at 7:35 PM, Jim Canfield wrote:
> On Sun, Jan 31, 2010 at 5:02 PM, wr
On Sun, Jan 31, 2010 at 5:02 PM, wrote:
> If centos 5.4 will install properly, there are some pretty easy steps that
> will get you an install that is very close to the ISO install.
I agree, the ISO install can be painful. Primarily because of the
Centos 5.2 madness. Here are the steps I use.
On Sun, 2010-01-31 at 14:33 -0800, Charles wrote:
> In a humorous way, this enhances my argument for a macintosh based
> port of sipx. I unfortunately do not have the capabilities to do it
> however ;)
There is, alas, nothing magical about the Mac environment that makes
these things automatic a
until this gets fixed I patched it with a cron job
for i in `find /var/sipxdata/mediaserver/data/mailstore -name "*xml" -print | grep
saved`; do sed -i 's/sip:.*/sip:2...@sipx.company.net\>\<\/from\>/g' $i; done;
-gabriel
On Fri, 29 Jan 2010, Todd Hodgen wrote:
Seems to be the case. Maybe
If centos 5.4 will install properly, there are some pretty easy steps that will
get you an install that is very close to the ISO install.
Sent via BlackBerry from T-Mobile
-Original Message-
From: Charles
Date: Sun, 31 Jan 2010 14:26:36
To: Tony Graziano
Cc:
Subject: Re: [sipx-users]
"If" you researched your hardware and linux compatibilities you wouldn't
have put yourself in such a pickle. The overhead to run a MAC port of the
sipx system would obviously lead to more ridiculous issues though, really.
There needs be no gui, the extra overhead is, um, unnecessary, adding layers
I see this in not an expandable system...
I'd try adding this in the
/etc/rc.d/rc.local
file
*
*
rmmod tg3
insmod /lib/modules/$(uname -r)/kernel/drivers/net/phy/broadcom.ko
insmod /lib/modules/$(uname -r)/kernel/drivers/net/tg3.ko
It's a well known issue in the fedora and centos forums. it mig
In a humorous way, this enhances my argument for a macintosh based port of
sipx. I unfortunately do not have the capabilities to do it however ;)
On Jan 31, 2010, at 2:29 PM, Tony Graziano wrote:
This is really a centos/hardware compatibility thing. Disable the onboard
nic and throw a plain n
This is really a centos/hardware compatibility thing. Disable the onboard
nic and throw a plain network card in it and it WILL work. Sipx is hardware
agnostic for the most part. Its the linux compatibility which sipx is not
involved in.
Tony Graziano, Manager
Telephone
Oh great Sorry to vent but this leads back to the question awhile back of
how to make things simpler. I decided to change gears and get a small PC with
a dual core so that I wouldn't have these potential problems that I was
experiencing with the macintosh [which I can administer much better
On Sun, Jan 31, 2010 at 4:58 PM, Scott Lawrence wrote:
> On Sun, 2010-01-31 at 15:50 -0600, Eric Varsanyi wrote:
>
> > I cannot establish a voice path with any of the polycoms and the talk
> > path to the IVR only works for about 30 seconds or so.
>
> > so I believe the firewall and its SIP s
There is still an issue with the Centos OS not having an adequate driver for
your network card. This happens frequently when the hardware or chipsets are
new and the distro has not caught up yet.
You should be able to search the centos forums for your hardware and centos
5.2 and see if there is a
I see a local loopback but no eth0 listed when I run ifconfig
On Jan 31, 2010, at 1:53 PM, Tony Graziano wrote:
Methinks he is using mac hardware. If this is the case, he should go to the
centos or redhat forums to see if his NIC is supported. Copying the needed
files to CD or USB and mounting
On Sun, 2010-01-31 at 15:50 -0600, Eric Varsanyi wrote:
> I cannot establish a voice path with any of the polycoms and the talk
> path to the IVR only works for about 30 seconds or so.
> so I believe the firewall and its SIP support are roughly working.
Those two statements don't seem to go
Would it matter if it is running an AMD chip instead of intel?
On Jan 31, 2010, at 1:53 PM, Tony Graziano wrote:
Methinks he is using mac hardware. If this is the case, he should go to the
centos or redhat forums to see if his NIC is supported. Copying the needed
files to CD or USB and mountin
No I was. This is a brand new Dell.. installing straight off the
iso...
On Jan 31, 2010, at 1:53 PM, Tony Graziano wrote:
Methinks he is using mac hardware. If this is the case, he should go to the
centos or redhat forums to see if his NIC is supported. Copying the needed
files to C
I think he uses mac hardware.
On Sun, Jan 31, 2010 at 3:58 PM, Eric Varsanyi wrote:
> WRT BIOS restart I'll add that there is a common "bug" in server bios loads
> (used by Supermicro and Tyan server class boards, I think its Pheonix) where
> if you set it to 'power on after power fail' it will
Unless you specify an SBC other than sipXbridge for Internet calling,
enabling it using sipXbridge breaks remotes users in some functions (cant
receive calls, but can make calls, for example).
Internet Calling does work without enabling it with sipXbridge if it is not
specified.
On Sun, Jan 31, 2
Methinks he is using mac hardware. If this is the case, he should go to the
centos or redhat forums to see if his NIC is supported. Copying the needed
files to CD or USB and mounting would be the only real method to get that
working. It might also be a kernel patch or even unsupported. This is an
o
I've seen a bunch of traffic on the list implying that to use an ITSP you have
to turn off 'Internet calling'.
Should I be able to follow the cheat sheet on the wiki wrt remote workers and
have it not break my ITSP functionality or these mutually exclusive?
FWIW I already have the ports forward
WRT BIOS restart I'll add that there is a common "bug" in server bios loads
(used by Supermicro and Tyan server class boards, I think its Pheonix) where if
you set it to 'power on after power fail' it will not turn back on when the
power is applied in some cases. What works on boards that act li
It sounds like maybe the kernel isn't finding your network card (unsupported,
broken, ?); the configuration scripts get generated for every found card. On an
existing system if you change the mac address of a card (by swapping it for
instance) you can end up with the card showing up as eth1 or e
How many nic's are in the system?
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431
Email: tgrazi...@myitdepartment.net
LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426
Fax: 434.984.8427
Helpdesk Contract Customers:
http://w
I am trying to run install with the 4.0.4 ISO on a new machine and am getting
an abort after the DNS entry screen. It doesn't matter if I choose, no or yes
for the this should be my or shouldn't be my DNS server page.
The error message is:
sipxecs-setup could not find network file
/etc/syscon
sorry, bootup scripts are in
/etc/rc.d/init.d
You don't want to touch them, only command them to start/stop or be on or
off at bootup.
On Sun, Jan 31, 2010 at 11:55 AM, Tony Graziano <
tgrazi...@myitdepartment.net> wrote:
> On linux there is a script for:
>
> /etc/init.d/sipxecs
>
> chkconfig s
On linux there is a script for:
/etc/init.d/sipxecs
chkconfig sipxecs off
chkconfig sipxecs on
One turns sipxecs off at bootup, the other is on.
By default it is on.
How the hardware behaves with power before the OS can do anything is a
completely different issue. It is more likely you are ta
I notice that auto restart on power failure is listed as a feature and the
wiki says it can be configured from the browser interface. I don't see
where/how to configure this?
Am I missing something? If this is not turned on by default, I would think
this should be the default setting. I tried m
On 1/31/10 2:52 AM, Winson (Elabram) wrote:
May i know where to check my sip account is connect from Sipxecs?
sip trunk: look at registrations at your sip trunk provider
sip phone: look at registrations on sipx, under users: registrations.
--
Michael Scheidell, CTO
Phone: 561-999-5000, x 1
32 matches
Mail list logo
