B410P BRI Help!

Asterisk Asterisk Support
1

Hi,

Asterisk 1.2.18 / Zaptel 1.2.18 / Digium B410P Bri Card.

I have B410P card installed, LED’s are green, misdn commands available on Asterisk cli. I cannot receive calls. (or make them but I am more concerned about receiving as I use SIP trunks for outbound).

If I dial the ISDN number on my mobile I get dead tone (single continuous tone).

I have 2 BRI lines (4 channels) plugged into card ports 3 and 4.

My /etc/misdn-init.conf has the following lines.
card=1,0x4
te_ptmp=3,4 (I also tried with te_ptp=3,4)
poll=128
dsp_options=0
debug=0xf

My /etc/asterisk/misdn.conf has the following lines
[general]
debug=3
bridging=no
[default]
echocancel=yes
context=from-pstn
[sean]
ports=3,4
context=from-internal

Here is output from misdnportinfo

[root@localhost ~]# misdnportinfo

Port 1: TE-mode BRI S/T interface line (for phone lines)
-> Protocol: DSS1 (Euro ISDN)
-> childcnt: 2

Port 2: TE-mode BRI S/T interface line (for phone lines)
-> Protocol: DSS1 (Euro ISDN)
-> childcnt: 2

Port 3: TE-mode BRI S/T interface line (for phone lines)
-> Protocol: DSS1 (Euro ISDN)
-> Layer 4 protocol 0x04000001 is detected, but not allowed for TE lib.
-> childcnt: 2

  • Port NOT useable for PBX

Port 4: TE-mode BRI S/T interface line (for phone lines)
-> Protocol: DSS1 (Euro ISDN)
-> Layer 4 protocol 0x04000001 is detected, but not allowed for TE lib.
-> childcnt: 2

  • Port NOT useable for PBX

mISDN_close: fid(3) isize(131072) inbuf(0x96cd060) irp(0x96cd060) iend(0x96cd060)

In Asterisk ‘misdn show port 3’ shows port as UP as does port 4.
‘misdn show channels’ returns Chan List: (nil)

misdn show config returns…

localhost*CLI> misdn show config
Misdn General-Config:
-> Version: chan_misdn-0.3.0
-> misdn_init: /etc/misdn-init.conf -> debug: 3
-> tracefile: /var/log/asterisk/misdn.log -> bridging: no
-> stop_tone_after_first_digit: yes -> append_digits2exten: yes
-> dynamic_crypt: no -> crypt_prefix:
-> crypt_keys: -> ntdebugflags: 0
-> ntdebugfile: /var/log/misdn-nt.log

[PORT 3]
-> name: sean -> allowed_bearers: all
-> far_alerting: no -> rxgain: 0
-> txgain: 0 -> te_choose_channel: no
-> pmp_l1_check: no -> reject_cause: 21
-> block_on_alarm: no -> hdlc: no
-> context: from-intisdn -> language: en
-> musicclass: default -> callerid:
-> method: standard -> dialplan: 0
-> localdialplan: 0 -> cpndialplan: 0
-> nationalprefix: 0 -> internationalprefix: 00
-> presentation: -1 -> screen: -1
-> always_immediate: no -> nodialtone: no
-> immediate: no -> senddtmf: no
-> hold_allowed: no -> early_bconnect: yes
-> incoming_early_audio: no -> echocancel: 128
-> need_more_infos: no -> noautorespond_on_setup: no
-> nttimeout: no -> jitterbuffer: 4000
-> jitterbuffer_upper_threshold: 0 -> callgroup:
-> pickupgroup: -> msns: *
-> ptp: no

