Date   

No Audio

David
 

I have no Audio outbound. I have checked the audio going into the sound card and its fine. When you dial up the echo reflector there is no audio back. Nodes can be dialed into. Port forwarding has been checked. I do get an error message at the prompt {help- malformed sysct1 tree on free}. Does anyone have any idea?


David N9CZV Node 3360


Re: node locking up

Butch Bussen
 

I can't log in once it locks up. It isn't seen on the network, nor does it respond to dtmf codes. All I can do is power down and reboot.
Thanks.
73
Butch
WA0VJR
Node 3148
Wallace, ks.

On Mon, 9 Jan 2012, ve7ltd wrote:

Since the computer seems to be sort of "soft locking" (you can still communicate with it through the network), it may be logging the problems in

/var/log/messages

The contents of the folder

/etc/cron.daily/

are also run around that time every day.

Dave

--- In irlp@..., Butch Bussen <butchb@...> wrote:

I tried scandisk and I don't know what happened, but the machine
wouldn't boot back up. When I had my cousin look at the monitor I got
an invalid boot option error and some numbers which I don't recall.
Anyhow, I restored an image and everything is working fine except for
the lock up. I've determined it is something run in a cron somewhere.
My time and date are set correct, and the machine locks up at around 4
o'clock every morning. This morning, at 3 til, it was fine and when I
again checked at five past 4, it was nonresponsive. Where can I look to
see what is causing this?

Thanks.

73
Butch
WA0VJR
Node 3148
Wallace, ks.


On Fri, 6 Jan 2012, John wrote:


Thinking outside the square here Butch,
as I often do when wanting a simple answer..:)

1. Wondering if the Dell has "hibernate" active.
2. I once had a sick HD on my IRLP node and found it
by running 'shutdown -F -r now' (-F = scandisk on reboot -case sensitive)
3. It may also pay to scan the RAM, but I can't locate the command right now.

Goodluck

73 John
6163


On 05-Jan-12 9:25:22 PM, Butch Bussen (butchb@ wrote:
I moved my node to another computer as the old one
wouldn't boot most of
the time. I moved the hard drive, irlp board and sound card. The new
computer is a Del desktop, I forget the model. Everything seems to work
find except every night my node stops responding. I get no response from
touch tone commands, and although I can connect via my terminal program, I
don't
get a login prompt.
I'm thinking this has something to do with the
update that is sent out each night, as the node quits about the same time
in the early morning.As I recall an update is sent out around four
mountain time. This morning at ten til 4 mountain time, node was fine. I
checked again at ten after four and it is locked up again. If I reboot,
it comes back fine. Am I on the right track? What do I look for? I'm
running fc3 and until my computer switch, have had no problems for many
years.


Re: node locking up

David Cameron - IRLP
 

Since the computer seems to be sort of "soft locking" (you can still communicate with it through the network), it may be logging the problems in

/var/log/messages

The contents of the folder

/etc/cron.daily/

are also run around that time every day.

Dave

--- In irlp@..., Butch Bussen <butchb@...> wrote:

I tried scandisk and I don't know what happened, but the machine
wouldn't boot back up. When I had my cousin look at the monitor I got
an invalid boot option error and some numbers which I don't recall.
Anyhow, I restored an image and everything is working fine except for
the lock up. I've determined it is something run in a cron somewhere.
My time and date are set correct, and the machine locks up at around 4
o'clock every morning. This morning, at 3 til, it was fine and when I
again checked at five past 4, it was nonresponsive. Where can I look to
see what is causing this?

Thanks.

73
Butch
WA0VJR
Node 3148
Wallace, ks.


On Fri, 6 Jan 2012, John wrote:


Thinking outside the square here Butch,
as I often do when wanting a simple answer..:)

1. Wondering if the Dell has "hibernate" active.
2. I once had a sick HD on my IRLP node and found it
by running 'shutdown -F -r now' (-F = scandisk on reboot -case sensitive)
3. It may also pay to scan the RAM, but I can't locate the command right now.

Goodluck

73 John
6163


On 05-Jan-12 9:25:22 PM, Butch Bussen (butchb@ wrote:
I moved my node to another computer as the old one
wouldn't boot most of
the time. I moved the hard drive, irlp board and sound card. The new
computer is a Del desktop, I forget the model. Everything seems to work
find except every night my node stops responding. I get no response from
touch tone commands, and although I can connect via my terminal program, I
don't
get a login prompt.
I'm thinking this has something to do with the
update that is sent out each night, as the node quits about the same time
in the early morning.As I recall an update is sent out around four
mountain time. This morning at ten til 4 mountain time, node was fine. I
checked again at ten after four and it is locked up again. If I reboot,
it comes back fine. Am I on the right track? What do I look for? I'm
running fc3 and until my computer switch, have had no problems for many
years.


Re: node locking up

Butch Bussen
 

I tried scandisk and I don't know what happened, but the machine wouldn't boot back up. When I had my cousin look at the monitor I got an invalid boot option error and some numbers which I don't recall. Anyhow, I restored an image and everything is working fine except for the lock up. I've determined it is something run in a cron somewhere. My time and date are set correct, and the machine locks up at around 4 o'clock every morning. This morning, at 3 til, it was fine and when I again checked at five past 4, it was nonresponsive. Where can I look to see what is causing this?

Thanks.

73
Butch
WA0VJR
Node 3148
Wallace, ks.

On Fri, 6 Jan 2012, John wrote:


Thinking outside the square here Butch,
as I often do when wanting a simple answer..:)

1. Wondering if the Dell has "hibernate" active.
2. I once had a sick HD on my IRLP node and found it
by running 'shutdown -F -r now' (-F = scandisk on reboot -case sensitive)
3. It may also pay to scan the RAM, but I can't locate the command right now.

Goodluck

73 John
6163


