Issue with Hangup after first keying

App_rpt-users
1

Hello,

It is my first posting on here. I have ALMOST gotten the
ACID installation working. I’m using the URI interfaced to ACID and to my
radio. The asterisk can properly key the radio and its working just fine with
that. I can also connect to the node with iaxRpt directly with no problem and
transmit OUT of my radio.

However I am having some issues when my radio receives
communication in that as soon as I get my first radio RX, asterisk will then
play a tone out of the URI into the radio over and over again at about a one
second interval. In the asterisk terminal it just keeps repeating:

– Hungup ‘Zap/pseudo-1726358622’

– Hungup ‘Zap/pseudo-1774817359’

– Hungup ‘Zap/pseudo-691532115’

– Hungup ‘Zap/pseudo-81389311’

– Hungup ‘Zap/pseudo-465154784’

– Hungup ‘Zap/pseudo-627058532’

– Hungup ‘Zap/pseudo-1656870264’

– Hungup ‘Zap/pseudo-1671691803’

– Hungup ‘Zap/pseudo-50274194’

forever keeping my radio always keyed.

I have the COR from the radio going into the URI. I do not
plan on using CTCSS and have tried tying it to ground as well as tying it to
the COR as well. My usbradio.conf has the following:

carrierfrom=usb

ctcssfrom=no

I have tried also ctcssfrom=usb as well.

Any help would be appreciated.

Thanks,

Josh

2

sounds to me you are using a simplex node.

In your simpleusb.conf or usbradio.conf, ensure duplex=0, and not
duplex=1. This is different from duplex= in rpt.conf

I had the same symptoms when I first setup my node.

Also, make sure you use the radio-tune-menu with a service monitor or
some other methods to make sure your have good, clean audio being
transmitted over the internet and over your node radio.

~Benjamin, KB9LFZ

···

On Wed, 2013-07-03 at 13:58 -0600, Joshua Hintze wrote:

Hello,

It is my first posting on here. I have ALMOST gotten the ACID
installation working. I'm using the URI interfaced to ACID and to my
radio. The asterisk can properly key the radio and its working just
fine with that. I can also connect to the node with iaxRpt directly
with no problem and transmit OUT of my radio.

However I am having some issues when my radio receives communication
in that as soon as I get my first radio RX, asterisk will then play a
tone out of the URI into the radio over and over again at about a one
second interval. In the asterisk terminal it just keeps repeating:

    -- Hungup 'Zap/pseudo-1726358622'

    -- Hungup 'Zap/pseudo-1774817359'

    -- Hungup 'Zap/pseudo-691532115'

    -- Hungup 'Zap/pseudo-81389311'

    -- Hungup 'Zap/pseudo-465154784'

   -- Hungup 'Zap/pseudo-627058532'

    -- Hungup 'Zap/pseudo-1656870264'

    -- Hungup 'Zap/pseudo-1671691803'

    -- Hungup 'Zap/pseudo-50274194'

forever keeping my radio always keyed.

I have the COR from the radio going into the URI. I do not plan on
using CTCSS and have tried tying it to ground as well as tying it to
the COR as well. My usbradio.conf has the following:

carrierfrom=usb

ctcssfrom=no

I have tried also ctcssfrom=usb as well.

Any help would be appreciated.

Thanks,

Josh

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
ohnosec.org

3

Thanks Ben for the quick feedback. I think I might have figured it out. It turns out my COR signal might not necessarily be the best COR signal. It looks like the signal goes high on BOTH RX and TX. This is probably causing asterisk to think its receiving when its sending getting into a nice infinite loop.

I'm going to try an AND gate with the PTT so that PTT has to be high (i.e. NOT TX) and speaker mute (my COR) has to be high for a true COR output on RX.

In the meantime I tried carrierfrom=vox but it didn't really seem to work. Anybody get this working properly?

Thanks,

Josh

···

-----Original Message-----
From: Benjamin Naber [mailto:benjamin@kb9lfz.com]
Sent: Wednesday, July 03, 2013 2:37 PM
To: Joshua Hintze
Cc: app_rpt-users@ohnosec.org
Subject: Re: [Bulk] [App_rpt-users] Issue with Hangup after first keying

sounds to me you are using a simplex node.

In your simpleusb.conf or usbradio.conf, ensure duplex=0, and not
duplex=1. This is different from duplex= in rpt.conf

I had the same symptoms when I first setup my node.

Also, make sure you use the radio-tune-menu with a service monitor or
some other methods to make sure your have good, clean audio being
transmitted over the internet and over your node radio.

~Benjamin, KB9LFZ

On Wed, 2013-07-03 at 13:58 -0600, Joshua Hintze wrote:

Hello,

It is my first posting on here. I have ALMOST gotten the ACID
installation working. I'm using the URI interfaced to ACID and to my
radio. The asterisk can properly key the radio and its working just
fine with that. I can also connect to the node with iaxRpt directly
with no problem and transmit OUT of my radio.

However I am having some issues when my radio receives communication
in that as soon as I get my first radio RX, asterisk will then play a
tone out of the URI into the radio over and over again at about a one
second interval. In the asterisk terminal it just keeps repeating:

    -- Hungup 'Zap/pseudo-1726358622'

    -- Hungup 'Zap/pseudo-1774817359'

    -- Hungup 'Zap/pseudo-691532115'

    -- Hungup 'Zap/pseudo-81389311'

    -- Hungup 'Zap/pseudo-465154784'

   -- Hungup 'Zap/pseudo-627058532'

    -- Hungup 'Zap/pseudo-1656870264'

    -- Hungup 'Zap/pseudo-1671691803'

    -- Hungup 'Zap/pseudo-50274194'

forever keeping my radio always keyed.

I have the COR from the radio going into the URI. I do not plan on
using CTCSS and have tried tying it to ground as well as tying it to
the COR as well. My usbradio.conf has the following:

carrierfrom=usb

ctcssfrom=no

I have tried also ctcssfrom=usb as well.

Any help would be appreciated.

Thanks,

Josh

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
ohnosec.org

4

I used carrierfrom=dsp and ctcssfrom=dsp

I am not sure why folks are having serious issues with that, but it
works very well, and I have zero issues with it. I do crude signal
testing with it, and even when the signal from the node radio is choppy,
I can still command the node to do things.

I would say the biggest hurdle for getting DSP to work correctly is
using the radio-tune-menu with a service monitor. This is to ensure the
input and output audio audio levels are correctly set, and the DSP
functions can understand the different audio freqs coming to it.

I do not use a COR/COS and the node does all the CTCSS stuff. Just TX/RX
audio, and PTT connections are made to the node radio.

for the radio that requires 5V or active HIGH, use the K0KN PLRI
interface. Very simple: a couple resistors and transistors. No need to
waste time modifying a USB sound FOB, which is difficult to do because
of the size of components one would be working with.

~Benjamin, KB9LFZ

···

On Wed, 2013-07-03 at 14:48 -0600, Joshua Hintze wrote:

Thanks Ben for the quick feedback. I think I might have figured it out. It turns out my COR signal might not necessarily be the best COR signal. It looks like the signal goes high on BOTH RX and TX. This is probably causing asterisk to think its receiving when its sending getting into a nice infinite loop.

I'm going to try an AND gate with the PTT so that PTT has to be high (i.e. NOT TX) and speaker mute (my COR) has to be high for a true COR output on RX.

In the meantime I tried carrierfrom=vox but it didn't really seem to work. Anybody get this working properly?

Thanks,

Josh

-----Original Message-----
From: Benjamin Naber [mailto:benjamin@kb9lfz.com]
Sent: Wednesday, July 03, 2013 2:37 PM
To: Joshua Hintze
Cc: app_rpt-users@ohnosec.org
Subject: Re: [Bulk] [App_rpt-users] Issue with Hangup after first keying

