vicidial.org

Hello,

I am trying to install VICIDIALNOW 1.1 on a PC with the below config:

Core2Duo 2.8 GHz
RAM - 4 GB
HDD - 250 GB SATA
Motherboard - NVIDIA - nFORCE 610i-Value

When I run the VICIDIALNOW disk, it stops after the first few commands with the following message:

ERROR DOWNLOADING KICK START FILE
"Unable to download the kickstart file.Please verify the kickstart parameter below or press cancel to proceed as an interactive installation

Cdrom://ks.cfg

(OK / CANCEL)"

If I press " Cancel", it prompts me to select the language options and prompts me to choose the media that contains the file (CD ROM / HDD etc) and when I choose CD ROM, It brings up another error message

"NO DRIVER FOUND"
Unable to find any devices of the type selected for the installation type. Would you like to manually select your driver or use the driver disk?

(SELECT DRIVER / USE A DRIVER DISK/ BACK)

I'm pretty much stuck here. It was working just fine when I used the same disk on a diff PC. What could possibly have gone wrong?

The only other difference I could think of is, I use NVIDIA motherboard on this one against the INTEL on the one that worked. Is VICIDIALNOW not compatible with NVIDIA motherboard?

Thanks,
Kris

VicidialNOW 1.1 is based on CentOS 5.1. It may not have driver support for your Nvidia board. Try using VicidialNOW 1.2rc1. It's based on CentOS 5.2 and may have support for your hardware. You can also try using an IDE optical drive and see if that helps.

Hi Gardo,

Thank you for your input. It actually works on 1.2. So, the higher version like you mentioned seems to have addressed this issue.

now, the second question I have is: do I need a static IP to be able to get my dialer working..?. or can I set up a LAN static IP?

do I need a static IP to be able to get my dialer working..?. or can I set up a LAN static IP?

You can use either. If using a LAN based IP setting, make sure of the following on your external WAN network router:

1. Ports for your SIP/IAX provider are not blocked. Normally these ports are (SIP 5060-5061, 10000-20000; IAX 4569). Forward UDP packets on these ports to your vicidialnow server's IP.
2. In sip.conf, you have nat=yes for the provider you are setting up.[/quote]

ykhan wrote:

do I need a static IP to be able to get my dialer working..?. or can I set up a LAN static IP?

You can use either. If using a LAN based IP setting, make sure of the following on your external WAN network router:

1. Ports for your SIP/IAX provider are not blocked. Normally these ports are (SIP 5060-5061, 10000-20000; IAX 4569). Forward UDP packets on these ports to your vicidialnow server's IP.
2. In sip.conf, you have nat=yes for the provider you are setting up.

[/quote]

Let me explain a little more about my setup so it helps you help me better

I just have a regular 512 KBPS setup that I'm going to pilot this dialer with. If this works out well, I'll go for a IBM server and a leased line after 3 days of trying out.
My setup currently is Core2duo as the server connected to a D-Link 601(load sharing router).The clients are 3 PCs. The internet just a 512 Kbps broadband connection (no static IP provided by ISP). How exactly should I go about in configuring this?.

Is it enough if I port forward the UDP to my server IP (192.168.0.5) and open the SIP ports as mentioned above?

Will the Voip provider need WAN static IP to be able to register me?. Just as much details as you can give on this..would help me cross this hurdle..

I already have so much appreciation for this community!

Thanks,
Kris

your system can "reach out" to register you as whatever IP you have (as long as you actually HAVE an IP and are not inside a shared IP, dynamic is fine).

although you do not need a static ip, if your ip changes you may have an interruption of service. most internet providers only change your IP if you power down for a period of time or every 6 months. (In the US.)

if you have your VOIP providers set up as dynamic, there may not be an interruption at all. this depends on the provider you have. most allow for dynamic connections so you can use their service from any ip address and in fact from several at once if you like.

do you have a voip account with a provider yet? good idea to get that going soon, sometimes it takes a little while.

williamconley wrote:if you have your VOIP providers set up as dynamic, there may not be an interruption at all. this depends on the provider you have. most allow for dynamic connections so you can use their service from any ip address and in fact from several at once if you like.

do you have a voip account with a provider yet? good idea to get that going soon, sometimes it takes a little while.

Do you know any VoIP providers at all who can work with dynamic IP?. Also, the kind of providers who knows Vicidial and knows where to do the setting for their integration?. If not, how do I configure the server with the voip provider?. is that a simple procedure?

Thanks,
Kris

binfone.com is a sponsor of this project, there is a lot of help to be had if you have them on your system.

i also like voipstreet.com and gafachi.com. it never hurts to have 'extra' voip accounts for testing, comparison, and backup.

I have been using vitelity and minutehub for a while with good results. Also, it depends where you are dialing. If dialing in the US or Canada to residential customers, you will need a provider that supports CLI passthrough (send your caller ID to the customer).

Most providers will have a sample for sip.conf and extensions.conf files as well.

I am at the "TEXT MODE SETUP UTILITY" page where it shows options such as:

Authentication configuration
Firewall Configuration
Keyboard config
Network config
system services
Time zone config
X config

Now, I am trying to select "Network configuration" to input the "Static IP". When I select and enter, it just won't open up anything. It stay son the same page.

When I select any other options such as Firewall config or keyboard config it opens just fine. When I check with my teach people, they always bounce back with the Nvidia is not supported. This is the most recent 1.2 version of VICIDIAL.

Should I just change the motherboard to Intel?. or am I just opening the pandora's box?

Help!

This is the most recent 1.2 version of VICIDIAL

Do you mean VicidialNOW version 1.2rc1? Because for Vicidial latest release so far is 2.0.5rc3.

ykhan wrote:

This is the most recent 1.2 version of VICIDIAL

Do you mean VicidialNOW version 1.2rc1? Because for Vicidial latest release so far is 2.0.5rc3.

Hi,

Oh..I didn't realize that. All I knew was I had the latest copy from vicidialnow.com. I guess they still carry the older version. Could that be the problem?.

Not a problem, you can upgrade after you go through the VicidialNOW install. With regards to your issue, I am not sure when you might get the options window you mentioned. You could try using the console to update your network info. Take a look at this post:

http://www.eflo.net/VICIDIALforum/viewt ... orkscripts

If you are just using a single server VicidialNOW setup and have not build a multiserver cluster you can make the IP that vicidial uses 127.0.0.1 and it will connect through to localhost. I have done this several times for things like the laptops we use at our training sessions. Just run the ADMIN_update_server_ip.pl script in the /usr/share/astguiclient/ directory and use 127.0.0.1 as the new IP, you will also need to change the ip in extension.conf to 127*000*000*001.

Also most SIP providers have no problems with dynamic IP addresses it just means that you will need to have Asterisk register with them on a regular basis rather than setting up host based authentication.

ykhan wrote:Not a problem, you can upgrade after you go through the VicidialNOW install. With regards to your issue, I am not sure when you might get the options window you mentioned. You could try using the console to update your network info. Take a look at this post:

http://www.eflo.net/VICIDIALforum/viewt ... orkscripts

Hi,

I looked at the other post and I found this part:

From the list pickup "Network Configuration" and press Enter

Press Enter for "eth0....."

This is exactly my problem. I am at the console and I see "Network Configuration" and I press enter... nothing happens! all other options opens up except this.

I meant to look at my post for setting up the IP from the console.

ykhan wrote:I meant to look at my post for setting up the IP from the console.

OK. The problem is
Code:
# vi /etc/sysconfig/network-scripts/ifcfg-eth0 . After this, there is just ablank screen. Ideally, I am supposed to see the commands like below which I took from the other post:

Code:
# Intel Corporation 82573E Gigabit Ethernet Controller (Copper)
DEVICE=eth0
BOOTPROTO=static
#DHCPCLASS=
HWADDR=YOUR MAC ADDRESS
IPADDR=YOUR SERVER IP ADDRESS HERE
NETMASK=255.255.255.0
GATEWAY=YOUR GATEWAY ADDRESS HERE
ONBOOT=yes

I don't see any of these. Just the blank screen.

Please post output of:

ls /etc/sysconfig/network-scripts/

ykhan wrote:Please post output of:

ls /etc/sysconfig/network-scripts/

Hi Yousaf,

When I type "ls /etc/sysconfig/network-scripts/" , I see 5 rows of various commands such as ifups and ifdowns. Do you want me to post the whole text in here?

Thanks,
Krisha

yes, he does.

williamconley wrote:yes, he does.

