Peer Oliver Schmidt
2005-Jan-25 02:40 UTC
[Asterisk-Users] Bristuff ZapHFC and Loosing D-Channel
Using the latest(?) bristuff (Asterisk 1.0.4-BRIstuffed-0.2.0-RC3a) I have problems with loosing the D-channel. Most of the time, after the message "PRI D-channel down" it only takes a second or so to come back up, noted by the message "PRI D-channel up" However, today most of the time the D-channel stays down. Calls come in, but can't be answered. Does anyone know of a fix for this, or might have some insights on how to circumvent this problem? Any and all help is greatly appreciated. -- Best regards Peer Oliver Schmidt
Remco Barende
2005-Jan-27 08:01 UTC
[Asterisk-Users] Bristuff ZapHFC and Loosing D-Channel
Hi! Did you ever find the answer to your question? I am getting the same message on the console every second: == Primary D-Channel on span 1 down == Primary D-Channel on span 1 up == Primary D-Channel on span 1 down == Primary D-Channel on span 1 up == Primary D-Channel on span 1 down == Primary D-Channel on span 1 up etc. etc. etc. I'm running Asterisk 1.0.5-BRIstuffed-0.2.0-RC5 The error is only visible however if I run * with -vvvvv (but I guess I shouldn't see these messages nonetheless)? On Tue, 25 Jan 2005, Peer Oliver Schmidt wrote:> Using the latest(?) bristuff (Asterisk 1.0.4-BRIstuffed-0.2.0-RC3a) I have > problems with loosing the D-channel. Most of the time, after the message > > "PRI D-channel down" > > it only takes a second or so to come back up, noted by the message > > "PRI D-channel up" > > However, today most of the time the D-channel stays down. Calls come in, but > can't be answered. > > Does anyone know of a fix for this, or might have some insights on how to > circumvent this problem? > > Any and all help is greatly appreciated. >
Michiel van Baak
2005-Jan-27 11:41 UTC
[Asterisk-Users] Bristuff ZapHFC and Loosing D-Channel
> >> > >> The error is only visible however if I run * with -vvvvv > >> (but I guess I shouldnt see these messages nonetheless)? > > > > No, I still have these messages, and was hoping RC5 would fix them. Nice to > > know that upgrading wont help :-( > > Are you running asterisk with -vvvvvv too? If I run it without verbose > mode on I do not get these messages. Klaus-Peter Junghanns just replied to > the message to and confirmed that this message is normal expected > behaviour > > > > Do you get calls which stop in the middle of the conversation as well? > > No but it is a completely new setup and line and I havent used it much. > > You may try putting busydetect=no in /etc/asterisk/zapata.conf, I have > seen several messages on the list about calls getting cut off and this > being the solution. >The busydetect=no did the trick here. Remco, are you running * on a SMP system ? I cant get the bristuffed thing stable on my P4 HT. I am now running it with i4l and HT disabled, but since it also hosts our internal communication application coded in php with postgres as backend it would be nice to be able to run a second thread when the database is busy.> Cheers! > RemcoMichiel.
Nils Segerdahl
2005-Jan-27 14:05 UTC
[Asterisk-Users] Bristuff ZapHFC and Loosing D-Channel
Hi This is normal behaviour if you are running isdn in PTMP mode, at least in sweden. It is bothering with these messages, but I'we been running my test site with two PTMP lines for months and everything worked fine. It is said that some operators keep trying to turn off the D-channel in PTMP-mode. But asteriskt keeps trying to turn it on. This is usually no problem. If you can't recceive calls, my exeprience is that there is some problem with the msn that is set on the line. /Nils On Tue, 25 Jan 2005, Peer Oliver Schmidt wrote:> Using the latest(?) bristuff (Asterisk 1.0.4-BRIstuffed-0.2.0-RC3a) I > have problems with loosing the D-channel. Most of the time, after the > message > > "PRI D-channel down" > > it only takes a second or so to come back up, noted by the message > > "PRI D-channel up" > > However, today most of the time the D-channel stays down. Calls come in, > but can't be answered. > > Does anyone know of a fix for this, or might have some insights on how > to circumvent this problem? > > Any and all help is greatly appreciated. > -- > Best regards > > Peer Oliver Schmidt > > _______________________________________________ > 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 >Nils Segerdahl --------------------------------------------------------------- Upsala Systemkonsult, UPSYS AB Telefon:(+46) (0)18 56 80 41 Glunten, 751 83 Uppsala Mobil: (+46) (0)703 55 65 03 http://www.upsys.se Fax: (+46) (0)18 56 80 49 --------------------------------------------------------------- Jan 27 Grissom, White and Chaffe burned to death in Apollo 1, 1967 Jan 27 Vietnam War cease-fire signed, 1973 Jan 28 First ski tow, Woodstock VT, 1914 Jan 28 Space Shuttle Challenger (51-L) explodes 74 seconds after liftoff killing Scobee, Smith, McNair, Resnick, Jarvis, Onizuka and McAuliffe, 1986 ---------------------------------------------------------------