asterisk users - Mar 2007 - Asterisk 1.4 with Digium B410P - Timing problem

Hi list,

we have a dual Xeon server with 2GB RAM running Debian Etch 2.6.18.4-686 
kernel. The server has 2 B410P cards plugged in. No other card.

We installed Asterisk 1.4 trunk with zaptel trunk, ran make b410p, the 
install mISDN1.1.0 (for bug 9064) configure and compile Asterisk with 
chan_misdn, all is fine. In misdn-init.conf we have added 
option=1,master_clock. Asterisk is up and running, voicemail, echo test, 
demo, MOH, everything works well.

Now we want to add conferences with meetme. So we load zaptel module who 
created /dev/zap/channel|ctl|pseudo|timer|transcode. Asterisk is running 
under asterisk:asterisk,we added this user to dialout group to have the 
good rights on those files. Problem: we can't open conferences, we 
always have

[Mar 30 10:55:37] WARNING[28302]: chan_zap.c:896 zt_open: Unable to open 
'/dev/zap/pseudo': No such device or address
[Mar 30 10:55:37] ERROR[28302]: chan_zap.c:7631 chandup: Unable to dup 
channel: No such device or address
[Mar 30 10:55:37] WARNING[28302]: app_meetme.c:758 build_conf: Unable to 
open pseudo channel - trying device
[Mar 30 10:55:37] WARNING[28302]: app_meetme.c:761 build_conf: Unable to 
open pseudo device


What's wrong? The B410P being a Digium card should gave us a timing 
source? Do we forgot to compile some module (no one wxxx from zaptel 
directory is activated)? More generally, how you get the timing working 
with B410P cards and 1.4?

We tried another way, ztdummy: by loading the module, the meetme 
application start to work but ... no more audio in all applications 
(voicemail, meetme, MOH, echo-test, demo,...)! In log we found

Mar 29 22:40:36 SrvPhone kernel: Zapata Telephony Interface Registered on major
196
Mar 29 22:40:36 SrvPhone kernel: Zaptel Version: SVN-branch-1.4-r2351
Mar 29 22:40:36 SrvPhone kernel: Zaptel Echo Canceller: MG2
Mar 29 22:40:39 SrvPhone kernel: ztdummy: RTC rate is 1024
Mar 29 22:40:39 SrvPhone kernel: rtc: lost some interrupts at 1024Hz.
Mar 29 22:40:39 SrvPhone kernel: Registered tone zone 0 (United States / North
America)
Mar 29 22:40:39 SrvPhone kernel: rtc: lost some interrupts at 1024Hz.
Mar 29 22:41:10 SrvPhone last message repeated 1514 times
Mar 29 22:42:11 SrvPhone last message repeated 3050 times
Mar 29 22:42:57 SrvPhone last message repeated 2348 times

Removing ztdummy give audio back but no more meetme :-(

Before opening a bug, we would like to know if some of you have a similar
working setup with B410P and meetme.

Thanks for your feedback.

-- 
Daniel

did you modprobe ztdummy?

On 3/30/07, Administrator TOOTAI <admin@tootai.net>
wrote:
>
> Hi list,
>
> we have a dual Xeon server with 2GB RAM running Debian Etch 2.6.18.4-686
> kernel. The server has 2 B410P cards plugged in. No other card.
>
> We installed Asterisk 1.4 trunk with zaptel trunk, ran make b410p, the
> install mISDN1.1.0 (for bug 9064) configure and compile Asterisk with
> chan_misdn, all is fine. In misdn-init.conf we have added
> option=1,master_clock. Asterisk is up and running, voicemail, echo test,
> demo, MOH, everything works well.
>
> Now we want to add conferences with meetme. So we load zaptel module who
> created /dev/zap/channel|ctl|pseudo|timer|transcode. Asterisk is running
> under asterisk:asterisk,we added this user to dialout group to have the
> good rights on those files. Problem: we can't open conferences, we
> always have
>
> [Mar 30 10:55:37] WARNING[28302]: chan_zap.c:896 zt_open: Unable to open
> '/dev/zap/pseudo': No such device or address
> [Mar 30 10:55:37] ERROR[28302]: chan_zap.c:7631 chandup: Unable to dup
> channel: No such device or address
> [Mar 30 10:55:37] WARNING[28302]: app_meetme.c:758 build_conf: Unable to
> open pseudo channel - trying device
> [Mar 30 10:55:37] WARNING[28302]: app_meetme.c:761 build_conf: Unable to
> open pseudo device
>
>
> What's wrong? The B410P being a Digium card should gave us a timing
> source? Do we forgot to compile some module (no one wxxx from zaptel
> directory is activated)? More generally, how you get the timing working
> with B410P cards and 1.4?
>
> We tried another way, ztdummy: by loading the module, the meetme
> application start to work but ... no more audio in all applications
> (voicemail, meetme, MOH, echo-test, demo,...)! In log we found
>
> Mar 29 22:40:36 SrvPhone kernel: Zapata Telephony Interface Registered on
> major 196
> Mar 29 22:40:36 SrvPhone kernel: Zaptel Version: SVN-branch-1.4-r2351
> Mar 29 22:40:36 SrvPhone kernel: Zaptel Echo Canceller: MG2
> Mar 29 22:40:39 SrvPhone kernel: ztdummy: RTC rate is 1024
> Mar 29 22:40:39 SrvPhone kernel: rtc: lost some interrupts at 1024Hz.
> Mar 29 22:40:39 SrvPhone kernel: Registered tone zone 0 (United States /
> North America)
> Mar 29 22:40:39 SrvPhone kernel: rtc: lost some interrupts at 1024Hz.
> Mar 29 22:41:10 SrvPhone last message repeated 1514 times
> Mar 29 22:42:11 SrvPhone last message repeated 3050 times
> Mar 29 22:42:57 SrvPhone last message repeated 2348 times
>
> Removing ztdummy give audio back but no more meetme :-(
>
> Before opening a bug, we would like to know if some of you have a similar
> working setup with B410P and meetme.
>
> Thanks for your feedback.
>
> --
> Daniel
>
> _______________________________________________
> --Bandwidth and Colocation provided by Easynews.com --
>
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>


-- 
Esta mensagem (incluindo quaisquer anexos) pode conter informa??o
confidencial para uso exclusivo do destinat?rio. Se n?o for o destinat?rio
pretendido, n?o dever? usar, distribuir ou copiar este e-mail. Se recebeu
esta mensagem por engano, por favor informe o emissor e elimine-a
imediatamente. Obrigado.

This e-mail message is intended only for individual(s) to whom it is
addressed and may contain information that is privileged, confidential,
proprietary, or otherwise exempt from disclosure under applicable law. If
you believe you have received this message in error, please advise the
sender by return e-mail and delete it from your mailbox. Thank you.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20070330/67cd27bf/attachment.htm