sounds to me you are using a simplex node.

In your simpleusb.conf or usbradio.conf, ensure duplex=0, and not
duplex=1. This is different from duplex= in rpt.conf

I had the same symptoms when I first setup my node.

Also, make sure you use the radio-tune-menu with a service monitor or
some other methods to make sure your have good, clean audio being
transmitted over the internet and over your node radio.

~Benjamin, KB9LFZ

On Wed, 2013-07-03 at 13:58 -0600, Joshua Hintze wrote:
> Hello,
>
>
>
> It is my first posting on here. I have ALMOST gotten the ACID
> installation working. I'm using the URI interfaced to ACID and to my
> radio. The asterisk can properly key the radio and its working just
> fine with that. I can also connect to the node with iaxRpt directly
> with no problem and transmit OUT of my radio.
>
>
>
> However I am having some issues when my radio receives communication
> in that as soon as I get my first radio RX, asterisk will then play a
> tone out of the URI into the radio over and over again at about a one
> second interval. In the asterisk terminal it just keeps repeating:
>
>
>
> -- Hungup 'Zap/pseudo-1726358622'
>
> -- Hungup 'Zap/pseudo-1774817359'
>
> -- Hungup 'Zap/pseudo-691532115'
>
> -- Hungup 'Zap/pseudo-81389311'
>
> -- Hungup 'Zap/pseudo-465154784'
>
> -- Hungup 'Zap/pseudo-627058532'
>
> -- Hungup 'Zap/pseudo-1656870264'
>
> -- Hungup 'Zap/pseudo-1671691803'
>
> -- Hungup 'Zap/pseudo-50274194'
>
>
>
> forever keeping my radio always keyed.
>
>
>
> I have the COR from the radio going into the URI. I do not plan on
> using CTCSS and have tried tying it to ground as well as tying it to
> the COR as well. My usbradio.conf has the following:
>
>
>
> carrierfrom=usb
>
> ctcssfrom=no
>
>
>
> I have tried also ctcssfrom=usb as well.
>
>
>
> Any help would be appreciated.
>
>
>
> Thanks,
>
>
>
> Josh
>
>
> _______________________________________________
> App_rpt-users mailing list
> App_rpt-users@ohnosec.org
> ohnosec.org

5

I too would suggest using the DSP.

Sure is easier to bring out discriminator audio than muck about building extra logic.

As to not using PL… please reconsider.

It’s quite frustrating to be connected to a large network and hearing the squelch on one node popping because of local noise or band conditions. Meanwhile, the DSP generally does a good job of decoding it.

···

–

Sent from my Android phone with K-9 Mail. Please excuse my brevity.

6

Thank you for all the suggestions thus far.

I'm using an ICOM IC-A110 VHF radio. I was able to find some
schematics/block diagrams in the service manual here:

This is my first time trying to dig through a radio and find a COR. I'm not
sure either where to get a discriminator audio signal either.

Josh

···

-----Original Message-----
From: Bryan D. Boyle [mailto:bdboyle@bdboyle.com]
Sent: Wednesday, July 03, 2013 3:29 PM
To: Joshua Hintze
Subject: Re: [App_rpt-users] [Bulk] Issue with Hangup after first keying

On 7/3/2013 4:48 PM, Joshua Hintze wrote:

Thanks Ben for the quick feedback. I think I might have figured it out. It

turns out my COR signal might not necessarily be the best COR signal. It
looks like the signal goes high on BOTH RX and TX. This is probably causing
asterisk to think its receiving when its sending getting into a nice
infinite loop.

Then you don't have a true COR signal. What radio (make/model) are you
using? Can you get discriminator audio?? If so, you can use dsp to
derive COR; otherwise, you need to look elsewhere. Sounds like you're
too far down the circuit.

I'm going to try an AND gate with the PTT so that PTT has to be high (i.e.

NOT TX) and speaker mute (my COR) has to be high for a true COR output on
RX.

Sounds complicated; I'm thinking some quality time with the schematic
will provide an answer that is more agreeable and doesn't require
building logic circuits. In all the machines I've built the most
complex interface has been a pullup resistor on the DB25 connector. And
that's for everything from a micor to wouxun HTs to maxtracs and gtx's
and systel, and ALinco radio-based repeaters. And throw in a couple GE
rigs (Mastr-IIs) along the way. Heck, I even interfaced a TR-33C as a
receiver in a pinch.

In the meantime I tried carrierfrom=vox but it didn't really seem to work.

Anybody get this working properly?

As our Maximum Leader Jim says: "Friends don't let friends use VOX".
Not a way to do it; and is an artifact of development.

BB WB0YLE
Allstar 27294, 27295, 27673, 27710, etc.

7

Try the top of either the volume or squelch controls.

···

Joshua Hintze joshh@imsar.com wrote:

Thank you for all the suggestions thus far.

I'm using an ICOM IC-A110 VHF radio. I was able to find some
schematics/block diagrams in the service manual here:

[http://elektrotanya.com/icom_ic-a110,_a110e_service_manual.pdf/download.html](http://elektrotanya.com/icom_ic-a110,_a110e_service_manual.pdf/download.html)

This is my first time trying to dig through a radio and find a COR. I'm not
sure either where to get a discriminator audio signal either.

Josh

-----Original Message-----
From: Bryan D. Boyle [mailto:bdboyle@bdboyle.com]
Sent: Wednesday, July 03, 2013 3:29 PM
To: Joshua Hintze
Subject: Re: [App_rpt-users] [Bulk] Issue with Hangup after first keying

On 7/3/2013 4:48 PM, Joshua Hintze wrote:
> Thanks Ben for the quick feedback. I think I might have figured it out. It
turns out my COR signal might not necessarily be the best COR signal. It
looks like the signal goes high on BOTH RX and TX. This is probably causing
asterisk to think its receiving when its sending getting into a nice
infinite loop.


Then you don't have a true COR signal. What radio (make/model) are you
using? Can you get discriminator audio?? If so, you can use dsp to
derive COR; otherwise, you need to look elsewhere. Sounds like you're
too far down the circuit.

> I'm going to try an AND gate with the PTT so that PTT has to be high (i.e.
NOT TX) and speaker mute (my COR) has to be high for a true COR output on
RX.


Sounds
complicated; I'm thinking some quality time with the schematic
will provide an answer that is more agreeable and doesn't require
building logic circuits. In all the machines I've built the most
complex interface has been a pullup resistor on the DB25 connector. And
that's for everything from a micor to wouxun HTs to maxtracs and gtx's
and systel, and ALinco radio-based repeaters. And throw in a couple GE
rigs (Mastr-IIs) along the way. Heck, I even interfaced a TR-33C as a
receiver in a pinch.

> In the meantime I tried carrierfrom=vox but it didn't really seem to work.
Anybody get this working properly?


As our Maximum Leader Jim says: "Friends don't let friends use VOX".
Not a way to do it; and is an artifact of development.

BB WB0YLE
Allstar 27294, 27295, 27673,
27710, etc.



---


App_rpt-users mailing list
App_rpt-users@ohnosec.org
[http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users](http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users)

–

Sent from my Android phone with K-9 Mail. Please excuse my brevity.

8

Ahh… now I understand… aircraft AM?

Looking at the block diagram, does the output of IC11, the squelch switch do what you want for COR?

···

–

Sent from my Android phone with K-9 Mail. Please excuse my brevity.

9

I did not see that one. Thanks for pointing it out. I will test
it out tomorrow when I get back into work.

Josh

