New Installation, Doesnt work?

[drakeharper]

I bought the manual and follwed it explicitly.. Ive set up a few of these, but .........

Its all installed, it did the OS update.. So I assume that it updated the kernel. That being said, I think I need to recompile asterisk, etc.. I do have a Sangoma UT50 VoiceTime USB stick installed. At least I think 'Suse recognized it... LOL

Anyway, my problem is that asterisk wont start. "Unable to connect to remote asterisk (does /var/run/asterisk.ctl exist?)"
I tried to manually start it, as I did yesterday, but it wont even manually start. Yesterday it worked, but when i tried to get in the dialer, it told me that it wasnt a valid conference??

Ok, so I beleive i need to recompile, but how? The iso didnt include the recompile scripts.. I searched this forum, found where Kumba said to extract from the iso? Im lost... any help would be greatly appreciated!

Thanks!

[rrb555]

Have u tried checking ur screens?

Code: Select all

screen -ls

Did u reboot after installation?

[drakeharper]

I did reboot after installation... Here is what happens when I try to login to the dialer... (Asterisk had to be started manually?? ) Something is weird here and this is my third reinstall...

Unable to open DAHDI pseudo device

That is what happens when I try to login to the dialer.. then it tells me its not a valid conference number?? Any help is VERY appreciated, Im about ready to pull my hair out.. Ive setup around 10-12 of these.. never have I had these problems??

[drakeharper]

I even skipped the OS update on this installation... Still it acts like it never setup dahdi, zap..asterisk.. anything really...

Code: Select all

vici*CLI> sip show peers
Name/username              Host            Dyn Nat ACL Port     Status         
gs102/gs102                (Unspecified)    D   N      0        UNKNOWN         
201/201                    192.168.1.7      D   N      5060     OK (29 ms)     
vitel-outbound             64.2.142.93          N      5060     OK (26 ms)

Code: Select all

vici*CLI> dahdi show status
No DAHDI interface found.
[May 15 14:35:25] WARNING[28984]: chan_dahdi.c:12661 dahdi_show_status: Unable to open /dev/dahdi/ctl: No such file or directory


[rrb555]

can u post the output of

Code: Select all

screen -ls

[drakeharper]

vici:~ # screen -ls
There are screens on:
5369.ASTVDadapt (Detached)
6246.ASTupdate (Detached)
6254.ASTVDauto (Detached)
5371.ASTfastlog (Detached)
6257.ASTVDremote (Detached)
6249.ASTsend (Detached)
6252.ASTlisten (Detached)
7 Sockets in /var/run/screens/S-root.

[drakeharper]

NOw I reinstalled again, this time with vicibox-express

Everything works fine except for one thing... I added a 2nd phone and I cant get it to be able to log in. I enter the phone uname and pword, sip show peers shows it as registered, but the dialer keeps sayin that its not active in the system... but it CLEARLY is... Any suggestions would help alot, I have scoured this forum and havent really found an answer to this issue yet.. This is all that stands between me and an active phone room... **HELP** LOL

[racosta79]

Hello, I have a Vicibox Cluster running with 5 Asterisk, 2 Web, 1 DB and 1 Archive servers. I do Inbound and Outbound. I have 130 seats. All my trunks are SIP and I got sometimes cross calls with two inbound calls from different campaigns to the one agent.
So I bought Sangoma's UT50 Voicetime device for each server, but when I was about to install I found that the dahdi version in my Vicibox installation is no longer supporte by this device or vice versa.
My installation is:
VERSION: 2.6-393a
BUILD: 130124-1721
© 2013 ViciDial Group

telephony1:~ # asterisk -rx "core show version"
Asterisk 1.4.44-vici built by abuild @ build18 on a i686 running Linux on 2013-01-24 19:07:26 UTC

telephony1:~ # uname -r
3.1.10-1.16-pae

telephony1:~ # rpm -qa | grep dahd
dahdi-tools-2.6.1-8.1.i586
dahdi-linux-kmp-pae-2.6.1_k3.1.10_1.16-12.1.i586
dahdi-linux-2.6.1-12.1.i586
asterisk-dahdi-1.4.44-26.4.i586

At the Sangoma UT50 support page they say "NOTE: DAHDI 2.6 and above is currently not supported."

So How do I fix my cross call problem instead? Is there a custom build driver for the UT50?

Thank you!
R063R