ifcfg ifdown-ipv6 ifup ifup-isdn ifup-tunnel
ifcfg-eth0 ifdown-isdn ifup-alisas ifup-plip ifup-wireless
ifcfg-l0 ifdown-post ifup-bnep ifup-plusb init.ipv6-global
ifdown ifdown-ppp ifup-eth ifup-post net.hotplug
ifdown-bnep ifdown-routes ifup-ippp ifup-ppp network-functions
ifdown-eth ifdown-sit ifup-ipsec ifup-routes network-functions-ipv6
ifdown-ippp ifdown-sl ifup-ipvb ifup-sit
ifdown-ipsec ifdown-tunnel ifup-ipx ifup-sl

Ok, so I can see that you have the file. So when you type vi /etc/sysconfig/network-scripts/ifcfg-eth0, just add the lines with your network configuration. You will need to press the [INSERT] key before typing anything into the file (if you don't know your way around vi).

ykhan wrote:Ok, so I can see that you have the file. So when you type vi /etc/sysconfig/network-scripts/ifcfg-eth0, just add the lines with your network configuration. You will need to press the [INSERT] key before typing anything into the file (if you don't know your way around vi).

I did exactly that - typed vi /etc/sysconfig/network-scripts/ifcfg-eth0 and pressed enter and it's showing a blank screen.

What do I do now?

[root@vicidialnow network-scripts]# vi ifcfg-eth0
# Intel Corporation PRO/100 VE Network Connection
DEVICE=eth0
HWADDR=00:1c:c0:87:ba:d8
IPADDR=192.168.0.2
NETMASK=255.255.255.0
ONBOOT=yes
TYPE=Ethernet

Try this...


[root@vicidialnow network-scripts]# lspci

Wait just a gol darn minute here.

When you type:
ls /etc/sysconfig/network-scripts/

do you get:
ifcfg-eth0

or:
ifcfg ifdown-ipv6 ifup ifup-isdn ifup-tunnel
ifcfg-eth0 ifdown-isdn ifup-alisas ifup-plip ifup-wireless
ifcfg-l0 ifdown-post ifup-bnep ifup-plusb init.ipv6-global
ifdown ifdown-ppp ifup-eth ifup-post net.hotplug
ifdown-bnep ifdown-routes ifup-ippp ifup-ppp network-functions
ifdown-eth ifdown-sit ifup-ipsec ifup-routes network-functions-ipv6
ifdown-ippp ifdown-sl ifup-ipvb ifup-sit
ifdown-ipsec ifdown-tunnel ifup-ipx ifup-sl

?

If you get a FILE, what's the file and what's in it?

if you get all those ifcfg's and ifdown's ... we have a problem. They should be IN ifcfg-eth0 ...

A quick note :


[root@vicidialnow network-scripts]# ls -la
total 404
drwxr-xr-x 2 root root 4096 Mar 27 15:17 .
drwxr-xr-x 11 root root 4096 Oct 30 09:07 ..
-rw-r--r-- 3 root root 153 Oct 29 18:48 ifcfg-eth0
-rw-r--r-- 2 root root 199 Oct 30 09:15 ifcfg-eth2
-rw-r--r-- 1 root root 254 Jun 20 2001 ifcfg-lo

williamconley wrote:Wait just a gol darn minute here.

When you type:
ls /etc/sysconfig/network-scripts/

If you get a FILE, what's the file and what's in it?

if you get all those ifcfg's and ifdown's ... we have a problem. They should be IN ifcfg-eth0 ...

This is what I get:
ifcfg ifdown-ipv6 ifup ifup-isdn ifup-tunnel
ifcfg-eth0 ifdown-isdn ifup-alisas ifup-plip ifup-wireless
ifcfg-l0 ifdown-post ifup-bnep ifup-plusb init.ipv6-global
ifdown ifdown-ppp ifup-eth ifup-post net.hotplug
ifdown-bnep ifdown-routes ifup-ippp ifup-ppp network-functions
ifdown-eth ifdown-sit ifup-ipsec ifup-routes network-functions-ipv6
ifdown-ippp ifdown-sl ifup-ipvb ifup-sit
ifdown-ipsec ifdown-tunnel ifup-ipx ifup-sl

Ok, i'm gonna guess there's a bit of a misfire in your install.

You may (just to be funny) want to try that install again. There may be OTHER misfires, too. did you verify your download was not corrupt when you burned the .iso?

Or you can use the examples given above to build your eth0 config file. If you only have one network card ...

try vi /etc/sysconfig/network-scripts/ifcfg-eth0
and place the text from the sample file above (altered for YOUR network) into the file and save it. Then delete all those other files that are actually script lines.

But I would rebuild the box possibly with a fresh .iso. Especially you just did it recently. Much faster and safer.

Everyone I know has somehow gotten a bad image and spent several hours (days?) trying to fix it at some point. Most regret hammering it out instead of checking the validity of the download immediately (for the rest it was extremely educational and they loved it).

Commonly, with a VicidialNOW install, you will see all of the files etc that Krishna has mentioned, so you can for the first attempt update the "BLANK" file and enter the content and then run "service network restart" to restart your network setup.

Alternatively, try downloading a fresh copy and reinstalling.

Best option though, if you are not very familiar with Linux, Asterisk or Vicidial and you are looking to go to production in a time constrained environment, hire a professional to do the initial install for you. I have seen too many customers loos e a lot of money cause they wantd to spend none and delay their dialing for months trying to figure out these type of trivial issues.

Do you think this is still a software issue?. Or should I try with Intel motherboard(which I'll have to buy if you recommend). I don't mind taking professional help once I figure out it's not just the basic incompatibility.

It's likely just a missing script. This could result from not having a wire in the network card (or not having the network card in the chasis during the install). It is possible that the system did not recognize the hardware in question. If you have a spare box you can install on, just to see if there's a difference, since it doesn't take much time you could try it. But remember (as pointed out earlier, and I realize this is redundant), there are hundreds of things to "try" and lots of time to waste "trying". Having someone else take care of the initial startup can save massive amounts of time.

I doubt that it would be a hardware issue, the Centos installs of the same version that I have done did not conflict with any hardware. Typically if you buy hardware that is just releasing, then it might not have support but most hardware now conforms to some standards and would be supported. I would suggest that you try the suggestions first, 1) attempt fix with manual creation of the ifcfg-eth0 file or, 2) re-install from a new ISO using version 1.2rc1. If it still does not work then get someone to look into your server before having to buy additional hardware.

Apparently you've never had a "virtual" network card built into the chipset of a motherboard make you scratch your head for an hour until you realized that linux hadn't caught up yet, even though the system has been out over a year ... simply because NOONE uses "Celeron" (or was it Sempron?) with a VIA chipset enough for it to be written.

Microsoft Small Business Server 2000 would not even talk to it, Gentoo denied its existence. In the end I left it with the SBS server because (at the time, last year) at least SBS eventually upgraded to latest updates finally had a driver for it (so i took out the spare NIC and left it to run).

But yes, weird hardware issues arise. CentOS did similar things with a couple Dells I had (back in the days of Asterisk@home and then TrixBox, before I discovered Vicidial and left CentOS far behind me).

A missing eth0 is very often either "missing" hardware or "missing" driver for the hardware from the kernel. Or in some circumstances, no wire plugged in at startup. That's my list. Any others?

Try Intel s3000ah mother board

globalme wrote:Try Intel s3000ah mother board

Is there a motherboard that's compatible with both Core2duo and Xeon 3.0 Ghz??. Just wondering if it's possible to upgrade from core2duo to Xeon without having to buy motehr board again??. I presume upgrading will also involve changing RAMs??

We have someone using Intel s3000ah with Xeon , Works gr8.

globalme wrote:We have someone using Intel s3000ah with Xeon , Works gr8.

I bought s3000ah and I find it not working with core2duo. Initially I thought it was smps and changed the smps but it wont even power on. Where am I going wrong?

Which RAM are u using ?

Which Make ?

globalme wrote:Which RAM are u using ?

Which Make ?

Dynet
2GB - DDR2

I'm learning it the hard way..here is what I found:

s3000ah is NOT compatible with core2duo 2.8 Ghz. It is compatible with lower versions till 2.66 GHz. Thats what their site shows and I also called the tech support to get this clarified. They suggested s3200sh instead which is supposedly compatible with higher speeds. This is the 3rd motherboard I'm gonna get for the same processor! and I hope this time it does work. any inputs?

I'll come back later to update what happened and to seek your support!

Thanks,
Kris