[This email is reposted without the log attaced. I have added more
information to the end of this email as well]
CVS head (unmodified) current as of today.
We have asterisk connected to both the pstn and our pbx via two E1 pri
connections. We use overlap dialing to cope with different number lengths
in Sweden.
Incoming calls work perfectly.
Outgoing calls seem to not get the repsonse it expects since the pbx does
not see that it is connected properly (it does not open it's microphone
path until an internal timer expires.
I have taken a log with "pri intense debug" on first the internal
(pbx)
span and then the externa (pstn) doing the same call both times. The call
is initiated from span 2 (the pbx), goes out span 1, comes back in span 1
on another channel and is finally forwarded back to span 2. The log is
available from
http://www.psv.nu/jbl/problemlog.txt
Asterisk receives a CONNECT (line 1427 in the log) for the outgoing leg on
the pstn span. That connect was originally sent when the incoming leg to
the pbx answered. It does not get delivered to the originating span (the
pbx). It sees neither the call proceeding, alerting or any other of the
indications that should have been sent.
This causes the originating channel not to be in state AST_STATE_RINGING
in ast_answer() called from ast_bridge_call(). The answer does not get
propagated down to the originating channel.
**** further digging *****
The problem apperas to be that the ALERTING indication from the pbx on the
inbound leg is not propagated back up to the inbound leg from the pstn.
The error is on the inbound leg.
The pbx inbound (terminating) leg sends
CALL PROCEEDING
ALERTING
CONNECT
but asterisk passes the following to the inbound pstn leg:
CALL PROCEEDING
PROGRESS
CONNECT
I can not figure out how the ALERTING is handled. If I understand the flow
correctly app_dial should eventually call zt_indicate in chan_zap.c. I
fail to see how it should send the ALERTING indication.
Peter
