It's normal, in fact I use it to be sure that everything's ok, since I think it will not occur unless we have no alarms on the spans!
Regards Scott Scott M. Stingel President, Emerging Voice Technology, Inc. Palo Alto California & London England www.evtmedia.com -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Christian Victor Sent: Sunday, September 12, 2004 9:03 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: [Asterisk-Users] TN405P running but with errors Hello! I am trying to install a TN405P on a P4-3GHz-HT machine running Debian Sarge with kernel 2.4.27. When I start Asterisk in -vvvvc mode it always shows == D-Channel on span 1 up == Restart on requested on entire span 1 == D-Channel on span 3 up == D-Channel on span 2 up == Restart on requested on entire span 3 == Restart on requested on entire span 2 == D-Channel on span 4 up == Restart on requested on entire span 4 -- B-channel 1 successfully restarted on span 2 -- B-channel 1 successfully restarted on span 3 -- B-channel 1 successfully restarted on span 4 -- B-channel 1 successfully restarted on span 1 . . . -- B-channel 31 successfully restarted on span 1 -- B-channel 31 successfully restarted on span 2 -- B-channel 31 successfully restarted on span 3 -- B-channel 31 successfully restarted on span 4 Once all B-channels have been restarted there seems to be no more problems. Is this normal behaviour? I saw the above messages in some posting concerning misconfigurations and now I am afraid to put the machine to production. Once I have the machine up I will gladly share my experience on using * in heavy-load enviroment. Thanks for your help Christian My /etc/zaptel.conf looks like this: span=1,1,0,ccs,hdb3,crc4 span=2,0,0,ccs,hdb3,crc4 span=3,0,0,ccs,hdb3,crc4 span=4,0,0,ccs,hdb3,crc4 bchan=1-15,17-31 dchan=16 bchan=32-46,48-62 dchan=47 bchan=63-77,79-93 dchan=78 bchan=94-108,110-124 dchan=109 loadzone = nl defaultzone=nl My carrier told me to use CAS signalling but then I get dchan up/dchan down messages every second and nothng works. When I use CCS inbound/outbound calls work fine. Mybe my carrier just lacks knowledge about their own equipment. ;-) My /etc/asterisk/zapate.conf is like: switchtype=euroisdn signalling=pri_cpe pridialplan=local ;overlapdial=yes ;usedistinctiveringdetection=yes usecallerid=yes hidecallerid=no ;callwaiting=yes ;restrictcid=no ;usecallingpres=yes ;callwaitingcallerid=yes ;threewaycalling=yes ;transfer=yes ;cancallforward=yes ;callreturn=yes echocancel=no echocancelwhenbridged=no ;echotraining=yes ;relaxdtmf=yes rxgain=0.0 txgain=0.0 group=1 ;callgroup=1 ;pickupgroup=1 immediate=no ;callerid=2564286000 ;amaflags=default ;accountcode=lss0101 ;adsi=yes ;busydetect=yes ;busycount=4 ;callprogress=yes ;musiconhold=default ;idledial=6999 ;[EMAIL PROTECTED] ;minunused=2 ;minidle=1 ;jitterbuffers=4 channel => 1-15,17-31 channel => 32-46,48-62 channel => 63-77,79-93 channel => 94-108,110-124 _______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] 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 [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
