Darren Round
2004-May-12 04:43 UTC
[Asterisk-Users] Calling CHRIS BARNET (PRI / E100P / ntl)
Chris you might know the answer to my HUUUUUUGE problem A few weeks ago you posted this message: "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." Thread: http://lists.digium.com/pipermail/asterisk-users/2004-April/044169.html I have exactly the same hardware, telephone company, setup and have exactly the same problem. Im in Lincoln and Im running asterisk version: Asterisk CVS-03/09/04-13:55:16 on a dual PIII500 Linux machine. I have no physical alarm lights, my E100P is working, zttool is reporting no alarms but everytime ntl try to bring up the line I get the same error as you: May 11 14:12:06 WARNING[1192491824]: Detected alarm on channel 1: Red Alarm May 11 14:12:06 WARNING[1192491824]: Unable to disable echo cancellation on channel 1 Etc... Etc.. Etc... For all my 10 channels. Did you managed to solve this by asking ntl to deliver ISDN 110 or was is something else? I hope you receive this because Im getting a bit desperate :( Thanks Darren Darren Round B.Sc.(HONS) MANAGING DIRECTOR Advanced I.T. Solutions Ltd The Upper Lodge Sewell Road Lincoln LN2 5QX UK T: 0800 952 0080 F: 0870 751 0590 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.681 / Virus Database: 443 - Release Date: 5/10/2004
Chris Barnett
2004-May-12 06:21 UTC
[Asterisk-Users] Calling CHRIS BARNET (PRI / E100P / ntl)
Hi, Following the *extremely* helpful assistance of Darren Storer I did establish that the NTL line I currently have is ISDN 85 (partial ETSI) whereas Asterisk and the E100P want *full* ETSI (ISDN 110). Not that NTL even understood what it was I was trying to achieve and were initially very confused at the difference between ISDN 85 and ISDN 110, they just kept repeating that their line was Q.931 and therefore should be fine - certainly not the case! They got there in the end though :) I did hit a brick wall with NTL on upgrading the line though, the equipment delivering the line to my premises is not up to the job and needs upgrading/replacing by NTL, this has meant it's all had to go off to their finance department for approval etc. etc. Basically I've got mired up in NTL red tape :( You may be luckier in that the equipment used to deliver your line has been upgraded over the last few years to cope with ISDN 110, you'll need to speak with your NTL account manager to find this out. I've been speaking with Darren recently and there *may* be a chance that ISDN 85 support could be coded into the drivers for *, but even if this were to happen it's a way off. If NTL can't upgrade your current line to ISDN 110 and you can't wait for any possible ISDN 85 support in * then your only other option is to look at changing teleco. For me it's not all doom and gloom as the nice people at BT have been able to put a *very* attractive proposal together to persuade me to switch from NTL and provide me with a pucker ETSI line in the process - so hopefully all's well that ends well! Chris -----Original Message----- From: asterisk-users-admin@lists.digium.com [mailto:asterisk-users-admin@lists.digium.com]On Behalf Of Darren Round Sent: 12 May 2004 12:43 To: asterisk-users@lists.digium.com Subject: [Asterisk-Users] Calling CHRIS BARNET (PRI / E100P / ntl) Chris you might know the answer to my HUUUUUUGE problem A few weeks ago you posted this message: "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." Thread: http://lists.digium.com/pipermail/asterisk-users/2004-April/044169.html I have exactly the same hardware, telephone company, setup and have exactly the same problem. Im in Lincoln and Im running asterisk version: Asterisk CVS-03/09/04-13:55:16 on a dual PIII500 Linux machine. I have no physical alarm lights, my E100P is working, zttool is reporting no alarms but everytime ntl try to bring up the line I get the same error as you: May 11 14:12:06 WARNING[1192491824]: Detected alarm on channel 1: Red Alarm May 11 14:12:06 WARNING[1192491824]: Unable to disable echo cancellation on channel 1 Etc... Etc.. Etc... For all my 10 channels. Did you managed to solve this by asking ntl to deliver ISDN 110 or was is something else? I hope you receive this because Im getting a bit desperate :( Thanks Darren Darren Round B.Sc.(HONS) MANAGING DIRECTOR Advanced I.T. Solutions Ltd The Upper Lodge Sewell Road Lincoln LN2 5QX UK T: 0800 952 0080 F: 0870 751 0590 Forza Ferrari! - *FIVE* times world champions in succession! - ************************************************** Chris Barnett - Managing Director inspHire Limited 5 Chase Park, Daleside Road Nottingham NG2 4GT United Kingdom Tel: +44 (0)870 013 0030 Fax: +44 (0)115 911 1447 chris.barnett@insphire.com www.insphire.com ************************************************** The statements and opinions expressed here are my own and may not represent those of the company. This e-mail is subject to copyright and the information contained in it is confidential. It is intended only for the named recipient. You are advised not to disclose the contents of this email to another person or take copies of it.
Darren Round
2004-May-12 07:26 UTC
[Asterisk-Users] Calling CHRIS BARNET (PRI / E100P / ntl)
Hi Chris Thanks for getting back to me :) Sounds like your having the same sort of game I am with them. Yeah I tracked Darren down and called him myself (one helpful chap indeed!) and he explained how the whole thing works. Ive rang ntl back and got to speak to one of the senior staff there who told me that the whole of the ntl network is ISDN85 apart from one area (sorry guys I cant remember which one) which is 110 and there is no information about their upgrade schedule. So it looks like for now until the new driver is written the E100P is not compatible with the ntl in the UK :( Believe me Id absolutely love to change Telco's but its not really financially viable for me as I've got these pri lines rent free as part of a bigger deal because we buy stacks of bandwidth from ntl. Do you know the irony is that there are talking about putting up the cost of my internet bandwidth if I don?t start using their outdated pri service! Thanks for your Help Chris and thanks to Darren also... Now where did I put that receipt for my e100p????? :) Thanks guys Darren Round> -----Original Message----- > From: asterisk-users-admin@lists.digium.com > [mailto:asterisk-users-admin@lists.digium.com] On Behalf Of > Chris Barnett > Sent: 12 May 2004 14:22 > To: asterisk-users@lists.digium.com > Subject: RE: [Asterisk-Users] Calling CHRIS BARNET (PRI / E100P / ntl) > > Hi, > > Following the *extremely* helpful assistance of Darren Storer > I did establish that the NTL line I currently have is ISDN 85 > (partial ETSI) whereas Asterisk and the E100P want *full* > ETSI (ISDN 110). Not that NTL even understood what it was I > was trying to achieve and were initially very confused at the > difference between ISDN 85 and ISDN 110, they just kept > repeating that their line was Q.931 and therefore should be > fine - certainly not the case! They got there in the end though :) > > I did hit a brick wall with NTL on upgrading the line though, > the equipment delivering the line to my premises is not up to > the job and needs upgrading/replacing by NTL, this has meant > it's all had to go off to their finance department for > approval etc. etc. Basically I've got mired up in NTL red > tape :( You may be luckier in that the equipment used to > deliver your line has been upgraded over the last few years > to cope with ISDN 110, you'll need to speak with your NTL > account manager to find this out. > > I've been speaking with Darren recently and there *may* be a > chance that ISDN 85 support could be coded into the drivers > for *, but even if this were to happen it's a way off. If NTL > can't upgrade your current line to ISDN 110 and you can't > wait for any possible ISDN 85 support in * then your only > other option is to look at changing teleco. For me it's not > all doom and gloom as the nice people at BT have been able to put a > *very* attractive proposal together to persuade me to switch > from NTL and provide me with a pucker ETSI line in the > process - so hopefully all's well that ends well! > > Chris > > -----Original Message----- > From: asterisk-users-admin@lists.digium.com > [mailto:asterisk-users-admin@lists.digium.com]On Behalf Of > Darren Round > Sent: 12 May 2004 12:43 > To: asterisk-users@lists.digium.com > Subject: [Asterisk-Users] Calling CHRIS BARNET (PRI / E100P / ntl) > > > Chris you might know the answer to my HUUUUUUGE problem > > A few weeks ago you posted this message: > "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." > > Thread: > http://lists.digium.com/pipermail/asterisk-users/2004-April/04 > 4169.html > > I have exactly the same hardware, telephone company, setup > and have exactly the same problem. Im in Lincoln and Im > running asterisk version: > Asterisk > CVS-03/09/04-13:55:16 on a dual PIII500 Linux machine. I > have no physical alarm lights, my E100P is working, zttool is > reporting no alarms but everytime ntl try to bring up the > line I get the same error as you: > May 11 14:12:06 WARNING[1192491824]: Detected alarm on > channel 1: Red Alarm May 11 14:12:06 WARNING[1192491824]: > Unable to disable echo cancellation on channel 1 Etc... Etc.. > Etc... For all my 10 channels. > > Did you managed to solve this by asking ntl to deliver ISDN > 110 or was is something else? > > I hope you receive this because Im getting a bit desperate :( > > Thanks > > Darren > > Darren Round B.Sc.(HONS) > MANAGING DIRECTOR > Advanced I.T. Solutions Ltd > The Upper Lodge > Sewell Road > Lincoln > LN2 5QX > UK > T: 0800 952 0080 > F: 0870 751 0590 > > Forza Ferrari! - *FIVE* times world champions in succession! - > > ************************************************** > Chris Barnett - Managing Director > inspHire Limited > 5 Chase Park, Daleside Road > Nottingham NG2 4GT > United Kingdom > > Tel: +44 (0)870 013 0030 Fax: +44 (0)115 911 1447 > chris.barnett@insphire.com www.insphire.com > ************************************************** > The statements and opinions expressed here are my own and may > not represent those of the company. This e-mail is subject to > copyright and the information contained in it is > confidential. It is intended only for the named recipient. > You are advised not to disclose the contents of this email to > another person or take copies of it. > _______________________________________________ > 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 > > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.681 / Virus Database: 443 - Release Date: 5/10/2004 > >--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.681 / Virus Database: 443 - Release Date: 5/10/2004