vicidial.org

Hi there

iv got a bit of a problem with this vicidial install that i really have to get sorted as soon as possible.

the box i've put together has a Digium 4 port BRI card in it (B410p).

as in the title, the problem i have is that the agent is getting a call from teh server, but is hanging up immediately.

the outsput from the asterisk CLI is:

Dec 18 12:25:41 WARNING[18174]: pbx.c:1700 pbx_extension_helper: No application 'Meetme' for extension (default, 8600052, 1)
== Spawn extension (default, 8600052, 1) exited non-zero on 'SIP/201-09672f08'
-- Executing DeadAGI("SIP/201-09672f08", "call_log.agi|h") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/call_log.agi
-- AGI Script call_log.agi completed, returning 0
-- Executing DeadAGI("SIP/201-09672f08", "VD_hangup.agi|PRI-----NODEBUG-----16---------------") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/VD_hangup.agi
-- AGI Script VD_hangup.agi completed, returning 0
== Manager 'sendcron' logged off from 192.168.1.222


screen -r gives the following output:

[root@asterisk ~]# screen -r
There are several suitable screens on:
5516.ASTsend (Detached)
5537.ASTVDremote (Detached)
5534.ASTupdate (Detached)
5526.ASTVDauto (Detached)
5522.ASTVDadapt (Detached)
5508.ASTlisten (Detached)
Type "screen [-d] -r [pid.]tty.host" to resume one of them.



from this it looks like the meetme module isnt loaded properly, but running lsmod shows that zaptel and ztdummy are running fine.

doing ztcfg -vvv shows no chanels which kinda makes me thing that the ztdumy timing source isnt working as it should.

if anyone could point me in the right direction i would be eternally grateful. thanks

make sure you have meetme in "meetme.conf" as well as in "extension.conf"

yup, in meetme.conf i have:


[rooms]
;
; Usage is conf => confno[,pin][,adminpin]
;
conf => 8600011
conf => 8600012
conf => 8600013
conf => 8600014
conf => 8600015
conf => 8600016
conf => 8600017
< snipped >


and in extensions i have:

exten => 8600011,1,Meetme,8600011|q
exten => 8600012,1,Meetme,8600012|q
exten => 8600013,1,Meetme,8600013|q
exten => 8600014,1,Meetme,8600014|q
exten => 8600015,1,Meetme,8600015|q
exten => 8600016,1,Meetme,8600016|q
exten => 8600017,1,Meetme,8600017|q
exten => 8600018,1,Meetme,8600018|q
exten => 8600019,1,Meetme,8600019|q
exten => 8600020,1,Meetme,8600020|q
exten => 8600021,1,Meetme,8600021|q
exten => 8600022,1,Meetme,8600022|q
exten => 8600023,1,Meetme,8600023|q
exten => 8600024,1,Meetme,8600024|q
exten => 8600025,1,Meetme,8600025|q
exten => 8600026,1,Meetme,8600026|q
exten => 8600027,1,Meetme,8600027|q
exten => 8600028,1,Meetme,8600028|q
exten => 8600029,1,Meetme,8600029|q


iv still go the feeling that this is to do with the timing. am i barking up the wrong tree?

did you add meetme in mysql?

if you mean inthe conferences table, then yup:

# [astrix - dds] Query Window
# Connection: astrix - dds
# Host: 192.168.1.222
# Saved: 2006-12-18 14:49:24
#
# Query:
# SELECT *
# FROM `conferences`
#
'conf_exten','server_ip','extension'
'8600011','192.168.1.222',''
'8600012','192.168.1.222',''
'8600013','192.168.1.222',''
'8600014','192.168.1.222',''
'8600015','192.168.1.222',''
'8600016','192.168.1.222',''
'8600017','192.168.1.222',''
'8600018','192.168.1.222',''
'8600019','192.168.1.222',''
'8600020','192.168.1.222',''
'8600021','192.168.1.222',''
'8600022','192.168.1.222',''
'8600023','192.168.1.222',''
'8600024','192.168.1.222',''
'8600025','192.168.1.222',''
'8600026','192.168.1.222',''
'8600027','192.168.1.222',''
'8600028','192.168.1.222',''
'8600029','192.168.1.222',''

post your "lsmod" and also last part on "dmesg" stated your zaptel.

also make sure your timer frequenzy is set to 1000HZ..

hi there, thanks so much for helping me try to debug this.
lsmod:

