OK guys I'm glad you have found out what was wrong - this has been a
real problem for me for the last few months. Thank you.
But it's still fairly untidy as far as I can see.
Scenario: Single BRI line with two channels. One channel open with an
outgoing call.
Call in through second channel to dialplan that attempts to dial out to
a mobile.
[Nov 13 13:41:13] WARNING[14501]: app_dial.c:1242 dial_exec_full: Unable
to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion)
-- Correct - busy
[Nov 13 13:41:17] ERROR[14501]: chan_dahdi.c:2798 dahdi_hangup: What is
wrong with you? You cannot use cause 34 number when in state 6!
-- Odd message. Channel state is INUSE (6) and could therefore be
busy surely? Not just ringing or whatever the other approved cases are.
[Nov 13 13:41:17] WARNING[14484]: chan_dahdi.c:8706 pri_fixup_principle:
Call specified, but not found?
[Nov 13 13:41:17] WARNING[14484]: chan_dahdi.c:9823 pri_dchannel: Hangup
on bad channel 0/2 on span 1
-- Is this just untidy or a real error? Relating to closing down the
channel we tried to open I suppose.
[Nov 13 13:41:22] WARNING[14484]: chan_dahdi.c:8706 pri_fixup_principle:
Call specified, but not found?
[Nov 13 13:41:22] WARNING[14484]: chan_dahdi.c:9823 pri_dchannel: Hangup
on bad channel 0/2 on span 1
--- Now why all these errors? Relating to closing down the incoming
channel I assume. A perfectly correct sequence of actions has been
taken. Admittedly the channel is not incorrectly marked as in use any more.
Is there more of a fix? Or am I the only one getting this?
_______________________________________________
Bristuff-users mailing list
[email protected]
http://lists.three-dimensional.net/mailman/listinfo/bristuff-users
