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 Feb 24, 2008 6:16 pm Post subject: [asterisk-users] beta4: outgoing call causes Red Alarm on TD |
 |
|
Calling out on PSTN over a TDM400P seems to generate a Red Alarm -
whatever that is. I have another extension on the PSTN, and I can dial
out over that. zttool shows no alarms.
asterisk*CLI> 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)
-- Starting simple switch on 'Zap/2-1'
-- Executing [2560597 at internal:1] Answer("Zap/2-1", "") in new stack
-- Executing [2560597 at internal:2] Set("Zap/2-1", "CALLERID="house"
<2038447>") in new stack
-- Executing [2560597 at internal:3] Dial("Zap/2-1", "Zap/4/2560597")
in new stack
-- Called 4/2560597
[Feb 24 17:57:54] WARNING[9024]: 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 [2560597 at internal:4] Congestion("Zap/2-1", "") in new
stack
[Feb 24 17:57:54] NOTICE[9024]: chan_zap.c:7514 handle_init_event: Alarm
cleared on channel 4
== Spawn extension (internal, 2560597, 4) exited non-zero on 'Zap/2-1'
-- Hungup 'Zap/2-1'
Sometimes it works, and then doesn't:
.............
-- Starting simple switch on 'Zap/2-1'
-- Executing [6378447 at internal:1] Answer("Zap/2-1", "") in new stack
-- Executing [6378447 at internal:2] Set("Zap/2-1", "CALLERID="house"
<2038447>") in new stack
-- Executing [6378447 at internal:3] Dial("Zap/2-1", "Zap/4/6378447")
in new stack
-- Called 4/6378447
-- Zap/4-1 answered Zap/2-1
-- Native bridging Zap/2-1 and Zap/4-1
-- Hungup 'Zap/4-1'
== Spawn extension (internal, 6378447, 3) exited non-zero on 'Zap/2-1'
-- Hungup 'Zap/2-1'
-- Starting simple switch on 'Zap/2-1'
-- Executing [2560597 at internal:1] Answer("Zap/2-1", "") in new stack
-- Executing [2560597 at internal:2] Set("Zap/2-1", "CALLERID="house"
<2038447>") in new stack
-- Executing [2560597 at internal:3] Dial("Zap/2-1", "Zap/4/2560597")
in new stack
-- Called 4/2560597
[Feb 24 17:56:55] WARNING[9024]: chan_zap.c:4424 zt_handle_event:
Detected alarm on channel 4: Red Alarm
............
This is beta4.
Any help appreciated.
sean |
|
| Back to top |
|
 |
novackster at gmail.com
Guest
|
| Posted: Sun Feb 24, 2008 6:49 pm Post subject: [asterisk-users] beta4: outgoing call causes Red Alarm on TD |
|
|
sean darcy wrote:
| Quote: | Calling out on PSTN over a TDM400P seems to generate a Red Alarm -
whatever that is.
|
Red Alarm USED to mean there was no battery on the line - assume this
references an FXO port connected to a PSTN POTS line.
Is it possible Channel 4 is not connected?
John Novack
| Quote: | I have another extension on the PSTN, and I can dial
out over that. zttool shows no alarms.
asterisk*CLI> 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)
-- Starting simple switch on 'Zap/2-1'
-- Executing [2560597 at internal:1] Answer("Zap/2-1", "") in new stack
-- Executing [2560597 at internal:2] Set("Zap/2-1", "CALLERID="house"
<2038447>") in new stack
-- Executing [2560597 at internal:3] Dial("Zap/2-1", "Zap/4/2560597")
in new stack
-- Called 4/2560597
[Feb 24 17:57:54] WARNING[9024]: 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 [2560597 at internal:4] Congestion("Zap/2-1", "") in new
stack
[Feb 24 17:57:54] NOTICE[9024]: chan_zap.c:7514 handle_init_event: Alarm
cleared on channel 4
== Spawn extension (internal, 2560597, 4) exited non-zero on 'Zap/2-1'
-- Hungup 'Zap/2-1'
Sometimes it works, and then doesn't:
.............
-- Starting simple switch on 'Zap/2-1'
-- Executing [6378447 at internal:1] Answer("Zap/2-1", "") in new stack
-- Executing [6378447 at internal:2] Set("Zap/2-1", "CALLERID="house"
<2038447>") in new stack
-- Executing [6378447 at internal:3] Dial("Zap/2-1", "Zap/4/6378447")
in new stack
-- Called 4/6378447
-- Zap/4-1 answered Zap/2-1
-- Native bridging Zap/2-1 and Zap/4-1
-- Hungup 'Zap/4-1'
== Spawn extension (internal, 6378447, 3) exited non-zero on 'Zap/2-1'
-- Hungup 'Zap/2-1'
-- Starting simple switch on 'Zap/2-1'
-- Executing [2560597 at internal:1] Answer("Zap/2-1", "") in new stack
-- Executing [2560597 at internal:2] Set("Zap/2-1", "CALLERID="house"
<2038447>") in new stack
-- Executing [2560597 at internal:3] Dial("Zap/2-1", "Zap/4/2560597")
in new stack
-- Called 4/2560597
[Feb 24 17:56:55] WARNING[9024]: chan_zap.c:4424 zt_handle_event:
Detected alarm on channel 4: Red Alarm
............
This is beta4.
Any help appreciated.
sean
_______________________________________________
-- 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
|
--
Dog is my co-pilot |
|
| Back to top |
|
|
seandarcy2 at gmail.com
Guest
|
| Posted: Sun Feb 24, 2008 7:17 pm Post subject: [asterisk-users] beta4: outgoing call causes Red Alarm on TD |
|
|
John Novack wrote:
| Quote: |
sean darcy wrote:
| Quote: | Calling out on PSTN over a TDM400P seems to generate a Red Alarm -
whatever that is.
|
Red Alarm USED to mean there was no battery on the line - assume this
references an FXO port connected to a PSTN POTS line.
|
Yes.
| Quote: | Is it possible Channel 4 is not connected?
|
But:
| Quote: | | Quote: | Sometimes it works, and then doesn't:
.............
-- Starting simple switch on 'Zap/2-1'
-- Executing [6378447 at internal:1] Answer("Zap/2-1", "") in new stack
-- Executing [6378447 at internal:2] Set("Zap/2-1", "CALLERID="house"
<2038447>") in new stack
-- Executing [6378447 at internal:3] Dial("Zap/2-1", "Zap/4/6378447")
in new stack
-- Called 4/6378447
-- Zap/4-1 answered Zap/2-1
-- Native bridging Zap/2-1 and Zap/4-1
-- Hungup 'Zap/4-1'
== Spawn extension (internal, 6378447, 3) exited non-zero on 'Zap/2-1'
-- Hungup 'Zap/2-1'
-- Starting simple switch on 'Zap/2-1'
-- Executing [2560597 at internal:1] Answer("Zap/2-1", "") in new stack
-- Executing [2560597 at internal:2] Set("Zap/2-1", "CALLERID="house"
<2038447>") in new stack
-- Executing [2560597 at internal:3] Dial("Zap/2-1", "Zap/4/2560597")
in new stack
-- Called 4/2560597
[Feb 24 17:56:55] WARNING[9024]: chan_zap.c:4424 zt_handle_event:
Detected alarm on channel 4: Red Alarm
........
|
|
sean |
|
| Back to top |
|
|
jfinstrom at rhinoequi...
Guest
|
| Posted: Sun Feb 24, 2008 7:38 pm Post subject: [asterisk-users] beta4: outgoing call causes Red Alarm on TD |
|
|
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sean,
I believe the alarm is generated by the bits flipping 1111.
In "kewl" 1111 is hangup so every time you hang-up you could
potentially alarm. I don't know what the timer delay is but I think
anything over a second would be safe otherwise you will see red alarms
but they will probably be more of an annoyance than a serious issue.
- --
James Finstrom
Rhino Equipment Corp.
All Rhino products are made in America, Come with a Money Back gurantee
and have a 5 Year warranty. Quality and Toughness built in!!
Phone: 1-800-785-7073 ~ FAX: +1 (480) 961-1826
IP: asterisk.rhinoequipment.com ~ FWD: 633686
THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received
this in error, please contact the sender and delete the email and its
attachments from all computers.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHwg4TdloC7YyaIOoRAhV5AJwLMLbl/3qwxljB8QDL8IqlbzaWZgCfZ2tr
/yKbisr+Xh2UIIy0Wr/VDUc=
=eoJl
-----END PGP SIGNATURE----- |
|
| Back to top |
|
|
tzafrir.cohen at xorco...
Guest
|
| Posted: Sun Feb 24, 2008 8:59 pm Post subject: [asterisk-users] beta4: outgoing call causes Red Alarm on TD |
|
|
On Sun, Feb 24, 2008 at 05:38:43PM -0700, James Finstrom wrote:
| Quote: | -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sean,
I believe the alarm is generated by the bits flipping 1111.
In "kewl" 1111 is hangup so every time you hang-up you could
potentially alarm.
|
That is: if the FXS uses KS, then upon hangup it will deny power for a
while. The FXO on the other side identifies this as if somebody
disconnected the wire, and is temporarily in alarm.
| Quote: | I don't know what the timer delay is but I think
anything over a second would be safe otherwise you will see red alarms
but they will probably be more of an annoyance than a serious issue.
|
Unless you actually want to keep the line open even upon recieving the
power denial. I can't think of a practical use for this.
--
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 Feb 24, 2008 11:10 pm Post subject: [asterisk-users] beta4: outgoing call causes Red Alarm on TD |
|
|
On Sun, Feb 24, 2008 at 7:38 PM, James Finstrom
<jfinstrom at rhinoequipment.com> wrote:
| Quote: | -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sean,
I believe the alarm is generated by the bits flipping 1111.
In "kewl" 1111 is hangup so every time you hang-up you could
potentially alarm. I don't know what the timer delay is but I think
anything over a second would be safe otherwise you will see red alarms
but they will probably be more of an annoyance than a serious issue.
|
Yes, the module uses kewlstart. But the next call you saw was a minute
or more later. In fact, now more 4 hours later I get the same error.
sean |
|
| Back to top |
|
|
seandarcy2 at gmail.com
Guest
|
| Posted: Tue Feb 26, 2008 6:33 pm Post subject: [asterisk-users] beta4: outgoing call causes Red Alarm on TD |
|
|
Tzafrir Cohen wrote:
| Quote: | On Sun, Feb 24, 2008 at 05:38:43PM -0700, James Finstrom wrote:
| Quote: | -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sean,
I believe the alarm is generated by the bits flipping 1111.
In "kewl" 1111 is hangup so every time you hang-up you could
potentially alarm.
|
That is: if the FXS uses KS, then upon hangup it will deny power for a
while. The FXO on the other side identifies this as if somebody
disconnected the wire, and is temporarily in alarm.
| Quote: | I don't know what the timer delay is but I think
anything over a second would be safe otherwise you will see red alarms
but they will probably be more of an annoyance than a serious issue.
|
Unless you actually want to keep the line open even upon recieving the
power denial. I can't think of a practical use for this.
|
I swapped to a different power connector for the card. Rebooted.
Still the same problem on the very first call after reboot.
Beginning to think this is a beta4 issue.
sean |
|
| Back to top |
|
|
seandarcy2 at gmail.com
Guest
|
| Posted: Tue Feb 26, 2008 9:42 pm Post subject: [asterisk-users] beta4: outgoing call causes Red Alarm on TD |
|
|
sean darcy wrote:
| Quote: | Tzafrir Cohen wrote:
| Quote: | On Sun, Feb 24, 2008 at 05:38:43PM -0700, James Finstrom wrote:
| Quote: | -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Sean,
I believe the alarm is generated by the bits flipping 1111.
In "kewl" 1111 is hangup so every time you hang-up you could
potentially alarm.
|
That is: if the FXS uses KS, then upon hangup it will deny power for a
while. The FXO on the other side identifies this as if somebody
disconnected the wire, and is temporarily in alarm.
| Quote: | I don't know what the timer delay is but I think
anything over a second would be safe otherwise you will see red alarms
but they will probably be more of an annoyance than a serious issue.
|
Unless you actually want to keep the line open even upon recieving the
power denial. I can't think of a practical use for this.
|
I swapped to a different power connector for the card. Rebooted.
Still the same problem on the very first call after reboot.
Beginning to think this is a beta4 issue.
|
Not beta4, but zaptel-1.4.8. zaptel svn 3883 solved it.
sean |
|
| 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
|
Search
