asterisk users - Jul 2005 - Fritz PCI card in ptp mode with chan_misdn

Hello !

I would like to get working a Fritz PCI card using chan_misdn
operating in ptp mode.
Afer compiling mISDN into the kernel and building chan_misdn
Asterisk stops loading with :

[chan_misdn.so] => (Channel driver for mISDN Support (Bri/Pri))
   == Parsing '/etc/asterisk/misdn.conf': Found
UnLocking config_mutex
   == Registered channel type 'mISDN' (This driver enables the asterisk 
to use hardware which is supported by the new )
debug_init: using stdout for debug log
debug_init: using stderr for warning log
debug_init: using stderr for error log
debug_init: debug_mask = 0
Locking Config Mutex
UnLocking Config Mutex
Init. Stack on port:1
unknown port(1) type 0x00000000
No lower Id port:1
init_stack: Success
aster1:/etc/asterisk #

But the above message "init_stack: Success" is not true.
The mISDN stuff is loaded as follows:

modprobe mISDN_core
modprobe mISDN_l1 debug=0
modprobe mISDN_l2 debug=0
modprobe l3udss1
modprobe mISDN_dsp debug=0 options=0x0

modprobe avmfritz layermask=0xf protocol=0x22

The relevant misdn.conf show:

; chan_misdn sample config
; general section:
;
[general]
; define your default context here
context=misdn
; default language
language=en
; set debugging flag:
; 0 - No Debug
; 1 - mISDN Messages and * - Messages, and * - State changes
; 2 - Messages + Message specific Informations (e.g. bearer capability)
; 3 - very Verbose, the above + lots of Driver specific infos
; 4 - even more Verbose than 3
;
debug=3
;
; Stops dialtone after getting first digit on nt Port
;
stop_tone_after_first_digit=yes
;
; Wether to append overlapdialed Digits to Extension or not
;
append_digits2exten=yes
; users sections:
;
; name your sections as you which but not "general" !
; the secions are Groups, you can dial out in extensions.conf
; with Dial(mISDN/g:extern/101) where extern is a section name,
; chan_misdn tries every port in this section to find a
; new free channel
;
[extern]
; define your ports, e.g. 1,2 (depends on mISDN-driver loading order)
ports=1
; context where to go to when incoming Call on one of the above ports
context=from_meridian
; uncomment the following to get into s extension at extension conf
; there you can use DigitTimeout if you can't or don't want to use
; isdn overlap dial.
;immediate=yes
; uncomment the following to have hold and retrieve support
;hold_allowed=yes
; Group Specific Language
language=en
; indicate the incoming calls to asterisk
; here you can give a comma seperated list or simply an '*' for
; any msn.
;msns=*
; here an example with given msns
;[second_extern]
;ports=5
;context=Extern2
;msns=102,144,101,104

Linux Debian
Kernel 2.6.12

Thanks for any hints !

Best regards

Hans

On 18:21, Mon 25 Jul 05, Johann Steinwendtner wrote:
> Hello !
> 
> I would like to get working a Fritz PCI card using chan_misdn
> operating in ptp mode.
As far as I know the fritz cards do not support ptp mode.
We tried all the possible config file options with chan_capi
and in the end we trashed them and installed a junghanns
QuadBRI.

If you get it working in ptp mode, please tell me how you
did it.
-- 
Michiel van Baak
http://michiel.vanbaak.info
michiel@vanbaak.info
GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7E0B9A2D

"Why is it drug addicts and computer afficionados are both called
users?"

The mISDN Fritz! driver supports PTP mode.  In your startup script where you
load the mISDN drivers call the fritz driver thusly:

    modprobe avmfritz protocol=34

Bit 5 sets PTP mode, bits 3-0 set the D-channel protocol ID (set bit one for
DSS1).

Craig

----- Original Message ----- 
From: "Michiel van Baak" <michiel@vanbaak.info>
To: <asterisk-users@lists.digium.com>
Sent: Wednesday, July 27, 2005 12:35 AM
Subject: Re: [Asterisk-Users] Fritz PCI card in ptp mode with chan_misdn

> On 18:21, Mon 25 Jul 05, Johann Steinwendtner wrote:
> > Hello !
> >
> > I would like to get working a Fritz PCI card using chan_misdn
> > operating in ptp mode.
>
> As far as I know the fritz cards do not support ptp mode.
> We tried all the possible config file options with chan_capi
> and in the end we trashed them and installed a junghanns
> QuadBRI.
>
> If you get it working in ptp mode, please tell me how you
> did it.
> -- 
> Michiel van Baak
> http://michiel.vanbaak.info
> michiel@vanbaak.info
> GnuPG key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7E0B9A2D
>
> "Why is it drug addicts and computer afficionados are both called
users?"
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>

Craig,

You obviously have has experience with chan_mISDN in AU and the Fritz.
Have you tried chan_capi? I am currently using a Fritz with chan_capi
in AU and am not entirely happy with it. Is chan_mISDN any better?