On 05-Jan-12 9:25:22 PM, Butch Bussen (butchb@ wrote:
I moved my node to another computer as the old one
wouldn't boot most of
the time. I moved the hard drive, irlp board and sound card. The new
computer is a Del desktop, I forget the model. Everything seems to work
find except every night my node stops responding. I get no response from
touch tone commands, and although I can connect via my terminal program, I
don't
get a login prompt.
I'm thinking this has something to do with the
update that is sent out each night, as the node quits about the same time
in the early morning.As I recall an update is sent out around four
mountain time. This morning at ten til 4 mountain time, node was fine. I
checked again at ten after four and it is locked up again. If I reboot,
it comes back fine. Am I on the right track? What do I look for? I'm
running fc3 and until my computer switch, have had no problems for many
years.


Keydown problem with new node

k7huw_james <k7huw@...>
 

Just setting up my new node (7674) and I'm having a problem. Maybe somebody can give me a clue.

NOTE: I've got my node outside the firewall on a public internet IP. So there is no firewall. All tests in troubleshoot-irlp pass. Internet is a business cable modem.

When connected to another node or reflector I can hear their audio just fine. However what they hear is a keyup, then my audio good and loud for a second or two, then keydown. A pause, then keyup and another second more or less of audio then keydown. And it continues that way until I stop talking.

I hear the same thing back from the echo reflector.

When transmitting my COS light stays lit the whole time. If I turn up the volume on my node radio I can hear my voice just fine with no cut outs.

If I plug an ipod playing music into the sound card on the node computer the other end hears the same thing; key-up, a second of music, key-down.

Anyone have any thoughts as to what else I might try?
-James K7HUW


Re: IRLP "Update Script" and ISP problems

k9dc
 

That was a by-hand typo, which he immediately corrected on the line below.
-k9dc

On Jan 8, 2012, at 11:09 AM, Cary Honeywell wrote:

One command was incorrect. " -bash: updtae: command not found "
Hope this solves the issue for you.

_ Cary _
VE3EV
2053


File - 2-Week Reminder

irlp@...
 

This Yahoolist was created for node owners to gather and share technical information and discuss the operation of their IRLP nodes. It has also become an official means for the IRLP Project Team to send out important announcements to node owners.

**NEW** SPAM SPAM SPAM
Yes - the occassional SPAM message will make it to the list. P L E A S E - DO NOT respond, comment or start a thread about same. This rule is critical to keeping sanity on the list.

SEARCH FOR TOPICS BEFORE POSTING THEM
Yahoogroups has a very nice Advanced Search feature which allows you to search the whole archive of messages in one search. Please type some keywords from your question in the "Message Body" and "Message Subject" to look for answers before asking them in the group. Thank you.

NODE PASSWORDS
Several nodes have been hacked as a result of brute force attacks. In each case these breaches were a result of password that was a common persons name or callsign. A brute force attack is one in which all possible words of a certain length are attempted until a correct one is found. Crack dictionaries which contain a list of common words and phrases can easily be found on the Internet. Many crack dictionaries contain entire scripts to popular movies and entire sets of song lyrics - so be warned.

A strong password is as long as possible. Always use at least six characters in your password. The longer the password, the more difficult it is to attack with a brute-force search.

STRONG PASSWORDS...
- Have both upper and lower case letters.
- Have digits and/or punctuation characters as well as letters.
- Are easy to remember, so they do not have to be written down.
- Are AT LEAST six or more characters long.

YOUR SSH PORT
Most attempts to compromise any box or done on the standard FTP/SFTP port numbers of 22 and 23. It is advisable to change the SSH port of your node to something other than 22. To do this log into your box as root and edit the file.... /etc /ssh/sshd_config

Uncomment out the port and change it to whatever you wish as long nothing else is using that port. You will need to restart SSH so as long as you are logged right at the node and NOT via ssh, enter the following commands -
service sshd stop
service sshd start

The new port will now be in effect. Remember to change your routers port forwarding or you will not be able to remotely access the node. And like your new secure password, remember the new port number.

MAIL VOLUME
NOTE: If you are overwhelmed by the traffic on this list do not choose the No Email option but rather configure your list membership using the following option: Special notices. Only send me important update emails from the group moderator. This option will assure you still receive infrequent yet important emails from the moderators.

YOUR RIGHTS
It is "NOT" your right as a node owner to have access to this list.
Node owners who cannot get along with the majority of this group will be unsubscribed .

This reminder is sent every two weeks to the list.

Thank you,
Dave VE7LTD


Re: IRLP "Update Script" and ISP problems

Cary Honeywell <caryhon139@...>
 

One command was incorrect. " -bash: updtae: command not found "

Hope this solves the issue for you.

_ Cary _
VE3EV
2053

On Sun, Jan 8, 2012 at 8:04 AM, Dave Gingrich <Dave@...> wrote:

**


Everything looks like it is operating properly to me. ipupdate is being
called at 15 minute intervals, and the manual update is correct. See
below...


RECENT IP address obtained from dyndns.org
Obtaining last IP from server.
The CURRENT IP is : 70.103.158.189
The LAST IP was : 70.103.158.189
Your IP address has not changed
The IP address here is the IP address assigned to your node. This time it
did not detect there was any change, so nothing further was done. If your
IP had changed, the CURRENT and LAST IP would be different, and there would
be be a couple of additional lines about the authenticating to the server,
and up updating IP address information. But it only does this if a change
is necessary.

Here is what happens if a change is required (I changed the IP reported on
one of my nodes which forced a change)

repeater@stn4735:~/local$ ipupdate
RECENT IP address obtained from dyndns.org
Obtaining last IP from server.
The CURRENT IP is : 173.167.156.75
The LAST IP was : 73.167.156.75
The IP has changed from 73.167.156.75 to 173.167.156.75
Registering 173.167.156.75
Trying 206.246.140.250, port 15426...
Connected to 206.246.140.250
Authentication Complete, sending Update info
My node (4735) prefers IRLP server3 206.246.140.250, but otherwise the
same.



Re: IRLP "Update Script" and ISP problems

k9dc
 

Everything looks like it is operating properly to me. ipupdate is being called at 15 minute intervals, and the manual update is correct. See below...

RECENT IP address obtained from dyndns.org
Obtaining last IP from server.
The CURRENT IP is : 70.103.158.189
The LAST IP was : 70.103.158.189
Your IP address has not changed
The IP address here is the IP address assigned to your node. This time it did not detect there was any change, so nothing further was done. If your IP had changed, the CURRENT and LAST IP would be different, and there would be be a couple of additional lines about the authenticating to the server, and up updating IP address information. But it only does this if a change is necessary.

Here is what happens if a change is required (I changed the IP reported on one of my nodes which forced a change)

repeater@stn4735:~/local$ ipupdate
RECENT IP address obtained from dyndns.org
Obtaining last IP from server.
The CURRENT IP is : 173.167.156.75
The LAST IP was : 73.167.156.75
The IP has changed from 73.167.156.75 to 173.167.156.75
Registering 173.167.156.75
Trying 206.246.140.250, port 15426...
Connected to 206.246.140.250
Authentication Complete, sending Update info
My node (4735) prefers IRLP server3 206.246.140.250, but otherwise the same.


[repeater@localhost ~]$ update
No argument given, assuming update files
Obtaining best server IP ... found IP = 208.67.255.163
Performing file update ...
Your node (I assume 7576) prefers server 2 for updates, which is 208.67.255.163 in the 'update' command. Unlike the ipupdate command, this is not your IP, rather the IP of chosen server.

In your case, everything is operating exactly as it should. But, if your Internet connection is flaky, the operation of your node will be flaky and there is not much you can do about it, other than get a more reliable Internet connection. Sorry.

-k9dc


On Jan 8, 2012, at 7:09 AM, w7boz wrote:

Here is the text from the cat command.


[root@localhost ~]# cat /var/log/cron Jan 8 04:15:01 localhost crond[12752]: (repeater) CMD ((/home/irlp/scripts/ipupdate_cron > /dev/null 2>&1))
Jan 8 04:18:01 localhost crond[12759]: (repeater) CMD ((/home/irlp/custom/aprs_status >/dev/null 2>&1) &)
Jan 8 04:22:01 localhost crond[12797]: (root) CMD (run-parts /etc/cron.weekly)
Jan 8 04:30:01 localhost crond[12998]: (repeater) CMD ((/home/irlp/scripts/speaktime &>/dev/null 2>&1) &)
Jan 8 04:30:01 localhost crond[13002]: (repeater) CMD ((/home/irlp/scripts/ipupdate_cron > /dev/null 2>&1))
Jan 8 04:32:41 localhost crond[2593]: (CRON) STARTUP (V5.0)
Jan 8 04:32:42 localhost crontab[2621]: (repeater) REPLACE (repeater)
Jan 8 04:32:51 localhost /usr/bin/crontab[2921]: (repeater) REPLACE (repeater)
Jan 8 04:33:01 localhost crond[2593]: (repeater) RELOAD (cron/repeater)
Jan 8 04:45:01 localhost crond[3806]: (repeater) CMD ((/home/irlp/scripts/ipupdate_cron > /dev/null 2>&1))
Jan 8 04:56:09 localhost crontab[3896]: (repeater) LIST (repeater)
Jan 8 05:00:01 localhost crond[3906]: (repeater) CMD ((/home/irlp/scripts/ipupdate_cron > /dev/null 2>&1))
Jan 8 05:00:01 localhost crond[3907]: (repeater) CMD ((/home/irlp/scripts/speaktime &>/dev/null 2>&1) &)
Jan 8 05:00:01 localhost crond[3909]: (repeater) CMD ((/home/irlp/scripts/process_check > /dev/null 2>&1))
Jan 8 05:01:01 localhost crond[3948]: (root) CMD (run-parts /etc/cron.hourly)

And here is the commands when I just ran IPUPDATE and UPDATE.


[repeater@localhost ~]$ ipupdate
RECENT IP address obtained from dyndns.org
4
Obtaining last IP from server.
The CURRENT IP is : 70.103.158.189
The LAST IP was : 70.103.158.189
Your IP address has not changed
[repeater@localhost ~]$ updtae
-bash: updtae: command not found
[repeater@localhost ~]$ update
No argument given, assuming update files
Obtaining best server IP ... found IP = 208.67.255.163
Performing file update ...
receiving file list ... done

sent 107 bytes received 5708 bytes 2326.00 bytes/sec
total size is 8817564 speedup is 1516.35



Looks like when I run IPUPDATE it comes back with an old IPADRESS. When I run UPDATE it seems to update to a differnet IP ADDRESS. Maybe you can look at this data and let me know of things are looking right.

Thanks, Kevin
W7BOZ


Re: IRLP "Update Script" and ISP problems

w7boz
 

Here is the text from the cat command.


[root@localhost ~]# cat /var/log/cron Jan 8 04:15:01 localhost crond[12752]: (repeater) CMD ((/home/irlp/scripts/ipupdate_cron > /dev/null 2>&1))
Jan 8 04:18:01 localhost crond[12759]: (repeater) CMD ((/home/irlp/custom/aprs_status >/dev/null 2>&1) &)
Jan 8 04:22:01 localhost crond[12797]: (root) CMD (run-parts /etc/cron.weekly)
Jan 8 04:30:01 localhost crond[12998]: (repeater) CMD ((/home/irlp/scripts/speaktime &>/dev/null 2>&1) &)
Jan 8 04:30:01 localhost crond[13002]: (repeater) CMD ((/home/irlp/scripts/ipupdate_cron > /dev/null 2>&1))
Jan 8 04:32:41 localhost crond[2593]: (CRON) STARTUP (V5.0)
Jan 8 04:32:42 localhost crontab[2621]: (repeater) REPLACE (repeater)
Jan 8 04:32:51 localhost /usr/bin/crontab[2921]: (repeater) REPLACE (repeater)
Jan 8 04:33:01 localhost crond[2593]: (repeater) RELOAD (cron/repeater)
Jan 8 04:45:01 localhost crond[3806]: (repeater) CMD ((/home/irlp/scripts/ipupdate_cron > /dev/null 2>&1))
Jan 8 04:56:09 localhost crontab[3896]: (repeater) LIST (repeater)
Jan 8 05:00:01 localhost crond[3906]: (repeater) CMD ((/home/irlp/scripts/ipupdate_cron > /dev/null 2>&1))
Jan 8 05:00:01 localhost crond[3907]: (repeater) CMD ((/home/irlp/scripts/speaktime &>/dev/null 2>&1) &)
Jan 8 05:00:01 localhost crond[3909]: (repeater) CMD ((/home/irlp/scripts/process_check > /dev/null 2>&1))
Jan 8 05:01:01 localhost crond[3948]: (root) CMD (run-parts /etc/cron.hourly)

And here is the commands when I just ran IPUPDATE and UPDATE.


[repeater@localhost ~]$ ipupdate
RECENT IP address obtained from dyndns.org
4
Obtaining last IP from server.
The CURRENT IP is : 70.103.158.189
The LAST IP was : 70.103.158.189
Your IP address has not changed
[repeater@localhost ~]$ updtae
-bash: updtae: command not found
[repeater@localhost ~]$ update
No argument given, assuming update files
Obtaining best server IP ... found IP = 208.67.255.163
Performing file update ...
receiving file list ... done

sent 107 bytes received 5708 bytes 2326.00 bytes/sec
total size is 8817564 speedup is 1516.35



Looks like when I run IPUPDATE it comes back with an old IPADRESS. When I run UPDATE it seems to update to a differnet IP ADDRESS. Maybe you can look at this data and let me know of things are looking right.

Thanks, Kevin
W7BOZ

--- In irlp@..., Dave Gingrich <Dave@...> wrote:

It is easy enough to check...

Log in as (or become) user repeater and run the command 'crontab -l' You should see several entries, including ipupdate_cron. The */15 at the beginning of the line means it is set to run every 15 minutes.

Cron keeps its own log file, but you have to be root to look at it. after becoming root, either the command 'cat /var/log/cron' That will produce a lot of data, but you are interested in the most recent stuff at the end. You should see the log of cron jobs executed with recent timestamps.

ipupdate first looks for a change in IP, and only contacts the IRLP server if it has detected a change. a crappy Internet connection can screw that up. You MUST have a reasonably reliable Internet connection. If you do not, all bets are off.

-k9dc

On Jan 7, 2012, at 8:44 AM, w7boz wrote:

Yeah, My ISP is crap! But the best I can afford for High Speed. I wonder if the ipupdate is actually being ran in my Cron. If it updates every 15 minutes than something is wrong. My node has gone days after and IP change and no one can get in or out until I actually run the update script. I guess I will try ipupdate from now on. Maybe I am missing something in my cron folder.....????

Kevin
W7BOZ


Re: DTMF Decode Time

Rick May
 

Interesting ...All of his radio gear is Yaesu.

Thanks for all the replies. We will get it sorted out.

73' Rick KC0HH
Lamar, Colorado

--- On Sat, 1/7/12, AG0N-3055 <mcduffie@...> wrote:

From: AG0N-3055 <mcduffie@...>
Subject: Re: [irlp] DTMF Decode Time
To: irlp@...
Date: Saturday, January 7, 2012, 10:24 AM
















 









On Sat, 7 Jan 2012 07:56:07 -0800 (PST), Rick KC0HH wrote:



I am convinced it is his voice... 


I'm right there with you.



The combination of his voice and the radio characteristics is likely the

problem. Some people "spike the decoder" easily. I do it myself

sometimes. The irritant in your case is the same as when it happens to

me or my friends. It triggers the node's status, or some other command,

disrupting the conversation and usually forcing silence during the mute

period on the other end. I've heard several of my friends on other

nodes around the country do that while talking to them. It is

frequently when they pause and have a long syllable Ah..., or similar

word. Some microphone/radio combinations are bad for it too. Watch out

for the Yaesu series (several) of radios that use the MH48 mic. They

over clip and have a peaky high response. A simple fix of a .1uv 50V

cap across the mic element fixes them right up and makes you close talk

them so there is very little background noise with light clipping in the

modulator. Very common problem with the 8800/7900/7800/2800/180x, etc.

The characteristic can also increase "spiking the decoder".



Spiking that many digits in a row is extreme. I'd love to hear a sample

of his audio sometime.



Gary

--

http://ag0n.net

3055: http://ag0n.net/irlp/3055

NodeOp Help Page: http://ag0n.net/irlp

























[Non-text portions of this message have been removed]


Re: DTMF Decode Time

Gary - AG0N
 

On Sat, 7 Jan 2012 07:56:07 -0800 (PST), Rick KC0HH wrote:

I am convinced it is his voice... 
I'm right there with you.

The combination of his voice and the radio characteristics is likely the
problem. Some people "spike the decoder" easily. I do it myself
sometimes. The irritant in your case is the same as when it happens to
me or my friends. It triggers the node's status, or some other command,
disrupting the conversation and usually forcing silence during the mute
period on the other end. I've heard several of my friends on other
nodes around the country do that while talking to them. It is
frequently when they pause and have a long syllable Ah..., or similar
word. Some microphone/radio combinations are bad for it too. Watch out
for the Yaesu series (several) of radios that use the MH48 mic. They
over clip and have a peaky high response. A simple fix of a .1uv 50V
cap across the mic element fixes them right up and makes you close talk
them so there is very little background noise with light clipping in the
modulator. Very common problem with the 8800/7900/7800/2800/180x, etc.
The characteristic can also increase "spiking the decoder".

Spiking that many digits in a row is extreme. I'd love to hear a sample
of his audio sometime.

Gary
--
http://ag0n.net
3055: http://ag0n.net/irlp/3055
NodeOp Help Page: http://ag0n.net/irlp


Re: DTMF Decode Time

k9dc
 

Is the audio de-emphasized and filtered between the MVS and the node? What is the source of the MVS audio? What level is hitting the IRLP card? I still think something is wrong with the interface. DaveC can specify, but I think the decode delay is way longer than 50 ms, probably 200 to 250.

-k9dc

On Jan 7, 2012, at 10:56, Rick KC0HH <kc0hh@...> wrote:

Hi Dave,

Equipment is a Micor UHF and a MSR2000 VHF using S-Com 7330 controllers. IRLP is at my house using a GE MVS UHF simplex link radio to an identical MVS on each repeater. The audio is quite good.

I am convinced it is his voice... I had to add 50mS to the "Anti-Falsing Timer" in the repeater controller because he would trigger the DTMF mute on the repeater and silence the repeat audio. That fixed the falsing on the repeater, but I was wondering if there was a delay available to the IRLP DTMF decoder. Dave C answered and said there is not. I didn't want to make a big deal out of this and I absolutely will not embarrass him. I can change the various IRLP status commands to three digits instead of two so he will not trigger these as he does now. If doesn't happen often, but he has triggered "73" with his voice. I hate to change the disconnect command.....

73' Rick KC0HH
Lamar, Colorado

--- On Sat, 1/7/12, Dave Gingrich <Dave@...> wrote:

From: Dave Gingrich <Dave@...>
Subject: Re: [irlp] DTMF Decode Time
To: irlp@...
Date: Saturday, January 7, 2012, 6:23 AM


























Unless you need it (hardly anyone does), you should turn off DTMFREGEN, that would clean out all of those entries. But something has to be terribly wrong with the audio to the IRLP card. I see extraneous digits on my nodes, maybe once monthly, if that. Something is broken in your set up.



Perhaps you could provide some details of the radio used, and the audio path from the radio to the IRLP card and sound card. Are you using de-emphasized audio?



I've NEVER seen it that bad.



-k9dc



On Jan 7, 2012, at 2:23 AM, Rick KC0HH wrote:



Hi Dave,
I scrolled back through the log file and here are some better short snippets of him and what I am talking about. Lengthening the decode time might fix this. I don't see any "B" tones decoded. I may have to use a "B" prefix on everything.....
Dec 02 2011 16:54:51 -0700 decode: DTMF = 52
Dec 02 2011 16:54:51 -0700 decode: Invalid command length: 52
Dec 02 2011 16:59:09 -0700 stn399 dtmfregen 7
Dec 02 2011 17:00:09 -0700 stn399 dtmfregen 5
Dec 02 2011 17:00:56 -0700 stn399 dtmfregen C
Dec 02 2011 17:01:28 -0700 decode: DTMF = 55
Dec 02 2011 17:01:28 -0700 decode: Invalid command length: 55
Dec 02 2011 17:03:07 -0700 decode: DTMF = 215
Dec 02 2011 17:03:07 -0700 decode: Invalid command length: 215
Dec 02 2011 17:04:23 -0700 stn399 dtmfregen 7
Dec 02 2011 17:05:20 -0700 stn399
dtmfregen 5
Dec 02 2011 17:06:16 -0700 decode: DTMF = 2
Dec 02 2011 17:06:16 -0700 decode: Invalid command length: 2
Dec 02 2011 17:07:41 -0700 decode: DTMF = 5
Dec 02 2011 17:07:41 -0700 decode: Invalid command
length: 5
Dec 02 2011 17:08:48 -0700 decode: DTMF = 5
Dec 02 2011 17:08:48 -0700 decode: Invalid command length: 5
Dec 02 2011 17:09:55 -0700 decode: DTMF = 6
Dec 02 2011 17:09:55 -0700 decode: Invalid command length: 6
Dec 02 2011 17:10:37 -0700 decode: DTMF = 1
Dec 02 2011 17:10:37 -0700 decode: Invalid command length: 1
Dec 02 2011 17:15:04 -0700 stn399 dtmfregen 1
Dec 02 2011 17:17:20 -0700 decode: DTMF = 11
Dec 02 2011 17:17:20 -0700 decode: Invalid command length: 11
Dec 02 2011 17:19:29 -0700 stn399 dtmfregen 7
Dec 02 2011 17:20:13 -0700 decode: DTMF = 55
Dec 02 2011 17:20:13 -0700 decode: Invalid command length: 55
Dec 02 2011 17:21:27 -0700 decode: DTMF = 5
Dec 02 2011 17:21:27 -0700 decode: Invalid command length: 5
Dec 09 2011 21:57:56 -0700 decode: DTMF = 38888888877
Dec 09 2011 21:57:56 -0700 decode: Invalid command length: 38888888877
Dec 09 2011 21:58:05 -0700 decode: DTMF = 88
Dec 09 2011 21:58:05 -0700 decode: Invalid command length: 88
Dec 09 2011 21:58:22 -0700 decode: DTMF = 33
Dec 09 2011 21:58:22 -0700 decode: Invalid command length: 33
Dec 09 2011 21:58:31 -0700 decode: DTMF = 33887
Dec 09 2011 21:58:31 -0700 decode: Invalid command length: 33887
Dec 09 2011 21:58:39 -0700 decode: DTMF = 44
Dec 14 2011 16:52:30 -0700 decode: DTMF = 5
Dec 14 2011 16:52:30 -0700 decode: Invalid command length: 5
Dec 14 2011 16:54:58 -0700 decode: DTMF = 5
Dec 14 2011
16:54:58 -0700 decode: Invalid command length: 5
Dec 14 2011 16:56:48 -0700 decode: DTMF = AA
Dec 14 2011 16:56:48 -0700 decode: The command contains a bad digit (S,P,A,B,C,D)
Dec 14 2011 16:57:47 -0700 decode: DTMF = 55AA5
Dec 14 2011 16:57:47 -0700 decode: The command contains a bad digit (S,P,A,B,C,D)
Dec 14 2011 16:59:26 -0700 stn399 dtmfregen 8
Dec 14 2011 17:00:00 -0700 decode: DTMF = A
Dec 14 2011 17:00:00 -0700 decode: The command contains a bad digit (S,P,A,B,C,D)
Dec 14 2011 17:02:54 -0700 stn399 dtmfregen C
Dec 14 2011 17:03:54 -0700 decode: DTMF = A
Dec 14 2011 17:03:54 -0700 decode: The command contains a bad digit (S,P,A,B,C,D)
Dec 14 2011 17:04:33 -0700 decode: DTMF = 3
Dec 14 2011 17:04:33 -0700 decode: Invalid command length: 3
73' Rick KC0HH
Lamar, Colorado
Node 3774
--- On Fri, 1/6/12, ve7ltd <dcameron@...> wrote:
From: ve7ltd <dcameron@...>
Subject: [irlp] Re: DTMF Decode Time
To: irlp@...
Date: Friday, January 6, 2012, 4:21 PM
The decode time is fixed and not adjustable. What is the result of his DTMF triggering? There is no way that he is dialing a 4 digit node :)
Dave
--- In irlp@..., "Rick" <kc0hh@...> wrote:
Hi All,
Is there a way to lengthen the DTMF decode time required for IRLP functions. I have a repeater user here that triggers DTMF functions with his voice inflections. He would actually trigger the DTMF tone mute on the repeater audio until I lengthened the required decode time in the controller. I would like to do the same for the IRLP decoder.
Rick KC0HH
Node 3774
Lamar, Colorado
[Non-text portions of this message have been removed]
------------------------------------
--- IRLP-Owners YahooGroups List ---Yahoo! Groups Links


