[root@asterisk ~]# lsmod
Module Size Used by
ztdummy 7748 0
zaptel 196740 1 ztdummy
crc_ccitt 6209 1 zaptel
md5 8129 1
ipv6 242657 20
parport_pc 28033 0
lp 15661 0
parport 38025 2 parport_pc,lp
mISDN_dsp 197868 0
hfcmulti 63176 0
mISDN_capi 95660 0
l3udss1 43752 0
mISDN_l2 42592 0
mISDN_l1 15304 0
mISDN_core 77536 6 mISDN_dsp,hfcmulti,mISDN_capi,l3udss1,mISDN_l2,mISDN_l1
capi 22913 0
capifs 10057 2 capi
kernelcapi 49601 2 mISDN_capi,capi
autofs4 23109 0
sunrpc 144037 1
button 10705 0
battery 12997 0
ac 8901 0
uhci_hcd 32857 0
ehci_hcd 32325 0
hw_random 9685 0
snd_azx 21713 0
snd_hda_codec 121665 1 snd_azx
snd_pcm_oss 52729 0
snd_mixer_oss 21953 1 snd_pcm_oss
snd_pcm 92357 3 snd_azx,snd_hda_codec,snd_pcm_oss
snd_timer 28229 1 snd_pcm
snd 57509 6 snd_azx,snd_hda_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
soundcore 13089 1 snd
snd_page_alloc 13897 2 snd_azx,snd_pcm
e1000 138256 0
via_rhine 24777 0
mii 9281 1 via_rhine
sr_mod 20965 0
dm_snapshot 21093 0
dm_zero 6337 0
dm_mirror 31645 0
ext3 118857 2
jbd 59609 1 ext3
dm_mod 60357 8 dm_snapshot,dm_zero,dm_mirror
ahci 18885 2
libata 67613 1 ahci
sd_mod 20545 3
scsi_mod 117709 4 sr_mod,ahci,libata,sd_mod



my dmesg output is just full of isdn messages, not really anythign interesting in there jsut lots of this:

hfcmulti_tx: fifo(2) has 383 bytes space left (z1=0011, z2=0011) sending 4 of 4 bytes HDLC
hfcmulti_rx: fifo(2) reading 7 bytes (z1=00ef, z2=00e9) HDLC COMPLETE (f1=2, f2=1) got=7
02 01 01 15
hfcmulti_tx: fifo(2) has 383 bytes space left (z1=0015, z2=0015) sending 4 of 4 bytes HDLC
hfcmulti_rx: fifo(2) reading 7 bytes (z1=00f6, z2=00f0) HDLC COMPLETE (f1=3, f2=2) got=7
00 01 01 15
hfcmulti_tx: fifo(2) has 383 bytes space left (z1=0019, z2=0019) sending 4 of 4 bytes HDLC
hfcmulti_rx: fifo(2) reading 7 bytes (z1=00fd, z2=00f7) HDLC COMPLETE (f1=4, f2=3) got=7
02 01 01 15
hfcmulti_tx: fifo(2) has 383 bytes space left (z1=001d, z2=001d) sending 4 of 4 bytes HDLC
hfcmulti_rx: fifo(2) reading 7 bytes (z1=0104, z2=00fe) HDLC COMPLETE (f1=5, f2=4) got=7
00 01 01 15


with regards to the clock frequency, how can i check this?

thanks again

the more i look at this problem, the more ibecome convinced that the answer lies with the lack of a timing source.

ztdummy isnt showing any channels

the usb modules are not loading on this machine (must be something to do with the usb chipset dell are using)

so, in a blind panic, i've ordered an x100p to arrive here on site first thing in teh morning.

does anyone think i may be on the wrong track here?

Asterisk will not install app_meetme if you do not have zaptel drivers loaded at the time of Asterisk compilation.

Did you install your BRI card and/or zaptel drivers after you compiled Asterisk?

You could also contact Digium for support since this is a legitemate support issue with their card and the driver software.

also i think you have loaded ztdummy instead your digium card.

hi matt:

im pretty sure i did install asterisk first and then the misdn drivers. when the x100p turns up tomorrow, ill recomplile zaptel, then asterisk after installing the card.

that sound right?

i would contact digium about this, but im not convinced anything would come of it. to be brutally honest, the installation of the misdn dirvers is a sodding headache!


gerski:

the 4 port bri card doesnt use zaptel drivers to run so i modprobed ztdummy and zaptel in later.


im hoping that the addition of the x100p will sort out my problems, will let you know how i got on...

You do need to install your card and the zaptel drivers before compiling Asterisk. If you didn't do that then Asterisk would not load app_meetme.

Try simply recompiling Asterisk again and see if app_meetme shows up when you start Asterisk up again.

hi matt,

got it sorted now.

it looks like i was on the right sort of track. once i had the a100p installed and had recompiled zaptel and asterisk etc... it sprang into life.

so this must really be a bug in asterisk, it should really have the option of using the misdn modules as a timing source.

anyway, woohoo, sorted, thanks for any and all help with sorting this out.

yeh u need to compile and install zaptel first ,, asterisk detects it and only after that it compiles meetme .