Advisory To change the courtesy tones from defaults it is necessary to have a telemetry=telemetry statement defined in each node configuration block in rpt.conf The default configuration files distributed with asterisk DO NOT have this statement in them. If the statement is left out, the courtesy tone lists in rpt.conf in the telemetry section will never be read in, and the defulat settings in app_rpt.c will always be used. Steve. ---------- Forwarded Message ---------- Subject: RE: Test results - Found the problem? Date: Tuesday 10 October 2006 20:38 From: "Gary" <gary@tcomeng.com> To: "'Steve Rodgers'" <hwstar@rodgers.sdcoxmail.com> By looking at the code you referenced I discovered the possible need for a 'telemetry = telemetry' statement in the node definition. As soon as I added that line the tones changed from default to the ones defined in the config file. I am going to assume this was the problem and it is supposed to work that way so you can define different telemetry for each node? FYI my sample config did not have that line in it and there is no reference I have found indicating it is required. Thanks for your help. Gary
-----Original Message----- From: Steve Rodgers [mailto:hwstar@rodgers.sdcoxmail.com] Sent: Tuesday, October 10, 2006 7:30 PM To: Gary Cc: telesistant@hotmail.com Subject: Re: Test results
Gary,
If you don't mind trying your hand at a little programming and "foop/feep" debugging, maybe a few judicious ast_log(LOG_WARNING, "foop"); statements might tell what is going on with app_rpt on your system. Save a copy of the app_rpt_055_pre.c file first so that you have something to go back to.
Adding an ast_log(LOG_WARNING,"foop"); between line 2301 and 2302 will tell you if the [telemetry] block was found in the config file.
Adding an ast_log(LOG_WARNING,"feep"); between line 2312 and 2313 of app_rpt_055_pre.c will tell you whether the telemetry entry in the file is being loaded or the default value was taken instead.
The function telem_lookup() is called whenever a telemetry event is occuring. You should see both foop and feep on the Asterisk console every time you unkey if the entries in the file are being used
Steve.
On Tuesday 10 October 2006 18:41, you wrote:
FYI, I tried it on a third node and it does the same thing. I can select any app_rpt.c pre-defined tone set, but cannot
define a new
tone set via rpt.conf.
This is not a big problem as I will just change app_rpt.c
to the tones I
want to use.
Gary
-----Original Message----- From: Steve Rodgers [mailto:hwstar@rodgers.sdcoxmail.com] Sent: Tuesday, October 10, 2006 6:55 AM To: Gary Cc: telesistant@hotmail.com Subject: Re: Test results
Gary,
Please try this version of app_rpt.c and let me know what the results are? This is the version I did the CT test on my system with. Also, could you tell me what version you are running on your system?
BTW: I'm also using asterisk 1.2.11 as well.
Steve, WA6ZFT
On Monday 09 October 2006 22:41, you wrote:
Test results are consistant.
I have two nodes and they both exhibit the same results.
Both built from
the same source files. Could I have bad source? I am using
asterisk 1.2.11
if that matters.
Gary
-----Original Message----- From: Steve Rodgers [mailto:hwstar@rodgers.sdcoxmail.com] Sent: Monday, October 09, 2006 10:09 PM To: Gary Subject: Re: Quad PCI pricing?
Gary, see my responses below:
On Monday 09 October 2006 21:07, you wrote:
Can you let me know what the Ham pricing is on the Quad
PCI cards?
The ham discount is 35% from the list price of $895.00 or $581.75 plus $20.00 shipping and handling.
Please confirm this board is required for controlling the
Yasue FT897 radio
and that a PC serial port is not supported?
The currently released app_rpt.c does not support PC serial port for FT897 control. The "bleeding edge" version as we call it, does support sending commands to the FT897 over a PC serial port, but it is not ready for general release as we speak at this moment.
If you don't mind a 'rough' version, wait a few days and it will be in a form we can give out for testing.
Also, regarding the problems with the CT telemetry:
Would you mind going back to the default config file trying it tout, then trying to modify a courtesy tone setting to see if that fixes your courtesy tone issue?
Steve.
-------------------------------------------------------