Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
Gordon Henderson wrote: On Sat, 23 May 2009, Dunc wrote: Hi Gordon, thanks for your reply, I was hoping to find someone who was involved in the thread before. See inline comments Hi everyone, I just found this thread, which is amazing as I'm on my first go with asterisk and so far I've been pulling my hair out for the last week :-) I have 2 questions which were raised while this fault was being debugged. 1) Gordon says:- Is this a place where you get a polarity reversal event on call startup? In the UK we do. (Well on BT lines - I've a funny feeling some Telewest/NTL lines use Bell signaling). On an incoming call we get: Polarity reversal. FSK Caller ID burst Ringing Well I've got an NTL phone line, can anyone tell me what to use for that? Throw it away and get a BT one ;-) I'd suggest running with verbose =3 and seeing what it says. However I have 2 clients with Teleworst lines and I've never been able to make caller ID work on them, even though teleworst insist they are providing caller ID.. Well that's a shame because I specifically went for NTL so that I haven't got BT to contend with when my Internet is broken. The Ethernet presentation instead of a pair of BT wires is very appealing. I'll be happy to get it up and running for now and worry about caller ID later though. So we'll press on :-) 2) Do I still need the same 2pin cable? Because I've been to Maplins too and bought one that I thought was right, but this one is a 4pin too. Can anyone tell me which pins on their 2pin cable are connected at each end? I'll bodge my cable until it works and then get a proper one once I'm sure. I think part of this same thread had something about modem vs. ordinary cables - however I put in a 4-pin modem cable to see what happenes and it continued to work as before, so I'm personally not convinced about that one... ie. I've not had a cable that didn't work. Gordon Right so I'm probably barking up the wrong red herring with the cable problem. I did wonder when the TDM card has 2 pins on the RJ11 socket what possible difference a 4 pin cable could make, but I've definitely had madness with phones before where wiring up seemingly unused wires made the extensions ring, so I'm willing to accept phone wiring is mad. In that case, I'll reply to an earlier post in the thread from someone requesting my config / symptoms, and we'll take it from there. Thanks for your help. Cheers, Dunc ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
Hi Tiago, I have an OpenVox A400P11, it shows up like this... eddie ~ # lsdahdi ### Span 1: WCTDM/4 Wildcard TDM400P REV E/F Board 5 (MASTER) 1 FXSFXSKS (EC: MG2) RED 2 FXOFXOLS (EC: MG2) Use of uninitialized value in string eq at /usr/lib64/perl5/site_perl/5.8.8/Dahdi/Chans.pm line 221. 3 unknown Use of uninitialized value in string eq at /usr/lib64/perl5/site_perl/5.8.8/Dahdi/Chans.pm line 221. 4 unknown eddie ~ # I'm pretty sure that the RED alarm is a bad thing. While googling about this error from the asterisk console *CLI [May 23 18:14:02] NOTICE[4469]: chan_dahdi.c:8164 handle_init_event: Alarm cleared on channel 1 [May 23 18:14:03] WARNING[4469]: chan_dahdi.c:4664 handle_alarms: Detected alarm on channel 1: Red Alarm I discovered this thread on the mailing list, and so signed up and mailed in with the same subject. It didn't link them together though it seems, so here's a URL http://www.mail-archive.com/asterisk-users@lists.digium.com/msg223429.html If you read this specific post, and the last few before http://www.mail-archive.com/asterisk-users@lists.digium.com/msg223523.html How is your configuration? Please post here. At first I thought you were using a A1200P, this card (which is very good) gave some headache some weeks ago, because it wasn't working properly with dahdi. I didn't have a chance to test it again. It's because for this card you need a module from Openvox. The A400P card that they made is a clone of the TDM and should work fine with DAHDI. For this card you shouldn't need any module from Openvox. Hi, My config is mostly out-of-the-box apart from where I've needed to tweak things. This is my first attempt with Asterisk though, but I've been playing on and off for a couple of weeks now. I'm pretty sure that I've got DAHDI set up correctly as you can see in lsdahdi above. Channel 1 connects to my PSTN and Channel 2 has an analogue phone connected. I can definitely make calls with the analogue phone connected straight into the PSTN to answer your question below. I'd still like to know what the RED alarm means if anyone can tell me though... I have also definitely got my wctdm loaded in UK mode eddie etc # dmesg | grep -i fx Module 0: Installed -- AUTO FXO (UK mode) Module 1: Installed -- AUTO FXS/DPO Here is my dahdi/system.conf # Span 1: WCTDM/4 Wildcard TDM400P REV E/F Board 5 (MASTER) fxsks=1 echocanceller=mg2,1 fxols=2 echocanceller=mg2,2 # channel 3, WCTDM/4/2, no module. # channel 4, WCTDM/4/3, no module. # Global data loadzone= uk defaultzone = uk Ok, on to asterisk. The tweaks I have made to the defaults are:- chan_dahdi.conf --- cidsignalling=v23 sendcalleridafter = 2 And I have #included an extra file like this. #include /etc/asterisk/dahdi-channels.conf which contains eddie asterisk # cat /etc/asterisk/dahdi-channels.conf ; Autogenerated by /usr/sbin/dahdi_genconf on Sat May 23 14:19:49 2009 -- do not hand edit ; Dahdi Channels Configurations (chan_dahdi.conf) ; ; This is not intended to be a complete chan_dahdi.conf. Rather, it is intended ; to be #include-d by /etc/asterisk/chan_dahdi.conf that will include the global settings ; ; Span 1: WCTDM/4 Wildcard TDM400P REV E/F Board 5 (MASTER) ;;; line=1 WCTDM/4/0 signalling=fxs_ks callerid=asreceived group=0 context=from-pstn channel = 1 callerid= group= context=default ;;; line=2 WCTDM/4/1 signalling=fxo_ls callerid=Channel 2 4002 mailbox=4002 group=5 context=from-internal channel = 2 callerid= mailbox= group= context=default sip.conf I have #included my own file in sip.conf too, it looks like this eddie asterisk # cat /etc/asterisk/sip_dunc.conf [deskphone] host=dynamic type=friend context=from-sip callerid=Desk Phone 202 mailbox=...@default secret=deskphonesecret extensions.conf --- And the same for extensions.conf.. eddie asterisk # cat /etc/asterisk/extensions_dunc.conf [from-sip] exten = 07875123456,1,Dial(DAHDI/1/07875123456,20) [from-internal] exten = 07875123456,1,Dial(DAHDI/1/07875123456,20) [from-pstn] exten = s,1,Dial(DAHDI/2/,20) N.B. I've changed my mobile number above but I can assure you I've checked that they all match :-) OK. Time to make some calls. If I try to dial out from either my IP phone or the analogue one, this happens (running with asterisk -c) *CLI -- Starting simple switch on 'DAHDI/2-1' -- Executing [07875123...@from-internal:1] Dial(DAHDI/2-1, DAHDI/1/07875123456,20) in new stack [May 24 12:06:57] WARNING[3968]: app_dial.c:1518 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 0 - Unknown) == Everyone is busy/congested at this time (1:0/0/1) -- Auto fallthrough, channel 'DAHDI/2-1' status is 'CHANUNAVAIL' -- Hungup 'DAHDI/2-1' *CLI and *CLI == Using SIP RTP CoS mark 5 -- Executing [07875123...@from-sip:1]
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
On Sun, 24 May 2009, Dunc wrote: However I have 2 clients with Teleworst lines and I've never been able to make caller ID work on them, even though teleworst insist they are providing caller ID.. Well that's a shame because I specifically went for NTL so that I haven't got BT to contend with when my Internet is broken. The Ethernet presentation instead of a pair of BT wires is very appealing. This is a thread for elsewhere, but personally, I'd rather have BT carry the copper into my premises, then stick a good router on the end, then work out which of the 130+ ISPs I have a choice to use to give me that Ethernet socket than be at the mercy of one single provider with known bad customer service and wooly traffic limiting. Go to the ThinkBroadband.com site and read the forums... My view: BT - Good for copper and keeping the line going, good at the wholesale provision, bad for Internet, but that's OK - I have a choice over 130 ISPs to use for Internet - don't fall into the trap of thinking you only have BT - there are well over 100 ISPs who use the BT wholesale network and they're (nearly) all better than BT themselves! (And that's without even thinking of the LLU ISPs...) I'll be happy to get it up and running for now and worry about caller ID later though. So we'll press on :-) Right so I'm probably barking up the wrong red herring with the cable problem. I did wonder when the TDM card has 2 pins on the RJ11 socket what possible difference a 4 pin cable could make, but I've definitely had madness with phones before where wiring up seemingly unused wires made the extensions ring, so I'm willing to accept phone wiring is mad. The BT (or standard UK) wiring is somewhat different from some other countries. The copper comes in on 2 pairs, (pins 2 and 5 in a standard 6-way wall socket) but a BT Master socket will create a 3rd wire (on pin 3) - the ringing wire. This sometimes confuses things. I think TW/NTL/VM do basically the same thing. Personally, I've never had problems going from a master socket into a TDM400 type card myself. My own setup takes pins 2 and 5 from my BT master socket into an ADSL splitter socket and from there into my router and PBX. However, most phones will still ring when connected up via the 2 wires. If buying the card from (eg) VoipON, the best way would be to buy the cable at the same time. Alternatively, see if you've an old analogue phone with a standard BT plug at the far-end with the phone end being on an rj11 plug and use that. Gordon ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
On Sun, 24 May 2009, Dunc wrote: extensions.conf --- And the same for extensions.conf.. eddie asterisk # cat /etc/asterisk/extensions_dunc.conf [from-sip] exten = 07875123456,1,Dial(DAHDI/1/07875123456,20) [from-internal] exten = 07875123456,1,Dial(DAHDI/1/07875123456,20) [from-pstn] exten = s,1,Dial(DAHDI/2/,20) Start simpler: [from-pstn] exten = s,1,Answer() exten = s,n,Playback(demo-congrats) exten = s,n,Hangup() Same for the analogue phone. Gordon ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
On Sun, May 24, 2009 at 12:36:26PM +0100, Dunc wrote: Hi Tiago, I have an OpenVox A400P11, it shows up like this... eddie ~ # lsdahdi ### Span 1: WCTDM/4 Wildcard TDM400P REV E/F Board 5 (MASTER) 1 FXSFXSKS (EC: MG2) RED 2 FXOFXOLS (EC: MG2) Something is wrong here. FXS channels should have FXO signalling and vice versa. The cause for that is probably a bug in dahdi_genconf (or rather: in Dahdi::Chan) in 2.1.0 (fixed shortly after the release) that misdetected the channels and thus generated a wrong dahdi_channels.conf and still misleads you here. If you'll switch to 2.2 the problem will go away :-( (Evidently system.conf has the right signalling, otherwise it wouldn't have applied). Use of uninitialized value in string eq at /usr/lib64/perl5/site_perl/5.8.8/Dahdi/Chans.pm line 221. 3 unknown Use of uninitialized value in string eq at /usr/lib64/perl5/site_perl/5.8.8/Dahdi/Chans.pm line 221. 4 unknown eddie ~ # I'm pretty sure that the RED alarm is a bad thing. While googling about this error from the asterisk console *CLI [May 23 18:14:02] NOTICE[4469]: chan_dahdi.c:8164 handle_init_event: Alarm cleared on channel 1 [May 23 18:14:03] WARNING[4469]: chan_dahdi.c:4664 handle_alarms: Detected alarm on channel 1: Red Alarm I discovered this thread on the mailing list, and so signed up and mailed in with the same subject. It didn't link them together though it seems, so here's a URL http://www.mail-archive.com/asterisk-users@lists.digium.com/msg223429.html If you read this specific post, and the last few before http://www.mail-archive.com/asterisk-users@lists.digium.com/msg223523.html How is your configuration? Please post here. At first I thought you were using a A1200P, this card (which is very good) gave some headache some weeks ago, because it wasn't working properly with dahdi. I didn't have a chance to test it again. It's because for this card you need a module from Openvox. The A400P card that they made is a clone of the TDM and should work fine with DAHDI. For this card you shouldn't need any module from Openvox. Hi, My config is mostly out-of-the-box apart from where I've needed to tweak things. This is my first attempt with Asterisk though, but I've been playing on and off for a couple of weeks now. I'm pretty sure that I've got DAHDI set up correctly as you can see in lsdahdi above. Channel 1 connects to my PSTN and Channel 2 has an analogue phone connected. I can definitely make calls with the analogue phone connected straight into the PSTN to answer your question below. I'd still like to know what the RED alarm means if anyone can tell me though... For an FXO channel: not connected. Or rather: not detecting battery current from the remote FXS. I have also definitely got my wctdm loaded in UK mode eddie etc # dmesg | grep -i fx Module 0: Installed -- AUTO FXO (UK mode) Module 1: Installed -- AUTO FXS/DPO Here is my dahdi/system.conf # Span 1: WCTDM/4 Wildcard TDM400P REV E/F Board 5 (MASTER) fxsks=1 echocanceller=mg2,1 fxols=2 echocanceller=mg2,2 # channel 3, WCTDM/4/2, no module. # channel 4, WCTDM/4/3, no module. # Global data loadzone = uk defaultzone = uk Ok, on to asterisk. The tweaks I have made to the defaults are:- chan_dahdi.conf --- cidsignalling=v23 sendcalleridafter = 2 And I have #included an extra file like this. #include /etc/asterisk/dahdi-channels.conf which contains eddie asterisk # cat /etc/asterisk/dahdi-channels.conf ; Autogenerated by /usr/sbin/dahdi_genconf on Sat May 23 14:19:49 2009 -- do not hand edit ; Dahdi Channels Configurations (chan_dahdi.conf) ; ; This is not intended to be a complete chan_dahdi.conf. Rather, it is intended ; to be #include-d by /etc/asterisk/chan_dahdi.conf that will include the global settings ; ; Span 1: WCTDM/4 Wildcard TDM400P REV E/F Board 5 (MASTER) ;;; line=1 WCTDM/4/0 signalling=fxs_ks signalling=fxo_ks callerid=asreceived group=0 context=from-pstn channel = 1 callerid= group= context=default ;;; line=2 WCTDM/4/1 signalling=fxo_ls signalling=fxs_ls callerid=Channel 2 4002 mailbox=4002 group=5 context=from-internal channel = 2 callerid= mailbox= group= context=default After those modifications, re-run dahdi-cfg and in Asterisk: asterisk -rx 'dahdi restart' -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
Tzafrir Cohen wrote: On Sun, May 24, 2009 at 12:36:26PM +0100, Dunc wrote: Hi Tiago, I have an OpenVox A400P11, it shows up like this... eddie ~ # lsdahdi ### Span 1: WCTDM/4 Wildcard TDM400P REV E/F Board 5 (MASTER) 1 FXSFXSKS (EC: MG2) RED 2 FXOFXOLS (EC: MG2) Something is wrong here. FXS channels should have FXO signalling and vice versa. The cause for that is probably a bug in dahdi_genconf (or rather: in Dahdi::Chan) in 2.1.0 (fixed shortly after the release) that misdetected the channels and thus generated a wrong dahdi_channels.conf and still misleads you here. If you'll switch to 2.2 the problem will go away :-( (Evidently system.conf has the right signalling, otherwise it wouldn't have applied). Hmm, my channel 1 is the FXO (i.e. connects to the wall socket) and channel 2 is FXS (that's where I plugged my phone line in) Use of uninitialized value in string eq at /usr/lib64/perl5/site_perl/5.8.8/Dahdi/Chans.pm line 221. 3 unknown Use of uninitialized value in string eq at /usr/lib64/perl5/site_perl/5.8.8/Dahdi/Chans.pm line 221. 4 unknown eddie ~ # I'm pretty sure that the RED alarm is a bad thing. While googling about this error from the asterisk console *CLI [May 23 18:14:02] NOTICE[4469]: chan_dahdi.c:8164 handle_init_event: Alarm cleared on channel 1 [May 23 18:14:03] WARNING[4469]: chan_dahdi.c:4664 handle_alarms: Detected alarm on channel 1: Red Alarm I discovered this thread on the mailing list, and so signed up and mailed in with the same subject. It didn't link them together though it seems, so here's a URL http://www.mail-archive.com/asterisk-users@lists.digium.com/msg223429.html If you read this specific post, and the last few before http://www.mail-archive.com/asterisk-users@lists.digium.com/msg223523.html How is your configuration? Please post here. At first I thought you were using a A1200P, this card (which is very good) gave some headache some weeks ago, because it wasn't working properly with dahdi. I didn't have a chance to test it again. It's because for this card you need a module from Openvox. The A400P card that they made is a clone of the TDM and should work fine with DAHDI. For this card you shouldn't need any module from Openvox. Hi, My config is mostly out-of-the-box apart from where I've needed to tweak things. This is my first attempt with Asterisk though, but I've been playing on and off for a couple of weeks now. I'm pretty sure that I've got DAHDI set up correctly as you can see in lsdahdi above. Channel 1 connects to my PSTN and Channel 2 has an analogue phone connected. I can definitely make calls with the analogue phone connected straight into the PSTN to answer your question below. I'd still like to know what the RED alarm means if anyone can tell me though... For an FXO channel: not connected. Or rather: not detecting battery current from the remote FXS. I have also definitely got my wctdm loaded in UK mode eddie etc # dmesg | grep -i fx Module 0: Installed -- AUTO FXO (UK mode) Module 1: Installed -- AUTO FXS/DPO Here is my dahdi/system.conf # Span 1: WCTDM/4 Wildcard TDM400P REV E/F Board 5 (MASTER) fxsks=1 echocanceller=mg2,1 fxols=2 echocanceller=mg2,2 # channel 3, WCTDM/4/2, no module. # channel 4, WCTDM/4/3, no module. # Global data loadzone = uk defaultzone = uk Ok, on to asterisk. The tweaks I have made to the defaults are:- chan_dahdi.conf --- cidsignalling=v23 sendcalleridafter = 2 And I have #included an extra file like this. #include /etc/asterisk/dahdi-channels.conf which contains eddie asterisk # cat /etc/asterisk/dahdi-channels.conf ; Autogenerated by /usr/sbin/dahdi_genconf on Sat May 23 14:19:49 2009 -- do not hand edit ; Dahdi Channels Configurations (chan_dahdi.conf) ; ; This is not intended to be a complete chan_dahdi.conf. Rather, it is intended ; to be #include-d by /etc/asterisk/chan_dahdi.conf that will include the global settings ; ; Span 1: WCTDM/4 Wildcard TDM400P REV E/F Board 5 (MASTER) ;;; line=1 WCTDM/4/0 signalling=fxs_ks signalling=fxo_ks callerid=asreceived group=0 context=from-pstn channel = 1 callerid= group= context=default ;;; line=2 WCTDM/4/1 signalling=fxo_ls signalling=fxs_ls callerid=Channel 2 4002 mailbox=4002 group=5 context=from-internal channel = 2 callerid= mailbox= group= context=default After those modifications, re-run dahdi-cfg and in Asterisk: asterisk -rx 'dahdi restart' Are you absolutely sure this is the right way round. I thought that an FXO module connected to the wall, and used FXS signalling. And vice versa. My channel 1 is the one connected to PSTN so surely it should have FXS signalling? Please excuse my ignorance, I don't mean to be telling you what to do, it's just that this is different to what I've read everywhere else.
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
On Sun, May 24, 2009 at 03:00:21PM +0100, Dunc wrote: Tzafrir Cohen wrote: On Sun, May 24, 2009 at 12:36:26PM +0100, Dunc wrote: ; Span 1: WCTDM/4 Wildcard TDM400P REV E/F Board 5 (MASTER) ;;; line=1 WCTDM/4/0 signalling=fxs_ks signalling=fxo_ks callerid=asreceived group=0 context=from-pstn channel = 1 callerid= group= context=default ;;; line=2 WCTDM/4/1 signalling=fxo_ls signalling=fxs_ls callerid=Channel 2 4002 mailbox=4002 group=5 context=from-internal channel = 2 callerid= mailbox= group= context=default After those modifications, re-run dahdi-cfg and in Asterisk: asterisk -rx 'dahdi restart' Are you absolutely sure this is the right way round. I thought that an FXO module connected to the wall, and used FXS signalling. And vice versa. My channel 1 is the one connected to PSTN so surely it should have FXS signalling? You're correct. I managed to confuse myself. Ignore this advice. But again: do you see the channels as '(In Use)' on lsdahdi / 'cat /proc/dahdi/*' ? -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
Gordon Henderson wrote: On Sun, 24 May 2009, Dunc wrote: extensions.conf --- And the same for extensions.conf.. eddie asterisk # cat /etc/asterisk/extensions_dunc.conf [from-sip] exten = 07875123456,1,Dial(DAHDI/1/07875123456,20) [from-internal] exten = 07875123456,1,Dial(DAHDI/1/07875123456,20) [from-pstn] exten = s,1,Dial(DAHDI/2/,20) Start simpler: [from-pstn] exten = s,1,Answer() exten = s,n,Playback(demo-congrats) exten = s,n,Hangup() Same for the analogue phone. Gordon Hi again Gordon, As suggested. eddie ~ # cat !$ cat /etc/asterisk/extensions_dunc.conf [from-internal] exten = 123456,1,Answer() exten = 123456,2,Playback(demo-congrats) exten = 123456,3,Hangup() [from-pstn] exten = s,1,Answer() exten = s,2,Playback(demo-congrats) exten = s,3,Hangup() If I dial 123456 on my analogue phone, then it's all cool. *CLI -- Starting simple switch on 'DAHDI/2-1' -- Executing [123...@from-internal:1] Answer(DAHDI/2-1, ) in new stack -- Executing [123...@from-internal:2] Playback(DAHDI/2-1, demo-congrats) in new stack -- DAHDI/2-1 Playing 'demo-congrats.gsm' (language 'en') -- Executing [123...@from-internal:3] Hangup(DAHDI/2-1, ) in new stack == Spawn extension (from-internal, 123456, 3) exited non-zero on 'DAHDI/2-1' -- Hungup 'DAHDI/2-1' *CLI (I'm not actually sure that it should exit non-zero or not, but I definitely got the recorded message and then it hung up) So that's fine. There's just incoming to fix now. When I dial in from external:- *CLI [May 24 15:16:56] NOTICE[3834]: chan_dahdi.c:8164 handle_init_event: Alarm cleared on channel 1 -- Starting simple switch on 'DAHDI/1-1' [May 24 15:16:56] NOTICE[3889]: chan_dahdi.c:7505 ss_thread: Got event 18 (Ring Begin)... [May 24 15:16:56] NOTICE[3889]: chan_dahdi.c:7505 ss_thread: Got event 2 (Ring/Answered)... [May 24 15:16:57] NOTICE[3889]: chan_dahdi.c:7505 ss_thread: Got event 4 (Alarm)... -- Executing [...@from-pstn:1] Answer(DAHDI/1-1, ) in new stack -- Executing [...@from-pstn:2] Playback(DAHDI/1-1, demo-congrats) in new stack -- DAHDI/1-1 Playing 'demo-congrats.gsm' (language 'en') -- Executing [...@from-pstn:3] Hangup(DAHDI/1-1, ) in new stack == Spawn extension (from-pstn, s, 3) exited non-zero on 'DAHDI/1-1' -- Hungup 'DAHDI/1-1' *CLI Looks good, but my incoming call from mobile doesn't actually stop ringing, I still end up at Virgin's voicemail. I notice that the first line is an alarm clear event. So it looks like my RED alarm is on right up until there's an incoming call. Other people on this thread have said that RED means can't detect a voltage from the line. So that's sort of making sense I think, as there'll definitely be a voltage I've just tried your suggestion from your other mail, where you were on about using the cable from a phone. So I pinched the one from my analogue phone (it's 2 wires.) The alarm cleared as soon as plugged it in, and now everything is working :-) So it WAS the cable all along! Who'd have thought. I've just tried using the cable I was using between the card and the wall on my phone, and it doesn't work. I can't believe I didn't think to try swapping them before. Now I need to hunt down another one of those cables then. Thanks so much to everyone who has helped me with this, it's much appreciated. Now I can get on with playing with asterisk. Cheers, Dunc ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
I can really only speak to questions 2; The other 2 pins in your cable are for your second phone line - if you have one that is. You should be able to plug in a 4 wire cable into any socket in the house and get access to Both lines. On Sat, 2009-05-23 at 16:02 +0100, Dunc wrote: Hi everyone, I just found this thread, which is amazing as I'm on my first go with asterisk and so far I've been pulling my hair out for the last week :-) I have 2 questions which were raised while this fault was being debugged. 1) Gordon says:- Is this a place where you get a polarity reversal event on call startup? In the UK we do. (Well on BT lines - I've a funny feeling some Telewest/NTL lines use Bell signaling). On an incoming call we get: Polarity reversal. FSK Caller ID burst Ringing Well I've got an NTL phone line, can anyone tell me what to use for that? 2) Do I still need the same 2pin cable? Because I've been to Maplins too and bought one that I thought was right, but this one is a 4pin too. Can anyone tell me which pins on their 2pin cable are connected at each end? I'll bodge my cable until it works and then get a proper one once I'm sure. Thanks in advance. Dunc ___ -- 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 -- Mark Phillips, G7LTT/NI2O Randolph, NJ ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
On Sun, 24 May 2009, Mark Phillips wrote: I can really only speak to questions 2; The other 2 pins in your cable are for your second phone line - if you have one that is. You should be able to plug in a 4 wire cable into any socket in the house and get access to Both lines. Mark Phillips, G7LTT/NI2O Randolph, NJ It's not done that way in the UK. BT (via OpenReach) will install a 2nd master socket for a 2nd phone line. Internally we normally run 3 wires. The 3rd wire carries the ringing current, isolatesd via a capacitor - also acts as a tinkle suppressor which stops bells tinkling on other phones when you use a phone with a loop-disconnect dialler. Here's an example: http://www.wppltd.demon.co.uk/WPP/Wiring/UK_telephone/uk_telephone.html In these enlightened days, it's normal to not use the 3rd wire internally on extension as it has been known to degrade an ADSL signal. Gordon ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
On 24/05/09 19:21, Gordon Henderson wrote: snip / Here's an example: http://www.wppltd.demon.co.uk/WPP/Wiring/UK_telephone/uk_telephone.html In these enlightened days, it's normal to not use the 3rd wire internally on extension as it has been known to degrade an ADSL signal. I think this last comment is very true indeed. I purchased something called an i-plate here in the UK. I'd seen many feedbacks about how it had improved broadband performance. It is a basically a small plugin device for the BT master socket that contains a decent filter and a terminator for the bell-wire. They cost around £10 and take only a minute to fit. Here's what happened when I plugged it in: http://www.theopensourcerer.com/2009/03/31/broadband-magic-with-the-i-plate/ And performance has even improved slightly more since that post too. Al ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
Hi everyone, I just found this thread, which is amazing as I'm on my first go with asterisk and so far I've been pulling my hair out for the last week :-) I have 2 questions which were raised while this fault was being debugged. 1) Gordon says:- Is this a place where you get a polarity reversal event on call startup? In the UK we do. (Well on BT lines - I've a funny feeling some Telewest/NTL lines use Bell signaling). On an incoming call we get: Polarity reversal. FSK Caller ID burst Ringing Well I've got an NTL phone line, can anyone tell me what to use for that? 2) Do I still need the same 2pin cable? Because I've been to Maplins too and bought one that I thought was right, but this one is a 4pin too. Can anyone tell me which pins on their 2pin cable are connected at each end? I'll bodge my cable until it works and then get a proper one once I'm sure. Thanks in advance. Dunc ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
On Sat, May 23, 2009 at 04:02:57PM +0100, Dunc wrote: In the UK we do. (Well on BT lines - I've a funny feeling some Telewest/NTL lines use Bell signaling). On an incoming call we get: Polarity reversal. FSK Caller ID burst Ringing https://issues.asterisk.org/view.php?id=9096 ? -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
Tzafrir Cohen wrote: On Sat, May 23, 2009 at 04:02:57PM +0100, Dunc wrote: In the UK we do. (Well on BT lines - I've a funny feeling some Telewest/NTL lines use Bell signaling). On an incoming call we get: Polarity reversal. FSK Caller ID burst Ringing https://issues.asterisk.org/view.php?id=9096 ? Thanks for the link, at the moment my stuff doesn't work properly at all though, it's not just the caller ID stuff. I'm guessing it's down to the cable though now after reading the previous posts on this thread. If someone knows exactly which pins at each end I need to connect with a 2 wire cable that would be amazing (UK NTL phone line.) (Bueller, anyone? :-) ) Once I have incoming calls working then I think I'll be back fixing the caller ID stuff :) Cheers, Dunc ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
Dunc On Sat, May 23, 2009 at 12:43 PM, Dunc d...@lemonia.org wrote: Tzafrir Cohen wrote: On Sat, May 23, 2009 at 04:02:57PM +0100, Dunc wrote: In the UK we do. (Well on BT lines - I've a funny feeling some Telewest/NTL lines use Bell signaling). On an incoming call we get: Polarity reversal. FSK Caller ID burst Ringing https://issues.asterisk.org/view.php?id=9096 ? Thanks for the link, at the moment my stuff doesn't work properly at all though, it's not just the caller ID stuff. I'm guessing it's down to the cable though now after reading the previous posts on this thread. If someone knows exactly which pins at each end I need to connect with a 2 wire cable that would be amazing (UK NTL phone line.) (Bueller, anyone? :-) ) Once I have incoming calls working then I think I'll be back fixing the caller ID stuff :) I've some experience with openvox cards, what card are you using? What problems are you having? Cheers, -- Tiago Durante ,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,., Perseverance is the hard work you do after you get tired of doing the hard work you already did. -- Newt Gingrich ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
Tiago Durante wrote: Dunc On Sat, May 23, 2009 at 12:43 PM, Dunc d...@lemonia.org wrote: Tzafrir Cohen wrote: On Sat, May 23, 2009 at 04:02:57PM +0100, Dunc wrote: In the UK we do. (Well on BT lines - I've a funny feeling some Telewest/NTL lines use Bell signaling). On an incoming call we get: Polarity reversal. FSK Caller ID burst Ringing https://issues.asterisk.org/view.php?id=9096 ? Thanks for the link, at the moment my stuff doesn't work properly at all though, it's not just the caller ID stuff. I'm guessing it's down to the cable though now after reading the previous posts on this thread. If someone knows exactly which pins at each end I need to connect with a 2 wire cable that would be amazing (UK NTL phone line.) (Bueller, anyone? :-) ) Once I have incoming calls working then I think I'll be back fixing the caller ID stuff :) I've some experience with openvox cards, what card are you using? What problems are you having? Cheers, Hi Tiago, I have an OpenVox A400P11, it shows up like this... eddie ~ # lsdahdi ### Span 1: WCTDM/4 Wildcard TDM400P REV E/F Board 5 (MASTER) 1 FXSFXSKS (EC: MG2) RED 2 FXOFXOLS (EC: MG2) Use of uninitialized value in string eq at /usr/lib64/perl5/site_perl/5.8.8/Dahdi/Chans.pm line 221. 3 unknown Use of uninitialized value in string eq at /usr/lib64/perl5/site_perl/5.8.8/Dahdi/Chans.pm line 221. 4 unknown eddie ~ # I'm pretty sure that the RED alarm is a bad thing. While googling about this error from the asterisk console *CLI [May 23 18:14:02] NOTICE[4469]: chan_dahdi.c:8164 handle_init_event: Alarm cleared on channel 1 [May 23 18:14:03] WARNING[4469]: chan_dahdi.c:4664 handle_alarms: Detected alarm on channel 1: Red Alarm I discovered this thread on the mailing list, and so signed up and mailed in with the same subject. It didn't link them together though it seems, so here's a URL http://www.mail-archive.com/asterisk-users@lists.digium.com/msg223429.html If you read this specific post, and the last few before http://www.mail-archive.com/asterisk-users@lists.digium.com/msg223523.html it seems that a 2-pin cable from the wall socket to the card is required. Now, I was warned about cables and did my best to get the one that sounded right, however mine definitely has 4 pins. So my 2 questions are 1) What are the pinouts for the 2 pin cable, and I'll make my own for now (For bonus points, unless the wires are crossed over, what possible difference could it make when the TDM card only has 2 pins anyway?) 2) Is this the correct cable for NTL too? I think I should find out definite answers to the above before I worry any further about the card and Asterisk :-) Thanks for getting back to me, hope you can help. Cheers, Dunc ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
Hi Dunc, On Sat, May 23, 2009 at 1:23 PM, Dunc d...@lemonia.org wrote: Tiago Durante wrote: Dunc On Sat, May 23, 2009 at 12:43 PM, Dunc d...@lemonia.org wrote: Tzafrir Cohen wrote: On Sat, May 23, 2009 at 04:02:57PM +0100, Dunc wrote: In the UK we do. (Well on BT lines - I've a funny feeling some Telewest/NTL lines use Bell signaling). On an incoming call we get: Polarity reversal. FSK Caller ID burst Ringing https://issues.asterisk.org/view.php?id=9096 ? Thanks for the link, at the moment my stuff doesn't work properly at all though, it's not just the caller ID stuff. I'm guessing it's down to the cable though now after reading the previous posts on this thread. If someone knows exactly which pins at each end I need to connect with a 2 wire cable that would be amazing (UK NTL phone line.) (Bueller, anyone? :-) ) Once I have incoming calls working then I think I'll be back fixing the caller ID stuff :) I've some experience with openvox cards, what card are you using? What problems are you having? Cheers, Hi Tiago, I have an OpenVox A400P11, it shows up like this... eddie ~ # lsdahdi ### Span 1: WCTDM/4 Wildcard TDM400P REV E/F Board 5 (MASTER) 1 FXS FXSKS (EC: MG2) RED 2 FXO FXOLS (EC: MG2) Use of uninitialized value in string eq at /usr/lib64/perl5/site_perl/5.8.8/Dahdi/Chans.pm line 221. 3 unknown Use of uninitialized value in string eq at /usr/lib64/perl5/site_perl/5.8.8/Dahdi/Chans.pm line 221. 4 unknown eddie ~ # I'm pretty sure that the RED alarm is a bad thing. While googling about this error from the asterisk console *CLI [May 23 18:14:02] NOTICE[4469]: chan_dahdi.c:8164 handle_init_event: Alarm cleared on channel 1 [May 23 18:14:03] WARNING[4469]: chan_dahdi.c:4664 handle_alarms: Detected alarm on channel 1: Red Alarm I discovered this thread on the mailing list, and so signed up and mailed in with the same subject. It didn't link them together though it seems, so here's a URL http://www.mail-archive.com/asterisk-users@lists.digium.com/msg223429.html If you read this specific post, and the last few before http://www.mail-archive.com/asterisk-users@lists.digium.com/msg223523.html How is your configuration? Please post here. At first I thought you were using a A1200P, this card (which is very good) gave some headache some weeks ago, because it wasn't working properly with dahdi. I didn't have a chance to test it again. It's because for this card you need a module from Openvox. The A400P card that they made is a clone of the TDM and should work fine with DAHDI. For this card you shouldn't need any module from Openvox. it seems that a 2-pin cable from the wall socket to the card is required. Now, I was warned about cables and did my best to get the one that sounded right, however mine definitely has 4 pins. So my 2 questions are 1) What are the pinouts for the 2 pin cable, and I'll make my own for now (For bonus points, unless the wires are crossed over, what possible difference could it make when the TDM card only has 2 pins anyway?) 2) Is this the correct cable for NTL too? This line that you're using, can you use a regular analog phone to make call through it? I don't have any server running in UK, only USA and Latin America... But I'll assume the cabling is the same... If so you should have a connector like this: http://img.zdnet.com/techDirectory/RJ11.GIF Test your line with a regular phone. Make sure it works fine. Also make sure not to connect the PSTN line on the FXS card, you can 'burn' your FXS doing that. I think I should find out definite answers to the above before I worry any further about the card and Asterisk :-) I agree... =) Thanks for getting back to me, hope you can help. No prob, I hope too! Cheers! -- Tiago Durante ,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,.,., Perseverance is the hard work you do after you get tired of doing the hard work you already did. -- Newt Gingrich ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
On Sat, 23 May 2009, Dunc wrote: Hi everyone, I just found this thread, which is amazing as I'm on my first go with asterisk and so far I've been pulling my hair out for the last week :-) I have 2 questions which were raised while this fault was being debugged. 1) Gordon says:- Is this a place where you get a polarity reversal event on call startup? In the UK we do. (Well on BT lines - I've a funny feeling some Telewest/NTL lines use Bell signaling). On an incoming call we get: Polarity reversal. FSK Caller ID burst Ringing Well I've got an NTL phone line, can anyone tell me what to use for that? Throw it away and get a BT one ;-) I'd suggest running with verbose =3 and seeing what it says. However I have 2 clients with Teleworst lines and I've never been able to make caller ID work on them, even though teleworst insist they are providing caller ID.. 2) Do I still need the same 2pin cable? Because I've been to Maplins too and bought one that I thought was right, but this one is a 4pin too. Can anyone tell me which pins on their 2pin cable are connected at each end? I'll bodge my cable until it works and then get a proper one once I'm sure. I think part of this same thread had something about modem vs. ordinary cables - however I put in a 4-pin modem cable to see what happenes and it continued to work as before, so I'm personally not convinced about that one... ie. I've not had a cable that didn't work. Gordon ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
- Steven J. Douglas stev...@moij.biz wrote: --[ UxBoD ]-- wrote: - Steven J. Douglas stev...@moij.biz wrote: --[ UxBoD ]-- wrote: - Gordon Henderson gordon+aster...@drogon.net wrote: On Fri, 1 May 2009, --[ UxBoD ]-- wrote: Okay, getting somewhere now ! I am now getting the following :- == Starting post polarity CID detection on channel 1 -- Starting simple switch on 'DAHDI/1-1' [May 1 12:03:10] NOTICE[4360]: chan_dahdi.c:7669 ss_thread: MWI: Channel 1 message waiting! -- Executing [...@inbound-dahdi:1] Answer(DAHDI/1-1, ) in new stack -- Executing [...@inbound-dahdi:2] Ringing(DAHDI/1-1, ) in new stack -- Executing [...@inbound-dahdi:3] Wait(DAHDI/1-1, 1) in new stack -- Executing [...@inbound-dahdi:4] Playback(DAHDI/1-1, home-message) in new stack -- DAHDI/1-1 Playing 'home-message.gsm' (language 'en') -- Executing [...@inbound-dahdi:5] Hangup(DAHDI/1-1, ) in new stack == Spawn extension (inbound-dahdi, s, 5) exited non-zero on 'DAHDI/1-1' -- Hungup 'DAHDI/1-1' The problem is that I never actually here the message playback. On the dialling phone I just hear it keep ringing. My test dialplan is as follows :- [inbound-dahdi] exten = s,1,Answer() exten = s,n,Ringing() exten = s,n,Wait(1) exten = s,n,Playback(home-message) exten = s,n,Hangup() I put that in mine and get: == Starting post polarity CID detection on channel 4 -- Starting simple switch on 'Zap/4-1' -- Executing Answer(Zap/4-1, ) in new stack -- Executing Ringing(Zap/4-1, ) in new stack -- Executing Wait(Zap/4-1, 1) in new stack -- Executing Playback(Zap/4-1, tt-ferrets) in new stack -- Playing 'tt-ferrets' (language 'en') -- Executing Hangup(Zap/4-1, ) in new stack == Spawn extension (incoming-zap-ddi, s, 5) exited non-zero on 'Zap/4-1' -- Hungup 'Zap/4-1' Personally I'd not put in the Ringing(), but it's doing no harm here... Looks like it's almost there - barring bugs in the dahdi code, but there must be 1000's of people out there using it with TDM400 cards or clones... The differences between UK and US lines are minimal give or take a line reversal, but who knows... Gordon ___ Yes, I agree with you Gordon, I really do think it is a bug in the DADHI code as it never plays back the message at all. I even tried removing the Ringing code and that makes no difference at all. With such a simple dialplan and configuration I can only think it is how BT signals the line. Though the fact that the dialplan does get executed suggests that it has noticed the inbound call; it just does not pick up the line :( Best Regards, Are you using a 2-pin BT to RJ-11 phone cable? If your cable is a 4-pin BT to RJ-11 version, then its a modem cable and it won't work. The symptoms will be similar to what you have described. Regards, Steve Hi Steve, Thank you for the reply. I have a RJ11 plugged into the TDM400 which has a standard BT connector on the end. This is then connected to a standard telephone extension cable and plugged into the BT socket. Should I be using something different ? Best Regards, Hi, Your BT connector should have only 2 pins. If there are 4 pins on the BT connector, then it is a modem cable, which is wrong. Regards, Steve. Well just a follow up to my fun and games! All is working wonderfully now :) It is amazing what difference the correct cable makes! ;) Though I have had to drop back to Asterisk 1.4 and DAHDI instead of 1.6.1 due to being unable to play back voicemail. As soon as I switched to 1.4, compiled with exactly the same options, and the same dialplan everything kicked into life. Thanks to all and I appreciate everybody who has taken the time out to reply. Now onto the next challenge :D Best Regards, -- SplatNIX IT Services :: Innovation through collaboration ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
--[ UxBoD ]-- wrote: - Steven J. Douglas stev...@moij.biz wrote: --[ UxBoD ]-- wrote: - Gordon Henderson gordon+aster...@drogon.net wrote: On Fri, 1 May 2009, --[ UxBoD ]-- wrote: Okay, getting somewhere now ! I am now getting the following :- == Starting post polarity CID detection on channel 1 -- Starting simple switch on 'DAHDI/1-1' [May 1 12:03:10] NOTICE[4360]: chan_dahdi.c:7669 ss_thread: MWI: Channel 1 message waiting! -- Executing [...@inbound-dahdi:1] Answer(DAHDI/1-1, ) in new stack -- Executing [...@inbound-dahdi:2] Ringing(DAHDI/1-1, ) in new stack -- Executing [...@inbound-dahdi:3] Wait(DAHDI/1-1, 1) in new stack -- Executing [...@inbound-dahdi:4] Playback(DAHDI/1-1, home-message) in new stack -- DAHDI/1-1 Playing 'home-message.gsm' (language 'en') -- Executing [...@inbound-dahdi:5] Hangup(DAHDI/1-1, ) in new stack == Spawn extension (inbound-dahdi, s, 5) exited non-zero on 'DAHDI/1-1' -- Hungup 'DAHDI/1-1' The problem is that I never actually here the message playback. On the dialling phone I just hear it keep ringing. My test dialplan is as follows :- [inbound-dahdi] exten = s,1,Answer() exten = s,n,Ringing() exten = s,n,Wait(1) exten = s,n,Playback(home-message) exten = s,n,Hangup() I put that in mine and get: == Starting post polarity CID detection on channel 4 -- Starting simple switch on 'Zap/4-1' -- Executing Answer(Zap/4-1, ) in new stack -- Executing Ringing(Zap/4-1, ) in new stack -- Executing Wait(Zap/4-1, 1) in new stack -- Executing Playback(Zap/4-1, tt-ferrets) in new stack -- Playing 'tt-ferrets' (language 'en') -- Executing Hangup(Zap/4-1, ) in new stack == Spawn extension (incoming-zap-ddi, s, 5) exited non-zero on 'Zap/4-1' -- Hungup 'Zap/4-1' Personally I'd not put in the Ringing(), but it's doing no harm here... Looks like it's almost there - barring bugs in the dahdi code, but there must be 1000's of people out there using it with TDM400 cards or clones... The differences between UK and US lines are minimal give or take a line reversal, but who knows... Gordon ___ Yes, I agree with you Gordon, I really do think it is a bug in the DADHI code as it never plays back the message at all. I even tried removing the Ringing code and that makes no difference at all. With such a simple dialplan and configuration I can only think it is how BT signals the line. Though the fact that the dialplan does get executed suggests that it has noticed the inbound call; it just does not pick up the line :( Best Regards, Are you using a 2-pin BT to RJ-11 phone cable? If your cable is a 4-pin BT to RJ-11 version, then its a modem cable and it won't work. The symptoms will be similar to what you have described. Regards, Steve Hi Steve, Thank you for the reply. I have a RJ11 plugged into the TDM400 which has a standard BT connector on the end. This is then connected to a standard telephone extension cable and plugged into the BT socket. Should I be using something different ? Best Regards, Hi, Your BT connector should have only 2 pins. If there are 4 pins on the BT connector, then it is a modem cable, which is wrong. Regards, Steve. ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
- Steven J. Douglas stev...@moij.biz wrote: --[ UxBoD ]-- wrote: - Steven J. Douglas stev...@moij.biz wrote: --[ UxBoD ]-- wrote: - Gordon Henderson gordon+aster...@drogon.net wrote: On Fri, 1 May 2009, --[ UxBoD ]-- wrote: Okay, getting somewhere now ! I am now getting the following :- == Starting post polarity CID detection on channel 1 -- Starting simple switch on 'DAHDI/1-1' [May 1 12:03:10] NOTICE[4360]: chan_dahdi.c:7669 ss_thread: MWI: Channel 1 message waiting! -- Executing [...@inbound-dahdi:1] Answer(DAHDI/1-1, ) in new stack -- Executing [...@inbound-dahdi:2] Ringing(DAHDI/1-1, ) in new stack -- Executing [...@inbound-dahdi:3] Wait(DAHDI/1-1, 1) in new stack -- Executing [...@inbound-dahdi:4] Playback(DAHDI/1-1, home-message) in new stack -- DAHDI/1-1 Playing 'home-message.gsm' (language 'en') -- Executing [...@inbound-dahdi:5] Hangup(DAHDI/1-1, ) in new stack == Spawn extension (inbound-dahdi, s, 5) exited non-zero on 'DAHDI/1-1' -- Hungup 'DAHDI/1-1' The problem is that I never actually here the message playback. On the dialling phone I just hear it keep ringing. My test dialplan is as follows :- [inbound-dahdi] exten = s,1,Answer() exten = s,n,Ringing() exten = s,n,Wait(1) exten = s,n,Playback(home-message) exten = s,n,Hangup() I put that in mine and get: == Starting post polarity CID detection on channel 4 -- Starting simple switch on 'Zap/4-1' -- Executing Answer(Zap/4-1, ) in new stack -- Executing Ringing(Zap/4-1, ) in new stack -- Executing Wait(Zap/4-1, 1) in new stack -- Executing Playback(Zap/4-1, tt-ferrets) in new stack -- Playing 'tt-ferrets' (language 'en') -- Executing Hangup(Zap/4-1, ) in new stack == Spawn extension (incoming-zap-ddi, s, 5) exited non-zero on 'Zap/4-1' -- Hungup 'Zap/4-1' Personally I'd not put in the Ringing(), but it's doing no harm here... Looks like it's almost there - barring bugs in the dahdi code, but there must be 1000's of people out there using it with TDM400 cards or clones... The differences between UK and US lines are minimal give or take a line reversal, but who knows... Gordon ___ Yes, I agree with you Gordon, I really do think it is a bug in the DADHI code as it never plays back the message at all. I even tried removing the Ringing code and that makes no difference at all. With such a simple dialplan and configuration I can only think it is how BT signals the line. Though the fact that the dialplan does get executed suggests that it has noticed the inbound call; it just does not pick up the line :( Best Regards, Are you using a 2-pin BT to RJ-11 phone cable? If your cable is a 4-pin BT to RJ-11 version, then its a modem cable and it won't work. The symptoms will be similar to what you have described. Regards, Steve Hi Steve, Thank you for the reply. I have a RJ11 plugged into the TDM400 which has a standard BT connector on the end. This is then connected to a standard telephone extension cable and plugged into the BT socket. Should I be using something different ? Best Regards, Hi, Your BT connector should have only 2 pins. If there are 4 pins on the BT connector, then it is a modem cable, which is wrong. Regards, Steve. Hi Steve, Every connector I have checked has four pins :( Do you know where in the UK I can get such a cable that will go from a TDM400 to a BT phone socket ? I have checked Maplins and could not see one :( Many thanks for your time. Best Regards, -- SplatNIX IT Services :: Innovation through collaboration ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
- Steven J. Douglas stev...@moij.biz wrote: --[ UxBoD ]-- wrote: - Steven J. Douglas stev...@moij.biz wrote: --[ UxBoD ]-- wrote: - Gordon Henderson gordon+aster...@drogon.net wrote: On Fri, 1 May 2009, --[ UxBoD ]-- wrote: Okay, getting somewhere now ! I am now getting the following :- == Starting post polarity CID detection on channel 1 -- Starting simple switch on 'DAHDI/1-1' [May 1 12:03:10] NOTICE[4360]: chan_dahdi.c:7669 ss_thread: MWI: Channel 1 message waiting! -- Executing [...@inbound-dahdi:1] Answer(DAHDI/1-1, ) in new stack -- Executing [...@inbound-dahdi:2] Ringing(DAHDI/1-1, ) in new stack -- Executing [...@inbound-dahdi:3] Wait(DAHDI/1-1, 1) in new stack -- Executing [...@inbound-dahdi:4] Playback(DAHDI/1-1, home-message) in new stack -- DAHDI/1-1 Playing 'home-message.gsm' (language 'en') -- Executing [...@inbound-dahdi:5] Hangup(DAHDI/1-1, ) in new stack == Spawn extension (inbound-dahdi, s, 5) exited non-zero on 'DAHDI/1-1' -- Hungup 'DAHDI/1-1' The problem is that I never actually here the message playback. On the dialling phone I just hear it keep ringing. My test dialplan is as follows :- [inbound-dahdi] exten = s,1,Answer() exten = s,n,Ringing() exten = s,n,Wait(1) exten = s,n,Playback(home-message) exten = s,n,Hangup() I put that in mine and get: == Starting post polarity CID detection on channel 4 -- Starting simple switch on 'Zap/4-1' -- Executing Answer(Zap/4-1, ) in new stack -- Executing Ringing(Zap/4-1, ) in new stack -- Executing Wait(Zap/4-1, 1) in new stack -- Executing Playback(Zap/4-1, tt-ferrets) in new stack -- Playing 'tt-ferrets' (language 'en') -- Executing Hangup(Zap/4-1, ) in new stack == Spawn extension (incoming-zap-ddi, s, 5) exited non-zero on 'Zap/4-1' -- Hungup 'Zap/4-1' Personally I'd not put in the Ringing(), but it's doing no harm here... Looks like it's almost there - barring bugs in the dahdi code, but there must be 1000's of people out there using it with TDM400 cards or clones... The differences between UK and US lines are minimal give or take a line reversal, but who knows... Gordon ___ Yes, I agree with you Gordon, I really do think it is a bug in the DADHI code as it never plays back the message at all. I even tried removing the Ringing code and that makes no difference at all. With such a simple dialplan and configuration I can only think it is how BT signals the line. Though the fact that the dialplan does get executed suggests that it has noticed the inbound call; it just does not pick up the line :( Best Regards, Are you using a 2-pin BT to RJ-11 phone cable? If your cable is a 4-pin BT to RJ-11 version, then its a modem cable and it won't work. The symptoms will be similar to what you have described. Regards, Steve Hi Steve, Thank you for the reply. I have a RJ11 plugged into the TDM400 which has a standard BT connector on the end. This is then connected to a standard telephone extension cable and plugged into the BT socket. Should I be using something different ? Best Regards, Hi, Your BT connector should have only 2 pins. If there are 4 pins on the BT connector, then it is a modem cable, which is wrong. Regards, Steve. Steve, You rock! :) Found a BT old cordless phone in the cupboard with a long cable. Plugged in and away she goes! Thank you so so much indeed (and your help aswell Gordon). Now just need to get rid of :- NOTICE[7097]: chan_dahdi.c:7669 ss_thread: MWI: Channel 1 message waiting! Best Regards, -- SplatNIX IT Services :: Innovation through collaboration ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
- Steven J. Douglas stev...@moij.biz wrote: --[ UxBoD ]-- wrote: - Gordon Henderson gordon+aster...@drogon.net wrote: On Fri, 1 May 2009, --[ UxBoD ]-- wrote: Okay, getting somewhere now ! I am now getting the following :- == Starting post polarity CID detection on channel 1 -- Starting simple switch on 'DAHDI/1-1' [May 1 12:03:10] NOTICE[4360]: chan_dahdi.c:7669 ss_thread: MWI: Channel 1 message waiting! -- Executing [...@inbound-dahdi:1] Answer(DAHDI/1-1, ) in new stack -- Executing [...@inbound-dahdi:2] Ringing(DAHDI/1-1, ) in new stack -- Executing [...@inbound-dahdi:3] Wait(DAHDI/1-1, 1) in new stack -- Executing [...@inbound-dahdi:4] Playback(DAHDI/1-1, home-message) in new stack -- DAHDI/1-1 Playing 'home-message.gsm' (language 'en') -- Executing [...@inbound-dahdi:5] Hangup(DAHDI/1-1, ) in new stack == Spawn extension (inbound-dahdi, s, 5) exited non-zero on 'DAHDI/1-1' -- Hungup 'DAHDI/1-1' The problem is that I never actually here the message playback. On the dialling phone I just hear it keep ringing. My test dialplan is as follows :- [inbound-dahdi] exten = s,1,Answer() exten = s,n,Ringing() exten = s,n,Wait(1) exten = s,n,Playback(home-message) exten = s,n,Hangup() I put that in mine and get: == Starting post polarity CID detection on channel 4 -- Starting simple switch on 'Zap/4-1' -- Executing Answer(Zap/4-1, ) in new stack -- Executing Ringing(Zap/4-1, ) in new stack -- Executing Wait(Zap/4-1, 1) in new stack -- Executing Playback(Zap/4-1, tt-ferrets) in new stack -- Playing 'tt-ferrets' (language 'en') -- Executing Hangup(Zap/4-1, ) in new stack == Spawn extension (incoming-zap-ddi, s, 5) exited non-zero on 'Zap/4-1' -- Hungup 'Zap/4-1' Personally I'd not put in the Ringing(), but it's doing no harm here... Looks like it's almost there - barring bugs in the dahdi code, but there must be 1000's of people out there using it with TDM400 cards or clones... The differences between UK and US lines are minimal give or take a line reversal, but who knows... Gordon ___ Yes, I agree with you Gordon, I really do think it is a bug in the DADHI code as it never plays back the message at all. I even tried removing the Ringing code and that makes no difference at all. With such a simple dialplan and configuration I can only think it is how BT signals the line. Though the fact that the dialplan does get executed suggests that it has noticed the inbound call; it just does not pick up the line :( Best Regards, Are you using a 2-pin BT to RJ-11 phone cable? If your cable is a 4-pin BT to RJ-11 version, then its a modem cable and it won't work. The symptoms will be similar to what you have described. Regards, Steve Hi Steve, Thank you for the reply. I have a RJ11 plugged into the TDM400 which has a standard BT connector on the end. This is then connected to a standard telephone extension cable and plugged into the BT socket. Should I be using something different ? Best Regards, -- SplatNIX IT Services :: Innovation through collaboration ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
On Mon, 4 May 2009, --[ UxBoD ]-- wrote: Your BT connector should have only 2 pins. If there are 4 pins on the BT connector, then it is a modem cable, which is wrong. Regards, Steve. Steve, You rock! :) Found a BT old cordless phone in the cupboard with a long cable. Plugged in and away she goes! Thank you so so much indeed (and your help aswell Gordon). Well I'm astounded by that too. And I thought I knew all about UK phone wiring - master sockets, ring capacitors and so on, but what on-earth does a modem cable do? And looking through my spares drawer, I seem to have a mix of 2-pin and 4-pin cables... And I've just put a 4-pin cable on my home system and it's working OK... So what gives? Gordon ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
- Gordon Henderson gordon+aster...@drogon.net wrote: On Fri, 1 May 2009, --[ UxBoD ]-- wrote: Okay, getting somewhere now ! I am now getting the following :- == Starting post polarity CID detection on channel 1 -- Starting simple switch on 'DAHDI/1-1' [May 1 12:03:10] NOTICE[4360]: chan_dahdi.c:7669 ss_thread: MWI: Channel 1 message waiting! -- Executing [...@inbound-dahdi:1] Answer(DAHDI/1-1, ) in new stack -- Executing [...@inbound-dahdi:2] Ringing(DAHDI/1-1, ) in new stack -- Executing [...@inbound-dahdi:3] Wait(DAHDI/1-1, 1) in new stack -- Executing [...@inbound-dahdi:4] Playback(DAHDI/1-1, home-message) in new stack -- DAHDI/1-1 Playing 'home-message.gsm' (language 'en') -- Executing [...@inbound-dahdi:5] Hangup(DAHDI/1-1, ) in new stack == Spawn extension (inbound-dahdi, s, 5) exited non-zero on 'DAHDI/1-1' -- Hungup 'DAHDI/1-1' The problem is that I never actually here the message playback. On the dialling phone I just hear it keep ringing. My test dialplan is as follows :- [inbound-dahdi] exten = s,1,Answer() exten = s,n,Ringing() exten = s,n,Wait(1) exten = s,n,Playback(home-message) exten = s,n,Hangup() I put that in mine and get: == Starting post polarity CID detection on channel 4 -- Starting simple switch on 'Zap/4-1' -- Executing Answer(Zap/4-1, ) in new stack -- Executing Ringing(Zap/4-1, ) in new stack -- Executing Wait(Zap/4-1, 1) in new stack -- Executing Playback(Zap/4-1, tt-ferrets) in new stack -- Playing 'tt-ferrets' (language 'en') -- Executing Hangup(Zap/4-1, ) in new stack == Spawn extension (incoming-zap-ddi, s, 5) exited non-zero on 'Zap/4-1' -- Hungup 'Zap/4-1' Personally I'd not put in the Ringing(), but it's doing no harm here... Looks like it's almost there - barring bugs in the dahdi code, but there must be 1000's of people out there using it with TDM400 cards or clones... The differences between UK and US lines are minimal give or take a line reversal, but who knows... Gordon ___ Yes, I agree with you Gordon, I really do think it is a bug in the DADHI code as it never plays back the message at all. I even tried removing the Ringing code and that makes no difference at all. With such a simple dialplan and configuration I can only think it is how BT signals the line. Though the fact that the dialplan does get executed suggests that it has noticed the inbound call; it just does not pick up the line :( Best Regards, -- SplatNIX IT Services :: Innovation through collaboration ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
--[ UxBoD ]-- wrote: - Gordon Henderson gordon+aster...@drogon.net wrote: On Fri, 1 May 2009, --[ UxBoD ]-- wrote: Okay, getting somewhere now ! I am now getting the following :- == Starting post polarity CID detection on channel 1 -- Starting simple switch on 'DAHDI/1-1' [May 1 12:03:10] NOTICE[4360]: chan_dahdi.c:7669 ss_thread: MWI: Channel 1 message waiting! -- Executing [...@inbound-dahdi:1] Answer(DAHDI/1-1, ) in new stack -- Executing [...@inbound-dahdi:2] Ringing(DAHDI/1-1, ) in new stack -- Executing [...@inbound-dahdi:3] Wait(DAHDI/1-1, 1) in new stack -- Executing [...@inbound-dahdi:4] Playback(DAHDI/1-1, home-message) in new stack -- DAHDI/1-1 Playing 'home-message.gsm' (language 'en') -- Executing [...@inbound-dahdi:5] Hangup(DAHDI/1-1, ) in new stack == Spawn extension (inbound-dahdi, s, 5) exited non-zero on 'DAHDI/1-1' -- Hungup 'DAHDI/1-1' The problem is that I never actually here the message playback. On the dialling phone I just hear it keep ringing. My test dialplan is as follows :- [inbound-dahdi] exten = s,1,Answer() exten = s,n,Ringing() exten = s,n,Wait(1) exten = s,n,Playback(home-message) exten = s,n,Hangup() I put that in mine and get: == Starting post polarity CID detection on channel 4 -- Starting simple switch on 'Zap/4-1' -- Executing Answer(Zap/4-1, ) in new stack -- Executing Ringing(Zap/4-1, ) in new stack -- Executing Wait(Zap/4-1, 1) in new stack -- Executing Playback(Zap/4-1, tt-ferrets) in new stack -- Playing 'tt-ferrets' (language 'en') -- Executing Hangup(Zap/4-1, ) in new stack == Spawn extension (incoming-zap-ddi, s, 5) exited non-zero on 'Zap/4-1' -- Hungup 'Zap/4-1' Personally I'd not put in the Ringing(), but it's doing no harm here... Looks like it's almost there - barring bugs in the dahdi code, but there must be 1000's of people out there using it with TDM400 cards or clones... The differences between UK and US lines are minimal give or take a line reversal, but who knows... Gordon ___ Yes, I agree with you Gordon, I really do think it is a bug in the DADHI code as it never plays back the message at all. I even tried removing the Ringing code and that makes no difference at all. With such a simple dialplan and configuration I can only think it is how BT signals the line. Though the fact that the dialplan does get executed suggests that it has noticed the inbound call; it just does not pick up the line :( Best Regards, Are you using a 2-pin BT to RJ-11 phone cable? If your cable is a 4-pin BT to RJ-11 version, then its a modem cable and it won't work. The symptoms will be similar to what you have described. Regards, Steve ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
- Tzafrir Cohen tzafrir.co...@xorcom.com wrote: On Mon, Apr 27, 2009 at 07:37:05AM +0100, --[ UxBoD ]-- wrote: Hi, Built a new server at the weekend and install Asterisk 1.6.0.9 and IAX and SIP work great :) The one problem I am having is getting the OpenVox (TDM400 type card) to work. It is successfully identified using WCTDM kernel module and dahdi_scan picks it up just fine. The issue is when I try and setup dahdi_channel.conf as it fails everytime. What is dahdi_channel.conf ? What is the output of: lsdahdi asterisk -rx 'dahdi show channels' When running asterisk -r I see the port pick up the ring but the it shows a RED Alarm failure. RED alarm: nothing connected to the port (applies to FXO as well as to digital ports - E1, T1, J1, BRI). Sorry for the delay! Okay here is the information requested :- dahdi_chan.conf --- [channels] group=0 language=en context=inbound-dahdi signalling=fxs_ks dahdichan = 1 lsdahdi --- [r...@voip asterisk]# lsdahdi ### Span 1: WCTDM/4 Wildcard TDM400P REV E/F Board 5 (MASTER) 1 FXOFXSKS (In use) (SWEC: MG2) RED 2 EMPTY 3 EMPTY 4 EMPTY [r...@voip asterisk]# asterisk -rx 'dahdi show channels' Chan Extension Context Language MOH InterpretBlocked State pseudodefaultdefault In Service 1inbound-dahdi en default In Service Cable is plugged in fine, but when it tries to pick up the call I get :- [May 1 07:15:03] NOTICE[10601]: chan_dahdi.c:8164 handle_init_event: Alarm cleared on channel 1 [May 1 07:15:04] WARNING[10601]: chan_dahdi.c:4664 handle_alarms: Detected alarm on channel 1: Red Alarm Would be really nice to get this working and complete my VoIP installation :( Best Regards, -- SplatNIX IT Services :: Innovation through collaboration ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
On Fri, May 01, 2009 at 07:16:19AM +0100, --[ UxBoD ]-- wrote: - Tzafrir Cohen tzafrir.co...@xorcom.com wrote: On Mon, Apr 27, 2009 at 07:37:05AM +0100, --[ UxBoD ]-- wrote: Hi, Built a new server at the weekend and install Asterisk 1.6.0.9 and IAX and SIP work great :) The one problem I am having is getting the OpenVox (TDM400 type card) to work. It is successfully identified using WCTDM kernel module and dahdi_scan picks it up just fine. The issue is when I try and setup dahdi_channel.conf as it fails everytime. What is dahdi_channel.conf ? What is the output of: lsdahdi asterisk -rx 'dahdi show channels' When running asterisk -r I see the port pick up the ring but the it shows a RED Alarm failure. RED alarm: nothing connected to the port (applies to FXO as well as to digital ports - E1, T1, J1, BRI). Sorry for the delay! Okay here is the information requested :- dahdi_chan.conf --- [channels] group=0 language=en context=inbound-dahdi signalling=fxs_ks dahdichan = 1 lsdahdi --- [r...@voip asterisk]# lsdahdi ### Span 1: WCTDM/4 Wildcard TDM400P REV E/F Board 5 (MASTER) 1 FXOFXSKS (In use) (SWEC: MG2) RED 2 EMPTY 3 EMPTY 4 EMPTY [r...@voip asterisk]# asterisk -rx 'dahdi show channels' Chan Extension Context Language MOH InterpretBlocked State pseudodefaultdefault In Service 1inbound-dahdi en default In Service Cable is plugged in fine, but when it tries to pick up the call I get :- [May 1 07:15:03] NOTICE[10601]: chan_dahdi.c:8164 handle_init_event: Alarm cleared on channel 1 [May 1 07:15:04] WARNING[10601]: chan_dahdi.c:4664 handle_alarms: Detected alarm on channel 1: Red Alarm Would be really nice to get this working and complete my VoIP installation :( Is this a place where you get a polarity reversal event on call startup? -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
- Tzafrir Cohen tzafrir.co...@xorcom.com wrote: On Fri, May 01, 2009 at 07:16:19AM +0100, --[ UxBoD ]-- wrote: - Tzafrir Cohen tzafrir.co...@xorcom.com wrote: On Mon, Apr 27, 2009 at 07:37:05AM +0100, --[ UxBoD ]-- wrote: Hi, Built a new server at the weekend and install Asterisk 1.6.0.9 and IAX and SIP work great :) The one problem I am having is getting the OpenVox (TDM400 type card) to work. It is successfully identified using WCTDM kernel module and dahdi_scan picks it up just fine. The issue is when I try and setup dahdi_channel.conf as it fails everytime. What is dahdi_channel.conf ? What is the output of: lsdahdi asterisk -rx 'dahdi show channels' When running asterisk -r I see the port pick up the ring but the it shows a RED Alarm failure. RED alarm: nothing connected to the port (applies to FXO as well as to digital ports - E1, T1, J1, BRI). Sorry for the delay! Okay here is the information requested :- dahdi_chan.conf --- [channels] group=0 language=en context=inbound-dahdi signalling=fxs_ks dahdichan = 1 lsdahdi --- [r...@voip asterisk]# lsdahdi ### Span 1: WCTDM/4 Wildcard TDM400P REV E/F Board 5 (MASTER) 1 FXO FXSKS (In use) (SWEC: MG2) RED 2 EMPTY 3 EMPTY 4 EMPTY [r...@voip asterisk]# asterisk -rx 'dahdi show channels' Chan Extension Context Language MOH Interpret Blocked State pseudo default default In Service 1 inbound-dahdi en default In Service Cable is plugged in fine, but when it tries to pick up the call I get :- [May 1 07:15:03] NOTICE[10601]: chan_dahdi.c:8164 handle_init_event: Alarm cleared on channel 1 [May 1 07:15:04] WARNING[10601]: chan_dahdi.c:4664 handle_alarms: Detected alarm on channel 1: Red Alarm Would be really nice to get this working and complete my VoIP installation :( Is this a place where you get a polarity reversal event on call startup? Hmmm, possibly :) I tried adding :- usecallerid=yes cidsignalling=v23 cidstart=polarity to chan_dahdi.conf and now get :- [May 1 08:12:33] NOTICE[10802]: chan_dahdi.c:8164 handle_init_event: Alarm cleared on channel 1 [May 1 08:12:34] WARNING[10802]: chan_dahdi.c:4664 handle_alarms: Detected alarm on channel 1: Red Alarm == Starting post polarity CID detection on channel 1 -- Starting simple switch on 'DAHDI/1-1' [May 1 08:12:39] NOTICE[10811]: chan_dahdi.c:7253 ss_thread: Got event 17 (Polarity Reversal)... [May 1 08:12:41] WARNING[10811]: chan_dahdi.c:7311 ss_thread: CID timed out waiting for ring. Exiting simple switch -- Hungup 'DAHDI/1-1' == Starting post polarity CID detection on channel 1 -- Starting simple switch on 'DAHDI/1-1' [May 1 08:12:57] NOTICE[10813]: chan_dahdi.c:7253 ss_thread: Got event 17 (Polarity Reversal)... [May 1 08:12:59] WARNING[10813]: chan_dahdi.c:7311 ss_thread: CID timed out waiting for ring. Exiting simple switch -- Hungup 'DAHDI/1-1' == Starting post polarity CID detection on channel 1 Best Regards, -- SplatNIX IT Services :: Innovation through collaboration ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
On Fri, 1 May 2009, Tzafrir Cohen wrote: Is this a place where you get a polarity reversal event on call startup? In the UK we do. (Well on BT lines - I've a funny feeling some Telewest/NTL lines use Bell signaling). On an incoming call we get: Polarity reversal. FSK Caller ID burst Ringing I've not upgraded any analogue systems to dahdi yet, but from what I've read so-far, there's not much difference between the config files (other than their names and locations), but a typical /etc/zaptel.conf file looks like: fxoks=1 fxsks=4 loadzone=uk defaultzone=uk This has one FXO and one FXS port. The corresponding zapata.conf is: [trunkgroups] [channels] usecallerid=yes cidsignalling=v23 cidstart=polarity hidecallerid=no callwaiting=no threewaycalling=yes transfer=yes echocancel=yes ;echotraining=yes; off for oslec ;echocancelwhenbridged=yes immediate=no faxdetect=no ; Channel 1: Local analogue line context=internal group=0 signalling=fxo_ks sendcalleridafter=2 rxgain=0 txgain=0 mailbox=202 callerid=The Red Phone 202 channel = 1 ; Channel 4: PSTN line context=incoming-zap-ddi group=1 usecallerid=yes faxdetect=none signalling=fxs_ks rxgain=8 txgain=8 callerid=asreceived channel = 4 Hope this is may be some use. Gordon ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
- Gordon Henderson gordon+aster...@drogon.net wrote: On Fri, 1 May 2009, Tzafrir Cohen wrote: Is this a place where you get a polarity reversal event on call startup? In the UK we do. (Well on BT lines - I've a funny feeling some Telewest/NTL lines use Bell signaling). On an incoming call we get: Polarity reversal. FSK Caller ID burst Ringing I've not upgraded any analogue systems to dahdi yet, but from what I've read so-far, there's not much difference between the config files (other than their names and locations), but a typical /etc/zaptel.conf file looks like: fxoks=1 fxsks=4 loadzone=uk defaultzone=uk This has one FXO and one FXS port. The corresponding zapata.conf is: [trunkgroups] [channels] usecallerid=yes cidsignalling=v23 cidstart=polarity hidecallerid=no callwaiting=no threewaycalling=yes transfer=yes echocancel=yes ;echotraining=yes ; off for oslec ;echocancelwhenbridged=yes immediate=no faxdetect=no ; Channel 1: Local analogue line context=internal group=0 signalling=fxo_ks sendcalleridafter=2 rxgain=0 txgain=0 mailbox=202 callerid=The Red Phone 202 channel = 1 ; Channel 4: PSTN line context=incoming-zap-ddi group=1 usecallerid=yes faxdetect=none signalling=fxs_ks rxgain=8 txgain=8 callerid=asreceived channel = 4 Hope this is may be some use. Gordon ___ Hi Gordon, Gave those settings a try and still no joy :( I have managed to get rid of the Red Alarm by changing the cable! But I still get :- == Starting post polarity CID detection on channel 1 -- Starting simple switch on 'DAHDI/1-1' [May 1 08:59:04] WARNING[11653]: chan_dahdi.c:7311 ss_thread: CID timed out waiting for ring. Exiting simple switch -- Hungup 'DAHDI/1-1' This is so annoying :( Best Regards, -- SplatNIX IT Services :: Innovation through collaboration ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
- --[ UxBoD ]-- ux...@splatnix.net wrote: - Gordon Henderson gordon+aster...@drogon.net wrote: On Fri, 1 May 2009, Tzafrir Cohen wrote: Is this a place where you get a polarity reversal event on call startup? In the UK we do. (Well on BT lines - I've a funny feeling some Telewest/NTL lines use Bell signaling). On an incoming call we get: Polarity reversal. FSK Caller ID burst Ringing I've not upgraded any analogue systems to dahdi yet, but from what I've read so-far, there's not much difference between the config files (other than their names and locations), but a typical /etc/zaptel.conf file looks like: fxoks=1 fxsks=4 loadzone=uk defaultzone=uk This has one FXO and one FXS port. The corresponding zapata.conf is: [trunkgroups] [channels] usecallerid=yes cidsignalling=v23 cidstart=polarity hidecallerid=no callwaiting=no threewaycalling=yes transfer=yes echocancel=yes ;echotraining=yes ; off for oslec ;echocancelwhenbridged=yes immediate=no faxdetect=no ; Channel 1: Local analogue line context=internal group=0 signalling=fxo_ks sendcalleridafter=2 rxgain=0 txgain=0 mailbox=202 callerid=The Red Phone 202 channel = 1 ; Channel 4: PSTN line context=incoming-zap-ddi group=1 usecallerid=yes faxdetect=none signalling=fxs_ks rxgain=8 txgain=8 callerid=asreceived channel = 4 Hope this is may be some use. Gordon ___ Could of bugs I have found relating to this issue but it appears to have been resolved :( http://bugs.digium.com/view.php?id=12531nbn=13 http://bugs.digium.com/view.php?id=14163nbn=3 Best Regards, -- SplatNIX IT Services :: Innovation through collaboration ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
On Fri, 1 May 2009, --[ UxBoD ]-- wrote: Gave those settings a try and still no joy :( I have managed to get rid of the Red Alarm by changing the cable! But I still get :- == Starting post polarity CID detection on channel 1 -- Starting simple switch on 'DAHDI/1-1' [May 1 08:59:04] WARNING[11653]: chan_dahdi.c:7311 ss_thread: CID timed out waiting for ring. Exiting simple switch -- Hungup 'DAHDI/1-1' This is so annoying :( I see those overnight when BT does a line test. Only think I could suggest is to drop back to 1.2 with Zaptel oslec. I've a multitude of boxes runing that with no problems at all with no plans to upgrade to dhadi for now. Gordon ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
- Gordon Henderson gordon+aster...@drogon.net wrote: On Fri, 1 May 2009, --[ UxBoD ]-- wrote: Gave those settings a try and still no joy :( I have managed to get rid of the Red Alarm by changing the cable! But I still get :- == Starting post polarity CID detection on channel 1 -- Starting simple switch on 'DAHDI/1-1' [May 1 08:59:04] WARNING[11653]: chan_dahdi.c:7311 ss_thread: CID timed out waiting for ring. Exiting simple switch -- Hungup 'DAHDI/1-1' This is so annoying :( I see those overnight when BT does a line test. Only think I could suggest is to drop back to 1.2 with Zaptel oslec. I've a multitude of boxes runing that with no problems at all with no plans to upgrade to dhadi for now. Gordon ___ Hi Gordon, Don't really want to go backwards as 1.6.1 is working pretty darn well. I have opened up http://bugs.digium.com/view.php?id=15010 so hopefully a developer will be able to help. Will just have to pick up a standard POTS phone for the time being and not push the PSTN through to my SNOM M3s :( Best Regards, UxBoD ps. I went for a 1U rackmount and a Intel Atom 330 Mini-ITX in the end :) -- SplatNIX IT Services :: Innovation through collaboration ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
On Fri, 1 May 2009, --[ UxBoD ]-- wrote: - Gordon Henderson gordon+aster...@drogon.net wrote: On Fri, 1 May 2009, --[ UxBoD ]-- wrote: Gave those settings a try and still no joy :( I have managed to get rid of the Red Alarm by changing the cable! But I still get :- == Starting post polarity CID detection on channel 1 -- Starting simple switch on 'DAHDI/1-1' [May 1 08:59:04] WARNING[11653]: chan_dahdi.c:7311 ss_thread: CID timed out waiting for ring. Exiting simple switch -- Hungup 'DAHDI/1-1' This is so annoying :( I see those overnight when BT does a line test. Only think I could suggest is to drop back to 1.2 with Zaptel oslec. I've a multitude of boxes runing that with no problems at all with no plans to upgrade to dhadi for now. Gordon ___ Hi Gordon, Don't really want to go backwards as 1.6.1 is working pretty darn well. I have opened up http://bugs.digium.com/view.php?id=15010 so hopefully a developer will be able to help. Will just have to pick up a standard POTS phone for the time being and not push the PSTN through to my SNOM M3s :( You've got M3's that work? I've stopped using them and thrown 2 sets to the dogs. ps. I went for a 1U rackmount and a Intel Atom 330 Mini-ITX in the end :) Excellent. I'm using quite a few Atom servers (Only one pair for VoIP right now though) They make good cheap LAMP boxes too. Sticking to VIA stuff for small PBXs for now. (and 1.2!) Gordon ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
- Gordon Henderson gordon+aster...@drogon.net wrote: On Fri, 1 May 2009, --[ UxBoD ]-- wrote: Gave those settings a try and still no joy :( I have managed to get rid of the Red Alarm by changing the cable! But I still get :- == Starting post polarity CID detection on channel 1 -- Starting simple switch on 'DAHDI/1-1' [May 1 08:59:04] WARNING[11653]: chan_dahdi.c:7311 ss_thread: CID timed out waiting for ring. Exiting simple switch -- Hungup 'DAHDI/1-1' This is so annoying :( I see those overnight when BT does a line test. Only think I could suggest is to drop back to 1.2 with Zaptel oslec. I've a multitude of boxes runing that with no problems at all with no plans to upgrade to dhadi for now. Gordon ___ Okay, getting somewhere now ! I am now getting the following :- == Starting post polarity CID detection on channel 1 -- Starting simple switch on 'DAHDI/1-1' [May 1 12:03:10] NOTICE[4360]: chan_dahdi.c:7669 ss_thread: MWI: Channel 1 message waiting! -- Executing [...@inbound-dahdi:1] Answer(DAHDI/1-1, ) in new stack -- Executing [...@inbound-dahdi:2] Ringing(DAHDI/1-1, ) in new stack -- Executing [...@inbound-dahdi:3] Wait(DAHDI/1-1, 1) in new stack -- Executing [...@inbound-dahdi:4] Playback(DAHDI/1-1, home-message) in new stack -- DAHDI/1-1 Playing 'home-message.gsm' (language 'en') -- Executing [...@inbound-dahdi:5] Hangup(DAHDI/1-1, ) in new stack == Spawn extension (inbound-dahdi, s, 5) exited non-zero on 'DAHDI/1-1' -- Hungup 'DAHDI/1-1' The problem is that I never actually here the message playback. On the dialling phone I just hear it keep ringing. My test dialplan is as follows :- [inbound-dahdi] exten = s,1,Answer() exten = s,n,Ringing() exten = s,n,Wait(1) exten = s,n,Playback(home-message) exten = s,n,Hangup() Any ideas please ? Best Regards, -- SplatNIX IT Services :: Innovation through collaboration ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
- --[ UxBoD ]-- ux...@splatnix.net wrote: - Gordon Henderson gordon+aster...@drogon.net wrote: On Fri, 1 May 2009, --[ UxBoD ]-- wrote: Gave those settings a try and still no joy :( I have managed to get rid of the Red Alarm by changing the cable! But I still get :- == Starting post polarity CID detection on channel 1 -- Starting simple switch on 'DAHDI/1-1' [May 1 08:59:04] WARNING[11653]: chan_dahdi.c:7311 ss_thread: CID timed out waiting for ring. Exiting simple switch -- Hungup 'DAHDI/1-1' This is so annoying :( I see those overnight when BT does a line test. Only think I could suggest is to drop back to 1.2 with Zaptel oslec. I've a multitude of boxes runing that with no problems at all with no plans to upgrade to dhadi for now. Gordon ___ Okay, getting somewhere now ! I am now getting the following :- == Starting post polarity CID detection on channel 1 -- Starting simple switch on 'DAHDI/1-1' [May 1 12:03:10] NOTICE[4360]: chan_dahdi.c:7669 ss_thread: MWI: Channel 1 message waiting! -- Executing [...@inbound-dahdi:1] Answer(DAHDI/1-1, ) in new stack -- Executing [...@inbound-dahdi:2] Ringing(DAHDI/1-1, ) in new stack -- Executing [...@inbound-dahdi:3] Wait(DAHDI/1-1, 1) in new stack -- Executing [...@inbound-dahdi:4] Playback(DAHDI/1-1, home-message) in new stack -- DAHDI/1-1 Playing 'home-message.gsm' (language 'en') -- Executing [...@inbound-dahdi:5] Hangup(DAHDI/1-1, ) in new stack == Spawn extension (inbound-dahdi, s, 5) exited non-zero on 'DAHDI/1-1' -- Hungup 'DAHDI/1-1' The problem is that I never actually here the message playback. On the dialling phone I just hear it keep ringing. My test dialplan is as follows :- [inbound-dahdi] exten = s,1,Answer() exten = s,n,Ringing() exten = s,n,Wait(1) exten = s,n,Playback(home-message) exten = s,n,Hangup() Any ideas please ? Well just cannot get this to work :( DAHDI will not pick up the call at all ... Tried just about every combination and it will never work :(:( Best Regards, -- SplatNIX IT Services :: Innovation through collaboration ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
On Fri, 1 May 2009, --[ UxBoD ]-- wrote: Okay, getting somewhere now ! I am now getting the following :- == Starting post polarity CID detection on channel 1 -- Starting simple switch on 'DAHDI/1-1' [May 1 12:03:10] NOTICE[4360]: chan_dahdi.c:7669 ss_thread: MWI: Channel 1 message waiting! -- Executing [...@inbound-dahdi:1] Answer(DAHDI/1-1, ) in new stack -- Executing [...@inbound-dahdi:2] Ringing(DAHDI/1-1, ) in new stack -- Executing [...@inbound-dahdi:3] Wait(DAHDI/1-1, 1) in new stack -- Executing [...@inbound-dahdi:4] Playback(DAHDI/1-1, home-message) in new stack -- DAHDI/1-1 Playing 'home-message.gsm' (language 'en') -- Executing [...@inbound-dahdi:5] Hangup(DAHDI/1-1, ) in new stack == Spawn extension (inbound-dahdi, s, 5) exited non-zero on 'DAHDI/1-1' -- Hungup 'DAHDI/1-1' The problem is that I never actually here the message playback. On the dialling phone I just hear it keep ringing. My test dialplan is as follows :- [inbound-dahdi] exten = s,1,Answer() exten = s,n,Ringing() exten = s,n,Wait(1) exten = s,n,Playback(home-message) exten = s,n,Hangup() I put that in mine and get: == Starting post polarity CID detection on channel 4 -- Starting simple switch on 'Zap/4-1' -- Executing Answer(Zap/4-1, ) in new stack -- Executing Ringing(Zap/4-1, ) in new stack -- Executing Wait(Zap/4-1, 1) in new stack -- Executing Playback(Zap/4-1, tt-ferrets) in new stack -- Playing 'tt-ferrets' (language 'en') -- Executing Hangup(Zap/4-1, ) in new stack == Spawn extension (incoming-zap-ddi, s, 5) exited non-zero on 'Zap/4-1' -- Hungup 'Zap/4-1' Personally I'd not put in the Ringing(), but it's doing no harm here... Looks like it's almost there - barring bugs in the dahdi code, but there must be 1000's of people out there using it with TDM400 cards or clones... The differences between UK and US lines are minimal give or take a line reversal, but who knows... Gordon ___ -- 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
Re: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
On Mon, Apr 27, 2009 at 07:37:05AM +0100, --[ UxBoD ]-- wrote: Hi, Built a new server at the weekend and install Asterisk 1.6.0.9 and IAX and SIP work great :) The one problem I am having is getting the OpenVox (TDM400 type card) to work. It is successfully identified using WCTDM kernel module and dahdi_scan picks it up just fine. The issue is when I try and setup dahdi_channel.conf as it fails everytime. What is dahdi_channel.conf ? What is the output of: lsdahdi asterisk -rx 'dahdi show channels' When running asterisk -r I see the port pick up the ring but the it shows a RED Alarm failure. RED alarm: nothing connected to the port (applies to FXO as well as to digital ports - E1, T1, J1, BRI). -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir ___ -- 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