[Non-text portions of this message have been removed]



------------------------------------

--- IRLP-Owners YahooGroups List ---Yahoo! Groups Links



Re: DTMF Decode Time

Rick May
 

Hi Dave,

    Equipment is a Micor UHF and a MSR2000 VHF using S-Com 7330 controllers.  IRLP is at my house using a GE MVS UHF simplex link radio to an identical MVS on each repeater. The audio is quite good.

    I am convinced it is his voice...  I had to add 50mS to the "Anti-Falsing Timer" in the repeater controller because he would trigger the DTMF mute on the repeater and silence the repeat audio. That fixed the falsing on the repeater, but I was wondering if there was a delay available to the IRLP DTMF decoder. Dave C answered and said there is not. I didn't want to make a big deal out of this and I absolutely will not embarrass him. I can change the various IRLP status commands to three digits instead of two so he will not trigger these as he does now.  If doesn't happen often, but he has triggered "73" with his voice.  I hate to change  the disconnect command.....

73' Rick KC0HH
Lamar, Colorado

--- On Sat, 1/7/12, Dave Gingrich <Dave@...> wrote:

From: Dave Gingrich <Dave@...>
Subject: Re: [irlp] DTMF Decode Time
To: irlp@...
Date: Saturday, January 7, 2012, 6:23 AM
















 









