keywords:pbx ip pbx voip gateway gsm gateway

× Questions about B100/200/400/800 ISDN BRI Cards

b800p, Sporadically Dial out fail

10 years 3 months ago #3515 by slutec18
have a trixbox installation with a b800p with 6 ISDN lines configured in PTP mode.
Versions are Trixbox 2.6.2, mISDN 1.1.7, asterisk 1.4.25.
B800P board is configured with
in mISDN script i have the following settings
HFCMULTI_protocol[${i}]="0x22,0x22,0x22,0x22,0x22,0x22,0x22,0x22"
HFCMULTI_layermask[${i}]="0xf,0xf,0xf,0xf,0xf,0xf,0xf,0xf"

the mISDN.conf in /etc
<mISDNconf>
<module poll="128" debug="0" timer="no">hfcmulti</module>
<module debug="0" options="0">mISDN_dsp</module>
<devnode user="root" group="root" mode="644">mISDN</devnode>
<card type="BN8S0">
<port mode="te" link="ptp">1</port>
<port mode="te" link="ptp">2</port>
<port mode="te" link="ptp">3</port>
<port mode="te" link="ptp">4</port>
<port mode="te" link="ptp">5</port>
<port mode="te" link="ptp">6</port>
<port mode="te" link="ptp">7</port>
<port mode="te" link="ptp">8</port>
</card>
</mISDNconf>


The system works well but I have the following problem. Sometimes, usually twice a week the system gives me a dial out failure.
In that circumsance I can receive calls as before but I cannot perform outbound calls.
The only solution is to reach the ssh console in the system and givean "mISDN restart", after that the system returns to normal operation and i can perform outbound calls outbound calls again. I heard the some telcos power off their ISDN to save the power but the strange think is that I get a dial out failure when all the employees are working and not during the night or sundays when everybody is sleeping. Also in misdn.conf I have pmp_l1_check=no and the ports are not configured in group (ports=1,2,3,4,5,6,7,8), so in asterisk the outbound call is performed by choosing directly the channel in sequential mode (from the first to the sixth) and not by calling using a group of trunks.
I tried to search in the forums without success. Someone is telling that is related to telco interrupts in the line.
What can I do with this issue. Is there a way for debugging and try to reproduce this issue?
Your help is really appreciated.




below my misdn.conf

[general]
misdn_init=/etc/misdn-init.conf
debug=0
ntdebugflags=0
ntdebugfile=/var/log/misdn-nt.log
ntkeepcalls=no
bridging=no
l1watcher_timeout=0
stop_tone_after_first_digit=yes
append_digits2exten=yes
dynamic_crypt=no
crypt_prefix=**
crypt_keys=test,muh

[default]
context=misdn
language=en
musicclass=default
senddtmf=yes
far_alerting=no
allowed_bearers=all
nationalprefix=0
internationalprefix=00
rxgain=0
txgain=0
te_choose_channel=no
pmp_l1_check=no
reject_cause=16
need_more_infos=no
nttimeout=no
method=standard
overlapdial=yes
dialplan=0
localdialplan=0
cpndialplan=0
early_bconnect=yes
incoming_early_audio=no
nodialtone=no
presentation=-1
screen=-1
echotraining=no
jitterbuffer=4000
jitterbuffer_upper_threshold=0
hdlc=no
max_incoming=-1
max_outgoing=-1

[isdn]
ports=1,2,3,4,5,6,7,8
context=from-pstn
msns=*

Thank you in advance

