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