On 7/27/05, Craig Guy <cguy@bigpond.net.au> wrote:
> The mISDN Fritz! driver supports PTP mode.  In your startup script where
you
> load the mISDN drivers call the fritz driver thusly:
> 
>     modprobe avmfritz protocol=34
> 
> Bit 5 sets PTP mode, bits 3-0 set the D-channel protocol ID (set bit one
for
> DSS1).
> 
> Craig
> 
> ----- Original Message -----
> From: "Michiel van Baak" <michiel@vanbaak.info>
> To: <asterisk-users@lists.digium.com>
> Sent: Wednesday, July 27, 2005 12:35 AM
> Subject: Re: [Asterisk-Users] Fritz PCI card in ptp mode with chan_misdn
> 
> 
> > On 18:21, Mon 25 Jul 05, Johann Steinwendtner wrote:
> > > Hello !
> > >
> > > I would like to get working a Fritz PCI card using chan_misdn
> > > operating in ptp mode.
> >
> > As far as I know the fritz cards do not support ptp mode.
> > We tried all the possible config file options with chan_capi
> > and in the end we trashed them and installed a junghanns
> > QuadBRI.
> >
> > If you get it working in ptp mode, please tell me how you
> > did it.
> > --
> > Michiel van Baak
> > http://michiel.vanbaak.info
> > michiel@vanbaak.info
> > GnuPG key:
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7E0B9A2D
> >
> > "Why is it drug addicts and computer afficionados are both called
users?"
> > _______________________________________________
> > Asterisk-Users mailing list
> > Asterisk-Users@lists.digium.com
> > http://lists.digium.com/mailman/listinfo/asterisk-users
> > To UNSUBSCRIBE or update options visit:
> >    http://lists.digium.com/mailman/listinfo/asterisk-users
> >
> 
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>

http://www.asteriskguru.com/tutorials/bri.html
http://www.asteriskguru.com/tutorials/chan_misdn.html

These tutorials might be able to point you in the right direction.
(please let us know if they were helpful.)

Zoa,

Johann Steinwendtner wrote:
> Hello !
>
> I would like to get working a Fritz PCI card using chan_misdn
> operating in ptp mode.
> Afer compiling mISDN into the kernel and building chan_misdn
> Asterisk stops loading with :
>
> [chan_misdn.so] => (Channel driver for mISDN Support (Bri/Pri))
>   == Parsing '/etc/asterisk/misdn.conf': Found
> UnLocking config_mutex
>   == Registered channel type 'mISDN' (This driver enables the
asterisk
> to use hardware which is supported by the new )
> debug_init: using stdout for debug log
> debug_init: using stderr for warning log
> debug_init: using stderr for error log
> debug_init: debug_mask = 0
> Locking Config Mutex
> UnLocking Config Mutex
> Init. Stack on port:1
> unknown port(1) type 0x00000000
> No lower Id port:1
> init_stack: Success
> aster1:/etc/asterisk #
>
> But the above message "init_stack: Success" is not true.
> The mISDN stuff is loaded as follows:
>
> modprobe mISDN_core
> modprobe mISDN_l1 debug=0
> modprobe mISDN_l2 debug=0
> modprobe l3udss1
> modprobe mISDN_dsp debug=0 options=0x0
>
> modprobe avmfritz layermask=0xf protocol=0x22
>
> The relevant misdn.conf show:
>
> ; chan_misdn sample config
> ; general section:
> ;
> [general]
> ; define your default context here
> context=misdn
> ; default language
> language=en
> ; set debugging flag:
> ; 0 - No Debug
> ; 1 - mISDN Messages and * - Messages, and * - State changes
> ; 2 - Messages + Message specific Informations (e.g. bearer capability)
> ; 3 - very Verbose, the above + lots of Driver specific infos
> ; 4 - even more Verbose than 3
> ;
> debug=3
> ;
> ; Stops dialtone after getting first digit on nt Port
> ;
> stop_tone_after_first_digit=yes
> ;
> ; Wether to append overlapdialed Digits to Extension or not
> ;
> append_digits2exten=yes
> ; users sections:
> ;
> ; name your sections as you which but not "general" !
> ; the secions are Groups, you can dial out in extensions.conf
> ; with Dial(mISDN/g:extern/101) where extern is a section name,
> ; chan_misdn tries every port in this section to find a
> ; new free channel
> ;
> [extern]
> ; define your ports, e.g. 1,2 (depends on mISDN-driver loading order)
> ports=1
> ; context where to go to when incoming Call on one of the above ports
> context=from_meridian
> ; uncomment the following to get into s extension at extension conf
> ; there you can use DigitTimeout if you can't or don't want to use
> ; isdn overlap dial.
> ;immediate=yes
> ; uncomment the following to have hold and retrieve support
> ;hold_allowed=yes
> ; Group Specific Language
> language=en
> ; indicate the incoming calls to asterisk
> ; here you can give a comma seperated list or simply an '*' for
> ; any msn.
> ;msns=*
> ; here an example with given msns
> ;[second_extern]
> ;ports=5
> ;context=Extern2
> ;msns=102,144,101,104
>
> Linux Debian
> Kernel 2.6.12
>
> Thanks for any hints !
>
> Best regards
>
> Hans
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users@lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-users

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 254 bytes
Desc: OpenPGP digital signature
Url :
http://lists.digium.com/pipermail/asterisk-users/attachments/20050729/70981f3e/signature.pgp