Page 1 of 1

Vicidial Manual Dialing Mode - No Calls are Connecting

PostPosted: Fri Dec 18, 2009 6:30 pm
by aamiriqbal
vicidialnow 1.2 FINAL
vicidial VERSION: 2.0.5-203
BUILD: 90323-1554
Asterisk Version: 1.2.30.2

Hi All,

I have installed VicidialNow 1.2 FINAL. When I dial with Vicidial Manual Dialing Method, the X-Lite rings and I receive the call. The CLI displaying:

> Channel SIP/4407-0990cfa8 was answered.
-- Executing MeetMe("SIP/4407-0990cfa8", "8600051|F") in new stack
== Parsing '/etc/asterisk/meetme.conf': Found
-- Created MeetMe conference 1023 for conference '8600051'
-- Playing 'conf-onlyperson' (language 'en')

The issue is:

1. I can hear "you are currently the only person in this conference" after a very long time.

2. I can see the call is being dialed and answered but I can't hear anything on X-Lite.

3. When I Hangup the call on Vicidial Web Client and Logoff the Meetme Conference still not getting disconnected and X-Lite still stays connected "Call Established"

DIALPLAN:
exten => _1NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _1NXXNXXXXXX,2,MixMonitor(/usr/local/recordings/${EXTEN:1}-${TIMESTAMP}-${CALLERIDNUM}.wav|bv(0)V(0))
exten => _1NXXNXXXXXX,3,Dial(SIP/+${EXTEN}@${VOICEPULSE_GATEWAY_OUT_A},50,tT0)
exten => _1NXXNXXXXXX,4,GotoIf($["${DIALSTATUS}" = "CHANUNAVAIL"]?${EXTEN}|GatewayB)
exten => _1NXXNXXXXXX,5(GatewayB),Dial(SIP/+${EXTEN}@${VOICEPULSE_GATEWAY_OUT_B},50,tTo)

Please note that I can make manual calls with X-Lite but not with Vicidial Manual Dialing Mode.

Kindly advise.

Thanks in advance.

PostPosted: Fri Dec 18, 2009 9:57 pm
by williamconley
change your dial plan to one in the sample "carrier" setups and AFTER you have a functional, happy system you can play with "failover" and such a piece at a time.

do you have any OTHER software in this box?

PostPosted: Mon Dec 21, 2009 12:48 pm
by aamiriqbal
Hi,

Thanks for the reply Williamconley,

I have change the dialing plan according to the sample "carrier". I can make the manual calls through X-Lite but NOT with Vicidial Manual or Auto Mode:

1. The MeetMe session gets created, but, I cannot hear the "You are currently the only person in the conference". I do hear this sound after like 10 to 15 minutes.

2. On the CLI I can see the call is being dialed and Answered, but, I cannot hear any sound.

3. When I log-out of the Vicidial Manual or Auto Dialing Mode, the X-Lite does not hangup automatically.

Please advise.

Thanks in advance

PostPosted: Mon Dec 21, 2009 1:09 pm
by williamconley
after your vicidialnow installation, what ELSE did you install?

it's likely you have installed something that is interfering with vicidial or you have a bad installation. vicidialnow is not as prone to bad installs as vicibox can be (if you lose internet during install), but it's still not perfect.

but what you describe clearly sounds like a problem with interfering software or a bad install.

do you have any telephony hardware involved in the install?

PostPosted: Mon Dec 21, 2009 2:32 pm
by aamiriqbal
Hi Williamconley,

I do not have any telephony hardware or any other software installed on the box. I am sure, nothing went wrong during the installation process.

I can send you my extensions.conf file, if you think can be at any help?

PostPosted: Mon Dec 21, 2009 4:08 pm
by ykhan
Hi Aamir,

Check the output of "zttest". Also, do you get any Time synchronization errors on the agent screen once logged in? Can you post your Carrier's dialstring from extensions-vicidial.conf or extensions.conf (depending if you are using GUI for Vicidial or not)?

What is your network setup like? Agents are on the same subnet? Are you using NAT?

--Yousaf

PostPosted: Mon Dec 21, 2009 4:48 pm
by aamiriqbal
Hi Yousuf,

I did receive the Time Synchronization Error for the first time I installed Version 1.3 but upon setting the Time to 24 Hours and rebooting the box it was solved.

I am using STATIC IPs so not NATING on my router, but YES, in my SIP.conf I have: nat=yes

I have 2 NICs in the box ONE is connected into WAN (Static IP) and 2nd one is used for LAN purposes so yes all the agents are on the same subnet and can dial Manually (Softphone)

I tried running 'zttest'... nothing has happned for a long time... so I pressed Ctrl+C, got the message:

Opened pseudo zap interface, measuring accuracy...

--- Results after 0 passes ---
Best: 0.000000 -- Worst: 100.000000 -- Average: 100.000000

Thanks for your response.

Kind Regards,

PostPosted: Mon Dec 21, 2009 5:05 pm
by ykhan
Looks to me like a time synchronization issue due to your zttest. If you have no response from ZTTEST, then that is an issue. Update your rc.local file and change the 18.XXX.XXX.XXX entry to pool.ntp.org and uncomment the second entry.

Also try using IAX phone like Zoiper instead and post results.

PostPosted: Mon Dec 21, 2009 5:27 pm
by aamiriqbal
Hello Yousuf,

my usr/local/rc.local file does not have any entry starting with 18.XXX.XXX.XXX

Is this the correct location of the file?

Regards,

PostPosted: Mon Dec 21, 2009 7:22 pm
by williamconley
is ztdummy loading during startup?

PostPosted: Tue Dec 22, 2009 9:35 am
by aamiriqbal
Hi Yousuf,

Thanks for all your time and support.

I issue was my SATA HDD, I just replaced my SATA HDD with IDE and everything working fine now. Do you think SATA has some compatibility issues with Linux or Asterisk?

Maybe this could be a help to anyone else here.

Kind Regards,

PostPosted: Tue Dec 22, 2009 9:37 am
by aamiriqbal
Thanks williamconley,

For all your support and time. I just replaced the SATA HDD with IDE. Everything working fine now, I just followed the "vicidialnow-getting-started-guide" and I can dial Manually with Softphone as well as with Vicidial Manual Method.

Kind Regards,

PostPosted: Tue Dec 22, 2009 7:24 pm
by williamconley
sata vs ide should not be related at all. we build all our boxes with sata and a lot of our old "trash" tester boxes are still ide, all work the same. if the os starts and everything ELSE works, i don't think i can come up with a situation where that would be the issue.

however, i think that reinstalling onto a new drive could resolve the issue. did you reinstall or image the drive to the other drive?

if you had a "dirty install", that would certainly explain the resolution that worked for you. :)

PostPosted: Tue Dec 22, 2009 11:06 pm
by aamiriqbal
Hi Williamconley,

I reinstalled on IDE HDD. I remember having the same issue in the past. Suddenly I recalled and replaced the HDD.

Regards,