Home » Forums » Community Edition » Trunks

Issues with busy tone detection.

mickwilli
Posts: 33
 Member Since:
2007-02-07
Submitted by mickwilli on Thu, 04/15/2010 - 2:44am.

Hi all,

This is a continuation of the problem described here: http://trixbox.org/forums/trixbox-forums/help/odd-incoming-call-p...

Most specific problem relates to trixbox / asterisk incorrectly detecting the ringing tone from an incoming call as a 'busytone' and then attempts to hangup the line. As you can imagine this is most annoying. Turning the "busydetect" feature off stops this problem, but as currently I don't have the option of using a polarity switch for hangup detection (because TelstraClear are useless) then I need this feature.
As far as I can tell I have localised the Zapata card as best I can (I an in New Zealand) but I can't seam to remember which config file I edited to change that, so maybe best to check.

Does anyone have any ideas why this might be happening? I understand that the busydetect feature is not an exact science and that I would be far better off using a polarity reversal feature instead, but like I said, that currently isn't an option.

Any help would be much appreciated.
Michael

‹ Outbound calling Baring outgoing CID on a per call basis ›


Kbedford
Posts: 187
 Member Since:
2008-06-12
To get everything localised
Thu, 04/15/2010 - 8:05am

To get everything localised for the same card in Australia I had to change two files

/etc/modprobe.conf
and add
options wctdm24xxp opermode=AUSTRALIA fxshonormode=1 boostringer=1

in your case

options wctdm opermode=NEWZEALAND honormode=1 boostringer=1 fastringer=1

also /etc/zaptel.conf
loadzone = au
defaultzone = au

once you change /etc/modprobe.conf you need to remove and re insert the module, the lazy way to do this is re start the system.

basically if its right dmesg should show your version of

Port 3: Installed -- AUTO FXO (AUSTRALIA mode)
Port 4: Installed -- AUTO FXO (AUSTRALIA mode)
VPM100: Not Present
Found a Wildcard TDM: Wildcard TDM410P (4 modules)

Check it out and see what happens



mickwilli
Posts: 33
 Member Since:
2007-02-07
Hmm More Clarification
Thu, 04/15/2010 - 2:07pm

I have changed /etc/modprobe.conf and added this line to the bottom of the file "options wctdm opermode=NEWZEALAND honormode=1 boostringer=1 fastringer=1" and I have added the two entries you recommended into the /etc/asterisk/chan_dahdi.conf (I am running version 2.6.2.3 and there is not zaptel.conf file as it was replaced with the one mentioned). I had to add those parameters as there were not already in the file. Was that to be expected.
In the file is also "language=en". I don't know what this parameter does, is this one I should be editing?

The output of dmesg is:
Port 1: Installed -- AUTO FXO (FCC mode)
Port 2: Installed -- AUTO FXO (FCC mode)
Port 3: Installed -- AUTO FXO (FCC mode)
Port 4: Not installed
VPM100: Not Present

I also noticed this message in the output... "wctdm: Unknown parameter `honormode'".
Can anybody help any more with the correct localisation procedure for this setup.

Thanks,
Michael



Kbedford
Posts: 187
 Member Since:
2008-06-12
"language=en" means language
Thu, 04/15/2010 - 4:43pm

"language=en" means language is English which I assume is what you would want.

Port 1: Installed -- AUTO FXO (FCC mode) Indicates that it is still in American mode most likely it ignored the options when loading the module because honormode should be fxshonormode as in the above version in my previous post sorry I messed that up.

the "au" in
loadzone = au
defaultzone = au

Means Australia

You need to use

loadzone = nz
defaultzone = nz

Again because you need to edit modprobe.conf a restart is probably easiest then check dmesg to see if anything changed.



mickwilli
Posts: 33
 Member Since:
2007-02-07
Got it localised, but it hasn't helped.
Thu, 04/15/2010 - 6:04pm

It looks like I have managed to get it localised.

Here is the output:
Port 1: Installed -- AUTO FXO (NEWZEALAND mode)
Port 2: Installed -- AUTO FXO (NEWZEALAND mode)
Port 3: Installed -- AUTO FXO (NEWZEALAND mode)
Port 4: Not installed
VPM100: Not Present

