chan_dahdi doesn't hangup properly in some cases.

rsalgado

Joined
Jan 21, 2010
Messages
1
Likes
0
Points
0
#1
Hello everyone.

I'm having this issue:

Sometimes when a call is finishing it doesn't hungup and release the channel properly
or at least that's what Asterisk says.

The common messages while finishing a call are these:
[Jan 14 10:27:45] VERBOSE[408] logger.c: -- Executing [s@macro-hangupcall:11] Hangup("Zap/1-1", "") in new stack
[Jan 14 10:27:45] VERBOSE[408] logger.c: == Spawn extension (macro-hangupcall, s, 11) exited non-zero on 'Zap/1-1' in macro 'hangupcall'
[Jan 14 10:27:45] VERBOSE[408] logger.c: == Spawn h extension (macro-dial, h, 1) exited non-zero on 'Zap/1-1'
[Jan 14 10:27:45] VERBOSE[408] logger.c: == Spawn extension (macro-dial, s, 7) exited non-zero on 'Zap/1-1' in macro 'dial'
[Jan 14 10:27:45] VERBOSE[408] logger.c: == Spawn extension (macro-exten-vm, s, 9) exited non-zero on 'Zap/1-1' in macro 'exten-vm'
[Jan 14 10:27:45] VERBOSE[408] logger.c: == Spawn extension (from-internal-xfer, 505, 1) exited non-zero on 'Zap/1-1'
[Jan 14 10:27:45] DEBUG[408] chan_dahdi.c: Set option AUDIO MODE, value: ON(1) on Zap/1-1
[Jan 14 10:27:45] DEBUG[408] chan_dahdi.c: Not yet hungup... Calling hangup once with icause, and clearing call
[Jan 14 10:27:45] DEBUG[408] chan_dahdi.c: Set option AUDIO MODE, value: OFF(0) on Zap/1-1
[Jan 14 10:27:45] VERBOSE[408] logger.c: -- Hungup 'Zap/1-1'
[Jan 14 10:27:45] VERBOSE[3069] logger.c: Extension Changed 505[ext-local] new state Idle for Notify User 500

It seems there are no problems here. Actualy, the channel is available for the next call.

Sometimes I get this messages:
an 14 18:55:54] VERBOSE[1216] logger.c: -- Executing [s@macro-hangupcall:11] Hangup("SIP/500-0894edf0", "") in new stack
[Jan 14 18:55:54] VERBOSE[1216] logger.c: == Spawn extension (macro-hangupcall, s, 11) exited non-zero on 'SIP/500-0894edf0' in macro 'hangupcall'
[Jan 14 18:55:54] VERBOSE[1216] logger.c: == Spawn h extension (macro-dialout-trunk, h, 1) exited non-zero on 'SIP/500-0894edf0'
[Jan 14 18:55:54] DEBUG[1216] chan_dahdi.c: Set option AUDIO MODE, value: ON(1) on Zap/1-1
[Jan 14 18:55:54] DEBUG[1216] chan_dahdi.c: Set option AUDIO MODE, value: OFF(0) on Zap/1-1


So... the difference seems to be this line:
chan_dahdi.c: Not yet hungup... Calling hangup once with icause, and clearing call
between
chan_dahdi.c: Set option AUDIO MODE, value: ON(1) on Zap/1-1
and
chan_dahdi.c: Set option AUDIO MODE, value: OFF(0) on Zap/1-1

When log doesn't show that line... next outgoing calls always get an acoustic busy-channel-answer.
However, incoming calls work perfectly.
It requires to restart asterisk (using "amportal restart" ) to get it working back.

The system is using a common Elastix but BRIstuffed (BRIstuffed-0.4.0-RC3g) and asterisk 1.4.26.1.
I am leaving this message to BRIstuff developers too because I don't really know which is responsible
for this error.

Thank you for your answers.
 

james.zhu

Joined
Feb 13, 2008
Messages
99
Likes
0
Points
6
#2
hi:
suggest you changing to mISDN to try.
 

Siu

Joined
Jan 15, 2010
Messages
30
Likes
0
Points
0
#3
in the "chan_dahdi.conf" use below
busydetect=yes
busycount=5
 

dicko

Joined
Oct 24, 2008
Messages
4,099
Likes
0
Points
0
#4
Siu said:
in the "chan_dahdi.conf" use below
busydetect=yes
busycount=5
This advice is only appropriate for analog trunks (FXO) and only then when needed. ISDN is by definition not analog. These settings might well hangup a channel, but for completely the wrong reason, don't waste your time messing with them. All call setup and teardown is handled in the D channel (data channel)
 

james.zhu

Joined
Feb 13, 2008
Messages
99
Likes
0
Points
6
#5
yes, there is nothing related with busydetect for isdn.
 

saleh

Joined
Apr 18, 2007
Messages
249
Likes
0
Points
0
#6

Members online

No members online now.

Latest posts

Forum statistics

Threads
30,913
Messages
130,917
Members
17,589
Latest member
cristian.saiz
Top