MarkLeddy Posted July 16, 2007 Posted July 16, 2007 I have a Texecom speach/text dialer that has been just fine for several years. For some unknown reason it now will not send text alerts. It tries to send them but fails. The speach side seems fine. My opening question is has there been any change in the message centre numbers? It seems to dial out but not be able to make a remote connection. The only other thing I have changed is that the line it is on has been broadband enabled - everything including the dialer is filtered. Any help much appreciated.
Guest Dave the alarm man Posted July 16, 2007 Posted July 16, 2007 tried it with the router turned off?
MarkLeddy Posted July 16, 2007 Author Posted July 16, 2007 No - but will try and will report back later.
MarkLeddy Posted July 18, 2007 Author Posted July 18, 2007 No - but will try and will report back later. OK, tried it without broad band on and also with filter removed. Still no joy. Dials out, starts the handshake with the remote computer but then just get a long period of "static" type noise like when a remote modem is busy, then the connection times out and fails. Any ideas what next?
breff Posted July 18, 2007 Posted July 18, 2007 Try setting it to pulse dial, might not work but worth a try. My com2400 on an ntl line just wont work unless I set it to pulse dial, wierd but it works. The opinions I express are mine and are usually correct! (Except when I'm wrong)(which I'm not)
MarkLeddy Posted July 19, 2007 Author Posted July 19, 2007 Thanks for the advice, tried it but it still does exactly the same thing. Anybody any other ideas?
Guest anguscanplay Posted July 19, 2007 Posted July 19, 2007 have you still got cables connected to pin 3 in the BT master box? also try connecting it to the Broadband side rather than the voice side ( if that makes sense ) Angus
MarkLeddy Posted July 20, 2007 Author Posted July 20, 2007 Thanks for posting some more ideas - much appreciated. Here's the next installment... I haven't anything to try connecting to the broadband "side" - I'll have to patch a socket convertor together to try that if this information doesn't lead to anything. Direct connection without a filter and with no router or anything else attached doesn't solve the problem. Regarding pin 3; I went on an interesting investgiation into the telephone sockets in this house (built around 1986). The master socket is an old one (i.e. not an NTE 5). It has a 6 core cable going into it (all 6 cores wirded) and the same six core cables then go on to the other extension sockets (all cores wired at all sockets). I'm assuming only 2 of the incoming 6 cores coming into the master socket are actually wired to anything at the other end. Are you suggesting that I should remove the core to pin 3 for the extension socket that the dialer uses?
Guest anguscanplay Posted July 20, 2007 Posted July 20, 2007 Thanks for posting some more ideas - much appreciated. Here's the next installment...I haven't anything to try connecting to the broadband "side" - I'll have to patch a socket convertor together to try that if this information doesn't lead to anything. Direct connection without a filter and with no router or anything else attached doesn't solve the problem. Regarding pin 3; I went on an interesting investgiation into the telephone sockets in this house (built around 1986). The master socket is an old one (i.e. not an NTE 5). It has a 6 core cable going into it (all 6 cores wirded) and the same six core cables then go on to the other extension sockets (all cores wired at all sockets). I'm assuming only 2 of the incoming 6 cores coming into the master socket are actually wired to anything at the other end. Are you suggesting that I should remove the core to pin 3 for the extension socket that the dialer uses? firat thing to do would be to get BT to come and fit you a master NTE 5 remove everything except pins 2 and 5 - the rest of them are things like the bell ring and suppresion but all that stuff is handled by the broadband filters - quick pointer , broadband is a balanced signal so you have literaly 2 wires from the exchange to your house and obviously they have approx the same length , leave pin 3 connected and if youve got 100m of extension then one leg of the curcuit is now 100m longer than the other - doesnt sound much but if your a way away from the exchange it can make a real difference
MarkLeddy Posted December 13, 2007 Author Posted December 13, 2007 firat thing to do would be to get BT to come and fit you a master NTE 5 remove everything except pins 2 and 5 - the rest of them are things like the bell ring and suppresion but all that stuff is handled by the broadband filters - quick pointer , broadband is a balanced signal so you have literaly 2 wires from the exchange to your house and obviously they have approx the same length , leave pin 3 connected and if youve got 100m of extension then one leg of the curcuit is now 100m longer than the other - doesnt sound much but if your a way away from the exchange it can make a real difference OK to update you on this one. Finally got a master NTE5 fitted, now have every thing divided at one top quality filter. The TSD is on the voice/phone side of the filter, router on the data side. Despite all this still no joy. I spoke to Texecom support and their theory is that the line is not "Tap enabled" Not sure about the spelling there. Anyway, seems this enabling would allow the TSD to transmit data to the message centre. The explanation seems to make sense as it is during teh handshaking bit that no communication occurs. That was all fine until I spent a frustrating 40 mins on the phone to BT who seemed to have little clue what I was on about. After threatening to disable my broadband connection they went back to putting me on hold again then cut me off. Before I called them back I was hoping somebody on the forum might back up the comments from texecom and clarify exactly what I need to ask BT for. They ain't that helpful. Wonder if it is because I don't use them as my BB supplier? Anyway any help gratefully received.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.