VoIP Mailing List Archives
Mailing list archives for the VoIP community |
|
View previous topic :: View next topic |
Author |
Message |
seandarcy2 at gmail.com Guest
|
Posted: Sun Mar 02, 2008 11:36 am Post subject: [asterisk-users] TDM400P dialout problem |
|
|
Kevin P. Fleming wrote:
...........................
Quote: | The messages in bug 12099 are *not* errors, they are annoyances only.
The latest SVN branch 1.4 code of Asterisk will no longer generate them,
|
Using today's svn 3915:
..........................
Answer("Zap/2-1", "") in new stack
-- Executing [2375678 at internal:2] Dial("Zap/2-1", "Zap/4/2375678")
in new stack
-- Called 4/2375678
[Mar 2 11:15:35] WARNING[2320]: chan_zap.c:4424 zt_handle_event:
Detected alarm on channel 4: Red Alarm
-- Hungup 'Zap/4-1'
== Everyone is busy/congested at this time (1:0/0/1)
-- Executing [2375678 at internal:3] Congestion("Zap/2-1", "") in new
stack
[Mar 2 11:15:35] NOTICE[2320]: chan_zap.c:7514 handle_init_event: Alarm
cleared on channel 4
== Spawn extension (internal, 2375678, 3) exited non-zero on 'Zap/2-1'
-- Hungup 'Zap/2-1'
zap show status
Description Alarms IRQ bpviol CRC4
Fra Codi Options LBO
Wildcard TDM400P REV I Board 1 OK 0 0 0
CAS Unk YEL 0 db (CSU)/0-133 feet (DSX-1)
sean |
|
Back to top |
|
|
tzafrir.cohen at xorco... Guest
|
Posted: Sun Mar 02, 2008 11:42 am Post subject: [asterisk-users] TDM400P dialout problem |
|
|
On Sun, Mar 02, 2008 at 11:36:03AM -0500, sean darcy wrote:
Quote: | Kevin P. Fleming wrote:
...........................
Quote: | The messages in bug 12099 are *not* errors, they are annoyances only.
The latest SVN branch 1.4 code of Asterisk will no longer generate them,
|
Using today's svn 3915:
..........................
Answer("Zap/2-1", "") in new stack
-- Executing [2375678 at internal:2] Dial("Zap/2-1", "Zap/4/2375678")
in new stack
-- Called 4/2375678
[Mar 2 11:15:35] WARNING[2320]: chan_zap.c:4424 zt_handle_event:
Detected alarm on channel 4: Red Alarm
-- Hungup 'Zap/4-1'
== Everyone is busy/congested at this time (1:0/0/1)
-- Executing [2375678 at internal:3] Congestion("Zap/2-1", "") in new
stack
[Mar 2 11:15:35] NOTICE[2320]: chan_zap.c:7514 handle_init_event: Alarm
cleared on channel 4
== Spawn extension (internal, 2375678, 3) exited non-zero on 'Zap/2-1'
-- Hungup 'Zap/2-1'
zap show status
Description Alarms IRQ bpviol CRC4
Fra Codi Options LBO
Wildcard TDM400P REV I Board 1 OK 0 0 0
CAS Unk YEL 0 db (CSU)/0-133 feet (DSX-1)
|
This shows alarms on the whole span (the card). The alarms in question
are alarms on specific channels. The whole interface makes more sense in
the other meduims where the span usually corresponds to one physical
meduim.
--
Tzafrir Cohen
icq#16849755 jabber:tzafrir.cohen at xorcom.com
+972-50-7952406 mailto:tzafrir.cohen at xorcom.com
http://www.xorcom.com iax:guest at local.xorcom.com/tzafrir |
|
Back to top |
|
|
seandarcy2 at gmail.com Guest
|
Posted: Sun Mar 02, 2008 12:01 pm Post subject: [asterisk-users] TDM400P dialout problem |
|
|
Tzafrir Cohen wrote:
Quote: | On Sun, Mar 02, 2008 at 11:36:03AM -0500, sean darcy wrote:
Quote: | Kevin P. Fleming wrote:
...........................
Quote: | The messages in bug 12099 are *not* errors, they are annoyances only.
The latest SVN branch 1.4 code of Asterisk will no longer generate them,
| Using today's svn 3915:
..........................
Answer("Zap/2-1", "") in new stack
-- Executing [2375678 at internal:2] Dial("Zap/2-1", "Zap/4/2375678")
in new stack
-- Called 4/2375678
[Mar 2 11:15:35] WARNING[2320]: chan_zap.c:4424 zt_handle_event:
Detected alarm on channel 4: Red Alarm
-- Hungup 'Zap/4-1'
== Everyone is busy/congested at this time (1:0/0/1)
-- Executing [2375678 at internal:3] Congestion("Zap/2-1", "") in new
stack
[Mar 2 11:15:35] NOTICE[2320]: chan_zap.c:7514 handle_init_event: Alarm
cleared on channel 4
== Spawn extension (internal, 2375678, 3) exited non-zero on 'Zap/2-1'
-- Hungup 'Zap/2-1'
zap show status
Description Alarms IRQ bpviol CRC4
Fra Codi Options LBO
Wildcard TDM400P REV I Board 1 OK 0 0 0
CAS Unk YEL 0 db (CSU)/0-133 feet (DSX-1)
|
This shows alarms on the whole span (the card). The alarms in question
are alarms on specific channels. The whole interface makes more sense in
the other meduims where the span usually corresponds to one physical
meduim.
|
I'm a little confused. Are you responding to my including the zap show
status command ( which I did just for background), or to the call
description? If you are responding to the call description, doesn't the
alarm show up specifically on channel 4?
In any event, as least for me the TDM400P seems to have problems with
zaptel svn - not just an annoyance.
sean |
|
Back to top |
|
|
kpfleming at digium.com Guest
|
Posted: Sun Mar 02, 2008 12:37 pm Post subject: [asterisk-users] TDM400P dialout problem |
|
|
sean darcy wrote:
Quote: | In any event, as least for me the TDM400P seems to have problems with
zaptel svn - not just an annoyance.
|
As I've mentioned previously, the changes to fix this for good (assuming
they work properly) are in
http://svn.digium.com/svn/zaptel/team/kpfleming/battery_alarms, although
one tester has reported that incoming calls don't work properly using
that branch, so it still needs some work.
--
Kevin P. Fleming
Director of Software Technologies
Digium, Inc. - "The Genuine Asterisk Experience" (TM) |
|
Back to top |
|
|
seandarcy2 at gmail.com Guest
|
Posted: Sun Mar 02, 2008 4:15 pm Post subject: [asterisk-users] TDM400P dialout problem |
|
|
Kevin P. Fleming wrote:
Quote: | sean darcy wrote:
Quote: | In any event, as least for me the TDM400P seems to have problems with
zaptel svn - not just an annoyance.
|
As I've mentioned previously, the changes to fix this for good (assuming
they work properly) are in
http://svn.digium.com/svn/zaptel/team/kpfleming/battery_alarms, although
one tester has reported that incoming calls don't work properly using
that branch, so it still needs some work.
|
Sorry, I hadn't seen this mentioned. I'll try it asap.
thanks for the lead.
sean |
|
Back to top |
|
|
seandarcy2 at gmail.com Guest
|
Posted: Sun Mar 02, 2008 5:15 pm Post subject: [asterisk-users] TDM400P dialout problem |
|
|
Kevin P. Fleming wrote:
Quote: | sean darcy wrote:
Quote: | In any event, as least for me the TDM400P seems to have problems with
zaptel svn - not just an annoyance.
|
As I've mentioned previously, the changes to fix this for good (assuming
they work properly) are in
http://svn.digium.com/svn/zaptel/team/kpfleming/battery_alarms, although
one tester has reported that incoming calls don't work properly using
that branch, so it still needs some work.
| Got it. No more Red Alarms. Which is great.
But...now I keep getting incomplete number messages from the co. No
trouble on the console:
Starting simple switch on 'Zap/2-1'
-- Executing [6981000 at internal:1] Answer("Zap/2-1", "") in new stack
-- Executing [6981000 at internal:2] Dial("Zap/2-1", "Zap/4/6981000")
in new stack
-- Called 4/6981000
-- Zap/4-1 answered Zap/2-1
-- Native bridging Zap/2-1 and Zap/4-1
-- Hungup 'Zap/4-1'
which shows the correct local number, which can be dialed from a plain
telephone. It's as though the Dial command just didn't send some of the
digits correctly.
Thanks for all the help.
sean |
|
Back to top |
|
|
seandarcy2 at gmail.com Guest
|
Posted: Sun Mar 02, 2008 5:29 pm Post subject: [asterisk-users] TDM400P dialout problem |
|
|
sean darcy wrote:
Quote: | Kevin P. Fleming wrote:
Quote: | sean darcy wrote:
Quote: | In any event, as least for me the TDM400P seems to have problems with
zaptel svn - not just an annoyance.
| As I've mentioned previously, the changes to fix this for good (assuming
they work properly) are in
http://svn.digium.com/svn/zaptel/team/kpfleming/battery_alarms, although
one tester has reported that incoming calls don't work properly using
that branch, so it still needs some work.
| Got it. No more Red Alarms. Which is great.
But...now I keep getting incomplete number messages from the co. No
trouble on the console:
Starting simple switch on 'Zap/2-1'
-- Executing [6981000 at internal:1] Answer("Zap/2-1", "") in new stack
-- Executing [6981000 at internal:2] Dial("Zap/2-1", "Zap/4/6981000")
in new stack
-- Called 4/6981000
-- Zap/4-1 answered Zap/2-1
-- Native bridging Zap/2-1 and Zap/4-1
-- Hungup 'Zap/4-1'
which shows the correct local number, which can be dialed from a plain
telephone. It's as though the Dial command just didn't send some of the
digits correctly.
| And incoming calls aren't answered. No ring event. No nothing.
svn-3915 incoming calls were answered, but generated a Red Alarm.
sean |
|
Back to top |
|
|
ra25 at wires.no-ip.org Guest
|
Posted: Sun Mar 02, 2008 9:04 pm Post subject: [asterisk-users] TDM400P dialout problem |
|
|
My incoming calls work just fine with 1.4.9.2 and TDM400P but I'm completely
unable to dial out the line.
even this doesn't work:
exten=>*903,1,Answer()
exten=>*903,n,Dial(Zap/3)
exten=>*903,n,Hangup()
I use this to pick up the line shared with analog phone. Zap/3 and Zap/4 are
connected to PSTN. Sometimes I have luck with Zap/3 but not a single call
through Zap/4
-- Executing [*903 at Martin:1] Answer("SIP/210-081e9968", "") in new stack
-- Executing [*903 at Martin:2] Dial("SIP/210-081e9968", "Zap/3") in new stack
-- Called 3
[2008-03-02 09:43:17] WARNING[5051]: chan_zap.c:4114 zt_handle_event:
Detected alarm on channel 3: No Alarm
-- Hungup 'Zap/3-1'
== Everyone is busy/congested at this time (1:0/0/1)
The alarm issue is not just annoyance....
What about downgrade Zaptel drivers...? Are they corrupted since 1.4.8? Im
only afraid older versions won't compile with latest kernels (2.6.24 in my
case) ... Sometimes its hard to find working combination of kernel and
zaptel
I will try the fix mentioned below first....
Martin
----- Original Message -----
From: "sean darcy" <seandarcy2 at gmail.com>
To: <asterisk-users at lists.digium.com>
Sent: 2. brezna 2008 17:29
Subject: Re: [asterisk-users] TDM400P dialout problem
How can I download this, do I need SVN installed....?
Quote: | Quote: | Quote: | one tester has reported that incoming calls don't work properly using
that branch, so it still needs some work.
| Got it. No more Red Alarms. Which is great.
But...now I keep getting incomplete number messages from the co. No
trouble on the console: |
|
|
|
Back to top |
|
|
seandarcy2 at gmail.com Guest
|
|
Back to top |
|
|
ra25 at wires.no-ip.org Guest
|
Posted: Sun Mar 02, 2008 10:29 pm Post subject: [asterisk-users] TDM400P dialout problem |
|
|
A simple inrease of DEFAULT_BATT_DEBOUNCE to 32 (originally 4) work for
me... Probably a nasty hack but allows me to dial....
(I also need DEFAULT_RING_DEBOUNCE increased to 256 to minimize problems
with caller ID, which is right above)
Martin
Quote: | My incoming calls work just fine with 1.4.9.2 and TDM400P but I'm
completely
unable to dial out the line.
even this doesn't work:
exten=>*903,1,Answer()
exten=>*903,n,Dial(Zap/3)
exten=>*903,n,Hangup()
I use this to pick up the line shared with analog phone. Zap/3 and Zap/4
are
connected to PSTN. Sometimes I have luck with Zap/3 but not a single call
through Zap/4
-- Executing [*903 at Martin:1] Answer("SIP/210-081e9968", "") in new stack
-- Executing [*903 at Martin:2] Dial("SIP/210-081e9968", "Zap/3") in new
stack
-- Called 3
[2008-03-02 09:43:17] WARNING[5051]: chan_zap.c:4114 zt_handle_event:
Detected alarm on channel 3: No Alarm
-- Hungup 'Zap/3-1'
== Everyone is busy/congested at this time (1:0/0/1) |
|
|
Back to top |
|
|
ra25 at wires.no-ip.org Guest
|
Posted: Tue Mar 04, 2008 7:50 am Post subject: [asterisk-users] TDM400P dialout problem |
|
|
I've tried this branch, but no luck again.... Dialing out work just fine,
but no incoming calls are recognized. With absolutely no message in logs
I also have seen this mentioned here:
http://bugs.digium.com/view.php?id=12099
Martin
----- Original Message -----
From: "sean darcy" <seandarcy2 at gmail.com>
To: <asterisk-users at lists.digium.com>
Sent: 2. brezna 2008 22:24
Subject: Re: [asterisk-users] TDM400P dialout problem
|
|
Back to top |
|
|
sruffell at digium.com Guest
|
Posted: Tue Mar 04, 2008 11:33 am Post subject: [asterisk-users] TDM400P dialout problem |
|
|
Martin wrote:
Quote: | I've tried this branch, but no luck again.... Dialing out work just fine,
but no incoming calls are recognized. With absolutely no message in logs
I also have seen this mentioned here:
http://bugs.digium.com/view.php?id=12099
|
I think it might work for you if you try the latest revision of the
battery_alarms branch, revision 3924.
Thanks, Shaun |
|
Back to top |
|
|
|
|
|
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
|
Powered by phpBB © 2001, 2005 phpBB Group
|