Good Day, I have just installed the ACID build today to get my node online on Echolink and AllStar. I have an issue though where the box that runs Asterisk is interfacing with an SCOM 7330 controller which handles all ID'ing. I have looked through the docs and can't seem to find a place where I can turn off apt_rpt sending a CW ID. Is there any way to turn this off? Our system is set up to drop PL on ID from the controller so it's a bit annoying when the Asterisk install sends ID through the controller. Thank you, Matt, NM1B
I believe that's just a matter of setting: idtime=0 At least that's how I've done it in the past... 73 - Jeremy, KD0EAV Matt Brennan wrote:
Good Day,
I have just installed the ACID build today to get my node online on Echolink and AllStar. I have an issue though where the box that runs Asterisk is interfacing with an SCOM 7330 controller which handles all ID'ing. I have looked through the docs and can't seem to find a place where I can turn off apt_rpt sending a CW ID. Is there any way to turn this off? Our system is set up to drop PL on ID from the controller so it's a bit annoying when the Asterisk install sends ID through the controller.
Thank you, Matt, NM1B _______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
Jeremy, Thanks, I'll give that a try. I was going to try that, but I read in the code something about enforcing a minimum of 600 seconds so I just assumed it wouldn't work. I guess I'll see. Two other questions for the group: 1) Is there an easy way to stop it from saying "to node # # # #" when it announces someone connecting. I have it set to say the callsign, which is sufficient. I don't need to know my node # every time someone connects. 2) Anyone had an issue with it saying the wrong callsigns on EchoLink? KB1PSB connected the other day, and it announced KT0EE. It has done this with a few different call signs, afaik all of them on mobile devices. Thanks, Matt, NM1B On Sun, Oct 24, 2010 at 19:32, "Jeremy R. Geeo [KDØEAV]" <kd0eav@clear-sky.net> wrote:
I believe that's just a matter of setting: idtime=0
At least that's how I've done it in the past...
73
- Jeremy, KD0EAV
Matt Brennan wrote:
Good Day,
I have just installed the ACID build today to get my node online on Echolink and AllStar. I have an issue though where the box that runs Asterisk is interfacing with an SCOM 7330 controller which handles all ID'ing. I have looked through the docs and can't seem to find a place where I can turn off apt_rpt sending a CW ID. Is there any way to turn this off? Our system is set up to drop PL on ID from the controller so it's a bit annoying when the Asterisk install sends ID through the controller.
Thank you, Matt, NM1B _______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
On Tuesday, October 26, 2010 12:05:03 pm Matt Brennan wrote:
Jeremy,
Thanks, I'll give that a try. I was going to try that, but I read in the code something about enforcing a minimum of 600 seconds so I just assumed it wouldn't work. I guess I'll see.
Two other questions for the group:
1) Is there an easy way to stop it from saying "to node # # # #" when it announces someone connecting. I have it set to say the callsign, which is sufficient. I don't need to know my node # every time someone connects.
Take a look at app-rpt.c and you will see a list of functions you can assign to DTMF sequences. There are 3 functions that control EchoLink announcements. I have my node set to just announce node numbers. Create a directory named /etc/asterisk/custom and put an rpt.conf file there with a stanza for your node functions. Add a '(+) right after the stanza name. Now you can add custom DTMF codes and associate them with any app_rpt function you want to use, just like in the main rpt.conf file. I have defined several new codes here and they will be added to your node's function list on startup. The new codes will be added everytime you restart asterisk.
2) Anyone had an issue with it saying the wrong callsigns on EchoLink? KB1PSB connected the other day, and it announced KT0EE. It has done this with a few different call signs, afaik all of them on mobile devices.
It will only announce the callsign of the node that is connectiong, which may or may not be the callsign of the actual user. 8-Dale
On Sun, Oct 24, 2010 at 19:32, "Jeremy R. Geeo [KDØEAV]"
<kd0eav@clear-sky.net> wrote:
I believe that's just a matter of setting: idtime=0
At least that's how I've done it in the past...
73
- Jeremy, KD0EAV
Matt Brennan wrote:
Good Day,
I have just installed the ACID build today to get my node online on Echolink and AllStar. I have an issue though where the box that runs Asterisk is interfacing with an SCOM 7330 controller which handles all ID'ing. I have looked through the docs and can't seem to find a place where I can turn off apt_rpt sending a CW ID. Is there any way to turn this off? Our system is set up to drop PL on ID from the controller so it's a bit annoying when the Asterisk install sends ID through the controller.
Thank you, Matt, NM1B _______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
-- Open your mind, Read, Learn, Think, Apply.. AllStar Node 2392 / EchoLink 541558 / 73, from N7PKT! http://www.hybotics.com - NEW main site Just because we can, does it follow that we should?
Dale, Thanks for your response. I have been trying to figure out what you mean and I must say, unfortunately, I'm at a loss. I have gone through app_rpt.c and looked through the code and while I understand a great deal of it I cannot find the DTMF functions you are referencing. As far as I know I am running the most recent version from SVN. Any chance there's an example of what you're talking about out there that I'm missing? Also, setting eannmode to 0 doesn't work. Setting it to 2 currently seems broken as it is announcing node numbers instead of call signs. Thanks, Matt, NM1B On Tue, Oct 26, 2010 at 15:30, Dale Weber <n7pkt@hybotics.org> wrote:
On Tuesday, October 26, 2010 12:05:03 pm Matt Brennan wrote:
Jeremy,
Thanks, I'll give that a try. I was going to try that, but I read in the code something about enforcing a minimum of 600 seconds so I just assumed it wouldn't work. I guess I'll see.
Two other questions for the group:
1) Is there an easy way to stop it from saying "to node # # # #" when it announces someone connecting. I have it set to say the callsign, which is sufficient. I don't need to know my node # every time someone connects.
Take a look at app-rpt.c and you will see a list of functions you can assign to DTMF sequences. There are 3 functions that control EchoLink announcements. I have my node set to just announce node numbers.
Create a directory named /etc/asterisk/custom and put an rpt.conf file there with a stanza for your node functions. Add a '(+) right after the stanza name. Now you can add custom DTMF codes and associate them with any app_rpt function you want to use, just like in the main rpt.conf file. I have defined several new codes here and they will be added to your node's function list on startup. The new codes will be added everytime you restart asterisk.
2) Anyone had an issue with it saying the wrong callsigns on EchoLink? KB1PSB connected the other day, and it announced KT0EE. It has done this with a few different call signs, afaik all of them on mobile devices.
It will only announce the callsign of the node that is connectiong, which may or may not be the callsign of the actual user.
8-Dale
On Sun, Oct 24, 2010 at 19:32, "Jeremy R. Geeo [KDØEAV]"
<kd0eav@clear-sky.net> wrote:
I believe that's just a matter of setting: idtime=0
At least that's how I've done it in the past...
73
- Jeremy, KD0EAV
Matt Brennan wrote:
Good Day,
I have just installed the ACID build today to get my node online on Echolink and AllStar. I have an issue though where the box that runs Asterisk is interfacing with an SCOM 7330 controller which handles all ID'ing. I have looked through the docs and can't seem to find a place where I can turn off apt_rpt sending a CW ID. Is there any way to turn this off? Our system is set up to drop PL on ID from the controller so it's a bit annoying when the Asterisk install sends ID through the controller.
Thank you, Matt, NM1B _______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
-- Open your mind, Read, Learn, Think, Apply.. AllStar Node 2392 / EchoLink 541558 / 73, from N7PKT! http://www.hybotics.com - NEW main site Just because we can, does it follow that we should? _______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
try about line 34 or so in app_rpt.c
Date: Thu, 4 Nov 2010 00:04:48 -0400 From: brennanma@gmail.com To: n7pkt@hybotics.org CC: app_rpt-users@qrvc.com Subject: Re: [App_rpt-users] ID Question
Dale,
Thanks for your response. I have been trying to figure out what you mean and I must say, unfortunately, I'm at a loss. I have gone through app_rpt.c and looked through the code and while I understand a great deal of it I cannot find the DTMF functions you are referencing. As far as I know I am running the most recent version from SVN. Any chance there's an example of what you're talking about out there that I'm missing?
Also, setting eannmode to 0 doesn't work. Setting it to 2 currently seems broken as it is announcing node numbers instead of call signs.
Thanks, Matt, NM1B
On Tue, Oct 26, 2010 at 15:30, Dale Weber <n7pkt@hybotics.org> wrote:
On Tuesday, October 26, 2010 12:05:03 pm Matt Brennan wrote:
Jeremy,
Thanks, I'll give that a try. I was going to try that, but I read in the code something about enforcing a minimum of 600 seconds so I just assumed it wouldn't work. I guess I'll see.
Two other questions for the group:
1) Is there an easy way to stop it from saying "to node # # # #" when it announces someone connecting. I have it set to say the callsign, which is sufficient. I don't need to know my node # every time someone connects.
Take a look at app-rpt.c and you will see a list of functions you can assign to DTMF sequences. There are 3 functions that control EchoLink announcements. I have my node set to just announce node numbers.
Create a directory named /etc/asterisk/custom and put an rpt.conf file there with a stanza for your node functions. Add a '(+) right after the stanza name. Now you can add custom DTMF codes and associate them with any app_rpt function you want to use, just like in the main rpt.conf file. I have defined several new codes here and they will be added to your node's function list on startup. The new codes will be added everytime you restart asterisk.
2) Anyone had an issue with it saying the wrong callsigns on EchoLink? KB1PSB connected the other day, and it announced KT0EE. It has done this with a few different call signs, afaik all of them on mobile devices.
It will only announce the callsign of the node that is connectiong, which may or may not be the callsign of the actual user.
8-Dale
On Sun, Oct 24, 2010 at 19:32, "Jeremy R. Geeo [KDØEAV]"
<kd0eav@clear-sky.net> wrote:
I believe that's just a matter of setting: idtime=0
At least that's how I've done it in the past...
73
- Jeremy, KD0EAV
Matt Brennan wrote:
Good Day,
I have just installed the ACID build today to get my node online on Echolink and AllStar. I have an issue though where the box that runs Asterisk is interfacing with an SCOM 7330 controller which handles all ID'ing. I have looked through the docs and can't seem to find a place where I can turn off apt_rpt sending a CW ID. Is there any way to turn this off? Our system is set up to drop PL on ID from the controller so it's a bit annoying when the Asterisk install sends ID through the controller.
Thank you, Matt, NM1B _______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
-- Open your mind, Read, Learn, Think, Apply.. AllStar Node 2392 / EchoLink 541558 / 73, from N7PKT! http://www.hybotics.com - NEW main site Just because we can, does it follow that we should? _______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
_______________________________________________ App_rpt-users mailing list App_rpt-users@qrvc.com http://qrvc.com/mailman/listinfo/app_rpt-users
1) Is there an easy way to stop it from saying "to node # # # #" when it announces someone connecting. I have it set to say the callsign, which is sufficient. I don't need to know my node # every time someone connects.
I'll defer on this one; the only other option I'm aware of is the ability to turn off the announcements all-together... telemdefault=0
2) Anyone had an issue with it saying the wrong callsigns on EchoLink? KB1PSB connected the other day, and it announced KT0EE. It has done this with a few different call signs, afaik all of them on mobile devices.
This is very common - and almost makes the announcements pointless - Echolink has an ability to be proxied through various servers around the Internet in an effort to better enable the mobile (iPhone, and presumably Andriod) versions of the software to work on the various carriers networks which don't always (ever?) work when using UDP on their networks. The nature of the proxy is to establish a stateful TCP connection from the mobile device to one of the various proxy servers on the network. That proxy will then initiate the connection to the (your) node; the side effect is that the incoming connection then assumes both the Callsign AND the Echolink node ID of the proxy server (by IP address), not the originating device. Conversely, a mobile Echolink device behind a proxy can not receive an incoming connection. Read this instead of what I wrote: http://www.echolink.org/proxy.htm
Actually this *was* very common for me, until I upgraded to the version that did away with astdb. In the new version, the half-dozen proxy connects that I have done - using a couple of different proxy servers - all announced my call correctly - AND - I was able to get connected as fast as I could work the mouse. No more waiting 5 minutes. 73 Ken 27021 W4BRM/R
-----Original Message----- From: app_rpt-users-bounces@qrvc.com [mailto:app_rpt-users- bounces@qrvc.com] On Behalf Of "Jeremy R. Geeo [KDØEAV]" Sent: Tuesday, October 26, 2010 3:38 PM To: app_rpt-users@qrvc.com Subject: Re: [App_rpt-users] ID Question
2) Anyone had an issue with it saying the wrong callsigns on EchoLink? KB1PSB connected the other day, and it announced KT0EE. It has done this with a few different call signs, afaik all of them on mobile devices.
This is very common - and almost makes the announcements pointless -
vc.com/mailman/listinfo/app_rpt-users
participants (5)
-
"Jeremy R. Geeo [KDØEAV]" -
Dale Weber -
Jim Duuuude -
Ken -
Matt Brennan