[App_rpt] app_rpt.c test version 0-46-6
Well, I decided I didn't like the way the autopatch default overrides (patchfarenddisconnect, patchnoct, patchdialtime) were implemented in app_rpt.pre-0-46-4.c so I ripped them out and started over. This method provides much more flexibility. Instead of specifying settings in the node configuration block, you now override the defaults in the function block for autopatch up. In other words, autopatchup can can optionally take comma delimited setting=value pairs. There are currently 5 setting=value pairs defined in app_rpt.pre-0-46-6.c: context=string Override default context with "string" dialtime=ms Specify the max number of milliseconds between phone number ) farenddisconnect=1 Automatically disconnect when called party hangs up noct=1 Don't send repeater courtesy tone during autopatch calls quiet=1 Don't send dial tone, or connect messages. Do not send patch down message when called party hangs up Example: 123=autopatchup,dialtime=20000,noct=1,farenddisconnect=1 The example will set a 20 second limit on dial time between phone number digits, not send the courtesy tone during the time the patch is up, and disconnect the patch if the called party hangs up. By redoing this, we gain a whole bunch more flexibility because we can define several different DTMF sequences for autopatchup which can direct the autopatch to act differently. By defining 3 different patch up sequences, you can now for example, have one for emergency numbers, one for normal numbers, and one for system information messages. You can set the individual autopatch up sequences to use different contexts which can then be added to extensions.conf. Note: I did not remove the autopatch up and down messages from the telemetry block. These are still there so that you can override the default up and down messages. app_rpt.pre-0-46-6c can be downloaded from http://zapatatelephony.com using the following URL: http://zapatatelephony.com/app_rpt.pre-0-46-6.c Note: are running asterisk 1.2.7.1 or earlier, you will need to uncomment the #define for OLD_ASTERISK at the top of the file. Steve WA6ZFT
URL not found... is it in SVN? Eric NI3S Steve Rodgers wrote:
Well, I decided I didn't like the way the autopatch default overrides (patchfarenddisconnect, patchnoct, patchdialtime) were implemented in app_rpt.pre-0-46-4.c so I ripped them out and started over.
This method provides much more flexibility. Instead of specifying settings in the node configuration block, you now override the defaults in the function block for autopatch up. In other words, autopatchup can can optionally take comma delimited setting=value pairs.
There are currently 5 setting=value pairs defined in app_rpt.pre-0-46-6.c:
context=string
Override default context with "string"
dialtime=ms
Specify the max number of milliseconds between phone number )
farenddisconnect=1
Automatically disconnect when called party hangs up
noct=1
Don't send repeater courtesy tone during autopatch calls
quiet=1
Don't send dial tone, or connect messages. Do not send patch down message when called party hangs up
Example: 123=autopatchup,dialtime=20000,noct=1,farenddisconnect=1
The example will set a 20 second limit on dial time between phone number digits, not send the courtesy tone during the time the patch is up, and disconnect the patch if the called party hangs up.
By redoing this, we gain a whole bunch more flexibility because we can define several different DTMF sequences for autopatchup which can direct the autopatch to act differently. By defining 3 different patch up sequences, you can now for example, have one for emergency numbers, one for normal numbers, and one for system information messages. You can set the individual autopatch up sequences to use different contexts which can then be added to extensions.conf.
Note: I did not remove the autopatch up and down messages from the telemetry block. These are still there so that you can override the default up and down messages.
app_rpt.pre-0-46-6c can be downloaded from http://zapatatelephony.com using the following URL:
http://zapatatelephony.com/app_rpt.pre-0-46-6.c
Note: are running asterisk 1.2.7.1 or earlier, you will need to uncomment the #define for OLD_ASTERISK at the top of the file.
Steve WA6ZFT
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
-- Eric Tichansky Administrator LYLIX.NET http://lylix.net/ (724) 602-2264
Eric, Yes app_rpt version 0.46 is in Digium SVN as revision 29935 or later. Better to use the the released version as it has a notch filtering feature as well. Steve. On Monday 05 June 2006 17:12, Eric Tichansky wrote:
URL not found... is it in SVN?
Eric NI3S
Steve Rodgers wrote:
Well, I decided I didn't like the way the autopatch default overrides (patchfarenddisconnect, patchnoct, patchdialtime) were implemented in app_rpt.pre-0-46-4.c so I ripped them out and started over.
This method provides much more flexibility. Instead of specifying settings in the node configuration block, you now override the defaults in the function block for autopatch up. In other words, autopatchup can can optionally take comma delimited setting=value pairs.
There are currently 5 setting=value pairs defined in app_rpt.pre-0-46-6.c:
context=string
Override default context with "string"
dialtime=ms
Specify the max number of milliseconds between phone number )
farenddisconnect=1
Automatically disconnect when called party hangs up
noct=1
Don't send repeater courtesy tone during autopatch calls
quiet=1
Don't send dial tone, or connect messages. Do not send patch down message when called party hangs up
Example: 123=autopatchup,dialtime=20000,noct=1,farenddisconnect=1
The example will set a 20 second limit on dial time between phone number digits, not send the courtesy tone during the time the patch is up, and disconnect the patch if the called party hangs up.
By redoing this, we gain a whole bunch more flexibility because we can define several different DTMF sequences for autopatchup which can direct the autopatch to act differently. By defining 3 different patch up sequences, you can now for example, have one for emergency numbers, one for normal numbers, and one for system information messages. You can set the individual autopatch up sequences to use different contexts which can then be added to extensions.conf.
Note: I did not remove the autopatch up and down messages from the telemetry block. These are still there so that you can override the default up and down messages.
app_rpt.pre-0-46-6c can be downloaded from http://zapatatelephony.com using the following URL:
http://zapatatelephony.com/app_rpt.pre-0-46-6.c
Note: are running asterisk 1.2.7.1 or earlier, you will need to uncomment the #define for OLD_ASTERISK at the top of the file.
Steve WA6ZFT
_______________________________________________ App_rpt mailing list App_rpt@lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt
Super. Just built version 0.47 from SVN on my Asterisk 1.2.5 system. The new autopatch features are excellent additions! Thumbs up! I finally acquired two mini HTs (2M and 440) from a recent local hamfest, and have been able to do alot of testing. Between the additional duplex states and the new autopatch features, the system is quite robust and fits the bill perfectly. It is nice to be able to run a full duplex autopatch w/o RX audio injection to the transmit side. Great work. Eventually we plan to setup remote links to another app_rpt enabled repeater for greater coverage. Eric NI3S Steve Rodgers wrote:
Eric,
Yes app_rpt version 0.46 is in Digium SVN as revision 29935 or later. Better to use the the released version as it has a notch filtering feature as well.
Steve.
-- Eric Tichansky Administrator LYLIX.NET http://lylix.net/ (724) 602-2264
participants (2)
-
Eric Tichansky -
Steve Rodgers