From:
app_rpt-users-bounces@ohnosec.org [mailto:app_rpt-users-bounces@ohnosec.org] On
Behalf Of Robert a. Poff

···

Sent: Wednesday, July 03, 2013 6:02 PM
To: app_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] [Bulk] Issue with Hangup after first keying

Ahh… now I understand… aircraft AM?

Looking at the block diagram, does the output of IC11, the squelch switch do
what you want for COR?

–

Sent from my Android phone with K-9 Mail. Please excuse my brevity.

10

The Icom IC-A110 is an AM aircraft radio. Being AM there is no discriminator audio, and DSP derived COR won't work due to the nature of the AM signal. You're going to have to dig around in the squelch circuit to find a point that toggles. Most AM type squelch are usually derived from the AGC. Don't what they're doing in the Icom.

Ed, W8VT
Nodes 27849 29496
Beckley WV

···

On 07/03/2013 07:37 PM, Joshua Hintze wrote:

Thank you for all the suggestions thus far.

I'm using an ICOM IC-A110 VHF radio. I was able to find some
schematics/block diagrams in the service manual here:

ICOM IC-A110, A110E SERVICE MANUAL Service Manual download, schematics, eeprom, repair info for electronics experts

This is my first time trying to dig through a radio and find a COR. I'm not
sure either where to get a discriminator audio signal either.

Josh

-----Original Message-----
From: Bryan D. Boyle [mailto:bdboyle@bdboyle.com]
Sent: Wednesday, July 03, 2013 3:29 PM
To: Joshua Hintze
Subject: Re: [App_rpt-users] [Bulk] Issue with Hangup after first keying

On 7/3/2013 4:48 PM, Joshua Hintze wrote:

Thanks Ben for the quick feedback. I think I might have figured it out. It

turns out my COR signal might not necessarily be the best COR signal. It
looks like the signal goes high on BOTH RX and TX. This is probably causing
asterisk to think its receiving when its sending getting into a nice
infinite loop.
Then you don't have a true COR signal. What radio (make/model) are you
using? Can you get discriminator audio?? If so, you can use dsp to
derive COR; otherwise, you need to look elsewhere. Sounds like you're
too far down the circuit.

I'm going to try an AND gate with the PTT so that PTT has to be high (i.e.

NOT TX) and speaker mute (my COR) has to be high for a true COR output on
RX.
Sounds complicated; I'm thinking some quality time with the schematic
will provide an answer that is more agreeable and doesn't require
building logic circuits. In all the machines I've built the most
complex interface has been a pullup resistor on the DB25 connector. And
that's for everything from a micor to wouxun HTs to maxtracs and gtx's
and systel, and ALinco radio-based repeaters. And throw in a couple GE
rigs (Mastr-IIs) along the way. Heck, I even interfaced a TR-33C as a
receiver in a pinch.

In the meantime I tried carrierfrom=vox but it didn't really seem to work.

Anybody get this working properly?
As our Maximum Leader Jim says: "Friends don't let friends use VOX".
Not a way to do it; and is an artifact of development.

BB WB0YLE
Allstar 27294, 27295, 27673, 27710, etc.

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
ohnosec.org

11

Detecting squelch break in AM is a lot different that breaking squelch
in FM...

iirc, you have to depend on the AGC circuit to do what it's supposed to
do in order to detect a signal level delta greater than the background
hash, which is a variable. FM looks for the detector to open up when
the frequency swing happens...a bit more binary than AM transmissions,
which means there's a constant noise level vice AM (just listen on the
HF bands to see the difference in the noise levels from minute to
minute...). Kind of hard to detect amplitude changes as being a
legitimate carrier vice noise, since they're both the same general
modulation envelope, whereas in FM, the intelligence is carried in a
different mode than the background noise.

Don't know whether I'm explaining it clearly enough, but it's in that
general neighborhood or some such.

Just what are you trying to do?

BB

···

On 7/3/2013 7:37 PM, Joshua Hintze wrote:

Thank you for all the suggestions thus far.

I'm using an ICOM IC-A110 VHF radio. I was able to find some
schematics/block diagrams in the service manual here:

ICOM IC-A110, A110E SERVICE MANUAL Service Manual download, schematics, eeprom, repair info for electronics experts

This is my first time trying to dig through a radio and find a COR. I'm not
sure either where to get a discriminator audio signal either.

12

Joshua, I’m going to take a chance here and state what seems to be the obvious; all your additional work to get your node functional seem to stem from the rather unusual radio you are using. So why not just bite the bullet and change radios to something a bit more standard, like a ham dual-band FM radio for some flexability, or maybe a ham monoband HT or mobile radio to save both time and money? Seems the time and effort you have put into getting the AM aircraft radio to function would be moot with just about any ham FM radio replacing it. And if you get one with a data-access conection, all the signals you need are there so you can run COR or stratight audio relatively easily, whatever your choice? Or have I missed something obvious related to your choice of radios? Just a thought.

···

— On ** Wed, 7/3/13, Joshua Hintze joshh@imsar.com** wrote:

From: Joshua Hintze joshh@imsar.com
Subject: Re: [App_rpt-users] [Bulk] Issue with Hangup after first keying
To: “‘Benjamin Naber’” benjamin@kb9lfz.com
Cc: app_rpt-users@ohnosec.org
Date: Wednesday, July 3, 2013, 8:48 PM

Thanks Ben for the quick feedback. I think I might have figured it out. It turns out my COR signal might not necessarily be the best COR signal. It looks like the signal goes high on BOTH RX and TX. This is probably causing asterisk to think its receiving when its sending getting into a nice infinite loop.

I’m going to try an AND gate with the PTT so that PTT has to be high (i.e. NOT TX) and speaker mute (my COR) has to be high for a true COR output on RX.

In the meantime I tried carrierfrom=vox but it didn’t really seem to work. Anybody get this working properly?

Thanks,

Josh

-----Original Message-----
From: Benjamin Naber [mailto:benjamin@kb9lfz.com]
Sent: Wednesday, July 03, 2013 2:37 PM
To: Joshua Hintze
Cc: app_rpt-users@ohnosec.org
Subject: Re: [Bulk] [App_rpt-users] Issue with Hangup after first keying

sounds to me you are using a simplex node.

In your simpleusb.conf or usbradio.conf, ensure duplex=0, and not
duplex=1. This is different from duplex= in rpt.conf

I had the same symptoms when I first setup my node.

Also, make sure you use the radio-tune-menu with a service monitor or
some other methods to make sure your have good, clean audio being
transmitted over the internet and over your node radio.

~Benjamin, KB9LFZ

On Wed, 2013-07-03 at 13:58 -0600, Joshua Hintze wrote:

Hello,

It is my first posting on here. I have ALMOST gotten the ACID
installation working. I’m using the URI interfaced to ACID and to
my
radio. The asterisk can properly key the radio and its working just
fine with that. I can also connect to the node with iaxRpt directly
with no problem and transmit OUT of my radio.

However I am having some issues when my radio receives communication
in that as soon as I get my first radio RX, asterisk will then play a
tone out of the URI into the radio over and over again at about a one
second interval. In the asterisk terminal it just keeps repeating:

-- Hungup 'Zap/pseudo-1726358622'

-- Hungup 'Zap/pseudo-1774817359'

-- Hungup 'Zap/pseudo-691532115'

-- Hungup 'Zap/pseudo-81389311'

-- Hungup 'Zap/pseudo-465154784'

– Hungup ‘Zap/pseudo-627058532’

-- Hungup 'Zap/pseudo-1656870264'

-- Hungup 'Zap/pseudo-1671691803'

-- Hungup 'Zap/pseudo-50274194'

forever keeping my radio always keyed.

