[App_rpt-users] XIPAR question
Lu Vencl
vencl at att.net
Mon Nov 11 18:01:28 UTC 2013
Hmm, I will have to try that one. Thanks for the idea. Will report back my findings later tonight.
From: Johnny Keeker [mailto:cypresstower at yahoo.com]
Sent: Sunday, November 10, 2013 11:19 AM
To: Corey Dean; Lu Vencl; 'Kevin Custer'; 'App_rpt Users'
Subject: Re: [App_rpt-users] XIPAR question
I am no code guy, but I thought I would compared the app_rpt.c from acid to xipar just to amuse myself.
acid has the eannmode = 0 referenced in the code, xipar did not, but refered to eannmode= 1 through 3.
Just a thought, have you commented out the eannmode=x line? Shot in the dark of course...
I will be amazedd if that works. I think the default setting is earnnmode=1 but again, Im no code guy.
JK
From: Corey Dean <n3fe at repeater.net <mailto:n3fe at repeater.net> >
To: Lu Vencl <vencl at att.net <mailto:vencl at att.net> >; 'Johnny Keeker' <cypresstower at yahoo.com <mailto:cypresstower at yahoo.com> >; 'Kevin Custer' <kuggie at kuggie.com <mailto:kuggie at kuggie.com> >; 'App_rpt Users' <app_rpt-users at ohnosec.org <mailto:app_rpt-users at ohnosec.org> >
Sent: Sunday, November 10, 2013 1:15 AM
Subject: RE: [App_rpt-users] XIPAR question
Lu,
On Xipar, why don’t you just create an allow list of people you want to allow to connect in on the echolink side? That would solve that issue quick. You can still dial out to anywhere you want!
I also use a google voice phone number on node, both in and out and then I also have a pin that must be entered when you reverse patch into it just to play it safe.
Corey N3FE
From: app_rpt-users-bounces at ohnosec.org <mailto:app_rpt-users-bounces at ohnosec.org> [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Lu Vencl
Sent: Saturday, November 09, 2013 9:31 PM
To: 'Johnny Keeker'; 'Kevin Custer'; 'App_rpt Users'
Subject: Re: [App_rpt-users] XIPAR question
Well since you brought it up, I also agree, both acid and xipar are great packages. And both have their pluses and minuses.
ACID has the web interface and reverse autopatch provided as a courtesy and I have contributed financially to the cause.
ADID also has the ability to silence echolink telemetry for which I am not certain at this time if it is an option with XIPAR. For most, this is not a show stopper, but I do know some that would be against moving to XIPAR if that were the case. The issue is that there are too many echolink surfers and all I ever hear is connect and disconnect messages all day and all night. I for one would like to kill echolink on my box, but I find it handy to use the app in the app store.. I got to wonder why nobody has built and app for the iphone and android as of yet???
XIPAR has a great feature to reduce the telemetry level when there is actual traffic. I personally like that a lot. ACID does not at this time as far as I know. XIPAR also has a great set of optional audio filters as you pointed out Johnny, and that is my major reason for implementing XIPAR. Yes, the audio is that good!
I also found for some reason that some of my ASUS computers like XIPAR.. Not sure why under ACID, my ASUS machines that I have had major audio breakup. I have heard others complain about this, but I could never figure out what the issue was. I replaced USB ports with added cards with USB, no difference.. Looked at BIOS settings, you name it. I ended up throwing out about 5 of those PC’s because I gave up. Then when I happened to try XIPAR on a couple I still had, bingo it worked? Why??? To this date, nobody can explain it..
Again, not a real issue for me as I have 6 boxes on ACID and 3 on XIPAR.. All on Dell PCs. Which one do I like best? Well I am on the fence still, but leaning towards XIPAR.. If XIPAR can get the echolink telemetry fixed and Allmon going, then I might lean lots more.
The bottom line is that there is a choice and that is a nice thing with this hobby. Whatever you prefer, they both are great packages and the folks behind both of them offer great support. So be grateful and please do consider donating some funds as we near the holidays. I am sure it would be very much appreciated! The costs associate with allstarlink servers does cost money, so please don’t forget that.
73
Lu
KA4EPS
From: app_rpt-users-bounces at ohnosec.org <mailto:app_rpt-users-bounces at ohnosec.org> [mailto:app_rpt-users-bounces at ohnosec.org] On Behalf Of Johnny Keeker
Sent: Saturday, November 09, 2013 1:46 PM
To: Kevin Custer; 'App_rpt Users'
Subject: Re: [App_rpt-users] XIPAR question
Xipar has stuff missing in the initial setup. If your familiar with acid,
just compare the conf files. urd.conf is equivalent to the usbradio.conf.
My view is, both acid and xipar are incredible accomplishments; I have
no favorite. I realize others are going to disagree, and Ill probably get
flamed for saying this, but after having configured the filter settings on
xipar, I find a significant difference in audio, and the telemduck is good.
I havent heard any others voice their opinions on xipars audio so Ill
leave it at that...
Any observations or comments are kindly accepted
JK
From: Kevin Custer <kuggie at kuggie.com <mailto:kuggie at kuggie.com> >
To: 'App_rpt Users' <app_rpt-users at ohnosec.org <mailto:app_rpt-users at ohnosec.org> >
Sent: Saturday, November 9, 2013 9:57 AM
Subject: Re: [App_rpt-users] XIPAR question
telemetry = telemetry
wait_times = wait-times
morse = morse
All are/were missing in XIPAR by default. Not sure why.
Kevin
Well you hit it right on the nail! telemetry=telemetry was missing. Great catch! Not sure why it was, but I will let Steve know that the default file has that missing in the build.
Now the only item left is the eannmode=0 not working as it should.
Once I hear back from Steve / issue resolved, I will report back.
Thanks and 73
KA4EPS
From: Johnny Keeker [mailto:cypresstower at yahoo.com]
Sent: Friday, November 08, 2013 11:04 PM
To: Lu Vencl; App_rpt Users
Subject: Re: [App_rpt-users] XIPAR question
Lu;
as root~ The complete command is asterisk -rx reload
I should have mentioned, in case you havent come across this.
in my rpt.conf, telemetry=telemetry must be just that. I tried create 2 telemetry stanzas, one for
each registered node on that server. Doing so prevented me from using custom courtesy tones.
I only have one URI on that server. its possible that may have something to do with it, Im not sure.
I now only have one statement in both stanzas so both nodes share the telemetry stanza.
Its funny because I can have different functions and wait times per node but not telemetry.
example below is what didn't work until I changed both stanzas to telemetry=telemetry
[1999]
rxchannel = radio/usb
duplex = 2
functions = functions1999
telemetry=telemetry1999 ;this line was the error
wait_times=wait-times1999
macro=macro
startup_macro=
[2000]
rxchannel = radio/usb
duplex = 1
functions = functions2000
telemetry=telemetry2000 ;this line was the error
wait_times=wait-times2000
macro=macro
startup_macro=
JK
From: Lu Vencl <vencl at att.net <mailto:vencl at att.net> >
To: Johnny Keeker <cypresstower at yahoo.com <mailto:cypresstower at yahoo.com> >
Cc: "app_rpt-users at ohnosec.org <mailto:app_rpt-users at ohnosec.org> " <app_rpt-users at ohnosec.org <mailto:app_rpt-users at ohnosec.org> >
Sent: Friday, November 8, 2013 9:20 PM
Subject: Re: [App_rpt-users] XIPAR question
Johnny,
The install is from an ISO that was downloaded last week so I assume it has the latest loads.
Restarts seem to have no effects.
No matter what I I out into the rpt.conf file, it will not change.
I notice you mention
asterisk -rx for which I have not tried yet. What does it do?
Sent from my iPhone, Lu Vencl
On Nov 8, 2013, at 7:34 PM, Johnny Keeker <cypresstower at yahoo.com <mailto:cypresstower at yahoo.com> > wrote:
Lu;
Im experiencing a similar glitch, but Its probably my doing.
One of my nodes is in the Carolinas, Its Xipar centos6 Feb 2013 no updates.
I can change the courtesy tones etc, on the fly using putty and the asterisk -rx reload
command, or Freepbx and the update button, both methods works. On another node
with centos6 Feb 2013, I ran the update scripts, and now I have to reboot linux in order
for the telemetry 'courtesy tones' to take effect. ??? It use to work, the only thing I did
different was update the node. Ive tried the asterisk -rx reload, the amportal kill/start,
and Freepbx, I cant change the courtesy tones until I reboot the box. I was going to try
reloading xipar without the updates this weekend. Could you post your results here?
I would really like to know if a reboot works on your node. Thanks
ps. I dont have echolink configures on any xipar nodes.
JK
From: Lu Vencl <vencl at att.net <mailto:vencl at att.net> >
To: app_rpt-users at ohnosec.org <mailto:app_rpt-users at ohnosec.org>
Sent: Friday, November 8, 2013 1:23 PM
Subject: [App_rpt-users] XIPAR question
I have a question regarding XIPAR telemetry (courtesy Tones) and Echolink Telemetry.
Under ACID, I have always been able to tweak the courtesy tones to a custom set of tones I prefer.
But when I try to make changes under the XIPAR build, it seems to ignore them completely and do it’s own set of courtesy tones.
See example below.
Also, for echolink, I have used eannmode=0 to completely inhibit echolink telemetry and for some reason the =0 is the same as =1.
Is there a work around or a known bug with these two items?
Thanks in advance.
Lu, KA4EPS
;idtalkover=|iid ; Talkover ID (optional) default is none
unlinkedct=ct2 ; unlinked courtesy tone (optional) default is none
remotect=ct3 ; remote linked courtesy tone (indicates a remote is in the list of links)
linkunkeyct=ct8 ; sent when a transmission received over the link unkeys
;nolocallinkct=0 ; Send unlinkedct instead if another local node is connected to this node (hosted on the same PC).
;irplann=1 ; Default: 1 = Play IRLP connect and disconnect announcements
; 0 = Disable IRLP connect and disconnect announcements
eannmode=0 ; Default: 1 = Say only node number on EchoLink connects
nounkeyct=0
holdofftelem=1 ; 2 = say phonetic call sign only on EchoLink connects
; 3 = say phonetic call sign and node number on EchoLink connects
;connpgm=yourconnectprogram ; Default: Disabled. Execute a program you specify on connect.
; passes 2 command line arguments to your program:
; 1. node number in this stanza (us)
; 2. node number being connected to us (them)
;discpgm=yourdisconnectprogram ; Default: Disabled. Execute a program you specify on disconnect.
; passes 2 command line arguments to your program:
; 1. node number in this stanza (us)
; 2. node number being disconnected from us (them)
;linkactenable=0 ; Set to 1 to enable the link activity timer. Applicable to standard nodes only.
;lnkacttime=1800 ; Link activity timer time in seconds.
;lnkactmacro=*52 ; Function to execute when link activity timer expires.
;lnkacttimerwarn=30seconds ; Message to play when the link activity timer has 30 seconds left.
;remote_inact_timeout=1800 ; Inactivity timer for remote base nodes only (set to 0 to disable).
;remote_timeout=3600 ; Session time out for remote base. (set to 0 to disable)
; program and options to send information to stats server
statpost_program=/usr/bin/wget,-q,--output-document=/dev/null
statpost_url=http://stats.allstarlink.org/uhandler.php
irxgain=-10 ; IRLP receive gain adjustment
; Note: Gain is in db-volts (20logVI/VO)
itxgain=10 ; IRLP transmit gain adjustment
; Note: Gain is in db-volts (20logVI/VO)
erxgain=-3 ; Echolink receive gain adjustment
; Note: Gain is in db-volts (20logVI/VO)
etxgain=3 ; Echolink transmit gain adjustment
; Note: Gain is in db-volts (20logVI/VO)
;telemnomdb=0 ; Telemetry Nominal Amplitude reference in dB
telemduckdb=-12 ; Telemetry Ducking in dB when local or link voice tx in progress
[telemetry]
ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048)
ct2=|t(2175,0,2,1112)(0,0,2,0)(2175,0,2,700)(0,0,99,0)(350,440,75,1048)
ct3=|t(440,0,150,4096)
ct4=|t(550,0,150,2048)
ct5=|t(660,0,150,2048)
ct6=|t(880,0,150,2048)
ct7=|t(660,440,150,2048)
ct8=|t(350,440,75,1048)(0,0,80,0)(350,440,75,1048)
;ct8=|t(2175,0,2,1112)(0,0,2,0)(2175,0,2,700)(0,0,99,0)(350,440,75,1048)(0,0,80,0)(350,440,75,1048)
;ct8=|t(2175,0,80,512)(0,0,5,0)(1950,0,40,1048)(0,0,5,0)(1850,0,40,1048)
;ct8=|t(350,440,75,1048)(0,0,80,0)(350,440,75,1048)
remotetx=|t(440,0,50,3000)(0,0,80,0)(350,0,50,3000)
remotemon=|t(1209,0,50,2048)
cmdmode=|t(900,903,200,2048)
functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048)
_______________________________________________
App_rpt-users mailing list
App_rpt-users at ohnosec.org <mailto:App_rpt-users at ohnosec.org>
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
_______________________________________________
App_rpt-users mailing list
App_rpt-users at ohnosec.org <mailto:App_rpt-users at ohnosec.org>
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
No virus found in this message.
Checked by AVG - http://www.avg.com/
Version: 2013.0.3426 / Virus Database: 3222/6822 - Release Date: 11/09/13
_______________________________________________
App_rpt-users mailing list
App_rpt-users at ohnosec.org <mailto:App_rpt-users at ohnosec.org>
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users
--
This message was scanned and is believed to be clean.
Click here to report this message as spam. <http://simba.repeater.net:8080/cgi-bin/learn-msg.cgi?id=980DED03E3.A897E>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20131111/2a270403/attachment.html>
More information about the App_rpt-users
mailing list