Zapata.conf options, what do they mean?


I’m trying to figure out why the flash ® key on my phone is not recognized (connected to a TDM400 card).

On … apata.conf i find this list of options:
prewink: Sets the pre-wink timing.
preflash: Sets the pre-flash timing.
wink: Sets the wink timing.
rxwink: Sets the receive wink timing.
rxflash: Sets the receive flash timing.
flash: Sets the flash timing.
start: Sets the start timing.
debounce: Sets the debounce timing.

Can someone explain me what they do and how i could use them to get the key recognized? I see something happening when i set rxflash=110, then instead of no reaction, the flash-button hangs up the current line and gives me a new dialtone. So it looks to me that in that case, it’s recognizing the flash-button as a hangup. Any ideas?

The solution to my problem turned out to be one level lower: The zaptel driver recognized my flash key as a pulse dial 1. American phones seem to have a longer flash time then some European phones.

Changing ZT_MAXPULSETIME in zaptel-*/kernel/zaptel.h to 80ms and recompiling zaptel solved the problem.

But i still don’t know what all these zapata.conf options mean!

Register recall on UK PBX phones is normally done by earthing the B? leg.

The timed break recall used on the UK PSTN is a pulse dialled digit 1!

Well. i think it’s not exactly the same as a pulse dial 1 because they make the same physical shortcut, but not for the same amount of milliseconds…

At least that’s what it looks like om my ancient T65 pulse phone.

For BT, timed break recall is anywhere between 53 and 102 ms and a nominal, loop disconnect, digit 1 is 67ms. (SIN 351)