paok1926 wrote:I took your advice about posting my configuration very seriously, but i cant edit my profile and add it as a signature
Call me skeptical: You don't know how to edit your signature (which is a learning disability, not a fault with the system, IMHO) is not a reason to leave the information out of your post. Putting it directly in your post is preferable anyway so it won't change on your older posts when you update your system. But leaving it off is not viable even for the extremely lazy. lol
Preaching/flaming/picking on you session over. Back to our regularly scheduled programming:
paok1926 wrote:Yesterday, when i stuck with GoAutodial, i tried Vicibox. But administration pages, aesthetically, look older than me (I'm 57) and i think it offers much-much more than i can use..
Goautodial and Vicibox install the same underlying application (Vicidial). But Goautodial installs an older version and breaks some deeper and/or newer features while supplying a prettier interface. I would suggest that if you want a race car to get your bank account as full as possible, you want Vicibox. If, however, you want to create a pretty call-center so you can sell it to someone OR you have a deep requirement for CentOS (which some facilities have) Goautodial is marvelous.
Cooler yet: Vicidial (stock, unaltered, but slightly old) is likely installed on this server. The screens aren't linked or mentioned during the install, but they ARE there. Thus you can always test to see if a feature is broken by the goautodial interface by merely using the Vicidial interface instead for the same purpose. Albeit a full generation behind, it's still a valid install (goautodial is very good at installing Vicidial).
If you really are just now building your system: My best advice is that you start over with Vicibox now. After installing with Vicibox (instructions in a PDF on Vicibox.com) switch to the Vicidial manager's manual available on EFLO.net.
paok1926 wrote:- Code: Select all
[root@cc2 ~]# screen -r
There are several suitable screens on:
14013.ASTfastlog (Detached)
14010.ASTVDadapt (Detached)
14007.ASTVDremote (Detached)
14004.ASTVDauto (Detached)
14001.ASTlisten (Detached)
13998.ASTsend (Detached)
13995.ASTupdate (Detached)
12490.asterisk (Detached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.
Excellent. they are running. Now we go to "is it trying to dial". Asterisk is running in a screen and is likely writing to a log file (or several). You can either check the log file(s) or log in to the screen and see what happens when it tries to dial (IF it tries to dial).
- Code: Select all
/var/log/asterisk
/var/log/astguiclient
or
- Code: Select all
screen -r asterisk
Note that to get out of the screen, you do not type exit: You use 'ctrl-a' then 'ctrl-d' to "detach" from the screen and leave it running (important as asterisk is actually running in this console, exiting or 'ctrl-c' breaking would kill the pbx!)