i] Last edited by slutec18 at 2009-7-11 20:08 [/i
Attachments:
10 years 3 months ago #3520 by slutec18
James Zhu suggested to check the issue
https://issues.asterisk.org/view.php?id=13488

But since I'm using asterisk 1.4.25 this bug should be already solved :L
http://downloads.asterisk.org/pub/telephony/asterisk/releases/ChangeLog-1.4.25

Any suggestions?
Thanks
10 years 3 months ago #3521 by slutec18
Very Strange behaviour,
as I told the asterisk version is 1.4.25.1 and misdn 1.1.7
In that version the asterisk changelog states that bug Asterisk 0013488 is is
removed.
Anywa my log file is the following

Fri Jul 10 17:09:25 2009: P[ 1] **** Received CAUSE:44, so not cleaning up channel 1
Fri Jul 10 17:09:25 2009: P[ 1] **** This channel is now no longer available,
please try to restart it with 'misdn send restart <port> <channel>'
Fri Jul 10 17:09:25 2009: P[ 1] Sending Restarts on this port.
Fri Jul 10 17:09:25 2009: P[ 1] Restarting and cleaning channel 1
Fri Jul 10 17:09:25 2009: P[ 1] Restarting channel 1
Fri Jul 10 17:09:33 2009: P[ 1] Requested Channel Already in Use releasing this call with cause 34!!!!
Fri Jul 10 17:09:33 2009: P[ 1] couldn't handle event
Fri Jul 10 17:09:33 2009: P[ 1] CC_RELEASE_COMPLETE|CONFIRM [TE]
Fri Jul 10 17:09:46 2009: P[ 1] Requested Channel Already in Use releasing this call with cause 34!!!!
Fri Jul 10 17:09:46 2009: P[ 1] couldn't handle event
Fri Jul 10 17:09:46 2009: P[ 1] CC_RELEASE_COMPLETE|CONFIRM [TE]
Fri Jul 10 17:09:57 2009: P[ 1] Requested Channel Already in Use releasing this call with cause 34!!!!
Fri Jul 10 17:09:57 2009: P[ 1] couldn't handle event
Fri Jul 10 17:09:57 2009: P[ 1] CC_RELEASE_COMPLETE|CONFIRM [TE]
Fri Jul 10 17:10:43 2009: P[ 1] Requested Channel Already in Use releasing this call with cause 34!!!!
Fri Jul 10 17:10:43 2009: P[ 1] couldn't handle event
Fri Jul 10 17:10:43 2009: P[ 1] CC_RELEASE_COMPLETE|CONFIRM [TE]
Fri Jul 10 17:11:17 2009: P[ 1] Requested Channel Already in Use releasing this call with cause 34!!!!
Fri Jul 10 17:11:17 2009: P[ 1] couldn't handle event
Fri Jul 10 17:11:17 2009: P[ 1] CC_RELEASE_COMPLETE|CONFIRM [TE]
Fri Jul 10 17:12:59 2009: P[ 1] Requested Channel Already in Use releasing this call with cause 34!!!!
Fri Jul 10 17:12:59 2009: P[ 1] couldn't handle event
Fri Jul 10 17:12:59 2009: P[ 1] CC_RELEASE_COMPLETE|CONFIRM [TE]
Fri Jul 10 17:14:01 2009: P[ 1] Requested Channel Already in Use releasing this call with cause 34!!!!
Fri Jul 10 17:14:01 2009: P[ 1] couldn't handle event
Fri Jul 10 17:14:01 2009: P[ 1] CC_RELEASE_COMPLETE|CONFIRM [TE]
Fri Jul 10 17:14:29 2009: P[ 1] Requested Channel Already in Use releasing this call with cause 34!!!!
Fri Jul 10 17:14:29 2009: P[ 1] couldn't handle event
Fri Jul 10 17:14:29 2009: P[ 1] CC_RELEASE_COMPLETE|CONFIRM [TE]
Fri Jul 10 17:18:17 2009: P[ 0] -- mISDN Channel Driver Registered --

I don't know what to do
Thank you
10 years 3 months ago #3522 by james.zhu
hello:
please downgrade the asterisk to asterisk-1.4.20 and mISDN-1.1.7 to have a try.
regards!
James.zhu

10 years 1 week ago #3888 by slutec18
This is an asterisk issue for systems with heavy load
After 2 months of testing I think we solved it with success.
https://issues.asterisk.org/view.php?id=15490
and
https://issues.asterisk.org/view.php?id=15458
cheers
10 years 1 week ago #3889 by james.zhu
good。 :victory:

Time to create page: 0.024 seconds
Powered by Kunena Forum