I have the COR from the radio going into the URI. I do not plan on
using CTCSS and have tried tying it to ground as well as tying it to
the COR as well. My usbradio.conf has the following:

carrierfrom=usb

ctcssfrom=no

I have tried also ctcssfrom=usb as well.

Any help would be appreciated.

Thanks,

Josh

App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

13

Are you running full duplex on a simplex radio?

Corey N3FE

···

________________________________________
From: app_rpt-users-bounces@ohnosec.org [app_rpt-users-bounces@ohnosec.org] On Behalf Of Joshua Hintze [joshh@imsar.com]
Sent: Wednesday, July 03, 2013 3:58 PM
To: app_rpt-users@ohnosec.org
Subject: [App_rpt-users] Issue with Hangup after first keying

Hello,

It is my first posting on here. I have ALMOST gotten the ACID installation working. I'm using the URI interfaced to ACID and to my radio. The asterisk can properly key the radio and its working just fine with that. I can also connect to the node with iaxRpt directly with no problem and transmit OUT of my radio.

However I am having some issues when my radio receives communication in that as soon as I get my first radio RX, asterisk will then play a tone out of the URI into the radio over and over again at about a one second interval. In the asterisk terminal it just keeps repeating:

    -- Hungup 'Zap/pseudo-1726358622'
    -- Hungup 'Zap/pseudo-1774817359'
    -- Hungup 'Zap/pseudo-691532115'
    -- Hungup 'Zap/pseudo-81389311'
    -- Hungup 'Zap/pseudo-465154784'
   -- Hungup 'Zap/pseudo-627058532'
    -- Hungup 'Zap/pseudo-1656870264'
    -- Hungup 'Zap/pseudo-1671691803'
    -- Hungup 'Zap/pseudo-50274194'

forever keeping my radio always keyed.

I have the COR from the radio going into the URI. I do not plan on using CTCSS and have tried tying it to ground as well as tying it to the COR as well. My usbradio.conf has the following:

carrierfrom=usb
ctcssfrom=no

I have tried also ctcssfrom=usb as well.

Any help would be appreciated.

Thanks,

Josh

--
This message was scanned and is believed to be clean.
Click here to report this message as spam.<http://simba.repeater.net:8080/cgi-bin/learn-msg.cgi?id=6EF48221A.A93BD>

14

Forget this emaill. I should learn to read all my emails before replying to an old one...

Corey N3FE

···

________________________________________
From: app_rpt-users-bounces@ohnosec.org [app_rpt-users-bounces@ohnosec.org] On Behalf Of Corey Dean [n3fe@repeater.net]
Sent: Thursday, July 04, 2013 10:48 AM
To: Joshua Hintze; app_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] Issue with Hangup after first keying

Are you running full duplex on a simplex radio?

Corey N3FE
________________________________________
From: app_rpt-users-bounces@ohnosec.org [app_rpt-users-bounces@ohnosec.org] On Behalf Of Joshua Hintze [joshh@imsar.com]
Sent: Wednesday, July 03, 2013 3:58 PM
To: app_rpt-users@ohnosec.org
Subject: [App_rpt-users] Issue with Hangup after first keying

Hello,

It is my first posting on here. I have ALMOST gotten the ACID installation working. I'm using the URI interfaced to ACID and to my radio. The asterisk can properly key the radio and its working just fine with that. I can also connect to the node with iaxRpt directly with no problem and transmit OUT of my radio.

However I am having some issues when my radio receives communication in that as soon as I get my first radio RX, asterisk will then play a tone out of the URI into the radio over and over again at about a one second interval. In the asterisk terminal it just keeps repeating:

    -- Hungup 'Zap/pseudo-1726358622'
    -- Hungup 'Zap/pseudo-1774817359'
    -- Hungup 'Zap/pseudo-691532115'
    -- Hungup 'Zap/pseudo-81389311'
    -- Hungup 'Zap/pseudo-465154784'
   -- Hungup 'Zap/pseudo-627058532'
    -- Hungup 'Zap/pseudo-1656870264'
    -- Hungup 'Zap/pseudo-1671691803'
    -- Hungup 'Zap/pseudo-50274194'

forever keeping my radio always keyed.

I have the COR from the radio going into the URI. I do not plan on using CTCSS and have tried tying it to ground as well as tying it to the COR as well. My usbradio.conf has the following:

carrierfrom=usb
ctcssfrom=no

I have tried also ctcssfrom=usb as well.

Any help would be appreciated.

Thanks,

Josh

--
This message was scanned and is believed to be clean.
Click here to report this message as spam.<http://simba.repeater.net:8080/cgi-bin/learn-msg.cgi?id=6EF48221A.A93BD>
_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

--
This message was scanned and is believed to be clean.
Click here to report this message as spam.
http://simba.repeater.net/cgi-bin/learn-msg.cgi?id=E2134221A.A8DD0

15

Replacing the air band radio with an amateur grade FM radio would be rather useless when trying to communicate with aircraft on VHF-AM. I’m sure Josh has a perfectly valid reason for using that radio.

Brett KQ9N

···

On Thu, Jul 4, 2013 at 6:58 AM, Bill South wbs099@yahoo.com wrote:

Joshua, I’m going to take a chance here and state what seems to be the obvious; all your additional work to get your node functional seem to stem from the rather unusual radio you are using. So why not just bite the bullet and change radios to something a bit more standard, like a ham dual-band FM radio for some flexability, or maybe a ham monoband HT or mobile radio to save both time and money? Seems the time and effort you have put into getting the AM aircraft radio to function would be moot with just about any ham FM radio replacing it. And if you get one with a data-access conection, all the signals you need are there so you can run COR or stratight audio relatively easily, whatever your choice? Or have I missed something obvious related to your choice of radios? Just a thought.

16

Aware (painfully) of the diffferences, having owned a certificated (ie
could yellow-tag nav/comm/xpdr/mb/ils/etc) avionics shop years
ago...right about the time GPS came along (the KLN-88 was the hot
navigation device way back then...).

As long as the proper precautions were taken to not cross-service
connect...one service does not require an operator certificate (unless
traveling outside the US, in which case a restricted radiotelephone op
permit, IIRC, is required, though the aircraft station is licensed (call
sign is the N number)), the other requires both an op and station license.

IOW, you can't use 122.9 (multicom) as a simplex channel to bring up
your 145.25 repeater and talk to your mates....:wink:

Wasn't questioning what he was trying to do, just the mode, interface
differences, and equipment that he was using to do so.

bb

···

On 7/5/2013 12:17 AM, Brett Friermood wrote:

Replacing the air band radio with an amateur grade FM radio would be rather
useless when trying to communicate with aircraft on VHF-AM. I'm sure Josh
has a perfectly valid reason for using that radio.

17

Ok all I'm back to work today and playing with this setup again.

I was able to isolate a much better signal for COR than what I had before.
This now truely goes from 0V->5V only when receiving and not when
transmitting. However I'm still having issues.

As soon as asterisk receives a signal it immediately tries to transmit a
signal out. This then effectively pulls the PTT low and my receiver stops
receiving. It is almost like it is in duplex mode but I have in
usbradio.conf

duplex=0 ; Full Duplex

rxondelay=0 ; Uncomment and/or adjust for simplex nodes to
eliminate "Ping Ponging"
                        ; or "Relay Racing".
                        ; A positive value here will instruct the usbradio
driver to ignore the
                        ; COR line for a specified number of 20mSec
intervals following the
                        ; release of PTT. Use this only on simplex nodes,
and leave commented
                        ; out for repeaters or other full duplex nodes.
eeprom=1

Just for clarity I'll post my entire usbradio.conf below:

[general]

[usb]

