Page 1 of 1
cant make internal calls
Posted:
Sat Sep 28, 2013 1:12 am
by ambiorixg12
The dialer is working fine agents login at the campaign and can receive and place calls. But Every thing i tried to dial internally from one extension to other extension, i got the message the asterisk message : the person at the extension xxx is not available. What i m missing ?
Re: cant make internal calls
Posted:
Sat Sep 28, 2013 9:39 pm
by williamconley
1) Welcome to the Party!
2) As you are obviously new here, I have some suggestions to help us all help you:
When you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.
This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)
You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. If your installation is "Hosted" list the site name of the host.
If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.
Similar to This:
Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600
3) What extension did you dial and was it an extension matching the dialplan extension in admin->phones for the phone you were trying to dial? A bit of CLI output from a failed attempt along with the configuration details for the phone you were dialing may prove useful.
Re: cant make internal calls
Posted:
Sat Sep 28, 2013 9:55 pm
by ambiorixg12
Thanks for your answer. Right now im not in from of the vicidial Box. but the installation is VICIBOX SERVER : ViciBox5.i686-5.0.3.iso . No Hardware FXO or T1 Hardware just a sip trunk running on a dedicated server. I created 10 extensions like 101,102,103 etc. all running on the default context. when dial CLI show the person on the extension XXX is not available.
Re: cant make internal calls
Posted:
Sun Sep 29, 2013 3:54 pm
by williamconley
You cannot create "extensions" in Vicidial. You create users and phones. Perhaps it would be best if you answered when you WERE in front of your vicidial server instead of working from memory.
**SOLVED Re: cant make internal calls**
Posted:
Mon Sep 30, 2013 5:49 pm
by ambiorixg12
edited the extensions.conf Remove cc in from of the ${EXTEN}. Working fine. Thanks williamconley for be willing to help me.
Re: cant make internal calls
Posted:
Mon Sep 30, 2013 11:13 pm
by williamconley
You may wish to have another look at that when you get more used to the system.
If you edited extensions.conf, you'll have to do it again when you upgrade as that file is edited from time to time and failure to use the newer version can have odd effects.
If you edited extensions-vicidial.conf ... it will only work until the next time you save a phone or carrier. It will be overwritten by the system. So you'll need to make the changes in "admin->phones" to have them written to extensions-vicidial.conf automatically.
Good "self-help", though, since you did resolve your own issue AND post your solution. You're ahead of the game for most newbies!
Re: cant make internal calls
Posted:
Mon Sep 30, 2013 11:36 pm
by ambiorixg12
Thanks williamconley for your recommendations. The file that i edited was extensions.conf and not the
extensions-vicidial.conf witch is included in the extensions.conf.
#include extensions-vicidial.conf
I will be playing with the system i really love it , and thanks again for your support
Re: cant make internal calls
Posted:
Fri Oct 04, 2013 8:50 am
by scopor
I am having the same problem and I also cannot complete my agent login. See details below.
I have just installed a few days now my vicibox server ViciBox5.i686-5.0.3.iso . VERSION: 2.8-413a
BUILD: 130928-1130 No Hardware FXO or T1 Hardware. No extra software after installation. This is a base install.
This is just a test box. It's installed on an hp proliant ml330 g3 server with 2 dual core xeon processor, 2GB ram, 2x146GB scsi Harddrives.
I am still going through initial setup and configuration. I am following the Manager Manual and exercises. However when I login as an agent the phone does not ring to complete the login process. If I try to call from one extension to another just to test that my extensions are working I am getting either of two messages. Either the number is not in service or the person you are calling is unavailable. Please see below my CLI info.
Did I miss a step in my setup?
Connected to Asterisk 1.8.23.0-vici currently running on vici1 (pid = 2163)
Verbosity is at least 21
[Oct 4 09:28:27] -- Remote UNIX connection disconnected
[Oct 4 09:28:38] == Using SIP RTP CoS mark 5
[Oct 4 09:28:38] -- Executing [4002@trunkinbound:1] AGI("SIP/4000-0000000e", "agi-DID_route.agi") in new stack
[Oct 4 09:28:38] -- Launched AGI Script /usr/share/asterisk/agi-bin/agi-DID_route.agi
[Oct 4 09:28:38] -- <SIP/4000-0000000e>AGI Script agi-DID_route.agi completed, returning 0
[Oct 4 09:28:38] -- Executing [9998811112@default:1] Wait("SIP/4000-0000000e", "2") in new stack
[Oct 4 09:28:40] -- Executing [9998811112@default:2] Answer("SIP/4000-0000000e", "") in new stack
[Oct 4 09:28:40] -- Executing [9998811112@default:3] Playback("SIP/4000-0000000e", "ss-noservice") in new stack
[Oct 4 09:28:40] -- <SIP/4000-0000000e> Playing 'ss-noservice.gsm' (language 'en')
[Oct 4 09:28:45] -- Executing [9998811112@default:4] Playback("SIP/4000-0000000e", "vm-goodbye") in new stack
[Oct 4 09:28:45] -- <SIP/4000-0000000e> Playing 'vm-goodbye.gsm' (language 'en')
[Oct 4 09:28:46] -- Executing [9998811112@default:5] Hangup("SIP/4000-0000000e", "") in new stack
[Oct 4 09:28:46] == Spawn extension (default, 9998811112, 5) exited non-zero on 'SIP/4000-0000000e'
[Oct 4 09:28:46] -- Executing [h@default:1] AGI("SIP/4000-0000000e", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack
Re: cant make internal calls
Posted:
Sat Oct 05, 2013 7:41 pm
by mistert
I am having the same problem. The error in asterisk messages is invalid extension.
The dialer creates extensions in the format: exten => 101,1,Dial(SIP/101|60|).
This is incorrect and things work fine when I change them to exten => 101,1,Dial(SIP/101,60).
The problem is that is is not a real fix. I just identified an error, or I am doing something wrong.
I would appreciate anyone's feedback on this one.
Re: cant make internal calls
Posted:
Sat Oct 05, 2013 9:20 pm
by mistert
Well I tracked it back to the perl files and can see that there are two different formats. One for the older astersk version and one for the newer. The formating for the newer is correct, but I am creating the older. Thus my system must think it is running the wrong asterisk version. Any thoughts gents?
%ast_ver_str = parse_asterisk_version($asterisk_version);
if (( $ast_ver_str{major} = 1 ) && ($ast_ver_str{minor} < 6))
{
$Pext .= "exten => $dialplan[$i],1,Dial(IAX2/$extension[$i]|$phone_ring_timeout[$i]|)\n";
}
else
{
$Pext .= "exten => $dialplan[$i],1,Dial(IAX2/$extension[$i],$phone_ring_timeout[$i],)\n";
}
Currently fixed with a hack
/usr/share/astguiclient/ADMIN_keepalive_ALL.pl
#commented out the line that handled the version and hacked the right one in there.
#$asterisk_version = $aryA[3];
$asterisk_version = "1.8.23.0-vici";
Something is clearly wrong here and this is not a good solution, but it works.
Re: cant make internal calls
Posted:
Sun Oct 06, 2013 6:52 am
by mflorell
Check the Asterisk Version as shown in your "Admin -> Servers" settings. Make sure it matches the version of Asterisk you are using.
Re: cant make internal calls -- Solved
Posted:
Thu Dec 19, 2013 12:22 pm
by scopor
Thanks Matt for your reply. Just want to confirm that the version does have something to do with why this is not working. I experienced this issue twice. I have changed the asterisk version in the admin page and that resolved my issue. However I built a new vicibox from downloaded ISO file burnt to CD and got the exact same problem and could not remember how I solved it the first time. After trying for a while I remembered there was something up with the asterisk version. At the CLI I noticed the asterisk version was 1.8.23.0-vici and the asterisk version in the admin panel was 1.4.x. I copied the exact version I saw from the CLI and applied it to the admin section and that resolved my issue.
Re: cant make internal calls -- Solved
Posted:
Thu Dec 19, 2013 12:51 pm
by williamconley
scopor wrote:Thanks Matt for your reply. Just want to confirm that the version does have something to do with why this is not working. I experienced this issue twice. I have changed the asterisk version in the admin page and that resolved my issue. However I built a new vicibox from downloaded ISO file burnt to CD and got the exact same problem and could not remember how I solved it the first time. After trying for a while I remembered there was something up with the asterisk version. At the CLI I noticed the asterisk version was 1.8.23.0-vici and the asterisk version in the admin panel was 1.4.x. I copied the exact version I saw from the CLI and applied it to the admin section and that resolved my issue.
Yep, a known (slight) bug in Vicibox 5.0.3. Probably won't be a bug fix for it, but it'll be fixed in the next major or minor release I'm sure. Just make a note to resolve that each time you install. Along with another personalizations you undoubtedly perform immediately.
Re: cant make internal calls
Posted:
Sun Dec 20, 2015 3:51 pm
by corpusian
Checking the Asterisk Version as shown in "Admin -> Servers" , changed to match with the version of Asterisk i am using, worked for me to.
Re: cant make internal calls
Posted:
Thu Dec 19, 2019 5:53 am
by AyukRolandAgbor
Yeah,
Thank you guys for all the above contributions
Changing the asterisk version in Admin>>server>>TESTast from 1.14.2.0 to 13.21.0-vici, worked for me just right.
Thank you