Conference a call WITHOUT hardware/pci cards

I was reading that you have to have the pci interface card to conference calls. (i’m new by the way, so please try to be detailed). I don’t use any normal phone lines, and i need to conference 3 or 4 callers this weekend. All users will be using SIP phones / softphones. I need all 4 of us on the line at the same time to test an Information Management System that i have been developing and am about to release to the public, so if anyone knows how to do this, i would very much appreciate it.

TIA

Are you, perhaps, referring to the need for a timing source? If so, you should be able to use the ztdummy driver.

Ok, if i get the dummy driver, can i use conferencing with it? If so, where can i download it from please?

Thank you.

[quote=“AlexGrim”]Ok, if i get the dummy driver, can i use conferencing with it? If so, where can i download it from please?

Thank you.[/quote]http://downloads.asterisk.org/pub/telephony/zaptel/

Downloading now… Is it safe to assume that this will satisfy the requirements for conferencing?

thanks again.

What motherboard and chipset are you hosting on. Suggest you check,

cat /sys/devices/system/clocksource/clocksource0/available_clocksource

Mine, for example, returns,

[root@trixbox1 asterisk]# pg /sys/devices/system/clocksource/clocksource0/available_clocksource
acpi_pm jiffies tsc pit 

Them configure the linux kernel to use the best of the available (hpet - High Precision Event Timer, if it’s available should almost always be selected.) acpi_pm is usually the next best, though some older motherboard’s bios renders acpi_pm almost the worst choice.

On CENTOS, the asterisknow distro edit,

/etc/grub.conf

[root@trixbox1 asterisk]# pg /etc/grub.conf 
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE:  You have a /boot partition.  This means that
#          all kernel and initrd paths are relative to /boot/, eg.
#          root (hd0,0)
#          kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
#          initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=15
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.18-164.el5) with CDRW
        root (hd0,0)
        kernel /vmlinuz-2.6.18-164.el5 ro root=/dev/VolGroup00/LogVol00 clocksource=acpi_pm hdc=ide-scsi
        initrd /initrd-2.6.18-164.el5.img

attention to the argument “CLOCKSOURCE=” Put your good, better, best clocksource, on the right side of the = sign.

to verify the ACTUAL clocksource you’re kernel is using,

[root@trixbox1 asterisk]# cat /sys/devices/system/clocksource/clocksource0/current_clocksource  

reboot.

To test asterisk’s “happiness” with your timing source,

[root@trixbox1 asterisk]# dahdi_test
Opened pseudo dahdi interface, measuring accuracy...
99.998% 99.993% 99.996% 99.997% 99.996% 99.997% 99.996% 99.997% 
99.996% 99.994% 99.997% 99.997% 99.996% 99.997% 99.996% 99.997% 
99.996% 99.995% 99.996% 99.996% 99.996% 99.996% 99.997% 99.996% 
99.997% 99.996% 99.996% 99.996% 99.996% 99.997% 99.996% 99.996% 
--- Results after 32 passes ---
Best: 99.998 -- Worst: 99.993 -- Average: 99.996296, Difference: 99.996296

Before I forced acpi_pm my best accuracy was only 99.93%, with periodic stuttering at 99.83%. Now it’s always 99.99x%.

Good luck,
/S

Here are my results. I will perform a full replay later, when i have time to completely follow your instructions. My motherboard is an ECS (a year old), and i can’t remember what chipset it uses, but i believe that it is nVidia.

[^v^] cat /sys/devices/system/clocksource/clocksource0/available_clocksource hpet acpi_pm jiffies tsc [^v^]

Check which clocksource you’re system is using (by default),

cat /sys/devices/system/clocksource/clocksource0/current_clocksource 

If it is not HPET, then I’d suggest using the grub boot parameter to force it and try your dahdi_test (both before and after the force).

/S

[^v^] cat /sys/devices/system/clocksource/clocksource0/current_clocksource hpet [^v^]

[^v^] dahdi_test Unable to open dahdi interface: No such file or directory [^v^]

Then, as the saying goes, “you’re cooking with gas.” You should have the best clocksource going. How are your dahdi_test accuracies?

/S

[^v^] dahdi_test Unable to open dahdi interface: No such file or directory [^v^] [^v^] yum list *dahdi* ... Installed Packages asterisk-dahdi.x86_64 1.6.0.5-2.fc10 @updates dahdi-tools.x86_64 2.0.0-1.fc10 @fedora Available Packages dahdi-tools-devel.i386 2.0.0-1.fc10 fedora dahdi-tools-devel.x86_64 2.0.0-1.fc10 fedora dahdi-tools-libs.i386 2.0.0-1.fc10 fedora dahdi-tools-libs.x86_64 2.0.0-1.fc10 fedora [^v^]

I have another question, i noticed that dahdi-tools-libs was available, so i yummed it and got this error:

Transaction Check Error: file /usr/lib64/libtonezone.so.1.0 from install of dahdi-tools-libs-2.0.0-1.fc10.x86_64 conflicts with file from package zaptel-lib-1.4.12.1-1.fc10.x86_64

But i think i remember someone telling me that dahdi supersedes / replaces zaptel, so i can just remove the zaptel packages, and stay with dahdi, right?

Here is my zaptel packages:

[^v^] yum list *zaptel* ... Installed Packages zaptel.x86_64 1.4.12.1-1.fc10 @fedora zaptel-lib.x86_64 1.4.12.1-1.fc10 @fedora Available Packages callweaver-zaptel.x86_64 1.2.0.1-1.2.fc10 fedora zaptel-devel.i386 1.4.12.1-1.fc10 fedora zaptel-devel.x86_64 1.4.12.1-1.fc10 fedora zaptel-lib.i386 1.4.12.1-1.fc10 fedora zaptel-utils.x86_64 1.4.12.1-1.fc10 fedora [^v^]

Thanx

These type of dependencies issues are beyond my expertise.

But I think,

yum install "asterisk14-dahdi.i386"

handles the forward dependencies and tidies up the backwards facing zaptel issues. But you might want to drill into that some more.

This is where asterisk sometimes gets ugly.

/S

slideshare.net/david.motta/u … l-to-dahdi

Well, i read that guide (thanx), and then i did this, which got around the dependency issue:

[code][^v^] yum remove zaptel zaptel-lib

Package Arch Version Repository Size

Removing:
zaptel x86_64 1.4.12.1-1.fc10 installed 485 k
zaptel-lib x86_64 1.4.12.1-1.fc10 installed 188 k
Removing for dependencies:
asterisk-dahdi x86_64 1.6.0.5-2.fc10 installed 504 k


Erasing : asterisk-dahdi-1.6.0.5-2.fc10.x86_64 1/3
warning: /etc/asterisk/meetme.conf saved as /etc/asterisk/meetme.conf.rpmsave
Erasing : zaptel-lib-1.4.12.1-1.fc10.x86_64 2/3
Erasing : zaptel-1.4.12.1-1.fc10.x86_64 3/3
warning: /etc/zaptel.conf saved as /etc/zaptel.conf.rpmsave
warning: /etc/udev/rules.d/zaptel.rules saved as /etc/udev/rules.d/zaptel.rules.rpmsave

Removed:
zaptel.x86_64 0:1.4.12.1-1.fc10 zaptel-lib.x86_64 0:1.4.12.1-1.fc10

Dependency Removed:
asterisk-dahdi.x86_64 0:1.6.0.5-2.fc10

Complete!
[^v^] yum -y install dahdi-tools-libs

Package Arch Version Repository Size

Installing:
dahdi-tools-libs x86_64 2.0.0-1.fc10 fedora 25 k


Installed:
dahdi-tools-libs.x86_64 0:2.0.0-1.fc10

Complete!
[^v^] yum -y install asterisk-dahdi

Package Arch Version Repository Size

Installing:
asterisk-dahdi x86_64 1.6.0.5-2.fc10 updates 229 k


Installed:
asterisk-dahdi.x86_64 0:1.6.0.5-2.fc10

Complete!
[^v^] yum list dahdi zaptel

Installed Packages
asterisk-dahdi.x86_64 1.6.0.5-2.fc10 @updates
dahdi-tools.x86_64 2.0.0-1.fc10 @fedora
dahdi-tools-libs.x86_64 2.0.0-1.fc10 @fedora
Available Packages
callweaver-zaptel.x86_64 1.2.0.1-1.2.fc10 fedora
dahdi-tools-devel.i386 2.0.0-1.fc10 fedora
dahdi-tools-devel.x86_64 2.0.0-1.fc10 fedora
dahdi-tools-libs.i386 2.0.0-1.fc10 fedora
zaptel.x86_64 1.4.12.1-1.fc10 fedora
zaptel-devel.i386 1.4.12.1-1.fc10 fedora
zaptel-devel.x86_64 1.4.12.1-1.fc10 fedora
zaptel-lib.i386 1.4.12.1-1.fc10 fedora
zaptel-lib.x86_64 1.4.12.1-1.fc10 fedora
zaptel-utils.x86_64 1.4.12.1-1.fc10 fedora
[^v^]
[/code]

And then restarted asterisk and re-registered my sip client, and then tried to dial the conference extension, and got this:

Hate*CLI> == Using SIP RTP CoS mark 5 == Using SIP VRTP CoS mark 6 -- Executing [XXX@office:1] Answer("SIP/Vector-029873f0", "") in new stack -- Executing [XXX@office:2] Wait("SIP/Vector-029873f0", "1") in new stack -- Executing [XXX@office:3] Authenticate("SIP/Vector-029873f0", "XXX") in new stack -- <SIP/Vector-029873f0> Playing 'agent-pass.ulaw' (language 'en') -- <SIP/Vector-029873f0> Playing 'auth-thankyou.ulaw' (language 'en') -- Executing [XXX@office:4] MeetMe("SIP/Vector-029873f0", "18|pM") in new stack == Parsing '/etc/asterisk/meetme.conf': == Found == Spawn extension (office, XXX, 4) exited non-zero on 'SIP/Vector-029873f0' Hate*CLI>

and when using “module show” i DO see these lines:

app_meetme.so       MeetMe conference bridge                               0
chan_dahdi.so       DAHDI Telephony w/PRI & SS7                         0
codec_dahdi.so      Generic DAHDI Transcoder Codec Translato 0
app_dahdibarge.so      Barge in on DAHDI channel application   0
app_dahdiscan.so       Scan DAHDI channels application            0

So do you think that i may need some of those “available” packages listed in the output above?:

zaptel.x86_64                           1.4.12.1-1.fc10  
zaptel-lib.x86_64                       1.4.12.1-1.fc10
zaptel-utils.x86_64                     1.4.12.1-1.fc10

Nevermind, i already answered that question. It would appear that dahdi replaces all the zaptel stuff, so those packages should not be necessary:

[^v^] yum install zaptel zaptel-lib zaptel-utils ... Transaction Check Error: file /usr/sbin/fxotune from install of zaptel-utils-1.4.12.1-1.fc10.x86_64 conflicts with file from package dahdi-tools-2.0.0-1.fc10.x86_64 file /usr/share/man/man8/fxotune.8.gz from install of zaptel-utils-1.4.12.1-1.fc10.x86_64 conflicts with file from package dahdi-tools-2.0.0-1.fc10.x86_64 file /usr/lib64/libtonezone.so.1.0 from install of zaptel-lib-1.4.12.1-1.fc10.x86_64 conflicts with file from package dahdi-tools-libs-2.0.0-1.fc10.x86_64

So then, if i have all that i need, why does it still hang up when i enter the CORRECT password? If i enter the wrong password, is says so; but if it is correct, it says “thank you” and then hangs up…

Again, here is my meetme.conf

[rooms] conf => 999,XXXX,XXXXXXXXXX

and my extensions.conf, for the conference room:

exten => 999,1,Answer exten => 999,n,Wait(1) exten => 999,n,Authenticate(XXXX) exten => 999,n,MeetMe(18|pM) exten => 999,n,Playback(vm-goodbye) exten => 999,n,Hangup

Also, i still get this:

[^v^] dahdi_test Unable to open dahdi interface: No such file or directory [^v^]

thanx

This log file excerpt might help (you, not me :smiley:):

[Sep 21 16:48:42] NOTICE[2672] loader.c: 155 modules will be loaded. [Sep 21 16:48:44] NOTICE[2672] res_smdi.c: No SMDI interfaces are available to listen on, not starting SMDI listener. [Sep 21 16:48:47] ERROR[2672] chan_mobile.c: No Bluetooth device found. Not loading module. [Sep 21 16:48:47] WARNING[2672] translate.c: plc_samples 160 format f [Sep 21 16:48:47] ERROR[2672] codec_dahdi.c: Failed to open /dev/dahdi/transcode: No such file or directory [Sep 21 16:48:47] NOTICE[2672] pbx_ael.c: Starting AEL load process. [Sep 21 16:48:47] NOTICE[2672] ael.y: Note: In asterisk.conf, in the [compat] section, the app_set is set to 1.6 or greater. The Set() function no longer removes double quotes from the value. If this is a surprise to you, you can set app_set to 1.4. [Sep 21 16:48:47] NOTICE[2672] pbx_ael.c: AEL load process: parsed config file name '/etc/asterisk/extensions.ael'. [Sep 21 16:48:47] NOTICE[2672] pbx_ael.c: AEL load process: checked config file name '/etc/asterisk/extensions.ael'. [Sep 21 16:48:47] NOTICE[2672] pbx_ael.c: AEL load process: compiled config file name '/etc/asterisk/extensions.ael'. [Sep 21 16:48:47] NOTICE[2672] pbx_ael.c: AEL load process: merged config file name '/etc/asterisk/extensions.ael'. [Sep 21 16:48:47] NOTICE[2672] pbx_ael.c: AEL load process: verified config file name '/etc/asterisk/extensions.ael'. [Sep 21 16:48:47] WARNING[2672] config.c: Unknown directive '#exten' at line 33 of /etc/asterisk/extensions.conf [Sep 21 16:48:47] VERBOSE[2672] logger.c: SIP channel loading... [Sep 21 16:48:47] NOTICE[2672] chan_sip.c: The 'username' field for sip peers has been deprecated in favor of the term 'defaultuser' [Sep 21 16:48:47] WARNING[2672] app_voicemail.c: Invalid max failed login attempts [Sep 21 16:48:48] WARNING[2672] chan_iax2.c: Unable to open IAX timing interface: No such file or directory [Sep 21 16:48:48] WARNING[2672] chan_iax2.c: Error opening firmware directory '/usr/share/asterisk/firmware/iax': No such file or directory [Sep 21 16:48:48] WARNING[2672] chan_dahdi.c: Unable to open '/dev/dahdi/channel': No such file or directory [Sep 21 16:48:48] ERROR[2672] chan_dahdi.c: Unable to open channel 1: No such file or directory here = 0, tmp->channel = 1, channel = 1 [Sep 21 16:48:48] ERROR[2672] chan_dahdi.c: Unable to register channel '1' [Sep 21 16:48:48] WARNING[2672] chan_dahdi.c: Unable to open '/dev/dahdi/channel': No such file or directory [Sep 21 16:48:48] ERROR[2672] chan_dahdi.c: Unable to open channel 1: No such file or directory here = 0, tmp->channel = 1, channel = 1 [Sep 21 16:48:48] ERROR[2672] chan_dahdi.c: Unable to register channel '1' [Sep 21 16:48:48] WARNING[2672] chan_dahdi.c: Unable to open '/dev/dahdi/channel': No such file or directory [Sep 21 16:48:48] ERROR[2672] chan_dahdi.c: Unable to open channel 1: No such file or directory here = 0, tmp->channel = 1, channel = 1 [Sep 21 16:48:48] ERROR[2672] chan_dahdi.c: Unable to register channel '1' [Sep 21 16:51:29] NOTICE[2929] chan_sip.c: Peer 'Vector' is now Reachable. (5ms / 2000ms) [Sep 21 16:52:24] VERBOSE[2675] logger.c: -- Remote UNIX connection [Sep 21 16:52:28] VERBOSE[2929] logger.c: == Using SIP RTP CoS mark 5 [Sep 21 16:52:28] VERBOSE[2929] logger.c: == Using SIP VRTP CoS mark 6 [Sep 21 16:52:28] VERBOSE[3823] logger.c: -- Executing [999@office:1] Answer("SIP/Vector-019ad570", "") in new stack [Sep 21 16:52:28] VERBOSE[3823] logger.c: -- Executing [999@office:2] Wait("SIP/Vector-019ad570", "1") in new stack [Sep 21 16:52:29] VERBOSE[3823] logger.c: -- Executing [999@office:3] Authenticate("SIP/Vector-019ad570", "XXXX") in new stack [Sep 21 16:52:29] VERBOSE[3823] logger.c: -- <SIP/Vector-019ad570> Playing 'agent-pass.ulaw' (language 'en') [Sep 21 16:52:32] VERBOSE[3823] logger.c: -- <SIP/Vector-019ad570> Playing 'auth-thankyou.ulaw' (language 'en') [Sep 21 16:52:32] VERBOSE[3823] logger.c: -- Executing [999@office:4] MeetMe("SIP/Vector-019ad570", "18|pM") in new stack [Sep 21 16:52:32] VERBOSE[3823] logger.c: == Parsing '/etc/asterisk/meetme.conf': [Sep 21 16:52:32] VERBOSE[3823] logger.c: == Found [Sep 21 16:52:32] VERBOSE[3823] logger.c: == Spawn extension (office, 999, 4) exited non-zero on 'SIP/Vector-019ad570' [Sep 21 16:52:39] VERBOSE[3818] logger.c: -- Remote UNIX connection disconnected

You guys don’t have a way to flag posts? You may want to lease a User Forum Management System from me :wink:

Bump…

I noticed your trouble while digging for some info myself, perhaps this might be what you are looking for: Asterisk cmd Conference

Quit trying to wedge the Dahdi drivers in without hardware, it might be possible but it appears to be easier to go this route.

random: I noticed your trouble while digging for some info myself, perhaps this might be what you are looking for: voip-info.org/tiki-index.php … Conference

Me: Everyone and their mother has been there. I’m not sure what you are trying to point out? It doesn’t require a timer? I know that, but i don’t want anything that is not from a repo, and the dahdi and meetme are packaged in a repo already, meaning that they update when updates are available, and you don’t have to recompile each time you update your kernel.

random: Quit trying to wedge the Dahdi drivers in without hardware, it might be possible but it appears to be easier to go this route.

Me: Wtf do you mean? That is what one of the dahdi modules are for: a dummy driver for timing. Zaptel is obsolete.

I think that you may need to be more clear with your point, because i’m not sure what you are getting at, but thanx for the effort.