Summary:ASTERISK-01884: wrong channel state for outgoing calls on Zap
Reporter:Ryan Courtnage (rcourtna)Labels:
Date Opened:2004-06-24 13:22:11Date Closed:2008-01-15 15:00:39.000-0600
Versions:Frequency of
Environment:Attachments:( 0) zapata.conf
Description:Using the latest CVS for Asterisk and Zaptel, I make an outgoing (Zap) call from a SIP phone.  When the call is connected, issuing "show channels" at the * CLI will report the State for the Zap channel to be 'Dialing' and the SIP channel to by 'Ring'.

*CLI> show channels
       Channel  (Context    Extension    Pri )   State Appl.         Data
       Zap/3-1  (from-pstn  s            1   ) Dialing AppDial       (Outgoing Line)
  SIP/204-0497  (from-internal 92442790     1   )    Ring Dial          ZAP/g0/2442790||
2 active channel(s)

As a result, the proper SIP headers are not sent to phones. Some phones (ie: UIP200), will drop calls after a few minutes.

This problem does not exist in * build from BEFORE June 1, 2004


Here is a snippet of the context we are dialing out from:

ignorepat => ${DIAL_OUT}
exten => _${DIAL_OUT}NXXXXXX,1,Dial(${OUT}/${EXTEN:1},,)
exten => _${DIAL_OUT}NXXXXXX,2,Congestion
exten => _${DIAL_OUT}NXXXXXX,102,Macro(outisbusy)
exten => _${DIAL_OUT}NXXNXXXXXX,1,Dial(${OUT}/${EXTEN:1},,)
exten => _${DIAL_OUT}NXXNXXXXXX,2,Congestion
exten => _${DIAL_OUT}NXXNXXXXXX,102,Macro(outisbusy)
Comments:By: Ryan Courtnage (rcourtna) 2004-06-24 13:31:59

This is using a TDM400p with FXO modules.

By: twisted (twisted) 2004-06-24 13:53:17

I do not see how this is a MAJOR bug since it does not impact the performance of the system.  I have reassesed as 'minor'.  Please make note that MAJOR bugs are bugs that impact the performance of asterisk, CRASH are bugs that crash the system, and BLOCK are bugs that block operation of one or more components of the system.

The system in refrence is asterisk, but could be it's affect on the system as a whole.

By: Mark Spencer (markster) 2004-06-25 09:42:58

Are you using call progress?  Attach (do not paste as a bugnote) your zapata.conf

By: Ryan Courtnage (rcourtna) 2004-06-25 09:53:30

Mark, call progress is not being used.

Out of pure luck, someone stumbled across a different issue, which is related.

Having faxdetect=both in zapata.conf will cause the issue I describe above:

On Friday 25 June 2004 07:39, Andrew Yager wrote:
> The problem seems to be that when faxdetect is set in zapata.conf,
> asterisk does not inform the sip phones that a voice call has started
> actually been answered.

I've been plaqued by a different problem in CVS HEADs since June 2 - turns out, it's the same problem!

Andrew, try this:

With faxdetect enabled ('both' or 'incoming'), make an SIP->ZAP->PSTN call.
While that call is active, type 'show channels' at the * CLI.

You will see the STATE of your ZAP and SIP channels are reported incorrectly as DIALING and RING (the state whould be UP).

I was having a problem where Uniden phones would drop any call with the PSTN after 3 minutes - cuz they didn't realize that they were on a call.

The problem was introduced sometime shortly after CVS-D2004.06.02.

By: yogel (yogel) 2004-06-25 17:26:49

I'm experiencing the same problem. With faxdetect set, all of our phones remain in the ringing state on an outgoing call. This prevents us from placing the call on hold, transferring or doing anything except hanging up.

The output of show channels in the asterisk CLI reads:

       Channel  (Context    Extension    Pri )   State Appl.         Data          
       Zap/1-1  (incoming   s            1   ) Dialing AppDial       (Outgoing Line)
 SIP/1000-8ab9  (local      <phone number>   1   )    Ring Dial          Zap/1/<phone number>||m

during an active call.

Incoming calls function correctly. Calls between SIP phones function correctly. Calls to the FXS interfaces (with no faxdetect options set) on the Zaptel card also function correctly.

I will attach my zaptel.conf

I did not experience this problem prior to upgrading to CVS yesterday. I'm not sure which version we were using prior, but it was CVS head from around the end of may.

By: Mark Spencer (markster) 2004-06-25 17:31:17

Fixed in CVS head

By: yogel (yogel) 2004-06-25 17:48:38

Reminder sent to markster


I can't add anything to this bug now that it has been marked as resolved, and wanted to avoid creating a new bug.

It hasn't yet been fixed. I just checked out the head asterisk tree, and the behaviour is still the same. The call never moves out of the ringing state.


By: Digium Subversion (svnbot) 2008-01-15 15:00:39.000-0600

Repository: asterisk
Revision: 3308

U   trunk/channels/chan_zap.c

r3308 | markster | 2008-01-15 15:00:39 -0600 (Tue, 15 Jan 2008) | 2 lines

Don't munge outgoing call progress when fax enabled (bug ASTERISK-1884)