bilal ghayyad
2009-Jan-20 10:18 UTC
[asterisk-users] the FXS ports of Digium and damaging if connected to Tel Line
Hi All; I am facing a problem that always the users confused and connect the telephone line coming from the telephone service provider to the FXS port and cause it to be damaged, specially if the card was 2 fxs and 2 fxo, so they make mistake and connect the line to fxs while it should be connected to fxo. What is the solution for this disaster? Regards Bilal
Steve Howes
2009-Jan-20 10:28 UTC
[asterisk-users] the FXS ports of Digium and damaging if connected to Tel Line
On 20 Jan 2009, at 10:18, bilal ghayyad wrote:> Hi All; > > I am facing a problem that always the users confused and connect the > telephone line coming from the telephone service provider to the FXS > port and cause it to be damaged, specially if the card was 2 fxs and > 2 fxo, so they make mistake and connect the line to fxs while it > should be connected to fxo. > > What is the solution for this disaster?I have done this (very briefly) by accident. It survived. Is it definitely dead? Do the other ports work? If its just that port thats toasted then you might get away with just replacing that module.
Geoff Lane
2009-Jan-20 11:37 UTC
[asterisk-users] the FXS ports of Digium and damaging if connected to Tel Line
On Tuesday, January 20, 2009, bilal ghayyad wrote:> What is the solution for this disaster?I live in UK, where we don't use RJ11 for telephones and so need to use adapters, which I just leave hanging out of the FXO ports. With the adapters in place, it's difficult to plug the phones into the wrong ports. I've also stuck a large label on the computer cabinet to show which ports are for what. For info, I have a TDM400P. I suspect that the label idea might help but the other would depend on whether your country uses RJ11 for standard phone connections. HTH, -- Geoff
bilal ghayyad
2009-Jan-20 12:56 UTC
[asterisk-users] the FXS ports of Digium and damaging if connected to Tel Line
Dear Steve; But it is not logical to keep having damaging ports, till when these mistakes will be able to keep replace it? Regards Bilal> > Hi All; > > > > I am facing a problem that always the users confused > and connect the > > telephone line coming from the telephone service > provider to the FXS > > port and cause it to be damaged, specially if the card > was 2 fxs and > > 2 fxo, so they make mistake and connect the line to > fxs while it > > should be connected to fxo. > > > > What is the solution for this disaster? > > I have done this (very briefly) by accident. It survived. > Is it > definitely dead? Do the other ports work? If its just that > port thats > toasted then you might get away with just replacing that > module. > > > > ------------------------------ > > Message: 19 > Date: Tue, 20 Jan 2009 11:28:17 +0100 > From: sh0t <sh0t at sh0t.org> > Subject: Re: [asterisk-users] CDR problems -- two call legs > create > only one CDR. Using ForkCDR() not even working. > To: Asterisk Users Mailing List - Non-Commercial Discussion > <asterisk-users at lists.digium.com> > Message-ID: <4975A741.5060000 at sh0t.org> > Content-Type: text/plain; charset=UTF-8; format=flowed > > hello > > When I bridge an incoming and outgoing call > (attempting to simulate > > call-forwarding) I'm only getting one CDR -- that > of the outgoing call. > > A (PSTN) calls B (residing on Asterisk) and the > Asterisk calls C (cell > > phone on PSTN) and bridges the call. > > The only CDR created is from B to C. I have even tried > using Answer() > > and ForkCDR() to get two CDRs, but to no avail. > > I am starting to wonder if there's a bug in the > CDR generation in > > general, because I set up an extension to do only > that: > > exten => 5822558,1,Answer() > > exten => 5822558,n,ForkCDR() > > exten => 5822558,n,Playback(tt-monkeys) > > exten => 5822558,n,Hangup() > I have the same problem, try older version like 1.4.21 for > example.. > And look at: http://bugs.digium.com/view.php?id=13797, > there is some > patch that might help. > For me the only possible option to play with forkcdr as I > expected is > using older versions of Asterisk > > best regards > > > > ------------------------------ > > Message: 20 > Date: Tue, 20 Jan 2009 11:31:46 +0100 > From: Klaus Darilion <klaus.mailinglists at pernau.at> > Subject: Re: [asterisk-users] how to cancel new recorded > message from > voicemail menu? > To: Asterisk Users Mailing List - Non-Commercial Discussion > <asterisk-users at lists.digium.com> > Message-ID: <4975A812.8070401 at pernau.at> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > > Philipp Kempgen schrieb: > > Klaus Darilion schrieb: > > > >> If a user has recorded a new voicemail message > (e.g. unavailable > >> message) then it is prompted with 3 choices. > >> 1. accept recording > >> 2. listen to the recorded message > >> 3. rerecord the message > >> > >> Isn't it possible to cancel the recording? > > > > You could hang up. > > But users might not be aware of this simple solution. > > Stupid me :-) > > > > ------------------------------ > > Message: 21 > Date: Tue, 20 Jan 2009 11:34:38 +0100 > From: Klaus Darilion <klaus.mailinglists at pernau.at> > Subject: Re: [asterisk-users] Asterisk 1.6 T38 to G711 > transcoding is > this possible? > To: Asterisk Users Mailing List - Non-Commercial Discussion > <asterisk-users at lists.digium.com> > Message-ID: <4975A8BE.3020506 at pernau.at> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > What you need is a so called T38Gateway application. > > there is a patch o the tracker which you might want to try: > http://bugs.digium.com/view.php?id=13405 > > klaus > > Steve Gladden schrieb: > > The scenario we have is fax send/recieve software that > ONLY talks T38 > > and an asterisk box. > > > > We have ITSP providers that do NOT talk T38 but G711 > only. > > > > Does asterisk have the capability to take the T38 call > from an ATA > > or T38 software then bridge/transcode it and do G711 > out to the PSTN > > providers? > > > > If not is there another product PAID or FREE software > or hardware that can > > do this easily and reliably? > > > > Thanks very much! > > > > Steve Gladden > > > > > > > > > > > > ------------------------------ > > Message: 22 > Date: Tue, 20 Jan 2009 11:57:49 +0100 > From: Klaus Darilion <klaus.mailinglists at pernau.at> > Subject: [asterisk-users] SIP DTMF problem with SNOM > To: Asterisk Users Mailing List - Non-Commercial Discussion > <asterisk-users at lists.digium.com> > Message-ID: <4975AE2D.9050407 at pernau.at> > Content-Type: text/plain; charset=ISO-8859-15; > format=flowed > > Hi! > > I have two identical SIP accounts on Asterisk 1.4.22. One > account is > registered with eyebeam, the other one is registered with a > SNOM phone. > > When using the eyebeam client DMTF detection works fine, > when using the > SNOM phone many digits are missing in the DTMF detection. > > I analyzed with wireshark and both phones uses RFC 2833 and > the trace > looks pretty the same. Also the rtp debug log looks fine > (see below). > > What could be the reason? > > thanks > klaus > > trace: I have entered 1234#, but voicemail received as > secret just 123. > > > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042765, ts > 4066332168, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042766, ts > 4066332328, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042770, ts > 4066332968, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042771, ts > 4066333128, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042774, ts > 4066333608, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042775, ts > 4066333768, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042777, ts > 4066334088, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042778, ts > 4066334248, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042780, ts > 4066334648, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042780, ts > 4066334648, len 000004, mark 0, event 00000001, end 0, > duration 00320) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042781, ts > 4066334648, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042781, ts > 4066334648, len 000004, mark 0, event 00000001, end 0, > duration 00480) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042782, ts > 4066334648, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042782, ts > 4066334648, len 000004, mark 0, event 00000001, end 0, > duration 00640) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042785, ts > 4066334648, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042785, ts > 4066334648, len 000004, mark 0, event 00000001, end 0, > duration 01120) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042786, ts > 4066334648, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042786, ts > 4066334648, len 000004, mark 0, event 00000001, end 0, > duration 01280) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042788, ts > 4066334648, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042788, ts > 4066334648, len 000004, mark 0, event 00000001, end 0, > duration 01600) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042789, ts > 4066334648, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042789, ts > 4066334648, len 000004, mark 0, event 00000001, end 1, > duration 01760) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042789, ts > 4066334648, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042789, ts > 4066334648, len 000004, mark 0, event 00000001, end 1, > duration 01760) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042789, ts > 4066334648, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042789, ts > 4066334648, len 000004, mark 0, event 00000001, end 1, > duration 01760) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042790, ts > 4066336648, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042791, ts > 4066336808, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042792, ts > 4066336968, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042793, ts > 4066337128, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042794, ts > 4066337288, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042795, ts > 4066337448, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042798, ts > 4066337928, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042801, ts > 4066338408, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042802, ts > 4066338568, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042805, ts > 4066339048, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042806, ts > 4066339208, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042809, ts > 4066339688, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042812, ts > 4066340168, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042812, ts > 4066340168, len 000004, mark 0, event 00000002, end 0, > duration 00480) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042813, ts > 4066340168, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042813, ts > 4066340168, len 000004, mark 0, event 00000002, end 0, > duration 00640) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042815, ts > 4066340168, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042815, ts > 4066340168, len 000004, mark 0, event 00000002, end 0, > duration 00960) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042816, ts > 4066340168, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042816, ts > 4066340168, len 000004, mark 0, event 00000002, end 0, > duration 01120) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042817, ts > 4066340168, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042817, ts > 4066340168, len 000004, mark 0, event 00000002, end 0, > duration 01280) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042818, ts > 4066340168, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042818, ts > 4066340168, len 000004, mark 0, event 00000002, end 0, > duration 01440) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042822, ts > 4066340168, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042822, ts > 4066340168, len 000004, mark 0, event 00000002, end 1, > duration 02080) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042822, ts > 4066340168, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042822, ts > 4066340168, len 000004, mark 0, event 00000002, end 1, > duration 02080) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042822, ts > 4066340168, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042822, ts > 4066340168, len 000004, mark 0, event 00000002, end 1, > duration 02080) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042827, ts > 4066343048, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042830, ts > 4066343528, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042831, ts > 4066343688, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042832, ts > 4066343848, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042833, ts > 4066344008, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042835, ts > 4066344328, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042837, ts > 4066344648, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042840, ts > 4066345128, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042841, ts > 4066345688, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042841, ts > 4066345688, len 000004, mark 1, event 00000003, end 0, > duration 00160) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042842, ts > 4066345688, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042842, ts > 4066345688, len 000004, mark 0, event 00000003, end 0, > duration 00320) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042843, ts > 4066345688, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042843, ts > 4066345688, len 000004, mark 0, event 00000003, end 0, > duration 00480) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042848, ts > 4066345688, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042848, ts > 4066345688, len 000004, mark 0, event 00000003, end 0, > duration 01280) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042849, ts > 4066345688, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042849, ts > 4066345688, len 000004, mark 0, event 00000003, end 0, > duration 01440) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042850, ts > 4066345688, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042850, ts > 4066345688, len 000004, mark 0, event 00000003, end 0, > duration 01600) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042851, ts > 4066345688, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042851, ts > 4066345688, len 000004, mark 0, event 00000003, end 1, > duration 01760) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042851, ts > 4066345688, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042851, ts > 4066345688, len 000004, mark 0, event 00000003, end 1, > duration 01760) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042851, ts > 4066345688, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042851, ts > 4066345688, len 000004, mark 0, event 00000003, end 1, > duration 01760) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042852, ts > 4066347688, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042853, ts > 4066347848, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042856, ts > 4066348328, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042857, ts > 4066348488, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042858, ts > 4066348648, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042859, ts > 4066348808, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042861, ts > 4066349128, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042864, ts > 4066349608, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042865, ts > 4066349768, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042867, ts > 4066350088, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042868, ts > 4066350248, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042869, ts > 4066350408, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042870, ts > 4066350568, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042871, ts > 4066350728, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042872, ts > 4066351208, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042872, ts > 4066351208, len 000004, mark 1, event 00000004, end 0, > duration 00160) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042873, ts > 4066351208, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042873, ts > 4066351208, len 000004, mark 0, event 00000004, end 0, > duration 00320) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042874, ts > 4066351208, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042874, ts > 4066351208, len 000004, mark 0, event 00000004, end 0, > duration 00480) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042875, ts > 4066351208, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042875, ts > 4066351208, len 000004, mark 0, event 00000004, end 0, > duration 00640) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042876, ts > 4066351208, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042876, ts > 4066351208, len 000004, mark 0, event 00000004, end 0, > duration 00800) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042880, ts > 4066351208, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042880, ts > 4066351208, len 000004, mark 0, event 00000004, end 0, > duration 01440) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042883, ts > 4066353208, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042884, ts > 4066353368, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042885, ts > 4066353528, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042890, ts > 4066354328, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042891, ts > 4066354488, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042892, ts > 4066354648, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042896, ts > 4066355288, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042897, ts > 4066355448, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042898, ts > 4066355608, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042899, ts > 4066355768, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042900, ts > 4066355928, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042901, ts > 4066356088, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042902, ts > 4066356248, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 00, seq > 042904, ts > 4066356568, len 000160) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042905, ts > 4066356728, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042905, ts > 4066356728, len 000004, mark 1, event 0000000b, end 0, > duration 00160) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042908, ts > 4066356728, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042908, ts > 4066356728, len 000004, mark 0, event 0000000b, end 0, > duration 00640) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042911, ts > 4066356728, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042911, ts > 4066356728, len 000004, mark 0, event 0000000b, end 0, > duration 01120) > Got RTP packet from 83.136.33.3:64118 (type 101, seq > 042913, ts > 4066356728, len 000004) > Got RTP RFC2833 from 83.136.33.3:64118 (type 101, seq > 042913, ts > 4066356728, len 000004, mark 0, event 0000000b, end 1, > duration 01440) > -- Incorrect password '123' for user > '+4372012345' (context = vm) > > > > ------------------------------ > > _______________________________________________ > --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 > > End of asterisk-users Digest, Vol 54, Issue 54 > **********************************************
bilal ghayyad
2009-Jan-20 13:23 UTC
[asterisk-users] the FXS ports of Digium and damaging if connected to Tel Line
Dear Gordon; I did not understand the idea of the following: "If you're carefull, you can clip the tang of the RJ11 plug on the end of the BT adapter so that it needs a small screwdriver to remove it from the socket on the board..." Do u have any link? What do u mean by "clibing the tang of the RJ11 plug on the end of the BT adaptor? Regards Bilal ------------------------> >> What is the solution for this disaster? > > > > I live in UK, where we don't use RJ11 for > telephones and so need to > > use adapters, which I just leave hanging out of the > FXO ports. With > > the adapters in place, it's difficult to plug the > phones into the > > wrong ports. I've also stuck a large label on the > computer cabinet to > > show which ports are for what. For info, I have a > TDM400P. > > If you're carefull, you can clip the tang of the RJ11 > plug on the end of > the BT adapter so that it needs a small screwdriver to > remove it from the > socket on the board... > > I found this out after swapping a Panasonic unit out for an > Asterisk box > of my own and having a devil of a time removing the > connectors going into > the Panasonic box - I'm told they're supplied like > that and they were > punched-down directly into the DP! (not a BT > 'master' socket in sight!) > > > I suspect that the label idea might help but the other > would depend on > > whether your country uses RJ11 for standard phone > connections. > > Never underestimate the stupity of sheeple... > > Gordon > >
Phil Reynolds
2009-Jan-21 10:34 UTC
[asterisk-users] the FXS ports of Digium and damaging if connected to Tel Line
Quoting "bilal ghayyad" <bilmar_gh at yahoo.com>:> Hi All; > > I am facing a problem that always the users confused and connect the > telephone line coming from the telephone service provider to the FXS > port and cause it to be damaged, specially if the card was 2 fxs and > 2 fxo, so they make mistake and connect the line to fxs while it > should be connected to fxo. > > What is the solution for this disaster?What sort of environment is this in? If it's servers you have built and supplied to others, I can understand why it is such an issue. I have a 3 FXS, 1 FXO card. On the one occasion I had to move the box, I left the line cord in the FXO. Because the other end is not RJ11 here, that saved me making a mistake. I hadn't actually thought of the adaptor in FXS port idea, but that would work too. When I wired the internal lines at my house, I terminated each with RJ11 to fit the card. I could have used BT plugs and adaptors, perhaps. If you are in a country where RJ11 connectors are used on everything, it is much harder to resolve. -- Phil Reynolds mail: phil-asterisk at tinsleyviaduct.com Web: http://www.tinsleyviaduct.com/phil/ Waltham 66, Emley Moor 69, Droitwich 79, Windows 95 ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program.