hdwtype=0 ; Leave this set to 0 for USB sound fobs modified
using
                        ; the instructions from usbfob.pdf. Use a setting of
                        ; 1 is for Dingotel/Sph interfaces.

rxboost=1 ; 0 = 20db attenuator inserted, 1= 20db attenuator
removed
                        ; Set to 1 for additonal gain if using a low-level
receiver output

rxctcssrelax=1 ; reduce talkoff from radios w/o CTCSS Tx HPF
                        ; Do not change this, leave this as a 1

;txctcssdefault=100.0 ; default tx ctcss freq, any frequency permitted
;rxctcssfreqs=100.0 ; rx ctcss freqs in floating point. must be in table
;txctcssfreqs=100.0 ; tx ctcss freqs, any frequency permitted
rxctcssoverride=1 ; Set to 1 or yes to start out in carrier squelch
mode

carrierfrom=usb ; no,usb,usbinvert,dsp,vox
                        ; no - no carrier detection at all
                        ; usb - from the COR line on the modified USB sound
fob
                        ; usbinvert - from the inverted COR line on the
modified USB sound fob
                        ; dsp - from RX noise using dsp techniques
                        ; vox - voice activated from RX audio

ctcssfrom=no ; no,usb,dsp
                        ; no - CTCSS decoding, system will be carrier
squelch
                        ; usb - CTCSS decoding using input from USB FOB
                        ; (currently not supported)
                        ; dsp - CTCSS decoding using RX audio in DSP.
                        ; rxdemod option must be set to flat for this to
work.

rxdemod=speaker ; input type from radio: no,speaker,flat
                        ; no - RX audio input not used
                        ; flat - Use RX audio from discriminator (before
de-emphasis)
                        ; speaker - use de-emphasized audio

txprelim=no ; Audio processing on left output channel: no,yes
                        ; no - Audio is not pre-emphasized and limited.
                        ; Suitable for use on a microphone input
                        ; yes - Audio is pre-emphasized and limited.
                        ; Suitable for direct connection to an FM modulator

txlimonly=no ; Audio limiting with no pre-emphasis on output
channel: no,yes
                        ; no - Audio is not limited.
                        ; yes - Audio is limited.
                        ; Suitable for transmitters with no limiting but
with pre-emphasis.

txtoctype=no ; Transmit tone control type: no,phase,notone
                        ; no - CTCSS tone encoding with no hang time
                        ; phase - encode CTCSS and reverse phase
                        ; AKA ("reverse burst") before unkeying TX
                        ; notone - encode CTCSS and stop sending tone before
unkeying TX
                        ; AKA ("chicken burst")

txmixa=voice ; Left channel output: no,voice,tone,composite,auxvoice
                        ; no - Do not output anything
                        ; voice - output voice only
                        ; tone - CTCSS tone only
                        ; composite - voice and tone
                        ; auxvoice - auxiliary voice output at headphone
level for monitoring

txmixb=no ; Right channel output: no,voice,tone,composite,
auxvoice
                        ; See txmixa above.

invertptt=0 ; Invert PTT 0 = ground to transmit, 1 = open to
transmit
                        ; This is the collector lead of the 2n4401 on the
modified
                        ; usb sound fob.
                        ; please refer to the howto for the procedure to do
this.

duplex=0 ; Full Duplex

rxondelay=0 ; Uncomment and/or adjust for simplex nodes to
eliminate "Ping Ponging"
                        ; or "Relay Racing".
                        ; A positive value here will instruct the usbradio
driver to ignore the
                        ; COR line for a specified number of 20mSec
intervals following the
                        ; release of PTT. Use this only on simplex nodes,
and leave commented
                        ; out for repeaters or other full duplex nodes.
eeprom=1

Any thoughts on why asterisk would be trying to send a signal as soon as it
receives one? After the first time (upon asterisk restart) it receives a
signal it sends a beep followed by a morse code sequence.

Thanks,

Josh

···

-----Original Message-----
From: Corey Dean [mailto:n3fe@repeater.net]
Sent: Thursday, July 04, 2013 8:48 AM
To: Joshua Hintze; app_rpt-users@ohnosec.org
Subject: RE: [App_rpt-users] Issue with Hangup after first keying

Are you running full duplex on a simplex radio?

Corey N3FE
________________________________________
From: app_rpt-users-bounces@ohnosec.org [app_rpt-users-bounces@ohnosec.org]
On Behalf Of Joshua Hintze [joshh@imsar.com]
Sent: Wednesday, July 03, 2013 3:58 PM
To: app_rpt-users@ohnosec.org
Subject: [App_rpt-users] Issue with Hangup after first keying

Hello,

It is my first posting on here. I have ALMOST gotten the ACID installation
working. I'm using the URI interfaced to ACID and to my radio. The asterisk
can properly key the radio and its working just fine with that. I can also
connect to the node with iaxRpt directly with no problem and transmit OUT of
my radio.

However I am having some issues when my radio receives communication in that
as soon as I get my first radio RX, asterisk will then play a tone out of
the URI into the radio over and over again at about a one second interval.
In the asterisk terminal it just keeps repeating:

    -- Hungup 'Zap/pseudo-1726358622'
    -- Hungup 'Zap/pseudo-1774817359'
    -- Hungup 'Zap/pseudo-691532115'
    -- Hungup 'Zap/pseudo-81389311'
    -- Hungup 'Zap/pseudo-465154784'
   -- Hungup 'Zap/pseudo-627058532'
    -- Hungup 'Zap/pseudo-1656870264'
    -- Hungup 'Zap/pseudo-1671691803'
    -- Hungup 'Zap/pseudo-50274194'

forever keeping my radio always keyed.

I have the COR from the radio going into the URI. I do not plan on using
CTCSS and have tried tying it to ground as well as tying it to the COR as
well. My usbradio.conf has the following:

carrierfrom=usb
ctcssfrom=no

I have tried also ctcssfrom=usb as well.

Any help would be appreciated.

Thanks,

Josh

--
This message was scanned and is believed to be clean.
Click here to report this message as
spam.<http://simba.repeater.net:8080/cgi-bin/learn-msg.cgi?id=6EF48221A.A93B

18

For a simplex node be sure that you have the following defined in:

/etc/asterisk/rpt.conf

duplex=0 (for no telemetry / messasges)

or

duplex=1 (enables telemetry / messages / courtesy tones)

This is a different setting than the duplex = in your usbradio.conf file

N5ZUA

···

----- Original Message ----- From: "Joshua Hintze" <joshh@imsar.com>
To: "'Corey Dean'" <n3fe@repeater.net>; <app_rpt-users@ohnosec.org>
Sent: Friday, July 05, 2013 12:56 PM
Subject: Re: [App_rpt-users] Issue with Hangup after first keying

Ok all I'm back to work today and playing with this setup again.

I was able to isolate a much better signal for COR than what I had before.
This now truely goes from 0V->5V only when receiving and not when
transmitting. However I'm still having issues.

As soon as asterisk receives a signal it immediately tries to transmit a
signal out. This then effectively pulls the PTT low and my receiver stops
receiving. It is almost like it is in duplex mode but I have in
usbradio.conf

duplex=0 ; Full Duplex

rxondelay=0 ; Uncomment and/or adjust for simplex nodes to
eliminate "Ping Ponging"
                       ; or "Relay Racing".
                       ; A positive value here will instruct the usbradio
driver to ignore the
                       ; COR line for a specified number of 20mSec
intervals following the
                       ; release of PTT. Use this only on simplex nodes,
and leave commented
                       ; out for repeaters or other full duplex nodes.
eeprom=1

Just for clarity I'll post my entire usbradio.conf below:

[general]

[usb]

