Hello, the issue does occour some seconds after connection the line - but the hard reboot takes some time...
The cards are TE420 (4th Gen) - version c01a016a. Zaptel ist 1.4.12.1 The firmware on digium cards can not get flashed - or i am wrong (i have never heard about that) regards, Wolfgang Am Freitag, den 24.04.2009, 06:50 -0400 schrieb Matt Florell: > Hello, > > I would suggest that you first methodically try every possible > combination of zaptel.conf timing settings(each change follwed by a > hard reboot of the Asterisk server) to see if there is a magic > combination of settings that will work. I don't know if you have the > time for that, or if it takes a while for the timing issues to appear, > but that is what I would try. > > If that still doesn't work, we have solved similar issues with older(2 > years ago) Digium quad cards by switching to Sangoma hardware that > offers more options for forcing timing in it's wanpipe driver > software. Although when I posted about this before in another thread > the folks from Digium swear that newer Digium cards(with newer > firmware) do not have this problem using the newer Dahdi drivers. > > What version of Zaptel are you using and how old is your Digium card? > > > MATT--- > > > On 4/24/09, Wolfgang Pichler <[email protected]> wrote: > > hi all, > > > > we do have some troubles with zaptel timing source - we have a setup > > with 3 telco PRI lines, connected to asterisk digium card 0 - asterisk > > does some handling - calls are leaving on digium card 1 - going to a > > siemens hipath - there is some call handling - some of the calls then > > are going from the hipath over a qsig line to a bosch integral PBX - > > handling the rest of the calls. > > > > To be able to get away from the bosch system - we like to put asterisk > > (1 port free on each card) in the middle of the path siemens -> bosch - > > so that it will be siemens -> card 0 asterisk card 1 -> bosch. > > > > Currently the Siemens hipath is playing the network side - the bosch is > > cpe. So the siemens hipath does provide the timing source. > > > > With asterisk in the middle i can not take the timing source from the > > siemens link - because i have already the telco line as timing source. > > But when starting it in this setup - i will get lots of "timing source > > auto card 0!" messages. So i think the siemens timing is not in sync. > > with the telco timing - so mixed up on asterisk with telco line as > > primary timing will not work when the siemens does try to deliver > > timing. > > > > I have not tried as /etc/zaptel.conf parameter 0 als timing parameter (0 > > = be master) - but i think it wont work because the siemens wont accept > > the timing from the asterisk box. > > > > Changing configuration of the siemens is not possible. > > > > So - here the questions... > > - is it possible to do what i want to do ? > > - do you think timing=0 in zaptel.conf will work ? > > - would it be possible to connect a xorcom 2 PRI channel bank to > > asterisk to handle the qsig line between the two ? Or will the xorcom > > then also take the timing from the digum cards - telco lines ? > > > > any hints would be nice... > > > > many thanks > > Wolfgang > > > > > > _______________________________________________ > > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > > > > asterisk-users mailing list > > To UNSUBSCRIBE or update options visit: > > http://lists.digium.com/mailman/listinfo/asterisk-users > > _______________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
