Bug#399970: Asterisk and chan_misdn
lee-in-berlin at web.de
Mon Aug 4 16:12:50 UTC 2008
Victor Seva wrote:
> Lee Garrett escribió:
>> Victor Seva wrote:
>>> Hi all,
>>> I have now a version  of misdn-[kernel | user] with I can finally
>>> build chan_misdn  only adding the proper build-depends (
>>> libisdnnet-dev ). misdn-user builds static libraries as Simon point
>>> me to do.
>> I noticed that your asterisk_18.104.22.168~dfsg-2~bpo40+1_i386.deb in your
>> backports section doesn't have chan_misdn.so shipped. So I recompiled
>> that with the suggested build-depends. It compiles all right,
>> chan_misdn is there, but is not loadable. Asterisk's error log says:
> AFAIK asterisk_22.214.171.124~dfsg-2~bpo40+1_i386.deb has chan_misdn.so
> shipped .
> [studebaker]$ debc asterisk_126.96.36.199~dfsg-2~bpo40+1_i386.changes | grep
> -rw-r--r-- root/root 422976 2008-07-30 00:28:06
> -rw-r--r-- root/root 622520 2008-07-30 00:28:06
> [studebaker]$ pwd
Silly me. I looked into
http://linuxmaniac.torreviejawireless.org/debian/asterisk_backports/, which of
course does not have chan_misdn.
>> [Aug 3 20:29:57] WARNING loader.c: Error loading module
>> libisdnnet.so: cannot open shared object file: No such file or directory
> I can load chan_misdn.so with no such error:
I pulled the packages from
and they work great. I checked by routing a call from SIP to misdn.
So what's the plan for those packages? Having chan_misdn in Lenny would be
nice, although misdn V2 is being merged into linus tree right now. Or would it
be wiser to get the misdn V2 / chan_lcr combo in Lenny? Anyways, whatever the
decision is, it would be better than _no_ ISDN support for Asterisk.
Thanks for the hard work. It's been a pleasure!
More information about the Pkg-voip-maintainers