Advance apologies for the length of this mail; I have an ISDN PRI supplied by NTL (ex Diamond Cable, Nottingham) which is currently working happily with an SDX Index phone system. I have to replace this phone system shortly and I've been trying to get a * system working for some weeks now. I have configured the dial plan (which works) and all my SIP extensions (which all work) along with voice mail etc. etc. - all this works perfectly as an internal PBX. My problem comes when I try to connect it to my ISDN line. I have a Digium E100p card which is configured in zaptel.conf thus; span=1,0,5,ccs,hdb3,crc4 bchan=1-15 dchan=16 bchan=17-31 loadzone=uk defaultzone=uk The zapata.conf is like this; [channels] usecallerid=yes callerid=asreceived hidecallerid=no threewaycalling=yes transfer=yes cancelforward=yes callreturn=yes immediate=no callprogress=no language=en echotraining=yes echocancel=yes echocancelwhenbridged=yes rxgain=-5% txgain=+5% pridialplan=unknown overlapdial=yes signalling=pri_cpe switchtype=euroisdn context=inboundpstn group=1 channel => 1-15 callgroup=1 pickupgroup=1 Whenever I try to connect this up to the ISDN line I get a series of Red Alerts and any attempt at outgoing calls results in a no channels available message (essentially all the lines are shown in use and cannot be cleared). I have had my teleco reset the line which just results in further red alerts. NTL, bless them, came out with a test rig and plugged this in the back of my * box and we made a series of test calls which all worked fine, although the NTL chap said the attenuation was out as there was a lot of buzz on the line. He suggested we set the line build out to 6 (-15db) but we were still getting buzz on the test calls - other than that he was happy that the config was correct and as the test rig showed the * box talking properly and making outgoing calls OK we all reckoned that the next time we hooked up to the ISDN line it would be OK. I couldn't do this with him there as the system is in use during the day, so had to wait until the evening after he'd gone. However, I still get the red alerts. If I leave the * box connected to the ISDN line when the teleco attempt to reset the line it immediately trips with another series of red alerts, however it resets just fine when plugged back into the SDX Index system. The teleco says they can see it tripping, but don't know why (?). I have made sure that the card is not sharing interrupts and I've scoured the mail archives and google for any further information I can get my hands on. I just can't get past the red alerts. Does anyone on the list have any idea why this is happening (big question I know), I'm using the stable CVS tree from 15/4/04. Is there anyone else out there using * with an NTL ISDN PRI line? Many thanks for any help offered :) Chris Barnett
Hi Chris,> I have an ISDN PRI supplied by NTL (ex Diamond Cable, Nottingham) which > is currently working happily with an SDX Index phone system. I have toI can't see particular problems with your config, but I have a few comments: [snip]> I have a Digium E100p card which is configured in zaptel.conf thus; > > span=1,0,5,ccs,hdb3,crc4You do need to ensure you have networking timing otherwise you'll get frameslips. I don't know if the 'LBO' really has much effect here, so I would go for span=1,1,0,ccs,hdb3,crc4 Now, do you now you have CRC4 on the link? If you get this wrong, this will cause things not to work, and even if they do, you'll get noise on the link. Try without. span=1,1,0,ccs,hdb3> > The zapata.conf is like this; > > [channels][snip]> rxgain=-5% > txgain=+5%Whilst I know other people have posted differently, I can't see any legitmate reason for specifying gain on an end to end digital link. I'd suggest these should be zero.> further red alerts. NTL, bless them, came out with a test rig and > plugged this in the back of my * box and we made a series of test calls > which all worked fine, although the NTL chap said the attenuation was > out as there was a lot of buzz on the line. He suggested we set the lineSounds like pants to me, but what sort of 'buzz' are you talking about? Remember this is a digital link and not subject to analogue style interference.> Many thanks for any help offered :)My money is on the CRC4 setting. Try that first. Linus
Hi, Am Fr, 2004-04-23 um 20.32 schrieb Chris Barnett:> Advance apologies for the length of this mail; > > I have an ISDN PRI supplied by NTL (ex Diamond Cable, Nottingham) which > is currently working happily with an SDX Index phone system. I have to > replace this phone system shortly and I've been trying to get a * system > working for some weeks now. I have configured the dial plan (which > works) and all my SIP extensions (which all work) along with voice mail > etc. etc. - all this works perfectly as an internal PBX. My problem > comes when I try to connect it to my ISDN line. > > I have a Digium E100p card which is configured in zaptel.conf thus; > > span=1,0,5,ccs,hdb3,crc4I dont know if it makes a differnce when you only have 1 PRI span, but you should make the span connected to the telco your primary sync source, with: span=1,1,5,ccs,hdb3,crc4 best regards Klaus -- Klaus-Peter Junghanns CEO, CTO Junghanns.NET GmbH Breite Strasse 13a - 12167 Berlin - Germany fon: (de) +49 30 79705390 fon: (uk) +44 870 1244692 fax: (de) +49 30 79705391 iaxtel: 1-700-157-8753 http://www.Junghanns.NET/asterisk/