Unless you need it (hardly anyone does), you should turn off DTMFREGEN, that would clean out all of those entries. But something has to be terribly wrong with the audio to the IRLP card. I see extraneous digits on my nodes, maybe once monthly, if that. Something is broken in your set up.



Perhaps you could provide some details of the radio used, and the audio path from the radio to the IRLP card and sound card. Are you using de-emphasized audio?



I've NEVER seen it that bad.



-k9dc



On Jan 7, 2012, at 2:23 AM, Rick KC0HH wrote:



Hi Dave,
I scrolled back through the log file and here are some better short snippets of him and what I am talking about. Lengthening the decode time might fix this. I don't see any "B" tones decoded. I may have to use a "B" prefix on everything.....
Dec 02 2011 16:54:51 -0700 decode: DTMF = 52
Dec 02 2011 16:54:51 -0700 decode: Invalid command length: 52
Dec 02 2011 16:59:09 -0700 stn399 dtmfregen 7
Dec 02 2011 17:00:09 -0700 stn399 dtmfregen 5
Dec 02 2011 17:00:56 -0700 stn399 dtmfregen C
Dec 02 2011 17:01:28 -0700 decode: DTMF = 55
Dec 02 2011 17:01:28 -0700 decode: Invalid command length: 55
Dec 02 2011 17:03:07 -0700 decode: DTMF = 215
Dec 02 2011 17:03:07 -0700 decode: Invalid command length: 215
Dec 02 2011 17:04:23 -0700 stn399 dtmfregen 7
Dec 02 2011 17:05:20 -0700 stn399
dtmfregen 5
Dec 02 2011 17:06:16 -0700 decode: DTMF = 2
Dec 02 2011 17:06:16 -0700 decode: Invalid command length: 2
Dec 02 2011 17:07:41 -0700 decode: DTMF = 5
Dec 02 2011 17:07:41 -0700 decode: Invalid command
length: 5
Dec 02 2011 17:08:48 -0700 decode: DTMF = 5
Dec 02 2011 17:08:48 -0700 decode: Invalid command length: 5
Dec 02 2011 17:09:55 -0700 decode: DTMF = 6
Dec 02 2011 17:09:55 -0700 decode: Invalid command length: 6
Dec 02 2011 17:10:37 -0700 decode: DTMF = 1
Dec 02 2011 17:10:37 -0700 decode: Invalid command length: 1
Dec 02 2011 17:15:04 -0700 stn399 dtmfregen 1
Dec 02 2011 17:17:20 -0700 decode: DTMF = 11
Dec 02 2011 17:17:20 -0700 decode: Invalid command length: 11
Dec 02 2011 17:19:29 -0700 stn399 dtmfregen 7
Dec 02 2011 17:20:13 -0700 decode: DTMF = 55
Dec 02 2011 17:20:13 -0700 decode: Invalid command length: 55
Dec 02 2011 17:21:27 -0700 decode: DTMF = 5
Dec 02 2011 17:21:27 -0700 decode: Invalid command length: 5
Dec 09 2011 21:57:56 -0700 decode: DTMF = 38888888877
Dec 09 2011 21:57:56 -0700 decode: Invalid command length: 38888888877
Dec 09 2011 21:58:05 -0700 decode: DTMF = 88
Dec 09 2011 21:58:05 -0700 decode: Invalid command length: 88
Dec 09 2011 21:58:22 -0700 decode: DTMF = 33
Dec 09 2011 21:58:22 -0700 decode: Invalid command length: 33
Dec 09 2011 21:58:31 -0700 decode: DTMF = 33887
Dec 09 2011 21:58:31 -0700 decode: Invalid command length: 33887
Dec 09 2011 21:58:39 -0700 decode: DTMF = 44
Dec 14 2011 16:52:30 -0700 decode: DTMF = 5
Dec 14 2011 16:52:30 -0700 decode: Invalid command length: 5
Dec 14 2011 16:54:58 -0700 decode: DTMF = 5
Dec 14 2011
16:54:58 -0700 decode: Invalid command length: 5
Dec 14 2011 16:56:48 -0700 decode: DTMF = AA
Dec 14 2011 16:56:48 -0700 decode: The command contains a bad digit (S,P,A,B,C,D)
Dec 14 2011 16:57:47 -0700 decode: DTMF = 55AA5
Dec 14 2011 16:57:47 -0700 decode: The command contains a bad digit (S,P,A,B,C,D)
Dec 14 2011 16:59:26 -0700 stn399 dtmfregen 8
Dec 14 2011 17:00:00 -0700 decode: DTMF = A
Dec 14 2011 17:00:00 -0700 decode: The command contains a bad digit (S,P,A,B,C,D)
Dec 14 2011 17:02:54 -0700 stn399 dtmfregen C
Dec 14 2011 17:03:54 -0700 decode: DTMF = A
Dec 14 2011 17:03:54 -0700 decode: The command contains a bad digit (S,P,A,B,C,D)
Dec 14 2011 17:04:33 -0700 decode: DTMF = 3
Dec 14 2011 17:04:33 -0700 decode: Invalid command length: 3
73' Rick KC0HH
Lamar, Colorado
Node 3774
--- On Fri, 1/6/12, ve7ltd <dcameron@...> wrote:
From: ve7ltd <dcameron@...>
Subject: [irlp] Re: DTMF Decode Time
To: irlp@...
Date: Friday, January 6, 2012, 4:21 PM
The decode time is fixed and not adjustable. What is the result of his DTMF triggering? There is no way that he is dialing a 4 digit node :)
Dave
--- In irlp@..., "Rick" <kc0hh@...> wrote:
Hi All,
Is there a way to lengthen the DTMF decode time required for IRLP functions. I have a repeater user here that triggers DTMF functions with his voice inflections. He would actually trigger the DTMF tone mute on the repeater audio until I lengthened the required decode time in the controller. I would like to do the same for the IRLP decoder.
Rick KC0HH
Node 3774
Lamar, Colorado
[Non-text portions of this message have been removed]
------------------------------------
--- IRLP-Owners YahooGroups List ---Yahoo! Groups Links


























[Non-text portions of this message have been removed]


Re: IRLP "Update Script" and ISP problems

k9dc
 

crontab -l (that is a lowercase L)

On Jan 7, 2012, at 9:06 AM, Dave Gingrich wrote:

It is easy enough to check...

Log in as (or become) user repeater and run the command 'crontab -l' You should see several entries, including ipupdate_cron. The */15 at the beginning of the line means it is set to run every 15 minutes.


Re: IRLP "Update Script" and ISP problems

k9dc
 

It is easy enough to check...

Log in as (or become) user repeater and run the command 'crontab -l' You should see several entries, including ipupdate_cron. The */15 at the beginning of the line means it is set to run every 15 minutes.

Cron keeps its own log file, but you have to be root to look at it. after becoming root, either the command 'cat /var/log/cron' That will produce a lot of data, but you are interested in the most recent stuff at the end. You should see the log of cron jobs executed with recent timestamps.

ipupdate first looks for a change in IP, and only contacts the IRLP server if it has detected a change. a crappy Internet connection can screw that up. You MUST have a reasonably reliable Internet connection. If you do not, all bets are off.

-k9dc

On Jan 7, 2012, at 8:44 AM, w7boz wrote:

Yeah, My ISP is crap! But the best I can afford for High Speed. I wonder if the ipupdate is actually being ran in my Cron. If it updates every 15 minutes than something is wrong. My node has gone days after and IP change and no one can get in or out until I actually run the update script. I guess I will try ipupdate from now on. Maybe I am missing something in my cron folder.....????

Kevin
W7BOZ


Re: IRLP "Update Script" and ISP problems

w7boz
 

Yeah, My ISP is crap! But the best I can afford for High Speed. I wonder if the ipupdate is actually being ran in my Cron. If it updates every 15 minutes than something is wrong. My node has gone days after and IP change and no one can get in or out until I actually run the update script. I guess I will try ipupdate from now on. Maybe I am missing something in my cron folder.....????

Kevin
W7BOZ

--- In irlp@..., Dave Gingrich <Dave@...> wrote:

Ouch, that sounds really ugly.

The command 'ipupdate' is the one you want to use. Normally it runs every 15 minutes from cron, but if your IP changes, a manual 'ipupdate' can speed things up, but not by much. The 'update' command is used to make sure you have the most current version of IRLP installed. That runs once per day at 0300 (+/-) node time and normally does not have to be run manually.

For my mobile nodes (cell modem based), I hacked together a script that checks the node's external IP once per minute. If it ever changes (which happens frequently) it drops the current connection, performs an ipupdate, and reconnects to the node it just dropped. It does require an independent server somewhere to perform the IP address check against, and why I did not release to IRLPdom.

Honestly, if your Internet service is that bad, there really is nothing you can do to make IRLP work well for you. You are going to have to find a different ISP, or move the node to a friends house that has more reliable Internet.

-k9dc

On Jan 6, 2012, at 4:34 AM, w7boz wrote:

My ISP is Digis. Uses a dish on the roof to connect to their tower. Their system fails all the time, connections hang up (lag), and the IP Addresses changes when the connection fails and reconnects. Or when I have to manually reboot their (modem), and my Router. Their system is always intermittent, hangs, and goes down all the time.

Then I have to run the update script, or I get no IRLP connections in or out. Hope this is more clear for you.

Thanks, Kevin
W7BOZ

--- In irlp@..., Dave Gingrich <Dave@> wrote:

A problem with lag?... Exactly what do they mean? Also what type of connection (technology) are you using?

-k9dc

On Jan 5, 2012, at 5:52 AM, w7boz wrote:

Hello Group,

My ISP keeps having problems with lag and having to reset their "Modem". I have to manually run the "Update' script to get my IRLP connection to work again. Sometimes my ISP IP address changes, and I am unaware of it. Untill I run the "update" script my IRLP node will not work. I would like to know more about my problem, and what I can do to fix it.



------------------------------------

--- IRLP-Owners YahooGroups List ---Yahoo! Groups Links



Re: DTMF Decode Time

k9dc
 

Unless you need it (hardly anyone does), you should turn off DTMFREGEN, that would clean out all of those entries. But something has to be terribly wrong with the audio to the IRLP card. I see extraneous digits on my nodes, maybe once monthly, if that. Something is broken in your set up.

Perhaps you could provide some details of the radio used, and the audio path from the radio to the IRLP card and sound card. Are you using de-emphasized audio?

I've NEVER seen it that bad.

-k9dc

On Jan 7, 2012, at 2:23 AM, Rick KC0HH wrote:

Hi Dave,

I scrolled back through the log file and here are some better short snippets of him and what I am talking about. Lengthening the decode time might fix this. I don't see any "B" tones decoded. I may have to use a "B" prefix on everything.....


Dec 02 2011 16:54:51 -0700 decode: DTMF = 52
Dec 02 2011 16:54:51 -0700 decode: Invalid command length: 52
Dec 02 2011 16:59:09 -0700 stn399 dtmfregen 7
Dec 02 2011 17:00:09 -0700 stn399 dtmfregen 5
Dec 02 2011 17:00:56 -0700 stn399 dtmfregen C
Dec 02 2011 17:01:28 -0700 decode: DTMF = 55
Dec 02 2011 17:01:28 -0700 decode: Invalid command length: 55
Dec 02 2011 17:03:07 -0700 decode: DTMF = 215
Dec 02 2011 17:03:07 -0700 decode: Invalid command length: 215
Dec 02 2011 17:04:23 -0700 stn399 dtmfregen 7
Dec 02 2011 17:05:20 -0700 stn399
dtmfregen 5
Dec 02 2011 17:06:16 -0700 decode: DTMF = 2
Dec 02 2011 17:06:16 -0700 decode: Invalid command length: 2
Dec 02 2011 17:07:41 -0700 decode: DTMF = 5
Dec 02 2011 17:07:41 -0700 decode: Invalid command
length: 5
Dec 02 2011 17:08:48 -0700 decode: DTMF = 5
Dec 02 2011 17:08:48 -0700 decode: Invalid command length: 5
Dec 02 2011 17:09:55 -0700 decode: DTMF = 6
Dec 02 2011 17:09:55 -0700 decode: Invalid command length: 6
Dec 02 2011 17:10:37 -0700 decode: DTMF = 1
Dec 02 2011 17:10:37 -0700 decode: Invalid command length: 1
Dec 02 2011 17:15:04 -0700 stn399 dtmfregen 1
Dec 02 2011 17:17:20 -0700 decode: DTMF = 11
Dec 02 2011 17:17:20 -0700 decode: Invalid command length: 11
Dec 02 2011 17:19:29 -0700 stn399 dtmfregen 7
Dec 02 2011 17:20:13 -0700 decode: DTMF = 55
Dec 02 2011 17:20:13 -0700 decode: Invalid command length: 55
Dec 02 2011 17:21:27 -0700 decode: DTMF = 5
Dec 02 2011 17:21:27 -0700 decode: Invalid command length: 5

Dec 09 2011 21:57:56 -0700 decode: DTMF = 38888888877
Dec 09 2011 21:57:56 -0700 decode: Invalid command length: 38888888877
Dec 09 2011 21:58:05 -0700 decode: DTMF = 88
Dec 09 2011 21:58:05 -0700 decode: Invalid command length: 88
Dec 09 2011 21:58:22 -0700 decode: DTMF = 33
Dec 09 2011 21:58:22 -0700 decode: Invalid command length: 33
Dec 09 2011 21:58:31 -0700 decode: DTMF = 33887
Dec 09 2011 21:58:31 -0700 decode: Invalid command length: 33887
Dec 09 2011 21:58:39 -0700 decode: DTMF = 44

Dec 14 2011 16:52:30 -0700 decode: DTMF = 5
Dec 14 2011 16:52:30 -0700 decode: Invalid command length: 5
Dec 14 2011 16:54:58 -0700 decode: DTMF = 5
Dec 14 2011
16:54:58 -0700 decode: Invalid command length: 5
Dec 14 2011 16:56:48 -0700 decode: DTMF = AA
Dec 14 2011 16:56:48 -0700 decode: The command contains a bad digit (S,P,A,B,C,D)
Dec 14 2011 16:57:47 -0700 decode: DTMF = 55AA5
Dec 14 2011 16:57:47 -0700 decode: The command contains a bad digit (S,P,A,B,C,D)
Dec 14 2011 16:59:26 -0700 stn399 dtmfregen 8
Dec 14 2011 17:00:00 -0700 decode: DTMF = A
Dec 14 2011 17:00:00 -0700 decode: The command contains a bad digit (S,P,A,B,C,D)
Dec 14 2011 17:02:54 -0700 stn399 dtmfregen C
Dec 14 2011 17:03:54 -0700 decode: DTMF = A
Dec 14 2011 17:03:54 -0700 decode: The command contains a bad digit (S,P,A,B,C,D)
Dec 14 2011 17:04:33 -0700 decode: DTMF = 3
Dec 14 2011 17:04:33 -0700 decode: Invalid command length: 3


73' Rick KC0HH
Lamar, Colorado
Node 3774


--- On Fri, 1/6/12, ve7ltd <dcameron@...> wrote:

From: ve7ltd <dcameron@...>
Subject: [irlp] Re: DTMF Decode Time
To: irlp@...
Date: Friday, January 6, 2012, 4:21 PM


























The decode time is fixed and not adjustable. What is the result of his DTMF triggering? There is no way that he is dialing a 4 digit node :)



Dave



--- In irlp@..., "Rick" <kc0hh@...> wrote:

Hi All,
Is there a way to lengthen the DTMF decode time required for IRLP functions. I have a repeater user here that triggers DTMF functions with his voice inflections. He would actually trigger the DTMF tone mute on the repeater audio until I lengthened the required decode time in the controller. I would like to do the same for the IRLP decoder.
Rick KC0HH
Node 3774
Lamar, Colorado


























[Non-text portions of this message have been removed]



------------------------------------

--- IRLP-Owners YahooGroups List ---Yahoo! Groups Links



Re: DTMF Decode Time

Rick May
 

Hi Dave,

    I scrolled back through the log file and here are some better short snippets of him and what I am talking about.  Lengthening the decode time might fix this.  I don't see any "B" tones decoded. I may have to use a "B" prefix on everything.....


Dec 02 2011 16:54:51 -0700 decode: DTMF = 52
Dec 02 2011 16:54:51 -0700 decode: Invalid command length: 52
Dec 02 2011 16:59:09 -0700 stn399 dtmfregen 7
Dec 02 2011 17:00:09 -0700 stn399 dtmfregen 5
Dec 02 2011 17:00:56 -0700 stn399 dtmfregen C
Dec 02 2011 17:01:28 -0700 decode: DTMF = 55
Dec 02 2011 17:01:28 -0700 decode: Invalid command length: 55
Dec 02 2011 17:03:07 -0700 decode: DTMF = 215
Dec 02 2011 17:03:07 -0700 decode: Invalid command length: 215
Dec 02 2011 17:04:23 -0700 stn399 dtmfregen 7
Dec 02 2011 17:05:20 -0700 stn399
dtmfregen 5
Dec 02 2011 17:06:16 -0700 decode: DTMF = 2
Dec 02 2011 17:06:16 -0700 decode: Invalid command length: 2
Dec 02 2011 17:07:41 -0700 decode: DTMF = 5
Dec 02 2011 17:07:41 -0700 decode: Invalid command
length: 5
Dec 02 2011 17:08:48 -0700 decode: DTMF = 5
Dec 02 2011 17:08:48 -0700 decode: Invalid command length: 5
Dec 02 2011 17:09:55 -0700 decode: DTMF = 6
Dec 02 2011 17:09:55 -0700 decode: Invalid command length: 6
Dec 02 2011 17:10:37 -0700 decode: DTMF = 1
Dec 02 2011 17:10:37 -0700 decode: Invalid command length: 1
Dec 02 2011 17:15:04 -0700 stn399 dtmfregen 1
Dec 02 2011 17:17:20 -0700 decode: DTMF = 11
Dec 02 2011 17:17:20 -0700 decode: Invalid command length: 11
Dec 02 2011 17:19:29 -0700 stn399 dtmfregen 7
Dec 02 2011 17:20:13 -0700 decode: DTMF = 55
Dec 02 2011 17:20:13 -0700 decode: Invalid command length: 55
Dec 02 2011 17:21:27 -0700 decode: DTMF = 5
Dec 02 2011 17:21:27 -0700 decode: Invalid command length: 5

Dec 09 2011 21:57:56 -0700 decode: DTMF = 38888888877
Dec 09 2011 21:57:56 -0700 decode: Invalid command length: 38888888877
Dec 09 2011 21:58:05 -0700 decode: DTMF = 88
Dec 09 2011 21:58:05 -0700 decode: Invalid command length: 88
Dec 09 2011 21:58:22 -0700 decode: DTMF = 33
Dec 09 2011 21:58:22 -0700 decode: Invalid command length: 33
Dec 09 2011 21:58:31 -0700 decode: DTMF = 33887
Dec 09 2011 21:58:31 -0700 decode: Invalid command length: 33887
Dec 09 2011 21:58:39 -0700 decode: DTMF = 44

Dec 14 2011 16:52:30 -0700 decode: DTMF = 5
Dec 14 2011 16:52:30 -0700 decode: Invalid command length: 5
Dec 14 2011 16:54:58 -0700 decode: DTMF = 5
Dec 14 2011
16:54:58 -0700 decode: Invalid command length: 5
Dec 14 2011 16:56:48 -0700 decode: DTMF = AA
Dec 14 2011 16:56:48 -0700 decode: The command contains a bad digit (S,P,A,B,C,D)
Dec 14 2011 16:57:47 -0700 decode: DTMF = 55AA5
Dec 14 2011 16:57:47 -0700 decode: The command contains a bad digit (S,P,A,B,C,D)
Dec 14 2011 16:59:26 -0700 stn399 dtmfregen 8
Dec 14 2011 17:00:00 -0700 decode: DTMF = A
Dec 14 2011 17:00:00 -0700 decode: The command contains a bad digit (S,P,A,B,C,D)
Dec 14 2011 17:02:54 -0700 stn399 dtmfregen C
Dec 14 2011 17:03:54 -0700 decode: DTMF = A
Dec 14 2011 17:03:54 -0700 decode: The command contains a bad digit (S,P,A,B,C,D)
Dec 14 2011 17:04:33 -0700 decode: DTMF = 3
Dec 14 2011 17:04:33 -0700 decode: Invalid command length: 3

 
73' Rick KC0HH
Lamar, Colorado
Node 3774

--- On Fri, 1/6/12, ve7ltd <dcameron@...> wrote:

From: ve7ltd <dcameron@...>
Subject: [irlp] Re: DTMF Decode Time
To: irlp@...
Date: Friday, January 6, 2012, 4:21 PM
















 









The decode time is fixed and not adjustable. What is the result of his DTMF triggering? There is no way that he is dialing a 4 digit node :)



Dave



--- In irlp@..., "Rick" <kc0hh@...> wrote:

Hi All,
Is there a way to lengthen the DTMF decode time required for IRLP functions. I have a repeater user here that triggers DTMF functions with his voice inflections. He would actually trigger the DTMF tone mute on the repeater audio until I lengthened the required decode time in the controller. I would like to do the same for the IRLP decoder.
Rick KC0HH
Node 3774
Lamar, Colorado


Re: DTMF Decode Time

Rick May
 

Hi Dave,
 
    No, he does not send connect commands, but he will trigger a "73" and disconnect. We just keep hearing "Last Station Connected" , "Link Status" , and "You Are Currently Connected To Node Number ..."  announcements while he is speaking. I have IRLPvAux with status commands and he triggers these.  He moved here from Denver a short time ago and at first I thought someone here was screwing with him on the repeater/IRLP Node.   
Here is a short sample of the log when he is speaking.

Jan 03 2012 17:41:53 -0700 decode: DTMF = 3990
Jan 03 2012 17:41:53 -0700 IRLP call initiated to stn3990
Jan 03 2012 17:41:55 -0700 stn399 reply connectok UNCOMP
Jan 03 2012 17:47:43 -0700 decode: DTMF = AA
Jan 03 2012 17:47:43 -0700 decode: The command contains a bad digit (S,P,A,B,C,D)
Jan 03 2012 17:49:16 -0700 decode: DTMF = A5
Jan 03 2012 17:49:16 -0700 decode: The command contains a bad digit (S,P,A,B,C,D)
Jan 03 2012 17:50:03 -0700 decode: DTMF = 2
Jan 03 2012 17:50:03 -0700 decode: Invalid command length: 2
Jan 03 2012 17:54:07 -0700 decode: DTMF = A
Jan 03 2012 17:54:07 -0700 decode: The command contains a bad digit (S,P,A,B,C,D)
Jan 03 2012 17:56:23 -0700 decode: DTMF = 5
Jan 03 2012 17:56:23 -0700 decode: Invalid command length: 5
Jan 03 2012 17:58:44 -0700 decode: DTMF = 5
Jan 03 2012 17:58:44 -0700 decode: Invalid command length: 5
Jan 03 2012 18:00:09 -0700 decode: DTMF = A
Jan 03 2012 18:00:09 -0700 decode: The command contains a bad digit (S,P,A,B,C,D)
Jan 03 2012 18:02:39 -0700 decode: DTMF = 2
Jan 03 2012 18:02:39 -0700 decode: Invalid command length: 2
Jan 03 2012 18:03:47 -0700 decode: DTMF = 5
Jan 03 2012 18:03:48 -0700 decode: Invalid command length: 5
Jan 03 2012 18:03:59 -0700 decode: DTMF = 73
Jan 03 2012 18:03:59 -0700 Node Disconnect from stn3990

He actually disconnected the node with his voice.

73' Rick KC0HH
Lamar, Colorado

--- On Fri, 1/6/12, ve7ltd <dcameron@...> wrote:

From: ve7ltd <dcameron@...>
Subject: [irlp] Re: DTMF Decode Time
To: irlp@...
Date: Friday, January 6, 2012, 4:21 PM
















 









The decode time is fixed and not adjustable. What is the result of his DTMF triggering? There is no way that he is dialing a 4 digit node :)



Dave



--- In irlp@..., "Rick" <kc0hh@...> wrote:

Hi All,
Is there a way to lengthen the DTMF decode time required for IRLP functions. I have a repeater user here that triggers DTMF functions with his voice inflections. He would actually trigger the DTMF tone mute on the repeater audio until I lengthened the required decode time in the controller. I would like to do the same for the IRLP decoder.
Rick KC0HH
Node 3774
Lamar, Colorado