hdwtype=0 ; Leave this set to 0 for USB sound fobs modified
using
                       ; the instructions from usbfob.pdf. Use a setting of
                       ; 1 is for Dingotel/Sph interfaces.

rxboost=1 ; 0 = 20db attenuator inserted, 1= 20db attenuator
removed
                       ; Set to 1 for additonal gain if using a low-level
receiver output

rxctcssrelax=1 ; reduce talkoff from radios w/o CTCSS Tx HPF
                       ; Do not change this, leave this as a 1

;txctcssdefault=100.0 ; default tx ctcss freq, any frequency permitted
;rxctcssfreqs=100.0 ; rx ctcss freqs in floating point. must be in table
;txctcssfreqs=100.0 ; tx ctcss freqs, any frequency permitted
rxctcssoverride=1 ; Set to 1 or yes to start out in carrier squelch
mode

carrierfrom=usb ; no,usb,usbinvert,dsp,vox
                       ; no - no carrier detection at all
                       ; usb - from the COR line on the modified USB sound
fob
                       ; usbinvert - from the inverted COR line on the
modified USB sound fob
                       ; dsp - from RX noise using dsp techniques
                       ; vox - voice activated from RX audio

ctcssfrom=no ; no,usb,dsp
                       ; no - CTCSS decoding, system will be carrier
squelch
                       ; usb - CTCSS decoding using input from USB FOB
                       ; (currently not supported)
                       ; dsp - CTCSS decoding using RX audio in DSP.
                       ; rxdemod option must be set to flat for this to
work.

rxdemod=speaker ; input type from radio: no,speaker,flat
                       ; no - RX audio input not used
                       ; flat - Use RX audio from discriminator (before
de-emphasis)
                       ; speaker - use de-emphasized audio

txprelim=no ; Audio processing on left output channel: no,yes
                       ; no - Audio is not pre-emphasized and limited.
                       ; Suitable for use on a microphone input
                       ; yes - Audio is pre-emphasized and limited.
                       ; Suitable for direct connection to an FM modulator

txlimonly=no ; Audio limiting with no pre-emphasis on output
channel: no,yes
                       ; no - Audio is not limited.
                       ; yes - Audio is limited.
                       ; Suitable for transmitters with no limiting but
with pre-emphasis.

txtoctype=no ; Transmit tone control type: no,phase,notone
                       ; no - CTCSS tone encoding with no hang time
                       ; phase - encode CTCSS and reverse phase
                       ; AKA ("reverse burst") before unkeying TX
                       ; notone - encode CTCSS and stop sending tone before
unkeying TX
                       ; AKA ("chicken burst")

txmixa=voice ; Left channel output: no,voice,tone,composite,auxvoice
                       ; no - Do not output anything
                       ; voice - output voice only
                       ; tone - CTCSS tone only
                       ; composite - voice and tone
                       ; auxvoice - auxiliary voice output at headphone
level for monitoring

txmixb=no ; Right channel output: no,voice,tone,composite,
auxvoice
                       ; See txmixa above.

invertptt=0 ; Invert PTT 0 = ground to transmit, 1 = open to
transmit
                       ; This is the collector lead of the 2n4401 on the
modified
                       ; usb sound fob.
                       ; please refer to the howto for the procedure to do
this.

duplex=0 ; Full Duplex

rxondelay=0 ; Uncomment and/or adjust for simplex nodes to
eliminate "Ping Ponging"
                       ; or "Relay Racing".
                       ; A positive value here will instruct the usbradio
driver to ignore the
                       ; COR line for a specified number of 20mSec
intervals following the
                       ; release of PTT. Use this only on simplex nodes,
and leave commented
                       ; out for repeaters or other full duplex nodes.
eeprom=1

Any thoughts on why asterisk would be trying to send a signal as soon as it
receives one? After the first time (upon asterisk restart) it receives a
signal it sends a beep followed by a morse code sequence.

Thanks,

Josh

-----Original Message-----
From: Corey Dean [mailto:n3fe@repeater.net]
Sent: Thursday, July 04, 2013 8:48 AM
To: Joshua Hintze; app_rpt-users@ohnosec.org
Subject: RE: [App_rpt-users] Issue with Hangup after first keying

Are you running full duplex on a simplex radio?

Corey N3FE
________________________________________
From: app_rpt-users-bounces@ohnosec.org [app_rpt-users-bounces@ohnosec.org]
On Behalf Of Joshua Hintze [joshh@imsar.com]
Sent: Wednesday, July 03, 2013 3:58 PM
To: app_rpt-users@ohnosec.org
Subject: [App_rpt-users] Issue with Hangup after first keying

Hello,

It is my first posting on here. I have ALMOST gotten the ACID installation
working. I'm using the URI interfaced to ACID and to my radio. The asterisk
can properly key the radio and its working just fine with that. I can also
connect to the node with iaxRpt directly with no problem and transmit OUT of
my radio.

However I am having some issues when my radio receives communication in that
as soon as I get my first radio RX, asterisk will then play a tone out of
the URI into the radio over and over again at about a one second interval.
In the asterisk terminal it just keeps repeating:

   -- Hungup 'Zap/pseudo-1726358622'
   -- Hungup 'Zap/pseudo-1774817359'
   -- Hungup 'Zap/pseudo-691532115'
   -- Hungup 'Zap/pseudo-81389311'
   -- Hungup 'Zap/pseudo-465154784'
  -- Hungup 'Zap/pseudo-627058532'
   -- Hungup 'Zap/pseudo-1656870264'
   -- Hungup 'Zap/pseudo-1671691803'
   -- Hungup 'Zap/pseudo-50274194'

forever keeping my radio always keyed.

I have the COR from the radio going into the URI. I do not plan on using
CTCSS and have tried tying it to ground as well as tying it to the COR as
well. My usbradio.conf has the following:

carrierfrom=usb
ctcssfrom=no

I have tried also ctcssfrom=usb as well.

Any help would be appreciated.

Thanks,

Josh

--
This message was scanned and is believed to be clean.
Click here to report this message as
spam.<http://simba.repeater.net:8080/cgi-bin/learn-msg.cgi?id=6EF48221A.A93B
>

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
ohnosec.org

19

Wow that is it!

My rpt.conf did not even have a duplex setting in it so I had no idea that
it needed to be set. Grrrrr

Seems to be working much better now.

Thanks!

Josh

···

-----Original Message-----
From: app_rpt-users-bounces@ohnosec.org
[mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Steve Agee
Sent: Friday, July 05, 2013 12:05 PM
To: app_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] Issue with Hangup after first keying

For a simplex node be sure that you have the following defined in:

/etc/asterisk/rpt.conf

duplex=0 (for no telemetry / messasges)

or

duplex=1 (enables telemetry / messages / courtesy tones)

This is a different setting than the duplex = in your usbradio.conf file

N5ZUA

----- Original Message -----
From: "Joshua Hintze" <joshh@imsar.com>
To: "'Corey Dean'" <n3fe@repeater.net>; <app_rpt-users@ohnosec.org>
Sent: Friday, July 05, 2013 12:56 PM
Subject: Re: [App_rpt-users] Issue with Hangup after first keying

Ok all I'm back to work today and playing with this setup again.

I was able to isolate a much better signal for COR than what I had before.
This now truely goes from 0V->5V only when receiving and not when
transmitting. However I'm still having issues.

As soon as asterisk receives a signal it immediately tries to transmit a
signal out. This then effectively pulls the PTT low and my receiver stops
receiving. It is almost like it is in duplex mode but I have in
usbradio.conf

duplex=0 ; Full Duplex

rxondelay=0 ; Uncomment and/or adjust for simplex nodes to
eliminate "Ping Ponging"
                       ; or "Relay Racing".
                       ; A positive value here will instruct the usbradio
driver to ignore the
                       ; COR line for a specified number of 20mSec
intervals following the
                       ; release of PTT. Use this only on simplex nodes,
and leave commented
                       ; out for repeaters or other full duplex nodes.
eeprom=1

Just for clarity I'll post my entire usbradio.conf below:

[general]

[usb]

hdwtype=0 ; Leave this set to 0 for USB sound fobs modified
using
                       ; the instructions from usbfob.pdf. Use a setting
of
                       ; 1 is for Dingotel/Sph interfaces.

rxboost=1 ; 0 = 20db attenuator inserted, 1= 20db attenuator
removed
                       ; Set to 1 for additonal gain if using a low-level
receiver output

rxctcssrelax=1 ; reduce talkoff from radios w/o CTCSS Tx HPF
                       ; Do not change this, leave this as a 1

;txctcssdefault=100.0 ; default tx ctcss freq, any frequency permitted
;rxctcssfreqs=100.0 ; rx ctcss freqs in floating point. must be in
table
;txctcssfreqs=100.0 ; tx ctcss freqs, any frequency permitted
rxctcssoverride=1 ; Set to 1 or yes to start out in carrier squelch
mode

carrierfrom=usb ; no,usb,usbinvert,dsp,vox
                       ; no - no carrier detection at all
                       ; usb - from the COR line on the modified USB sound
fob
                       ; usbinvert - from the inverted COR line on the
modified USB sound fob
                       ; dsp - from RX noise using dsp techniques
                       ; vox - voice activated from RX audio

ctcssfrom=no ; no,usb,dsp
                       ; no - CTCSS decoding, system will be carrier
squelch
                       ; usb - CTCSS decoding using input from USB FOB
                       ; (currently not supported)
                       ; dsp - CTCSS decoding using RX audio in DSP.
                       ; rxdemod option must be set to flat for this to
work.

rxdemod=speaker ; input type from radio: no,speaker,flat
                       ; no - RX audio input not used
                       ; flat - Use RX audio from discriminator (before
de-emphasis)
                       ; speaker - use de-emphasized audio

txprelim=no ; Audio processing on left output channel: no,yes
                       ; no - Audio is not pre-emphasized and limited.
                       ; Suitable for use on a microphone input
                       ; yes - Audio is pre-emphasized and limited.
                       ; Suitable for direct connection to an FM modulator

txlimonly=no ; Audio limiting with no pre-emphasis on output
channel: no,yes
                       ; no - Audio is not limited.
                       ; yes - Audio is limited.
                       ; Suitable for transmitters with no limiting but
with pre-emphasis.

txtoctype=no ; Transmit tone control type: no,phase,notone
                       ; no - CTCSS tone encoding with no hang time
                       ; phase - encode CTCSS and reverse phase
                       ; AKA ("reverse burst") before unkeying TX
                       ; notone - encode CTCSS and stop sending tone
before
unkeying TX
                       ; AKA ("chicken burst")

txmixa=voice ; Left channel output: no,voice,tone,composite,auxvoice
                       ; no - Do not output anything
                       ; voice - output voice only
                       ; tone - CTCSS tone only
                       ; composite - voice and tone
                       ; auxvoice - auxiliary voice output at headphone
level for monitoring

txmixb=no ; Right channel output: no,voice,tone,composite,
auxvoice
                       ; See txmixa above.

invertptt=0 ; Invert PTT 0 = ground to transmit, 1 = open to
transmit
                       ; This is the collector lead of the 2n4401 on the
modified
                       ; usb sound fob.
                       ; please refer to the howto for the procedure to do
this.

duplex=0 ; Full Duplex

rxondelay=0 ; Uncomment and/or adjust for simplex nodes to
eliminate "Ping Ponging"
                       ; or "Relay Racing".
                       ; A positive value here will instruct the usbradio
driver to ignore the
                       ; COR line for a specified number of 20mSec
intervals following the
                       ; release of PTT. Use this only on simplex nodes,
and leave commented
                       ; out for repeaters or other full duplex nodes.
eeprom=1

Any thoughts on why asterisk would be trying to send a signal as soon as
it
receives one? After the first time (upon asterisk restart) it receives a
signal it sends a beep followed by a morse code sequence.

Thanks,

Josh

-----Original Message-----
From: Corey Dean [mailto:n3fe@repeater.net]
Sent: Thursday, July 04, 2013 8:48 AM
To: Joshua Hintze; app_rpt-users@ohnosec.org
Subject: RE: [App_rpt-users] Issue with Hangup after first keying

Are you running full duplex on a simplex radio?

Corey N3FE
________________________________________
From: app_rpt-users-bounces@ohnosec.org
[app_rpt-users-bounces@ohnosec.org]
On Behalf Of Joshua Hintze [joshh@imsar.com]
Sent: Wednesday, July 03, 2013 3:58 PM
To: app_rpt-users@ohnosec.org
Subject: [App_rpt-users] Issue with Hangup after first keying

Hello,

It is my first posting on here. I have ALMOST gotten the ACID installation
working. I'm using the URI interfaced to ACID and to my radio. The
asterisk
can properly key the radio and its working just fine with that. I can also
connect to the node with iaxRpt directly with no problem and transmit OUT
of
my radio.

However I am having some issues when my radio receives communication in
that
as soon as I get my first radio RX, asterisk will then play a tone out of
the URI into the radio over and over again at about a one second interval.
In the asterisk terminal it just keeps repeating:

   -- Hungup 'Zap/pseudo-1726358622'
   -- Hungup 'Zap/pseudo-1774817359'
   -- Hungup 'Zap/pseudo-691532115'
   -- Hungup 'Zap/pseudo-81389311'
   -- Hungup 'Zap/pseudo-465154784'
  -- Hungup 'Zap/pseudo-627058532'
   -- Hungup 'Zap/pseudo-1656870264'
   -- Hungup 'Zap/pseudo-1671691803'
   -- Hungup 'Zap/pseudo-50274194'

forever keeping my radio always keyed.

I have the COR from the radio going into the URI. I do not plan on using
CTCSS and have tried tying it to ground as well as tying it to the COR as
well. My usbradio.conf has the following:

carrierfrom=usb
ctcssfrom=no

I have tried also ctcssfrom=usb as well.

Any help would be appreciated.

Thanks,

Josh

--
This message was scanned and is believed to be clean.
Click here to report this message as

spam.<http://simba.repeater.net:8080/cgi-bin/learn-msg.cgi?id=6EF48221A.A93B

>

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
ohnosec.org

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

20

Correct. The default does not define that value, and thus it is assumed at full duplex / repeater setting.

Good deal!

N5ZUA

···

----- Original Message ----- From: "Joshua Hintze" <joshh@imsar.com>
To: "'Steve Agee'" <n5zua@earthlink.net>; <app_rpt-users@ohnosec.org>
Sent: Friday, July 05, 2013 1:06 PM
Subject: RE: [App_rpt-users] Issue with Hangup after first keying

Wow that is it!

My rpt.conf did not even have a duplex setting in it so I had no idea that
it needed to be set. Grrrrr

Seems to be working much better now.

Thanks!

Josh

-----Original Message-----
From: app_rpt-users-bounces@ohnosec.org
[mailto:app_rpt-users-bounces@ohnosec.org] On Behalf Of Steve Agee
Sent: Friday, July 05, 2013 12:05 PM
To: app_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] Issue with Hangup after first keying

For a simplex node be sure that you have the following defined in:

/etc/asterisk/rpt.conf

duplex=0 (for no telemetry / messasges)

or

duplex=1 (enables telemetry / messages / courtesy tones)

This is a different setting than the duplex = in your usbradio.conf file

N5ZUA

----- Original Message ----- From: "Joshua Hintze" <joshh@imsar.com>
To: "'Corey Dean'" <n3fe@repeater.net>; <app_rpt-users@ohnosec.org>
Sent: Friday, July 05, 2013 12:56 PM
Subject: Re: [App_rpt-users] Issue with Hangup after first keying

Ok all I'm back to work today and playing with this setup again.

I was able to isolate a much better signal for COR than what I had before.
This now truely goes from 0V->5V only when receiving and not when
transmitting. However I'm still having issues.

As soon as asterisk receives a signal it immediately tries to transmit a
signal out. This then effectively pulls the PTT low and my receiver stops
receiving. It is almost like it is in duplex mode but I have in
usbradio.conf

duplex=0 ; Full Duplex

rxondelay=0 ; Uncomment and/or adjust for simplex nodes to
eliminate "Ping Ponging"
                       ; or "Relay Racing".
                       ; A positive value here will instruct the usbradio
driver to ignore the
                       ; COR line for a specified number of 20mSec
intervals following the
                       ; release of PTT. Use this only on simplex nodes,
and leave commented
                       ; out for repeaters or other full duplex nodes.
eeprom=1

Just for clarity I'll post my entire usbradio.conf below:

[general]

[usb]

hdwtype=0 ; Leave this set to 0 for USB sound fobs modified
using
                       ; the instructions from usbfob.pdf. Use a setting
of
                       ; 1 is for Dingotel/Sph interfaces.

rxboost=1 ; 0 = 20db attenuator inserted, 1= 20db attenuator
removed
                       ; Set to 1 for additonal gain if using a low-level
receiver output

rxctcssrelax=1 ; reduce talkoff from radios w/o CTCSS Tx HPF
                       ; Do not change this, leave this as a 1

;txctcssdefault=100.0 ; default tx ctcss freq, any frequency permitted
;rxctcssfreqs=100.0 ; rx ctcss freqs in floating point. must be in
table
;txctcssfreqs=100.0 ; tx ctcss freqs, any frequency permitted
rxctcssoverride=1 ; Set to 1 or yes to start out in carrier squelch
mode

carrierfrom=usb ; no,usb,usbinvert,dsp,vox
                       ; no - no carrier detection at all
                       ; usb - from the COR line on the modified USB sound
fob
                       ; usbinvert - from the inverted COR line on the
modified USB sound fob
                       ; dsp - from RX noise using dsp techniques
                       ; vox - voice activated from RX audio

ctcssfrom=no ; no,usb,dsp
                       ; no - CTCSS decoding, system will be carrier
squelch
                       ; usb - CTCSS decoding using input from USB FOB
                       ; (currently not supported)
                       ; dsp - CTCSS decoding using RX audio in DSP.
                       ; rxdemod option must be set to flat for this to
work.

rxdemod=speaker ; input type from radio: no,speaker,flat
                       ; no - RX audio input not used
                       ; flat - Use RX audio from discriminator (before
de-emphasis)
                       ; speaker - use de-emphasized audio

txprelim=no ; Audio processing on left output channel: no,yes
                       ; no - Audio is not pre-emphasized and limited.
                       ; Suitable for use on a microphone input
                       ; yes - Audio is pre-emphasized and limited.
                       ; Suitable for direct connection to an FM modulator

txlimonly=no ; Audio limiting with no pre-emphasis on output
channel: no,yes
                       ; no - Audio is not limited.
                       ; yes - Audio is limited.
                       ; Suitable for transmitters with no limiting but
with pre-emphasis.

txtoctype=no ; Transmit tone control type: no,phase,notone
                       ; no - CTCSS tone encoding with no hang time
                       ; phase - encode CTCSS and reverse phase
                       ; AKA ("reverse burst") before unkeying TX
                       ; notone - encode CTCSS and stop sending tone
before
unkeying TX
                       ; AKA ("chicken burst")

txmixa=voice ; Left channel output: no,voice,tone,composite,auxvoice
                       ; no - Do not output anything
                       ; voice - output voice only
                       ; tone - CTCSS tone only
                       ; composite - voice and tone
                       ; auxvoice - auxiliary voice output at headphone
level for monitoring

txmixb=no ; Right channel output: no,voice,tone,composite,
auxvoice
                       ; See txmixa above.

invertptt=0 ; Invert PTT 0 = ground to transmit, 1 = open to
transmit
                       ; This is the collector lead of the 2n4401 on the
modified
                       ; usb sound fob.
                       ; please refer to the howto for the procedure to do
this.

duplex=0 ; Full Duplex

rxondelay=0 ; Uncomment and/or adjust for simplex nodes to
eliminate "Ping Ponging"
                       ; or "Relay Racing".
                       ; A positive value here will instruct the usbradio
driver to ignore the
                       ; COR line for a specified number of 20mSec
intervals following the
                       ; release of PTT. Use this only on simplex nodes,
and leave commented
                       ; out for repeaters or other full duplex nodes.
eeprom=1

Any thoughts on why asterisk would be trying to send a signal as soon as
it
receives one? After the first time (upon asterisk restart) it receives a
signal it sends a beep followed by a morse code sequence.

Thanks,

Josh

-----Original Message-----
From: Corey Dean [mailto:n3fe@repeater.net]
Sent: Thursday, July 04, 2013 8:48 AM
To: Joshua Hintze; app_rpt-users@ohnosec.org
Subject: RE: [App_rpt-users] Issue with Hangup after first keying

Are you running full duplex on a simplex radio?

Corey N3FE
________________________________________
From: app_rpt-users-bounces@ohnosec.org
[app_rpt-users-bounces@ohnosec.org]
On Behalf Of Joshua Hintze [joshh@imsar.com]
Sent: Wednesday, July 03, 2013 3:58 PM
To: app_rpt-users@ohnosec.org
Subject: [App_rpt-users] Issue with Hangup after first keying

Hello,

It is my first posting on here. I have ALMOST gotten the ACID installation
working. I'm using the URI interfaced to ACID and to my radio. The
asterisk
can properly key the radio and its working just fine with that. I can also
connect to the node with iaxRpt directly with no problem and transmit OUT
of
my radio.

However I am having some issues when my radio receives communication in
that
as soon as I get my first radio RX, asterisk will then play a tone out of
the URI into the radio over and over again at about a one second interval.
In the asterisk terminal it just keeps repeating:

   -- Hungup 'Zap/pseudo-1726358622'
   -- Hungup 'Zap/pseudo-1774817359'
   -- Hungup 'Zap/pseudo-691532115'
   -- Hungup 'Zap/pseudo-81389311'
   -- Hungup 'Zap/pseudo-465154784'
  -- Hungup 'Zap/pseudo-627058532'
   -- Hungup 'Zap/pseudo-1656870264'
   -- Hungup 'Zap/pseudo-1671691803'
   -- Hungup 'Zap/pseudo-50274194'

forever keeping my radio always keyed.

I have the COR from the radio going into the URI. I do not plan on using
CTCSS and have tried tying it to ground as well as tying it to the COR as
well. My usbradio.conf has the following:

carrierfrom=usb
ctcssfrom=no

I have tried also ctcssfrom=usb as well.

Any help would be appreciated.

Thanks,

Josh

--
This message was scanned and is believed to be clean.
Click here to report this message as

spam.<http://simba.repeater.net:8080/cgi-bin/learn-msg.cgi?id=6EF48221A.A93B

>

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
ohnosec.org

_______________________________________________
App_rpt-users mailing list
App_rpt-users@ohnosec.org
ohnosec.org