Summary:	ASTERISK-11137: tonezone=au causes incorrect tones to be dialed.
Reporter:	hterag (hterag)	Labels:
Date Opened:	2008-01-02 00:03:00.000-0600	Date Closed:	2011-06-07 14:02:55
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Channels/chan_zap
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	I updated to SVN r95577 and zaptel 3584 Dialing out would then produce a telco messdage saying the number was unavailable. correct number being dialed in dialplan and incoming calls unaffected Listening with zapscan the tones generated at dialing time sound weird (unusually high tones). If I set tonezone=us it works again but setting back to tonezone=au causes it to break again.
Comments:	By: Tzafrir Cohen (tzafrir) 2008-01-02 06:18:48.000-0600 Am I correct to assume that this is chan_zap (Zaptel devices)? What device? Have you set tonezone=au in indications.conf ? Do you use the sample one? Or otherwise one with the "au" tones as in the sample one? By: hterag (hterag) 2008-01-02 16:12:11.000-0600 You assume correctly, 2 x wildcard tdm400p. I checked indications.conf and it looked correct (was an older sample version) I copied over the newer sample one from the SVN tree and made sure country=au timezone=au was set in indications.conf. When I change zaptel.conf back to loadzone=au asterisk can no longe dial correct tones (i.e.The behaviour did not change). By: Tilghman Lesher (tilghman) 2008-01-03 18:06:13.000-0600 Okay, I'm confused.  If using tonezone=us works for you, why is this a major bug? By: hterag (hterag) 2008-02-05 03:38:07.000-0600 Well I have tried to replicate this on another system and I have could not I guess if no one else using tonezone=au is having this problem and the us setting is working in au then its not an issue must jst be soemthing weird on this system By: Joshua C. Colp (jcolp) 2008-02-05 09:08:38.000-0600 Closed per comment from reporter.