I've reported this issue as a bug, and learned that a workaround seems to be
disabling callwaiting :(. Since callwaiting was quite helpful on my systems,
I'm not happy with this.
Anyone interested can go to issue tracer and follow if a fix will be
released soon (ID# 0005188).
I really tend
I've been monitoring this problem for almost a month now. I realized that it
is more extensive than what I described previously. I can very easily
replicate this problem on every Zap channel. Following is the senario:
1. Call Zap/5 via say SIP/15 -
Zap/5-1 created and starts to ring
2. Call
I can replicate this issue on my test system with 1x FXS module too:
-- Executing Dial(SIP/202-ea85, ZAP/1|15|tr) in new stack
-- Called 1
-- Zap/1-1 is ringing
-- Zap/1-1 is ringing
-- Executing Dial(SIP/201-bf73, ZAP/1|15|tr) in new stack
-- Called 1
-- Zap/1-2 is ringing
I really tend to think that there is a bug in chan_zap.c, because this issue
happens only when the first caller hangs up first, never the otherwise. I
mean if the second caller hangs up first, the first caller continues as
usual without any problems and reaches to the VoiceMail system as