I have also edited /etc/dahdi/system.conf where I found both loadzone and defaultzone parameters which I have altered as below:
loadzone=nz
defaultzone=nz

This however has not fixed the problem. The phones still ring for a quantity of times (about 8 PSTN rings, which is the same as busycount) then they stop ringing. The external line remains ringing the whole time.

I think from what I can tell, this is the part of the log when the phones stop ringing:
[Apr 16 13:01:00] VERBOSE[2715] logger.c: -- SIP/201-0000000e is ringing
[Apr 16 13:01:01] VERBOSE[2721] logger.c: -- SIP/200-0000000f is ringing
[Apr 16 13:01:07] VERBOSE[2715] logger.c: == Spawn extension (macro-dial, s, 7) exited non-zero on 'DAHDI/1-1' in macro 'dial'
[Apr 16 13:01:07] VERBOSE[2715] logger.c: == Spawn extension (ext-group, 600, 13) exited non-zero on 'DAHDI/1-1'
[Apr 16 13:01:07] VERBOSE[2715] logger.c: -- Hungup 'DAHDI/1-1'
[Apr 16 13:01:07] VERBOSE[2718] logger.c: == Spawn extension (macro-dial, s, 7) exited non-zero on 'Local/200@from-internal-ab17;2' in macro 'dial'
[Apr 16 13:01:07] VERBOSE[2718] logger.c: == Spawn extension (from-internal, 200, 16) exited non-zero on 'Local/200@from-internal-ab17;2'
[Apr 16 13:01:07] VERBOSE[2721] logger.c: == Spawn extension (macro-dial, s, 7) exited non-zero on 'Local/FMPR-200@from-internal-a431;2' in macro 'dial'
[Apr 16 13:01:07] VERBOSE[2721] logger.c: == Spawn extension (macro-simple-dial, s, 6) exited non-zero on 'Local/FMPR-200@from-internal-a431;2' in macro 'simple-dial'
[Apr 16 13:01:07] VERBOSE[2721] logger.c: == Spawn extension (from-internal, FMPR-200, 5) exited non-zero on 'Local/FMPR-200@from-internal-a431;2'

Hopefully someone else can shed some more light on the subject, I don't understand what's happening.



Kbedford
Posts: 187
 Member Since:
2008-06-12
Assuming the call going
Fri, 04/16/2010 - 4:54am

Assuming the call going unanswered isn't causing some feature in your dial plan to hang up the call say due to a ring group timeout or something.

Have you listened to the ringing signal both as a caller and with a standard phone connected to the line. The reason I mention this is that Telstra (in Australia) if you use their message bank service, alter the ring tone on the line to tell you there are messages waiting.

Something interesting I discovered recently while connecting a phone line with such a service enabled to an Asterisk system was that Asterisk picking up the line grabbing callerid and ringing internal phones while it generated a ring tone back to the caller didn't stop the external message service grabbing the call at it's specified time even though the call had theoretically been answered. My only reasoning for this is that the exchange also being digital couldn't tell the difference between its own ring tone and the one generated by Asterisk.



mickwilli
Posts: 33
 Member Since:
2007-02-07
I don't think so.
Fri, 04/16/2010 - 5:30am

When I deactivate the busydetect feature then the call is handled as expected, with the call eventually going to voicemail as defined.
I have a fax machine connected directly to the same line as it uses fax ability so it grabs faxes before the phone system rings (usually) so I turned the ringer noise back on for that and it rings as normal. I have also tested with different phone lines and without the fax and this doesn't make any difference. And with the telephone system Telcom employ in New Zealand, who knows what mischeif might be going on in the exchange, but from the callers point of view (having called myself many times recently in the last few days) it sounds as if the call is ringing normally.

My theory is simply that Asterisk, or the Zapatel card is detecting the ringing tone as a 'busytone' and after 8 rings (which is the busycount number) tries to hangup the line. Since the line is ringing it can't hang it up, so suddenly it notices again that the line is ringing and starts the dial plan again, this time however it doesn't have caller ID (I assume this is related to the phone exchange only sending the Caller ID once when the call first starts ringing?).
If my theory is correct, then what would cause this?
Is there any way to check to see if the localisation settings are actually correct. Does Trixbox contain settings for a NewZealand mode at all?

Thanks for your continuing help.



Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.