[asterisk-bugs] [Asterisk 0013824]: pulsedial=yes does not work

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13824 
====================================================================== 
Reported By:                ajlill
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13824
Category:                   Channels/chan_zap
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.4.21.2 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-11-02 13:20 CST
Last Modified:              2008-11-03 19:05 CST
====================================================================== 
Summary:                    pulsedial=yes does not work
Description: 
Setting pulsedial=yes in zapata.conf does not work. I added debugging
statements in process_zap and the file is being parsed properly, and the
field  confp->chan.pulse is being set correctly. However, the value is
being reset to 0 somewhere, and so it only tries to tone dial. I added an
extra line so 'zap show channel' will print the value of that field, and it
is 0.

This is on Debian Etch. When I was using 1.2.x, it worked fine.
====================================================================== 

---------------------------------------------------------------------- 
 (0094532) ajlill (reporter) - 2008-11-03 19:05
 http://bugs.digium.com/view.php?id=13824#c94532 
---------------------------------------------------------------------- 
If I could place a call on that PSTN line, I wouldn't be opening a bug
report, now would I ?-} When you say it works for you, does that mean it
placed a call, or that you actually verified that it was pulsing.

In spite of the stupid names for those variables, I haven't confused them.
As an aside, since you've done an s/zt/dahdi/g between .21 and .22, how
about renaming those variables to something less confusing, like
pulsehandset and pulsetrunk.

As I said in in my original report, I ADDED a line of output to 'zap show
channel' to display the pulse variable. I also have debug output that shows
the dop.dialstr being constructed as T#######w instead of P#######w, and I
have a handset on that trunk so I could listen to it try to tone dial. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-03 19:05 ajlill         Note Added: 0094532                          
======================================================================