[PORT 4]
-> name: sean -> allowed_bearers: all
-> far_alerting: no -> rxgain: 0
-> txgain: 0 -> te_choose_channel: no
-> pmp_l1_check: no -> reject_cause: 21
-> block_on_alarm: no -> hdlc: no
-> context: from-intisdn -> language: en
-> musicclass: default -> callerid:
-> method: standard -> dialplan: 0
-> localdialplan: 0 -> cpndialplan: 0
-> nationalprefix: 0 -> internationalprefix: 00
-> presentation: -1 -> screen: -1
-> always_immediate: no -> nodialtone: no
-> immediate: no -> senddtmf: no
-> hold_allowed: no -> early_bconnect: yes
-> incoming_early_audio: no -> echocancel: 128
-> need_more_infos: no -> noautorespond_on_setup: no
-> nttimeout: no -> jitterbuffer: 4000
-> jitterbuffer_upper_threshold: 0 -> callgroup:
-> pickupgroup: -> msns: *
-> ptp: no
localhost*CLI>

For testing outbound dial I tried putting this in [from-internal] context of extensions.conf

123,1,Dial(mISDN/g:sean/07962403030)
123,n,Hangup()

Any help you can offer would be greatly appreciated.

Sean

2

Bump: still struglling with this one. Any help appreciated.

3

I’ll try and help. I’m using a QuadBRI card, but at least we have UK ISDN in common :smile:

Incidentally, make sure the ISDN is definitely working… I have never had an ISDN connection installed by BT working first time! If this chaceks out, i’ll do some more thinking.

4

Thanks Jeg,

There is an existing PBX in place and working. I hope to replace this with Asterisk. The lines are definately working!

Any further ideas appreciated.

5

Mmm… I think the Digium BRI card and the Junghanns cards do things differently… I’ve never even looked at the misdn.conf file and I don’t have a misdn-init.conf file. Can you post your zaptel.conf file?

John

6

Hmmm. Zaptel.conf.

I must say I haven’t tousched the zaptel.conf on this installation so it will be as per make samples.

I don’t think it is relevant to this kind of install - BUT I COULD BE WRONG!

Advice appreciated!

7

OK, I contacted Digium support and they informed me that I will need to upgrade my kernel as I need a minumum of 2.6.15 for B410P to work with mISDN.

I am going to upgrade tommorow. I will report back!

8

I must say I am really worried about losing this one. Main problem is that I do not have BRI lines so I cannot test in my office. I have to take box over to client and either have him open early or close late so I can try it.

I spent an hour on the phone to Digium Tech Supp on Monday night after the unsuccessful installation on Saturday. It was concluded that the jumpers might be in wrong position.

Tuesday morning, checked jumpers but they were correctly set. (TE Mode)

Tuesday evening, another hour on phone Digium Tech Supp and it was concluded that my Kernel version is not new enough. (need minimum 2.6.15) So I had to go away and upgrade kernel which I plan to do tonight.

In the meantime, I had an email from a friend in Italy to confirm he has a working install with B410P and same kernel as the one I currently have (2.6.9) which kind of goes against what digium TS have told me.

I am not confident upgrading kernel will fix this, but I will try anyway.

I didn’t install libpri, could this contribute to the problem? I was following instructions from asteriskguru and it was not included.

I am certain it should not be this difficult.

oh one last thing. The LED’s on the back of the card. My friend says his stay red when the cables are connected and go green when he makes a call. Mine go green as soon as I plug the cables in. Good or bad?

9

I have two Asterisk boxes with the B410P in Oz. Initially we had heaps of problems with the ISDN installs themselves, with PTP and PTMP issues etc etc.
If judging by past experience with our ISDN I would say that when the ISDN’s are in PTMP the led’s only go green when call’s are active. It could also be the terminating resisitors on the card. You’ll find some info on them on the beronet site.

Both working boxes have 2.6.18 kernel. There is a lot of banter around on the net about the misdn driver creating high CPU %, and possible kernel panics with less 2.6.15 so I wasn’t prepared to risk it. But then again I haven’t seen misdn in action with a lesser kernel.

First box we have was built by contractor with SUSE 10 with asterisk 1.2.17, and the one I put together is on Centos 5 with asterisk 1.4.5.

Make sure that your misdn-init.conf does suit the ISDN install you have.
Then I would suggest check misdn.conf.

10

Thanks Brett and thanks Digium support.

Upgrading to kernel > 2.6.15 solved the problem.

I installed Centos5 and was in business.