Posted: Sat May 23, 2009 2:08 pm Post subject: [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 --
Posted: Sat May 23, 2009 3:48 pm Post subject: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
Tzafrir Cohen wrote:
Quote:
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
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 --
Posted: Sat May 23, 2009 3:58 pm Post subject: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
Dunc
On Sat, May 23, 2009 at 12:43 PM, Dunc <dunc@lemonia.org> wrote:
Quote:
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 --
Posted: Sat May 23, 2009 4:28 pm Post subject: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
Tiago Durante wrote:
Quote:
Dunc
On Sat, May 23, 2009 at 12:43 PM, Dunc <dunc@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
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 --
Posted: Sat May 23, 2009 5:01 pm Post subject: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
Hi Dunc,
On Sat, May 23, 2009 at 1:23 PM, Dunc <dunc@lemonia.org> wrote:
Quote:
Tiago Durante wrote:
> Dunc
>
> On Sat, May 23, 2009 at 12:43 PM, Dunc <dunc@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
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.
Quote:
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:
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.
Quote:
I think I should find out definite answers to the above before I worry
any further about the card and Asterisk :-)
I agree... =)
Quote:
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 --
Posted: Sat May 23, 2009 8:24 pm Post subject: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
On Sat, 23 May 2009, Dunc wrote:
Quote:
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..
Quote:
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 --
Posted: Sun May 24, 2009 9:22 am Post subject: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
Gordon Henderson wrote:
Quote:
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....
Quote:
> 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 :-)
Quote:
> 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 --
Posted: Sun May 24, 2009 10:43 am Post subject: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
Quote:
> 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.
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
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
;
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 -vvvvc)....
*CLI> -- Starting simple switch on 'DAHDI/2-1'
-- Executing [07875123456@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 [07875123456@from-sip:1]
Dial("SIP/deskphone-008c70f8", "DAHDI/1/07875123456,20") in new stack
[May 24 12:07:37] WARNING[3970]: 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 'SIP/deskphone-008c70f8' status is
'CHANUNAVAIL'
*CLI>
(again I have changed the number)
It seems it can't use the line to dial out for some reason.
OK then on to incoming.
As far as I know my extensions.conf is correct to send an incoming call
to my analogue phone, and it does ring, but I can never actually get it
to connect.
*CLI> [May 24 12:18:38] NOTICE[3788]: chan_dahdi.c:8164
handle_init_event: Alarm cleared on channel 1
-- Starting simple switch on 'DAHDI/1-1'
[May 24 12:18:39] NOTICE[3841]: chan_dahdi.c:7505 ss_thread: Got event
18 (Ring Begin)...
[May 24 12:18:39] NOTICE[3841]: chan_dahdi.c:7505 ss_thread: Got event 2
(Ring/Answered)...
[May 24 12:18:40] NOTICE[3841]: chan_dahdi.c:7505 ss_thread: Got event 4
(Alarm)...
-- Executing [s@from-pstn:1] Dial("DAHDI/1-1", "DAHDI/2/,20") in
new stack
-- Called 2/
-- DAHDI/2-1 is ringing
-- DAHDI/2-1 is ringing
-- DAHDI/2-1 is ringing
-- DAHDI/2-1 answered DAHDI/1-1
-- Native bridging DAHDI/1-1 and DAHDI/2-1
...at this point my analogue phone stops ringing because I've picked it
up, but the incoming call (I'm ringing the house from my mobile) just
keeps ringing until I reach NTL(well Virgin now) voicemail.
If I then try ringing in again, it's worse, this happens:-
*CLI> [May 24 12:22:13] NOTICE[3788]: chan_dahdi.c:8164
handle_init_event: Alarm cleared on channel 1
-- Starting simple switch on 'DAHDI/1-1'
[May 24 12:22:13] ERROR[3856]: callerid.c:562 callerid_feed: No start
bit found in fsk data.
[May 24 12:22:13] WARNING[3856]: chan_dahdi.c:7545 ss_thread: CallerID
feed failed: Success
[May 24 12:22:13] WARNING[3856]: chan_dahdi.c:7649 ss_thread: CallerID
returned with error on channel 'DAHDI/1-1'
-- Executing [s@from-pstn:1] Dial("DAHDI/1-1", "DAHDI/2/,20") in
new stack
-- Called 2/
-- DAHDI/2-1 is ringing
-- DAHDI/2-1 is ringing
-- DAHDI/2-1 is ringing
[May 24 12:22:15] WARNING[3856]: chan_dahdi.c:4664 handle_alarms:
Detected alarm on channel 1: Red Alarm
-- Hungup 'DAHDI/2-1'
== Spawn extension (from-pstn, s, 1) exited non-zero on 'DAHDI/1-1'
-- Hungup 'DAHDI/1-1'
please not that I didn't pick up the analogue phone there, it just rang
once and then seemed to hang itself up. The incoming call on my mobile
again just kept on ringing. When I hangup my mobile, this happens....
CLI> [May 24 12:22:22] NOTICE[3788]: chan_dahdi.c:8164
handle_init_event: Alarm cleared on channel 1
[May 24 12:22:24] WARNING[3788]: chan_dahdi.c:4664 handle_alarms:
Detected alarm on channel 1: Red Alarm
I restarted asterisk and the first time, it didn't even notice the
incoming call, but after that seems to be quite consistent in the first
symptom above.
Just for the record I thought I'd direct incoming calls at my IP phone
and see what happens there. Here's the change to my context.
The deskphone rang once and then hung itself up to leave the incoming
call still ringing. Here's the logs
*CLI> [May 24 12:28:16] NOTICE[3995]: chan_dahdi.c:8164
handle_init_event: Alarm cleared on channel 1
-- Starting simple switch on 'DAHDI/1-1'
[May 24 12:28:16] NOTICE[4026]: chan_dahdi.c:7505 ss_thread: Got event
18 (Ring Begin)...
[May 24 12:28:17] NOTICE[4026]: chan_dahdi.c:7505 ss_thread: Got event 2
(Ring/Answered)...
[May 24 12:28:17] NOTICE[4026]: chan_dahdi.c:7505 ss_thread: Got event
17 (Polarity Reversal)...
-- Executing [s@from-pstn:1] Dial("DAHDI/1-1", "SIP/deskphone,20")
in new stack
== Using SIP RTP CoS mark 5
-- Called deskphone
-- SIP/deskphone-008c86f8 is ringing
[May 24 12:28:18] WARNING[4026]: chan_dahdi.c:4664 handle_alarms:
Detected alarm on channel 1: Red Alarm
== Spawn extension (from-pstn, s, 1) exited non-zero on 'DAHDI/1-1'
-- Hungup 'DAHDI/1-1'
[May 24 12:28:23] NOTICE[3995]: chan_dahdi.c:8164 handle_init_event:
Alarm cleared on channel 1
[May 24 12:28:24] WARNING[3995]: chan_dahdi.c:4664 handle_alarms:
Detected alarm on channel 1: Red Alarm
*CLI>
The next time I dialled in, asterisk never noticed the incoming call.
And then the time after, it behaved like my first symptom on the
analogue phone, i.e. it rang the deskphone no problems but when I picked
it up, the incoming call kept ringing.
Right, sorry for such a massive post, but I couldn't spot any patterns
so thought I'd better be extremely verbose. Hopefully someone can help
me narrow down my search and then we can get to gory details.
I think we can assume I've got a cable that works now (please correct me
if I'm wrong anyone) so hopefully the stuff below is irrelevant now.
Thanks in advance to anyone who makes it to here :-) and I hope someone
can point me in the right direction.
Cheers,
Dunc
Quote:
> 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:
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!
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
Posted: Sun May 24, 2009 11:08 am Post subject: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
On Sun, 24 May 2009, Dunc wrote:
Quote:
> 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...)
Quote:
I'll be happy to get it up and running for now and worry about caller ID
later though. So we'll press on :-)
Quote:
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 --
Posted: Sun May 24, 2009 11:10 am Post subject: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
On Sun, May 24, 2009 at 12:36:26PM +0100, Dunc wrote:
Quote:
>> 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)
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).
Quote:
>> 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.
Quote:
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
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
;
Posted: Sun May 24, 2009 1:06 pm Post subject: [asterisk-users] [UK SPECIFIC] DAHDI and a OpenVox Card
Tzafrir Cohen wrote:
Quote:
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 FXS FXSKS (EC: MG2) RED
>>> 2 FXO FXOLS (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)
Quote:
>>> 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
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.
Also, when I try your settings, nothing works at all, I don't even get a
dial tone on my analogue phone connected to channel 2
Cheers,
Dunc
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
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/*' ?
If I dial 123456 on my analogue phone, then it's all cool.
*CLI> -- Starting simple switch on 'DAHDI/2-1'
-- Executing [123456@from-internal:1] Answer("DAHDI/2-1", "") in
new stack
-- Executing [123456@from-internal:2] Playback("DAHDI/2-1",
"demo-congrats") in new stack
-- <DAHDI/2-1> Playing 'demo-congrats.gsm' (language 'en')
-- Executing [123456@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 [s@from-pstn:1] Answer("DAHDI/1-1", "") in new stack
-- Executing [s@from-pstn:2] Playback("DAHDI/1-1", "demo-congrats")
in new stack
-- <DAHDI/1-1> Playing 'demo-congrats.gsm' (language 'en')
-- Executing [s@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 --
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum