Date   

Re: DTMF tones not recognized

Albert Febraro <w6aax@...>
 

 The auto gain has an "OO" in it. Second Mic setting or Capture is set to 44 at the moment. You make an interesting point about the TYT level at the connector. I guess I can put a scope on it at some point and try to measure it if that is possible.

Again, thanks for all the troubleshooting help.
Al


From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> on behalf of David Cameron - IRLP <dcameron@...>
Sent: Thursday, May 14, 2020 11:32 AM
To: IRLP@irlp.groups.io <IRLP@irlp.groups.io>
Subject: Re: [IRLP] DTMF tones not recognized
 
The software mixer controls do not affect the level seen by the DTMF
decoder. It sees the raw audio from the receiver.

I think the audio point on the TYT connector is de-emphasized, but I
wonder how much level is there.

If you are using a Syba sound card, you are likely using a Pi setup. On
the program alsamixer, press TAB twice and:

Does the Auto Gain Control have an "MM" or an "OO" in it?
What is the second Mic setting with CAPTURE set to?

That will give me an idea if the level is too low or too high out of the
radio.

Dave
               

On 2020-05-14 11:08 a.m., Albert Febraro wrote:
> David:
>    I am using the TYT-9000D UHF radio for my node.
> The audio source comes directly from the radio main board (RX Audio) to
> the mic input to a SYBA USB sound adaptor to the Pi.
> The alsamixer MIC input  is set to 33.
> When I run the audio test , it passes the test using voice through my
> Alinco Ht. It fails if I send a DTMF tone for 8 seconds (reports 0
> clipping, ) audio).
>
>   Thanks,
> Al,
> W6AAX
>
> ------------------------------------------------------------------------
> *From:* IRLP@irlp.groups.io <IRLP@irlp.groups.io> on behalf of David
> Cameron - IRLP <dcameron@...>
> *Sent:* Thursday, May 14, 2020 10:30 AM
> *To:* IRLP@irlp.groups.io <IRLP@irlp.groups.io>
> *Subject:* Re: [IRLP] DTMF tones not recognized
> This is not a common problem, but it creeps up from time to time.
>
> What radio are you using for the node radio? What audio source are you
> using in the radio? If the source is not a squelched, de-emphasized
> source, then the DTMF decoder is not able to decode due to the variance
> in levels in the tones.
>
> What audio output are you using from the node radio? If it is a
> discriminator source, that is the problem.
>
> Also, if the level of the audio from the node radio to the node is
> either very high or very low, it can affect the ability for the decoder
> to work. What is the input audio settings like on the alsamixer screen?
>
> David Cameron
> VE7LTD
>
> On 2020-05-14 9:13 a.m., Albert Febraro wrote:
>> This may be a common issue but being new to IRLP I'm still fine tuning
>> my node and learning. The issue is that when I send DTMF tones from
>> different radios the node does not recognize the tones. I have one radio
>> (Kenwood TH-F6) that when I transmit tones the node doesn't decode them
>> at all, however another radio (Alinco DJ-MD5) works perfectly. What is
>> interesting is that when I'm using my mobile radio (ICOM ID-5100) I can
>> bring up the echo node 9993, but cannot disconnect. I send a "73" but I
>> only hear the 7 when the node returns the echoed audio. My audio levels
>> are adjusted correctly as far as I can tell. I then have to disconnect
>> with a different radio. When I use the Alinco HT, I get good reports
>> audio and received audio is fine.
>> Al
>> W6AAX
>> node 3913
>>
>
>
>
>




Re: DTMF tones not recognized

David Cameron - IRLP
 

One other thought is to make sure you are using 25KHz wide mode in the TYT-9000D for the receiver bandwidth. You can also try 20KHz and 12.5KHz to see if it affects the decode ability.

Something is out of alignment - either the sending radios or the receiving radio. The adjustment of the IF in the receiver is suspect on the cheap TYT radio.

Dave Cameron

On 2020-05-14 11:08 a.m., Albert Febraro wrote:
David:
  I am using the TYT-9000D UHF radio for my node.
The audio source comes directly from the radio main board (RX Audio) to the mic input to a SYBA USB sound adaptor to the Pi.
The alsamixer MIC input  is set to 33.
When I run the audio test , it passes the test using voice through my Alinco Ht. It fails if I send a DTMF tone for 8 seconds (reports 0 clipping, ) audio).
 Thanks,
Al,
W6AAX
------------------------------------------------------------------------
*From:* IRLP@irlp.groups.io <IRLP@irlp.groups.io> on behalf of David Cameron - IRLP <dcameron@...>
*Sent:* Thursday, May 14, 2020 10:30 AM
*To:* IRLP@irlp.groups.io <IRLP@irlp.groups.io>
*Subject:* Re: [IRLP] DTMF tones not recognized
This is not a common problem, but it creeps up from time to time.
What radio are you using for the node radio? What audio source are you
using in the radio? If the source is not a squelched, de-emphasized
source, then the DTMF decoder is not able to decode due to the variance
in levels in the tones.
What audio output are you using from the node radio? If it is a
discriminator source, that is the problem.
Also, if the level of the audio from the node radio to the node is
either very high or very low, it can affect the ability for the decoder
to work. What is the input audio settings like on the alsamixer screen?
David Cameron
VE7LTD
On 2020-05-14 9:13 a.m., Albert Febraro wrote:
This may be a common issue but being new to IRLP I'm still fine tuning my node and learning. The issue is that when I send DTMF tones from different radios the node does not recognize the tones. I have one radio (Kenwood TH-F6) that when I transmit tones the node doesn't decode them at all, however another radio (Alinco DJ-MD5) works perfectly. What is interesting is that when I'm using my mobile radio (ICOM ID-5100) I can bring up the echo node 9993, but cannot disconnect. I send a "73" but I only hear the 7 when the node returns the echoed audio. My audio levels are adjusted correctly as far as I can tell. I then have to disconnect with a different radio. When I use the Alinco HT, I get good reports audio and received audio is fine.
Al
W6AAX
node 3913


Re: DTMF tones not recognized

David Cameron - IRLP
 

The software mixer controls do not affect the level seen by the DTMF decoder. It sees the raw audio from the receiver.

I think the audio point on the TYT connector is de-emphasized, but I wonder how much level is there.

If you are using a Syba sound card, you are likely using a Pi setup. On the program alsamixer, press TAB twice and:

Does the Auto Gain Control have an "MM" or an "OO" in it?
What is the second Mic setting with CAPTURE set to?

That will give me an idea if the level is too low or too high out of the radio.

Dave

On 2020-05-14 11:08 a.m., Albert Febraro wrote:
David:
  I am using the TYT-9000D UHF radio for my node.
The audio source comes directly from the radio main board (RX Audio) to the mic input to a SYBA USB sound adaptor to the Pi.
The alsamixer MIC input  is set to 33.
When I run the audio test , it passes the test using voice through my Alinco Ht. It fails if I send a DTMF tone for 8 seconds (reports 0 clipping, ) audio).
 Thanks,
Al,
W6AAX
------------------------------------------------------------------------
*From:* IRLP@irlp.groups.io <IRLP@irlp.groups.io> on behalf of David Cameron - IRLP <dcameron@...>
*Sent:* Thursday, May 14, 2020 10:30 AM
*To:* IRLP@irlp.groups.io <IRLP@irlp.groups.io>
*Subject:* Re: [IRLP] DTMF tones not recognized
This is not a common problem, but it creeps up from time to time.
What radio are you using for the node radio? What audio source are you
using in the radio? If the source is not a squelched, de-emphasized
source, then the DTMF decoder is not able to decode due to the variance
in levels in the tones.
What audio output are you using from the node radio? If it is a
discriminator source, that is the problem.
Also, if the level of the audio from the node radio to the node is
either very high or very low, it can affect the ability for the decoder
to work. What is the input audio settings like on the alsamixer screen?
David Cameron
VE7LTD
On 2020-05-14 9:13 a.m., Albert Febraro wrote:
This may be a common issue but being new to IRLP I'm still fine tuning my node and learning. The issue is that when I send DTMF tones from different radios the node does not recognize the tones. I have one radio (Kenwood TH-F6) that when I transmit tones the node doesn't decode them at all, however another radio (Alinco DJ-MD5) works perfectly. What is interesting is that when I'm using my mobile radio (ICOM ID-5100) I can bring up the echo node 9993, but cannot disconnect. I send a "73" but I only hear the 7 when the node returns the echoed audio. My audio levels are adjusted correctly as far as I can tell. I then have to disconnect with a different radio. When I use the Alinco HT, I get good reports audio and received audio is fine.
Al
W6AAX
node 3913


Re: DTMF tones not recognized

Albert Febraro <w6aax@...>
 

David:
  I am using the TYT-9000D UHF radio for my node.
The audio source comes directly from the radio main board (RX Audio) to the mic input to a SYBA USB sound adaptor to the Pi. 
The alsamixer MIC input  is set to 33.
When I run the audio test , it passes the test using voice through my Alinco Ht. It fails if I send a DTMF tone for 8 seconds (reports 0 clipping, ) audio).

 Thanks,
Al,
W6AAX


From: IRLP@irlp.groups.io <IRLP@irlp.groups.io> on behalf of David Cameron - IRLP <dcameron@...>
Sent: Thursday, May 14, 2020 10:30 AM
To: IRLP@irlp.groups.io <IRLP@irlp.groups.io>
Subject: Re: [IRLP] DTMF tones not recognized
 
This is not a common problem, but it creeps up from time to time.

What radio are you using for the node radio? What audio source are you
using in the radio? If the source is not a squelched, de-emphasized
source, then the DTMF decoder is not able to decode due to the variance
in levels in the tones.

What audio output are you using from the node radio? If it is a
discriminator source, that is the problem.

Also, if the level of the audio from the node radio to the node is
either very high or very low, it can affect the ability for the decoder
to work. What is the input audio settings like on the alsamixer screen?

David Cameron
VE7LTD

On 2020-05-14 9:13 a.m., Albert Febraro wrote:
> This may be a common issue but being new to IRLP I'm still fine tuning
> my node and learning. The issue is that when I send DTMF tones from
> different radios the node does not recognize the tones. I have one radio
> (Kenwood TH-F6) that when I transmit tones the node doesn't decode them
> at all, however another radio (Alinco DJ-MD5) works perfectly. What is
> interesting is that when I'm using my mobile radio (ICOM ID-5100) I can
> bring up the echo node 9993, but cannot disconnect. I send a "73" but I
> only hear the 7 when the node returns the echoed audio. My audio levels
> are adjusted correctly as far as I can tell. I then have to disconnect
> with a different radio. When I use the Alinco HT, I get good reports
> audio and received audio is fine.
> Al
> W6AAX
> node 3913
>




Re: DTMF tones not recognized

Tony VA7TF, VE7ACF
 

If a transmitter is off by 1 or 2+ kHz of TX frequency, that may cause an issue also. Check with a frequency counter the accuracy of the 3 different transmitters.

 

 

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

Regards,

 

Tony

 

From: David Cameron - IRLP
Sent: May 14, 2020 10:30 AM
To: IRLP@irlp.groups.io
Subject: Re: [IRLP] DTMF tones not recognized

 

This is not a common problem, but it creeps up from time to time.

 

What radio are you using for the node radio? What audio source are you

using in the radio? If the source is not a squelched, de-emphasized

source, then the DTMF decoder is not able to decode due to the variance

in levels in the tones.

 

What audio output are you using from the node radio? If it is a

discriminator source, that is the problem.

 

Also, if the level of the audio from the node radio to the node is

either very high or very low, it can affect the ability for the decoder

to work. What is the input audio settings like on the alsamixer screen?

 

David Cameron

VE7LTD

 

On 2020-05-14 9:13 a.m., Albert Febraro wrote:

> This may be a common issue but being new to IRLP I'm still fine tuning

> my node and learning. The issue is that when I send DTMF tones from

> different radios the node does not recognize the tones. I have one radio

> (Kenwood TH-F6) that when I transmit tones the node doesn't decode them

> at all, however another radio (Alinco DJ-MD5) works perfectly. What is

> interesting is that when I'm using my mobile radio (ICOM ID-5100) I can

> bring up the echo node 9993, but cannot disconnect. I send a "73" but I

> only hear the 7 when the node returns the echoed audio. My audio levels

> are adjusted correctly as far as I can tell. I then have to disconnect

> with a different radio. When I use the Alinco HT, I get good reports

> audio and received audio is fine.

> Al

> W6AAX

> node 3913

>

 

 

 


Re: DTMF tones not recognized

k9dc
 

Become familiar with the use of the ‘readinput’ command. Very helpful tool when troubleshooting any dtmf decoding issues.

su - repeater
readinput

Ctrl-C to quit

-k9dc

On May 14, 2020, at 12:13, Albert Febraro <w6aax@...> wrote:

This may be a common issue but being new to IRLP I'm still fine tuning my node and learning. The issue is that when I send DTMF tones from different radios the node does not recognize the tones. I have one radio (Kenwood TH-F6) that when I transmit tones the node doesn't decode them at all, however another radio (Alinco DJ-MD5) works perfectly. What is interesting is that when I'm using my mobile radio (ICOM ID-5100) I can bring up the echo node 9993, but cannot disconnect. I send a "73" but I only hear the 7 when the node returns the echoed audio. My audio levels are adjusted correctly as far as I can tell. I then have to disconnect with a different radio. When I use the Alinco HT, I get good reports audio and received audio is fine.
Al
W6AAX
node 3913


Re: DTMF tones not recognized

David Cameron - IRLP
 

This is not a common problem, but it creeps up from time to time.

What radio are you using for the node radio? What audio source are you using in the radio? If the source is not a squelched, de-emphasized source, then the DTMF decoder is not able to decode due to the variance in levels in the tones.

What audio output are you using from the node radio? If it is a discriminator source, that is the problem.

Also, if the level of the audio from the node radio to the node is either very high or very low, it can affect the ability for the decoder to work. What is the input audio settings like on the alsamixer screen?

David Cameron
VE7LTD

On 2020-05-14 9:13 a.m., Albert Febraro wrote:
This may be a common issue but being new to IRLP I'm still fine tuning my node and learning. The issue is that when I send DTMF tones from different radios the node does not recognize the tones. I have one radio (Kenwood TH-F6) that when I transmit tones the node doesn't decode them at all, however another radio (Alinco DJ-MD5) works perfectly. What is interesting is that when I'm using my mobile radio (ICOM ID-5100) I can bring up the echo node 9993, but cannot disconnect. I send a "73" but I only hear the 7 when the node returns the echoed audio. My audio levels are adjusted correctly as far as I can tell. I then have to disconnect with a different radio. When I use the Alinco HT, I get good reports audio and received audio is fine.
Al
W6AAX
node 3913


DTMF tones not recognized

Albert Febraro <w6aax@...>
 

This may be a common issue but being new to IRLP I'm still fine tuning my node and learning. The issue is that when I send DTMF tones from different radios the node does not recognize the tones. I have one radio (Kenwood TH-F6) that when I transmit tones the node doesn't decode them at all, however another radio (Alinco DJ-MD5) works perfectly. What is interesting is that when I'm using my mobile radio (ICOM ID-5100) I can bring up the echo node 9993, but cannot disconnect. I send a "73" but I only hear the 7 when the node returns the echoed audio. My audio levels are adjusted correctly as far as I can tell. I then have to disconnect with a different radio. When I use the Alinco HT, I get good reports audio and received audio is fine.
Al
W6AAX
node 3913


Re: APRS script for Debian 10

Chris Pitre
 

the link to the scripts doesn't seem to be working,

irlp.kc6hur.net name or service not known.


Re: APRS script for Debian 10

Lonney [K1LH]
 
Edited

Yes, I tweaked the original some years ago to work with Debian:

https://github.com/lonney9/IRLPScripts

- Lonney
KL3NO


APRS script for Debian 10

Chris Pitre
 

Setting up a node using Debian , is there an APRS script available? If so where?  KC6HUR seems to no longer exist.

Thanks
Chris 
VE3ZO

NODE 2345 VE3ZZZ


Re: 15425 thru 15427 via comcast

k9dc
 

Nothing to add here.
Worst case, you could try IRLP VPN, although that requires Debian OS. Send your request to installs@ IRLP.net

-k9dc

On May 8, 2020, at 20:42, Allan Dunn, K1UCY <always_faithful@...> wrote:

Correction: It allows me to choose a node and add either a port number or a range of numbers. But when I select Next, nothing happens.

I did switch to DMZ, but when I connect to 9999 on air, I get no response. I do connect and later disconnect and able to return to home port 9122. I have no indication my voice goes to 9999 as nothing comes back.
On May 8, 2020, at 8:33 PM, k9dc <Dave@...> wrote:


Then that is a question for Comcast. “I’m trying to add a port forward, and the button doesn’t work, how come?”

-k9dc

On May 8, 2020, at 20:05, Allan Dunn, K1UCY <always_faithful@...> wrote:
Nothing. It does not accept it.
On May 8, 2020, at 6:38 PM, k9dc <Dave@...> wrote:

So what happens when you tap the Add Port Forward button?

-k9dc

On May 8, 2020, at 17:38, Allan Dunn, K1UCY <always_faithful@...> wrote:
The IP node is 10.0.0.184.

We agree on the ports that have to be opened, but even with the security disabled, I cannot add any of the ports needed. I have not tried DMZ.

BTW I host node 8581 for my local repeater and club. KD1YH until now has remotely monitored the logs picking up problems proactively as he understands the system better than I. His Telnet capability is no longer functioning

73
On May 8, 2020, at 5:13 PM, k9dc <Dave@...> wrote:

I cannot “see" anything, I do not have the service.

But I am not surprised you will have to disable Advanced Security, that is pretty standard. You will need to know the IP address of the node computer, on your LAN. Use that as target destination of the forward. Log in to the node and use the command ‘/sbin/ifconfig’ to determine the IP the node computer is using.

In addition to TCP 15425, you will need to include UDP 2074-2093. Or BTW, you could just set up the DMZ host address for the node. Do not attempt to do both however.

-k9dc










Re: 15425 thru 15427 via comcast

Allan Dunn, K1UCY
 

Correction: It allows me to choose a node and add either a port number or a range of numbers. But when I select Next, nothing happens.

I did switch to DMZ, but when I connect to 9999 on air, I get no response. I do connect and later disconnect and able to return to home port 9122. I have no indication my voice goes to 9999 as nothing comes back.

On May 8, 2020, at 8:33 PM, k9dc <Dave@...> wrote:


Then that is a question for Comcast. “I’m trying to add a port forward, and the button doesn’t work, how come?”

-k9dc

On May 8, 2020, at 20:05, Allan Dunn, K1UCY <always_faithful@...> wrote:

Nothing. It does not accept it.
On May 8, 2020, at 6:38 PM, k9dc <Dave@...> wrote:

So what happens when you tap the Add Port Forward button?

-k9dc

On May 8, 2020, at 17:38, Allan Dunn, K1UCY <always_faithful@...> wrote:
The IP node is 10.0.0.184.

We agree on the ports that have to be opened, but even with the security disabled, I cannot add any of the ports needed. I have not tried DMZ.

BTW I host node 8581 for my local repeater and club. KD1YH until now has remotely monitored the logs picking up problems proactively as he understands the system better than I. His Telnet capability is no longer functioning

73
On May 8, 2020, at 5:13 PM, k9dc <Dave@...> wrote:

I cannot “see" anything, I do not have the service.

But I am not surprised you will have to disable Advanced Security, that is pretty standard. You will need to know the IP address of the node computer, on your LAN. Use that as target destination of the forward. Log in to the node and use the command ‘/sbin/ifconfig’ to determine the IP the node computer is using.

In addition to TCP 15425, you will need to include UDP 2074-2093. Or BTW, you could just set up the DMZ host address for the node. Do not attempt to do both however.

-k9dc








Re: 15425 thru 15427 via comcast

k9dc
 

Then that is a question for Comcast. “I’m trying to add a port forward, and the button doesn’t work, how come?”

-k9dc

On May 8, 2020, at 20:05, Allan Dunn, K1UCY <always_faithful@...> wrote:

Nothing. It does not accept it.
On May 8, 2020, at 6:38 PM, k9dc <Dave@...> wrote:


So what happens when you tap the Add Port Forward button?

-k9dc

On May 8, 2020, at 17:38, Allan Dunn, K1UCY <always_faithful@...> wrote:
The IP node is 10.0.0.184.

We agree on the ports that have to be opened, but even with the security disabled, I cannot add any of the ports needed. I have not tried DMZ.

BTW I host node 8581 for my local repeater and club. KD1YH until now has remotely monitored the logs picking up problems proactively as he understands the system better than I. His Telnet capability is no longer functioning

73
On May 8, 2020, at 5:13 PM, k9dc <Dave@...> wrote:

I cannot “see" anything, I do not have the service.

But I am not surprised you will have to disable Advanced Security, that is pretty standard. You will need to know the IP address of the node computer, on your LAN. Use that as target destination of the forward. Log in to the node and use the command ‘/sbin/ifconfig’ to determine the IP the node computer is using.

In addition to TCP 15425, you will need to include UDP 2074-2093. Or BTW, you could just set up the DMZ host address for the node. Do not attempt to do both however.

-k9dc







Re: 15425 thru 15427 via comcast

Allan Dunn, K1UCY
 

Nothing. It does not accept it.

On May 8, 2020, at 6:38 PM, k9dc <Dave@...> wrote:


So what happens when you tap the Add Port Forward button?

-k9dc

On May 8, 2020, at 17:38, Allan Dunn, K1UCY <always_faithful@...> wrote:

The IP node is 10.0.0.184.

We agree on the ports that have to be opened, but even with the security disabled, I cannot add any of the ports needed. I have not tried DMZ.

BTW I host node 8581 for my local repeater and club. KD1YH until now has remotely monitored the logs picking up problems proactively as he understands the system better than I. His Telnet capability is no longer functioning

73
On May 8, 2020, at 5:13 PM, k9dc <Dave@...> wrote:

I cannot “see" anything, I do not have the service.

But I am not surprised you will have to disable Advanced Security, that is pretty standard. You will need to know the IP address of the node computer, on your LAN. Use that as target destination of the forward. Log in to the node and use the command ‘/sbin/ifconfig’ to determine the IP the node computer is using.

In addition to TCP 15425, you will need to include UDP 2074-2093. Or BTW, you could just set up the DMZ host address for the node. Do not attempt to do both however.

-k9dc





Re: 15425 thru 15427 via comcast

k9dc
 

So what happens when you tap the Add Port Forward button?

-k9dc

On May 8, 2020, at 17:38, Allan Dunn, K1UCY <always_faithful@...> wrote:

The IP node is 10.0.0.184.

We agree on the ports that have to be opened, but even with the security disabled, I cannot add any of the ports needed. I have not tried DMZ.

BTW I host node 8581 for my local repeater and club. KD1YH until now has remotely monitored the logs picking up problems proactively as he understands the system better than I. His Telnet capability is no longer functioning

73
On May 8, 2020, at 5:13 PM, k9dc <Dave@...> wrote:


I cannot “see" anything, I do not have the service.

But I am not surprised you will have to disable Advanced Security, that is pretty standard. You will need to know the IP address of the node computer, on your LAN. Use that as target destination of the forward. Log in to the node and use the command ‘/sbin/ifconfig’ to determine the IP the node computer is using.

In addition to TCP 15425, you will need to include UDP 2074-2093. Or BTW, you could just set up the DMZ host address for the node. Do not attempt to do both however.

-k9dc


Re: 15425 thru 15427 via comcast

Allan Dunn, K1UCY
 

The IP node is 10.0.0.184.

We agree on the ports that have to be opened, but even with the security disabled, I cannot add any of the ports needed. I have not tried DMZ.

BTW I host node 8581 for my local repeater and club. KD1YH until now has remotely monitored the logs picking up problems proactively as he understands the system better than I. His Telnet capability is no longer functioning

73

On May 8, 2020, at 5:13 PM, k9dc <Dave@...> wrote:


I cannot “see" anything, I do not have the service.

But I am not surprised you will have to disable Advanced Security, that is pretty standard. You will need to know the IP address of the node computer, on your LAN. Use that as target destination of the forward. Log in to the node and use the command ‘/sbin/ifconfig’ to determine the IP the node computer is using.

In addition to TCP 15425, you will need to include UDP 2074-2093. Or BTW, you could just set up the DMZ host address for the node. Do not attempt to do both however.

-k9dc

On May 8, 2020, at 16:54, Allan Dunn, K1UCY <always_faithful@...> wrote:

As you can see that when WiFi Advanced Security is enabled (which it is by default), both port forwarding and DMZ are disabled. I disabled that security feature (a 10 minute task) and proceded to the manual addition of ports to forward; three of my ports appeared but none are the IRLP ports. At that point nothing works and IRLP is inoperative even with the security disabled.

And yes the removal of port forwarding from the modem Admin tab is new, very new, probably this week.
On May 8, 2020, at 3:45 PM, k9dc <Dave@...> wrote:

This is the official (apparently) documentation on how to set up port forwarding using Xfi.

https://www.xfinity.com/support/articles/xfi-port-forwarding





Re: dtmfdial

Klaus Rung
 

Yes that is what was happening the script kept reverting after each restart. I will try your suggestion.

On May 8, 2020, at 5:04 PM, k9dc <dave@...> wrote:

Are you directly editing scripts/dtmfdial? That script is replaced every time the node restarts, or an update files happens (nightly). If you want to use it, you need to make a copy of it the into the custom directory and call it from there.

Sorry, I didn’t realize that might be what you are doing. the scripts directory (and all the others) are identical on all nodes, and forced back to the identical set of scripts every night.

-k9dc


On May 8, 2020, at 16:34, Klaus Rung via groups.io <k_rung=yahoo.com@groups.io> wrote:

I put the export TXDELAY=500000 into the environment file and restarted and it seems to work and the first digit is able to be heard and decoded more reliably but I went to 1500000 and I did not see a difference. the values in the dtmfdial file I should be able to change the values in but it keeps going back to the same original settings.

I would think I should be able to change the txdelay and dial volume in this file.


${BIN}/coscheck
${BIN}/key
usleep ${TXDELAY:-250000}

if [ -z "$DIAL_OPTIONS" ] ; then
${DIAL} --volume 25 ${1}p
else
${DIAL} ${DIAL_OPTIONS} ${1}p


On Friday, May 8, 2020, 4:01:16 p.m. EDT, k9dc <dave@...> wrote:



I’ve never used it myself, but the reference to $TXDELAY pulls the value set in the environment file. So perhaps you could increase it there. Perhaps it is not defined.

export TXDELAY=500000

But if you have a specific interval you want to use, just remove the reference and place a discrete value in your script.

usleep 500000

-k9dc


On May 8, 2020, at 15:42, Klaus Rung via groups.io <k_rung=yahoo.com@groups.io> wrote:

I am trying to send dtmf to the remote repeater so I am trying to increase the wait time of dtmf after keying before sending digits.

${BIN}/key
usleep ${TXDELAY:-250000}

if [ -z "$DIAL_OPTIONS" ] ; then
${DIAL} --volume 25 ${1}p

When I change txdelay to 500000 it changes back after the irlp software is restarted. How do I get to keep my new settings in this file?

Klaus
ve3kr
2450












Re: 15425 thru 15427 via comcast

k9dc
 

I cannot “see" anything, I do not have the service.

But I am not surprised you will have to disable Advanced Security, that is pretty standard. You will need to know the IP address of the node computer, on your LAN. Use that as target destination of the forward. Log in to the node and use the command ‘/sbin/ifconfig’ to determine the IP the node computer is using.

In addition to TCP 15425, you will need to include UDP 2074-2093. Or BTW, you could just set up the DMZ host address for the node. Do not attempt to do both however.

-k9dc

On May 8, 2020, at 16:54, Allan Dunn, K1UCY <always_faithful@...> wrote:

As you can see that when WiFi Advanced Security is enabled (which it is by default), both port forwarding and DMZ are disabled. I disabled that security feature (a 10 minute task) and proceded to the manual addition of ports to forward; three of my ports appeared but none are the IRLP ports. At that point nothing works and IRLP is inoperative even with the security disabled.

And yes the removal of port forwarding from the modem Admin tab is new, very new, probably this week.
On May 8, 2020, at 3:45 PM, k9dc <Dave@...> wrote:


This is the official (apparently) documentation on how to set up port forwarding using Xfi.

https://www.xfinity.com/support/articles/xfi-port-forwarding


Re: dtmfdial

k9dc
 

Are you directly editing scripts/dtmfdial? That script is replaced every time the node restarts, or an update files happens (nightly). If you want to use it, you need to make a copy of it the into the custom directory and call it from there.

Sorry, I didn’t realize that might be what you are doing. the scripts directory (and all the others) are identical on all nodes, and forced back to the identical set of scripts every night.

-k9dc

On May 8, 2020, at 16:34, Klaus Rung via groups.io <k_rung=yahoo.com@groups.io> wrote:

I put the export TXDELAY=500000 into the environment file and restarted and it seems to work and the first digit is able to be heard and decoded more reliably but I went to 1500000 and I did not see a difference. the values in the dtmfdial file I should be able to change the values in but it keeps going back to the same original settings.

I would think I should be able to change the txdelay and dial volume in this file.


${BIN}/coscheck
${BIN}/key
usleep ${TXDELAY:-250000}

if [ -z "$DIAL_OPTIONS" ] ; then
${DIAL} --volume 25 ${1}p
else
${DIAL} ${DIAL_OPTIONS} ${1}p


On Friday, May 8, 2020, 4:01:16 p.m. EDT, k9dc <dave@...> wrote:



I’ve never used it myself, but the reference to $TXDELAY pulls the value set in the environment file. So perhaps you could increase it there. Perhaps it is not defined.

export TXDELAY=500000

But if you have a specific interval you want to use, just remove the reference and place a discrete value in your script.

usleep 500000

-k9dc


On May 8, 2020, at 15:42, Klaus Rung via groups.io <k_rung=yahoo.com@groups.io> wrote:

I am trying to send dtmf to the remote repeater so I am trying to increase the wait time of dtmf after keying before sending digits.

${BIN}/key
usleep ${TXDELAY:-250000}

if [ -z "$DIAL_OPTIONS" ] ; then
${DIAL} --volume 25 ${1}p

When I change txdelay to 500000 it changes back after the irlp software is restarted. How do I get to keep my new settings in this file?

Klaus
ve3kr
2450