From n9yty at n9yty.com  Mon Jul 14 15:07:24 2008
From: n9yty at n9yty.com (Steven Palm)
Date: Mon, 14 Jul 2008 15:07:24 -0500
Subject: [App_rpt] Hot TX audio
Message-ID: <8D07779A-E625-407C-85E3-2C764E50A8C3@n9yty.com>

Hi all,

Just fishing for ideas...  I have my app_rpt node connected to a radio  
right now via the mic input, and the audio is HOT.  Using the 'radio  
tune txvoice' command, I get no audioble ouput when using a number  
below 27, but anything over 50 or so drives the radio way way wide in  
deviation and starts clipping.

I'm assuming that the parameter here is adjusting the volume on the  
USB sound fob, and it's just too much for the rig...  Thinking a  
resistor in the TX audio line would do it, any suggested for a  
size? :)  Then I can run over to Radio Shack and pay them $3.95 for an  
$0.18 resistor. LoL

Steve

From hwstar at rodgers.sdcoxmail.com  Mon Jul 14 17:52:31 2008
From: hwstar at rodgers.sdcoxmail.com (hwstar@rodgers.sdcoxmail.com)
Date: Mon, 14 Jul 2008 15:52:31 -0700
Subject: [App_rpt] Hot TX audio
Message-ID: <20080714225231.RFOP822.dukecmmtao04.coxmail.com@dukecmimpo03.coxmail.com>



Use an 'L' network made out of 2 resistors. Start with 68 kohms for the top resistor, and 470 ohms for the bottom resistor. Feed the output output from the fob to the top resistor, and take the audio at the tap for the microphone input. Connect the bottom of the 470 ohm resistor to mic ground.

There's no standard for microphone sensitivity across radios. It varies all over the place from a few millivolts
P-P to a volt P-P or so.

If you are willing to tear the radio apart, you could inject
the USB fob output right into the modulator of the radio. This will provide the best signal to noise ratio. This is what I prefer to do.

Steve
WA6ZFT
> 
> From: Steven Palm <n9yty at n9yty.com>
> Date: 2008/07/14 Mon PM 01:07:24 PDT
> To: Asterisk Repeater Controler <app_rpt at lists.illiana.net>
> Subject: [App_rpt] Hot TX audio
> 
> Hi all,
> 
> Just fishing for ideas...  I have my app_rpt node connected to a radio  
> right now via the mic input, and the audio is HOT.  Using the 'radio  
> tune txvoice' command, I get no audioble ouput when using a number  
> below 27, but anything over 50 or so drives the radio way way wide in  
> deviation and starts clipping.
> 
> I'm assuming that the parameter here is adjusting the volume on the  
> USB sound fob, and it's just too much for the rig...  Thinking a  
> resistor in the TX audio line would do it, any suggested for a  
> size? :)  Then I can run over to Radio Shack and pay them $3.95 for an  
> $0.18 resistor. LoL
> 
> Steve
> _______________________________________________
> App_rpt mailing list
> App_rpt at lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt
> 


From telesistant at hotmail.com  Wed Jul 16 18:51:14 2008
From: telesistant at hotmail.com (Jim Duuuude)
Date: Wed, 16 Jul 2008 16:51:14 -0700
Subject: [App_rpt] Hot TX audio
In-Reply-To: <8D07779A-E625-407C-85E3-2C764E50A8C3@n9yty.com>
References: <8D07779A-E625-407C-85E3-2C764E50A8C3@n9yty.com>
Message-ID: <BAY119-W266645E808AE3E8D297F8BB18F0@phx.gbl>


a resistor or 2 is always good for that, since it also makes for better decoupling
and thats good when you have such a sensitive input.

> From: n9yty at n9yty.com
> To: app_rpt at lists.illiana.net
> Date: Mon, 14 Jul 2008 15:07:24 -0500
> Subject: [App_rpt] Hot TX audio
> 
> Hi all,
> 
> Just fishing for ideas...  I have my app_rpt node connected to a radio  
> right now via the mic input, and the audio is HOT.  Using the 'radio  
> tune txvoice' command, I get no audioble ouput when using a number  
> below 27, but anything over 50 or so drives the radio way way wide in  
> deviation and starts clipping.
> 
> I'm assuming that the parameter here is adjusting the volume on the  
> USB sound fob, and it's just too much for the rig...  Thinking a  
> resistor in the TX audio line would do it, any suggested for a  
> size? :)  Then I can run over to Radio Shack and pay them $3.95 for an  
> $0.18 resistor. LoL
> 
> Steve
> _______________________________________________
> App_rpt mailing list
> App_rpt at lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.illiana.net/pipermail/app_rpt/attachments/20080716/fe822018/attachment.html

From kb4fxc at inttek.net  Sat Jul 19 15:43:30 2008
From: kb4fxc at inttek.net (David McGough)
Date: Sat, 19 Jul 2008 16:43:30 -0400 (EDT)
Subject: [App_rpt] URI configuration help
Message-ID: <Pine.LNX.4.44.0807191627230.11405-100000@goliath.inttek.net>



Hi Everyone,

I'm finally getting to "finish up" my URI based project and wondered if
someone could help point me to some advanced sample asterisk/app_rpt
config files (usbradio.conf, rpt.conf, primarily) for using the URI
adapters.

I've currently got 1 URI working properly with my TKR-850 repeater. Now, I
want to add 2 remote base radios for VHF and HF, do some linking, etc. I, 
mainly need more info about the syntax to use with multiple URI's, 
usbradio.conf options, etc.

Thanks in advance!

David KB4FXC




From hwstar at rodgers.sdcoxmail.com  Sat Jul 19 17:56:19 2008
From: hwstar at rodgers.sdcoxmail.com (Stephen Rodgers)
Date: Sat, 19 Jul 2008 15:56:19 -0700
Subject: [App_rpt] URI configuration help
In-Reply-To: <Pine.LNX.4.44.0807191627230.11405-100000@goliath.inttek.net>
References: <Pine.LNX.4.44.0807191627230.11405-100000@goliath.inttek.net>
Message-ID: <48827113.7090100@rodgers.sdcoxmail.com>

David,

This is one area where our documentation falls short. We have got
automated installs and config examples for single-node systems, but
no examples for multi-node systems. Basically for each usb mode
entries will need to be made in usbradio.conf, rpt.conf, and
extensions.conf.

*** usbradio.conf ***


[general]

; Nothing in the general section for multiple devices.

[usb] ; first node
; Insert all USB config options from usbradio.conf.sample here except
; for devicenum setting. Modify settings to suit configuration.
.
.
.
devicenum=0 ; unique for each device defined
.
.
.
[usb1] ; second node
.
.
.
devicenum=1
.
.
.

[usb2] ; third node
.
.
.
devicenum=2
.
.
.

*** extensions.conf ****

exten => 1234,1,rpt,1234 # first node
exten => 5678,1,rpt,5678 # second node
exten => 9012,1,rpt,9012 # third node


**** rpt.conf ****

rpt.conf

[1234] ; first node
rxchannel = Radio/usb
; Configuration settings from rpt.conf.sample tailored to your
application follow the channel definition above.
.
.
.
[5678] ; second node
rxchannel = Radio/usb1
; Configuration settings from rpt.conf.sample tailored to your
application follow the channel definition above.
.
.
.
[9012] ; third node
rxchannel = Radio/usb2
; Configuration settings from rpt.conf.sample tailored to your
application follow the channel definition above.
.
.
.


Standard disclaimer boilerplate: I tried to answer your question. I
haven't tested what is documented above. I just did some quick research
to come up with this answer, and the research was not in-depth, There
may very well be something I left out, so your mileage may vary. There
are no guarantees. If you find something and fix it, please post it back
to the list so everyone will benefit from it.


Steve
WA6ZFT



David McGough wrote:
> 
> Hi Everyone,
> 
> I'm finally getting to "finish up" my URI based project and wondered if
> someone could help point me to some advanced sample asterisk/app_rpt
> config files (usbradio.conf, rpt.conf, primarily) for using the URI
> adapters.
> 
> I've currently got 1 URI working properly with my TKR-850 repeater. Now, I
> want to add 2 remote base radios for VHF and HF, do some linking, etc. I, 
> mainly need more info about the syntax to use with multiple URI's, 
> usbradio.conf options, etc.
> 
> Thanks in advance!
> 
> David KB4FXC
> 
> 
> 
> _______________________________________________
> App_rpt mailing list
> App_rpt at lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt
> 


From w4rfj at comcast.net  Sat Jul 19 23:56:14 2008
From: w4rfj at comcast.net (Roger F. Jordan Sr.)
Date: Sun, 20 Jul 2008 00:56:14 -0400
Subject: [App_rpt] URI configuration help
In-Reply-To: <48827113.7090100@rodgers.sdcoxmail.com>
Message-ID: <mailman.0.1216529686.2537.app_rpt@lists.illiana.net>

Below are examples of MY SETUP as assisted by W9SH

I removed the Functions but notice the phone functions use two different
function lists for Phonepatch... They are not included for security
reasons...

I hope this helps!!!

Also Steve,  Did you get my apps for The GMRS, FRS and MURS and All the
registrations for the different systems I applied for (or is that not you)

I would also like to talk to You guys about Phone patch control... 

Best Regards to ALL 

Roger W4RFJ

; rpt.conf
; 20071103 0900 sphenke at xelatec.com

; Radio Repeater / Remote Base config for use with app_rpt
; manipulated by the app_rpt installation script
; text strings that begin with xxx_ should be manually edited
; if the install script does not replace them.

[101]
rxchannel = radio/usb
duplex = 2
functions = functions 		        ; DTMF function list
link_functions = functions-linked	; DTMF function list for link
phone_functions = functions-phone-1	; (optional) different functions for
'P' mode
tonezone = us				; use US tones (default)
context = from-internal		; dialing context for phone
callerid = "de w4rfj/r"<445.95 pl100>  	; Callerid for phone calls
idrecording=|ide w4rfj/r
accountcode=RADIO			; account code (optional)
funcchar = *				; function lead-in character
(defaults to '*')
endchar = #			        ; command mode end character
(defaults to '#')
hangtime=10			        ; squelch tail hang time (in ms)
(optional)
totime=180000				; transmit time-out time (in ms)
(optional)
idtime=600000				; id interval time (in ms)
(optional)
politeid=30000				; time in milliseconds before ID
timer
propagate_phonedtmf=yes	    	        ;propagate_phonedtmf = yes
unlinkedct=ct1 		                ; DTMF sent to system from phone
gets
				        ; repeated into main system output
and

[102]
rxchannel = radio/usb1
duplex = 0
functions = functions 		        ; DTMF function list
link_functions = functions-linked	; DTMF function list for link
phone_functions = functions-phone-1	;  different functions 
tonezone = us			        ; use US tones (default)
context = from-internal		        ; dialing context for phone
callerid = "wqex329"<FRS Channel 1>  	; Callerid for phone calls
idrecording=|iK
accountcode=RADIO			; account code (optional)
funcchar = *				; function lead-in character
(defaults to '*')
endchar = #				; command mode end character
(defaults to '#')
hangtime=3				; squelch tail hang time (in ms)
(optional)
totime=180000				; transmit time-out time (in ms)
(optional)
idtime=600000				; id interval time (in ms)
(optional)
politeid=30000				; time in milliseconds before ID
timer
propagate_phonedtmf=no

*************everything in between deals with DTMF Commands Etc...

101 = radio at 192.168.14.149:4569/101,NONE
102 = radio at 192.168.14.149:4569/102,NONE

; end of file - rpt.conf

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

; usbradio.conf
; Configuration for chan_usbradio
; 20071205 0845 sphenke at xelatec.com
; refer to globals_rpt_custom.conf for variable definitions
;
[general]

rxcpusaver=0
txcpusaver=0

[usb]
hwtype=0
rxboost=1
rxctcssrelax=0
txctcssdefault=100.0
rxctcssfreqs=100.0
txctcssfreqs=100.0
carrierfrom=dsp
ctcssfrom=dsp
rxdemod=flat
txprelim=yes
txtoctype=notone
txmixa=composite
txmixb=no
invertptt=0
;rxfreq=445.950000
;txfreq=147.490000
duplex=1
eeprom=0

[usb1]
hwtype=0
rxboost=1
rxctcssrelax=1
;txctcssdefault=0
;rxctcssfreq=0
;txctcssfreq=0
carrierfrom=vox
ctcssfrom=no
rxdemod=speaker
txprelim=no
txtoctype=no; notone
txmixa=voice
txmixb=no
invertptt=0
;rxfreq=462.562500
;txfreq=462.562500
duplex=0
eeprom=0




-----Original Message-----
From: app_rpt-bounces at lists.illiana.net
[mailto:app_rpt-bounces at lists.illiana.net] On Behalf Of Stephen Rodgers
Sent: Saturday, July 19, 2008 6:56 PM
To: Asterisk Repeater Controler
Subject: Re: [App_rpt] URI configuration help

David,

This is one area where our documentation falls short. We have got
automated installs and config examples for single-node systems, but
no examples for multi-node systems. Basically for each usb mode
entries will need to be made in usbradio.conf, rpt.conf, and
extensions.conf.

*** usbradio.conf ***


[general]

; Nothing in the general section for multiple devices.

[usb] ; first node
; Insert all USB config options from usbradio.conf.sample here except
; for devicenum setting. Modify settings to suit configuration.
.
.
.
devicenum=0 ; unique for each device defined
.
.
.
[usb1] ; second node
.
.
.
devicenum=1
.
.
.

[usb2] ; third node
.
.
.
devicenum=2
.
.
.

*** extensions.conf ****

exten => 1234,1,rpt,1234 # first node
exten => 5678,1,rpt,5678 # second node
exten => 9012,1,rpt,9012 # third node


**** rpt.conf ****

rpt.conf

[1234] ; first node
rxchannel = Radio/usb
; Configuration settings from rpt.conf.sample tailored to your
application follow the channel definition above.
.
.
.
[5678] ; second node
rxchannel = Radio/usb1
; Configuration settings from rpt.conf.sample tailored to your
application follow the channel definition above.
.
.
.
[9012] ; third node
rxchannel = Radio/usb2
; Configuration settings from rpt.conf.sample tailored to your
application follow the channel definition above.
.
.
.


Standard disclaimer boilerplate: I tried to answer your question. I
haven't tested what is documented above. I just did some quick research
to come up with this answer, and the research was not in-depth, There
may very well be something I left out, so your mileage may vary. There
are no guarantees. If you find something and fix it, please post it back
to the list so everyone will benefit from it.


Steve
WA6ZFT



David McGough wrote:
> 
> Hi Everyone,
> 
> I'm finally getting to "finish up" my URI based project and wondered if
> someone could help point me to some advanced sample asterisk/app_rpt
> config files (usbradio.conf, rpt.conf, primarily) for using the URI
> adapters.
> 
> I've currently got 1 URI working properly with my TKR-850 repeater. Now, I
> want to add 2 remote base radios for VHF and HF, do some linking, etc. I, 
> mainly need more info about the syntax to use with multiple URI's, 
> usbradio.conf options, etc.
> 
> Thanks in advance!
> 
> David KB4FXC
> 
> 
> 
> _______________________________________________
> App_rpt mailing list
> App_rpt at lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt
> 

_______________________________________________
App_rpt mailing list
App_rpt at lists.illiana.net
http://lists.illiana.net/mailman/listinfo/app_rpt


From josh.roberson at comcast.net  Sun Jul 20 00:08:26 2008
From: josh.roberson at comcast.net (Josh Roberson)
Date: Sun, 20 Jul 2008 00:08:26 -0500
Subject: [App_rpt] USB Radio for MAC??
Message-ID: <14E217CF-24D7-4BE1-85A4-86336C5010FD@comcast.net>

I was wondering if the usb radio drivers require zaptel (now known as  
DAHDI) drivers/hardware or if the usb radio drivers can be used  
standalone?  I run Apple equipment here, and I would love to tie my  
asterisk server (running on my osx server) into my radio, but zaptel  
is out of the question on this platform.

Any help is appreciated!

-Josh
WX4JRR

From hwstar at rodgers.sdcoxmail.com  Sun Jul 20 01:37:34 2008
From: hwstar at rodgers.sdcoxmail.com (Stephen Rodgers)
Date: Sat, 19 Jul 2008 23:37:34 -0700
Subject: [App_rpt] USB Radio for MAC??
In-Reply-To: <14E217CF-24D7-4BE1-85A4-86336C5010FD@comcast.net>
References: <14E217CF-24D7-4BE1-85A4-86336C5010FD@comcast.net>
Message-ID: <4882DD2E.9010103@rodgers.sdcoxmail.com>

Josh,

Yes, they require the use of the ztdummy driver in Zaptel as a timing
source.

Steve Rodgers
WA6ZFT





Josh Roberson wrote:
> I was wondering if the usb radio drivers require zaptel (now known as  
> DAHDI) drivers/hardware or if the usb radio drivers can be used  
> standalone?  I run Apple equipment here, and I would love to tie my  
> asterisk server (running on my osx server) into my radio, but zaptel  
> is out of the question on this platform.
> 
> Any help is appreciated!
> 
> -Josh
> WX4JRR
> _______________________________________________
> App_rpt mailing list
> App_rpt at lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt
> 


From hwstar at rodgers.sdcoxmail.com  Sun Jul 20 01:41:24 2008
From: hwstar at rodgers.sdcoxmail.com (Stephen Rodgers)
Date: Sat, 19 Jul 2008 23:41:24 -0700
Subject: [App_rpt] URI configuration help
In-Reply-To: <20080720045454.BIDJ26203.dukecmmtai01.coxmail.com@dukecmimpi02.coxmail.com>
References: <20080720045454.BIDJ26203.dukecmmtai01.coxmail.com@dukecmimpi02.coxmail.com>
Message-ID: <4882DE14.5050505@rodgers.sdcoxmail.com>

Roger,

Jim WB6NIL does all pttlink registration work, at least for now.

Steve,
WA6ZFT



Roger F. Jordan Sr. wrote:
> Below are examples of MY SETUP as assisted by W9SH
> 
> I removed the Functions but notice the phone functions use two different
> function lists for Phonepatch... They are not included for security
> reasons...
> 
> I hope this helps!!!
> 
> Also Steve,  Did you get my apps for The GMRS, FRS and MURS and All the
> registrations for the different systems I applied for (or is that not you)
> 
> I would also like to talk to You guys about Phone patch control... 
> 
> Best Regards to ALL 
> 
> Roger W4RFJ
> 
> ; rpt.conf
> ; 20071103 0900 sphenke at xelatec.com
> 
> ; Radio Repeater / Remote Base config for use with app_rpt
> ; manipulated by the app_rpt installation script
> ; text strings that begin with xxx_ should be manually edited
> ; if the install script does not replace them.
> 
> [101]
> rxchannel = radio/usb
> duplex = 2
> functions = functions 		        ; DTMF function list
> link_functions = functions-linked	; DTMF function list for link
> phone_functions = functions-phone-1	; (optional) different functions for
> 'P' mode
> tonezone = us				; use US tones (default)
> context = from-internal		; dialing context for phone
> callerid = "de w4rfj/r"<445.95 pl100>  	; Callerid for phone calls
> idrecording=|ide w4rfj/r
> accountcode=RADIO			; account code (optional)
> funcchar = *				; function lead-in character
> (defaults to '*')
> endchar = #			        ; command mode end character
> (defaults to '#')
> hangtime=10			        ; squelch tail hang time (in ms)
> (optional)
> totime=180000				; transmit time-out time (in ms)
> (optional)
> idtime=600000				; id interval time (in ms)
> (optional)
> politeid=30000				; time in milliseconds before ID
> timer
> propagate_phonedtmf=yes	    	        ;propagate_phonedtmf = yes
> unlinkedct=ct1 		                ; DTMF sent to system from phone
> gets
> 				        ; repeated into main system output
> and
> 
> [102]
> rxchannel = radio/usb1
> duplex = 0
> functions = functions 		        ; DTMF function list
> link_functions = functions-linked	; DTMF function list for link
> phone_functions = functions-phone-1	;  different functions 
> tonezone = us			        ; use US tones (default)
> context = from-internal		        ; dialing context for phone
> callerid = "wqex329"<FRS Channel 1>  	; Callerid for phone calls
> idrecording=|iK
> accountcode=RADIO			; account code (optional)
> funcchar = *				; function lead-in character
> (defaults to '*')
> endchar = #				; command mode end character
> (defaults to '#')
> hangtime=3				; squelch tail hang time (in ms)
> (optional)
> totime=180000				; transmit time-out time (in ms)
> (optional)
> idtime=600000				; id interval time (in ms)
> (optional)
> politeid=30000				; time in milliseconds before ID
> timer
> propagate_phonedtmf=no
> 
> *************everything in between deals with DTMF Commands Etc...
> 
> 101 = radio at 192.168.14.149:4569/101,NONE
> 102 = radio at 192.168.14.149:4569/102,NONE
> 
> ; end of file - rpt.conf
> 
> ------------------------------------------------------------------------
> 
> ; usbradio.conf
> ; Configuration for chan_usbradio
> ; 20071205 0845 sphenke at xelatec.com
> ; refer to globals_rpt_custom.conf for variable definitions
> ;
> [general]
> 
> rxcpusaver=0
> txcpusaver=0
> 
> [usb]
> hwtype=0
> rxboost=1
> rxctcssrelax=0
> txctcssdefault=100.0
> rxctcssfreqs=100.0
> txctcssfreqs=100.0
> carrierfrom=dsp
> ctcssfrom=dsp
> rxdemod=flat
> txprelim=yes
> txtoctype=notone
> txmixa=composite
> txmixb=no
> invertptt=0
> ;rxfreq=445.950000
> ;txfreq=147.490000
> duplex=1
> eeprom=0
> 
> [usb1]
> hwtype=0
> rxboost=1
> rxctcssrelax=1
> ;txctcssdefault=0
> ;rxctcssfreq=0
> ;txctcssfreq=0
> carrierfrom=vox
> ctcssfrom=no
> rxdemod=speaker
> txprelim=no
> txtoctype=no; notone
> txmixa=voice
> txmixb=no
> invertptt=0
> ;rxfreq=462.562500
> ;txfreq=462.562500
> duplex=0
> eeprom=0
> 
> 
> 
> 
> -----Original Message-----
> From: app_rpt-bounces at lists.illiana.net
> [mailto:app_rpt-bounces at lists.illiana.net] On Behalf Of Stephen Rodgers
> Sent: Saturday, July 19, 2008 6:56 PM
> To: Asterisk Repeater Controler
> Subject: Re: [App_rpt] URI configuration help
> 
> David,
> 
> This is one area where our documentation falls short. We have got
> automated installs and config examples for single-node systems, but
> no examples for multi-node systems. Basically for each usb mode
> entries will need to be made in usbradio.conf, rpt.conf, and
> extensions.conf.
> 
> *** usbradio.conf ***
> 
> 
> [general]
> 
> ; Nothing in the general section for multiple devices.
> 
> [usb] ; first node
> ; Insert all USB config options from usbradio.conf.sample here except
> ; for devicenum setting. Modify settings to suit configuration.
> .
> .
> .
> devicenum=0 ; unique for each device defined
> .
> .
> .
> [usb1] ; second node
> .
> .
> .
> devicenum=1
> .
> .
> .
> 
> [usb2] ; third node
> .
> .
> .
> devicenum=2
> .
> .
> .
> 
> *** extensions.conf ****
> 
> exten => 1234,1,rpt,1234 # first node
> exten => 5678,1,rpt,5678 # second node
> exten => 9012,1,rpt,9012 # third node
> 
> 
> **** rpt.conf ****
> 
> rpt.conf
> 
> [1234] ; first node
> rxchannel = Radio/usb
> ; Configuration settings from rpt.conf.sample tailored to your
> application follow the channel definition above.
> .
> .
> .
> [5678] ; second node
> rxchannel = Radio/usb1
> ; Configuration settings from rpt.conf.sample tailored to your
> application follow the channel definition above.
> .
> .
> .
> [9012] ; third node
> rxchannel = Radio/usb2
> ; Configuration settings from rpt.conf.sample tailored to your
> application follow the channel definition above.
> .
> .
> .
> 
> 
> Standard disclaimer boilerplate: I tried to answer your question. I
> haven't tested what is documented above. I just did some quick research
> to come up with this answer, and the research was not in-depth, There
> may very well be something I left out, so your mileage may vary. There
> are no guarantees. If you find something and fix it, please post it back
> to the list so everyone will benefit from it.
> 
> 
> Steve
> WA6ZFT
> 
> 
> 
> David McGough wrote:
>> Hi Everyone,
>>
>> I'm finally getting to "finish up" my URI based project and wondered if
>> someone could help point me to some advanced sample asterisk/app_rpt
>> config files (usbradio.conf, rpt.conf, primarily) for using the URI
>> adapters.
>>
>> I've currently got 1 URI working properly with my TKR-850 repeater. Now, I
>> want to add 2 remote base radios for VHF and HF, do some linking, etc. I, 
>> mainly need more info about the syntax to use with multiple URI's, 
>> usbradio.conf options, etc.
>>
>> Thanks in advance!
>>
>> David KB4FXC
>>
>>
>>
>> _______________________________________________
>> App_rpt mailing list
>> App_rpt at lists.illiana.net
>> http://lists.illiana.net/mailman/listinfo/app_rpt
>>
> 
> _______________________________________________
> App_rpt mailing list
> App_rpt at lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt
> 
> _______________________________________________
> App_rpt mailing list
> App_rpt at lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt
> 


From w4rfj at comcast.net  Sun Jul 20 15:22:54 2008
From: w4rfj at comcast.net (Roger F. Jordan Sr.)
Date: Sun, 20 Jul 2008 16:22:54 -0400
Subject: [App_rpt] URI configuration help
In-Reply-To: <4882DE14.5050505@rodgers.sdcoxmail.com>
Message-ID: <mailman.1.1216585280.2537.app_rpt@lists.illiana.net>

Thanks Steve,

Jim Dude,  Did you get my applications??

Best Regards,
Roger W4RFJ

-----Original Message-----
From: app_rpt-bounces at lists.illiana.net
[mailto:app_rpt-bounces at lists.illiana.net] On Behalf Of Stephen Rodgers
Sent: Sunday, July 20, 2008 2:41 AM
To: Asterisk Repeater Controler
Subject: Re: [App_rpt] URI configuration help

Roger,

Jim WB6NIL does all pttlink registration work, at least for now.

Steve,
WA6ZFT



Roger F. Jordan Sr. wrote:
> Below are examples of MY SETUP as assisted by W9SH
> 
> I removed the Functions but notice the phone functions use two different
> function lists for Phonepatch... They are not included for security
> reasons...
> 
> I hope this helps!!!
> 
> Also Steve,  Did you get my apps for The GMRS, FRS and MURS and All the
> registrations for the different systems I applied for (or is that not you)
> 
> I would also like to talk to You guys about Phone patch control... 
> 
> Best Regards to ALL 
> 
> Roger W4RFJ
> 
> ; rpt.conf
> ; 20071103 0900 sphenke at xelatec.com
> 
> ; Radio Repeater / Remote Base config for use with app_rpt
> ; manipulated by the app_rpt installation script
> ; text strings that begin with xxx_ should be manually edited
> ; if the install script does not replace them.
> 
> [101]
> rxchannel = radio/usb
> duplex = 2
> functions = functions 		        ; DTMF function list
> link_functions = functions-linked	; DTMF function list for link
> phone_functions = functions-phone-1	; (optional) different functions for
> 'P' mode
> tonezone = us				; use US tones (default)
> context = from-internal		; dialing context for phone
> callerid = "de w4rfj/r"<445.95 pl100>  	; Callerid for phone calls
> idrecording=|ide w4rfj/r
> accountcode=RADIO			; account code (optional)
> funcchar = *				; function lead-in character
> (defaults to '*')
> endchar = #			        ; command mode end character
> (defaults to '#')
> hangtime=10			        ; squelch tail hang time (in ms)
> (optional)
> totime=180000				; transmit time-out time (in ms)
> (optional)
> idtime=600000				; id interval time (in ms)
> (optional)
> politeid=30000				; time in milliseconds
before ID
> timer
> propagate_phonedtmf=yes	    	        ;propagate_phonedtmf = yes
> unlinkedct=ct1 		                ; DTMF sent to system from
phone
> gets
> 				        ; repeated into main system output
> and
> 
> [102]
> rxchannel = radio/usb1
> duplex = 0
> functions = functions 		        ; DTMF function list
> link_functions = functions-linked	; DTMF function list for link
> phone_functions = functions-phone-1	;  different functions 
> tonezone = us			        ; use US tones (default)
> context = from-internal		        ; dialing context for phone
> callerid = "wqex329"<FRS Channel 1>  	; Callerid for phone calls
> idrecording=|iK
> accountcode=RADIO			; account code (optional)
> funcchar = *				; function lead-in character
> (defaults to '*')
> endchar = #				; command mode end character
> (defaults to '#')
> hangtime=3				; squelch tail hang time (in ms)
> (optional)
> totime=180000				; transmit time-out time (in ms)
> (optional)
> idtime=600000				; id interval time (in ms)
> (optional)
> politeid=30000				; time in milliseconds
before ID
> timer
> propagate_phonedtmf=no
> 
> *************everything in between deals with DTMF Commands Etc...
> 
> 101 = radio at 192.168.14.149:4569/101,NONE
> 102 = radio at 192.168.14.149:4569/102,NONE
> 
> ; end of file - rpt.conf
> 
> ------------------------------------------------------------------------
> 
> ; usbradio.conf
> ; Configuration for chan_usbradio
> ; 20071205 0845 sphenke at xelatec.com
> ; refer to globals_rpt_custom.conf for variable definitions
> ;
> [general]
> 
> rxcpusaver=0
> txcpusaver=0
> 
> [usb]
> hwtype=0
> rxboost=1
> rxctcssrelax=0
> txctcssdefault=100.0
> rxctcssfreqs=100.0
> txctcssfreqs=100.0
> carrierfrom=dsp
> ctcssfrom=dsp
> rxdemod=flat
> txprelim=yes
> txtoctype=notone
> txmixa=composite
> txmixb=no
> invertptt=0
> ;rxfreq=445.950000
> ;txfreq=147.490000
> duplex=1
> eeprom=0
> 
> [usb1]
> hwtype=0
> rxboost=1
> rxctcssrelax=1
> ;txctcssdefault=0
> ;rxctcssfreq=0
> ;txctcssfreq=0
> carrierfrom=vox
> ctcssfrom=no
> rxdemod=speaker
> txprelim=no
> txtoctype=no; notone
> txmixa=voice
> txmixb=no
> invertptt=0
> ;rxfreq=462.562500
> ;txfreq=462.562500
> duplex=0
> eeprom=0
> 
> 
> 
> 
> -----Original Message-----
> From: app_rpt-bounces at lists.illiana.net
> [mailto:app_rpt-bounces at lists.illiana.net] On Behalf Of Stephen Rodgers
> Sent: Saturday, July 19, 2008 6:56 PM
> To: Asterisk Repeater Controler
> Subject: Re: [App_rpt] URI configuration help
> 
> David,
> 
> This is one area where our documentation falls short. We have got
> automated installs and config examples for single-node systems, but
> no examples for multi-node systems. Basically for each usb mode
> entries will need to be made in usbradio.conf, rpt.conf, and
> extensions.conf.
> 
> *** usbradio.conf ***
> 
> 
> [general]
> 
> ; Nothing in the general section for multiple devices.
> 
> [usb] ; first node
> ; Insert all USB config options from usbradio.conf.sample here except
> ; for devicenum setting. Modify settings to suit configuration.
> .
> .
> .
> devicenum=0 ; unique for each device defined
> .
> .
> .
> [usb1] ; second node
> .
> .
> .
> devicenum=1
> .
> .
> .
> 
> [usb2] ; third node
> .
> .
> .
> devicenum=2
> .
> .
> .
> 
> *** extensions.conf ****
> 
> exten => 1234,1,rpt,1234 # first node
> exten => 5678,1,rpt,5678 # second node
> exten => 9012,1,rpt,9012 # third node
> 
> 
> **** rpt.conf ****
> 
> rpt.conf
> 
> [1234] ; first node
> rxchannel = Radio/usb
> ; Configuration settings from rpt.conf.sample tailored to your
> application follow the channel definition above.
> .
> .
> .
> [5678] ; second node
> rxchannel = Radio/usb1
> ; Configuration settings from rpt.conf.sample tailored to your
> application follow the channel definition above.
> .
> .
> .
> [9012] ; third node
> rxchannel = Radio/usb2
> ; Configuration settings from rpt.conf.sample tailored to your
> application follow the channel definition above.
> .
> .
> .
> 
> 
> Standard disclaimer boilerplate: I tried to answer your question. I
> haven't tested what is documented above. I just did some quick research
> to come up with this answer, and the research was not in-depth, There
> may very well be something I left out, so your mileage may vary. There
> are no guarantees. If you find something and fix it, please post it back
> to the list so everyone will benefit from it.
> 
> 
> Steve
> WA6ZFT
> 
> 
> 
> David McGough wrote:
>> Hi Everyone,
>>
>> I'm finally getting to "finish up" my URI based project and wondered if
>> someone could help point me to some advanced sample asterisk/app_rpt
>> config files (usbradio.conf, rpt.conf, primarily) for using the URI
>> adapters.
>>
>> I've currently got 1 URI working properly with my TKR-850 repeater. Now,
I
>> want to add 2 remote base radios for VHF and HF, do some linking, etc. I,

>> mainly need more info about the syntax to use with multiple URI's, 
>> usbradio.conf options, etc.
>>
>> Thanks in advance!
>>
>> David KB4FXC
>>
>>
>>
>> _______________________________________________
>> App_rpt mailing list
>> App_rpt at lists.illiana.net
>> http://lists.illiana.net/mailman/listinfo/app_rpt
>>
> 
> _______________________________________________
> App_rpt mailing list
> App_rpt at lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt
> 
> _______________________________________________
> App_rpt mailing list
> App_rpt at lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt
> 

_______________________________________________
App_rpt mailing list
App_rpt at lists.illiana.net
http://lists.illiana.net/mailman/listinfo/app_rpt


From kb4fxc at inttek.net  Sun Jul 20 15:30:27 2008
From: kb4fxc at inttek.net (David McGough)
Date: Sun, 20 Jul 2008 16:30:27 -0400 (EDT)
Subject: [App_rpt] URI configuration help
In-Reply-To: <20080720045447.2543A263119@goliath.inttek.net>
Message-ID: <Pine.LNX.4.44.0807201620480.8722-100000@goliath.inttek.net>


Hi Steve and Roger,

Thanks so much for the assistance. I'll give it a try today and report 
back. I think most of my questions are now answered.

One thing I've noticed--it's not a big deal, and easily enough to overcome
by just using a sampled sound file--is that the CW ID timing generation
seems a little random. Has anyone else noticed this? I suspect this may be
an artifact of my Linux kernel and/or hardware config...I'm using the
easyvoxbox distro base, with hand compiled new versions of asterisk,
app_rpt and supporting tools. BTW, I'm using an Dual-core AMD64 4400+ CPU
and 3ware Raid 1....I'll investigate this more later-

Thanks again!

David KB4FXC




On Sun, 20 Jul 2008, Roger F. Jordan Sr. wrote:

> Below are examples of MY SETUP as assisted by W9SH
> 
> I removed the Functions but notice the phone functions use two different
> function lists for Phonepatch... They are not included for security
> reasons...
> 

<snip>


From josh.roberson at comcast.net  Sun Jul 20 15:38:47 2008
From: josh.roberson at comcast.net (Josh Roberson)
Date: Sun, 20 Jul 2008 15:38:47 -0500
Subject: [App_rpt] USB Radio for MAC??
In-Reply-To: <4882DD2E.9010103@rodgers.sdcoxmail.com>
References: <14E217CF-24D7-4BE1-85A4-86336C5010FD@comcast.net>
	<4882DD2E.9010103@rodgers.sdcoxmail.com>
Message-ID: <D9BB438B-5E1A-4370-8CEF-4B6C10A50411@comcast.net>

 From a quick glance at the code, I don't seen any direct link to  
zaptel, which means I *SHOULD* be able to modify this code to work  
under OS X using CoreAudio for audio control.

Since the underlying system on OS X is Darwin (a derivative of BSD),  
and there is already BSD support in chan_usbradio.c, I think this  
could work.  I already use meetme/etc on my os x server without issues  
in timing, and I don't see any timer specific code in the  
chan_usbradio driver..

If app_rpt requires zaptel to be involved, perhaps I can find a way to  
fix that as well, and open up the os x world to this wonderful  
utility.   I'll keep you all updated...also, Steve, not trying to be  
argumentative, just making a note :)


On Jul 20, 2008, at 1:37 AM, Stephen Rodgers wrote:

> Josh,
>
> Yes, they require the use of the ztdummy driver in Zaptel as a timing
> source.
>
> Steve Rodgers
> WA6ZFT
>
>
>
>
>
> Josh Roberson wrote:
>> I was wondering if the usb radio drivers require zaptel (now known as
>> DAHDI) drivers/hardware or if the usb radio drivers can be used
>> standalone?  I run Apple equipment here, and I would love to tie my
>> asterisk server (running on my osx server) into my radio, but zaptel
>> is out of the question on this platform.
>>
>> Any help is appreciated!
>>
>> -Josh
>> WX4JRR
>> _______________________________________________
>> App_rpt mailing list
>> App_rpt at lists.illiana.net
>> http://lists.illiana.net/mailman/listinfo/app_rpt
>>
>
> _______________________________________________
> App_rpt mailing list
> App_rpt at lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt


From hwstar at rodgers.sdcoxmail.com  Sun Jul 20 16:10:52 2008
From: hwstar at rodgers.sdcoxmail.com (Stephen Rodgers)
Date: Sun, 20 Jul 2008 14:10:52 -0700
Subject: [App_rpt] URI configuration help
In-Reply-To: <Pine.LNX.4.44.0807201620480.8722-100000@goliath.inttek.net>
References: <Pine.LNX.4.44.0807201620480.8722-100000@goliath.inttek.net>
Message-ID: <4883A9DC.1000004@rodgers.sdcoxmail.com>


We are painfully aware of this problem. The ID will suddenly shift speed
right in the middle of identifying. It is on the list to be
investigated. We think it is either a change to something in the kernel,
or core asterisk, but we don't know for sure which yet.

Steve
WA6ZFT



David McGough wrote:
> Hi Steve and Roger,
> 
> Thanks so much for the assistance. I'll give it a try today and report 
> back. I think most of my questions are now answered.
> 
> One thing I've noticed--it's not a big deal, and easily enough to overcome
> by just using a sampled sound file--is that the CW ID timing generation
> seems a little random. Has anyone else noticed this? I suspect this may be
> an artifact of my Linux kernel and/or hardware config...I'm using the
> easyvoxbox distro base, with hand compiled new versions of asterisk,
> app_rpt and supporting tools. BTW, I'm using an Dual-core AMD64 4400+ CPU
> and 3ware Raid 1....I'll investigate this more later-
> 
> Thanks again!
> 
> David KB4FXC
> 
> 
> 
> 
> On Sun, 20 Jul 2008, Roger F. Jordan Sr. wrote:
> 
>> Below are examples of MY SETUP as assisted by W9SH
>>
>> I removed the Functions but notice the phone functions use two different
>> function lists for Phonepatch... They are not included for security
>> reasons...
>>
> 
> <snip>
> 
> _______________________________________________
> App_rpt mailing list
> App_rpt at lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt
> 


From hwstar at rodgers.sdcoxmail.com  Sun Jul 20 16:17:45 2008
From: hwstar at rodgers.sdcoxmail.com (Stephen Rodgers)
Date: Sun, 20 Jul 2008 14:17:45 -0700
Subject: [App_rpt] USB Radio for MAC??
In-Reply-To: <D9BB438B-5E1A-4370-8CEF-4B6C10A50411@comcast.net>
References: <14E217CF-24D7-4BE1-85A4-86336C5010FD@comcast.net>	<4882DD2E.9010103@rodgers.sdcoxmail.com>
	<D9BB438B-5E1A-4370-8CEF-4B6C10A50411@comcast.net>
Message-ID: <4883AB79.3080107@rodgers.sdcoxmail.com>

Josh,


Zap pseudo channels and conferences are indeed used in app_rpt:


>         /* allocate a pseudo-channel thru asterisk */
>         myrpt->pchannel = ast_request("zap",AST_FORMAT_SLINEAR,"pseudo",NULL);
>         if (!myrpt->pchannel)
>         {
>                 fprintf(stderr,"rpt:Sorry unable to obtain pseudo channel\n");
>                 rpt_mutex_unlock(&myrpt->lock);                if (myrpt->txchannel != myrpt->rxchannel)
>                         ast_hangup(myrpt->txchannel);
>                 ast_hangup(myrpt->rxchannel);
>                 myrpt->rpt_thread = AST_PTHREADT_STOP;
>                 pthread_exit(NULL);
>         



App_rpt uses zaptel conferences and pseudo channels which rely on
ztdummy as a timing source. The whole app_rpt application would have to
be rewritten to not use zaptel conferences, and new kernel driver
outside of zaptel would be required to time the transmfer of the bytes
within the conference.


Steve
WA6ZFT


Josh Roberson wrote:
>  From a quick glance at the code, I don't seen any direct link to  
> zaptel, which means I *SHOULD* be able to modify this code to work  
> under OS X using CoreAudio for audio control.
> 
> Since the underlying system on OS X is Darwin (a derivative of BSD),  
> and there is already BSD support in chan_usbradio.c, I think this  
> could work.  I already use meetme/etc on my os x server without issues  
> in timing, and I don't see any timer specific code in the  
> chan_usbradio driver..
> 
> If app_rpt requires zaptel to be involved, perhaps I can find a way to  
> fix that as well, and open up the os x world to this wonderful  
> utility.   I'll keep you all updated...also, Steve, not trying to be  
> argumentative, just making a note :)
> 
> 
> On Jul 20, 2008, at 1:37 AM, Stephen Rodgers wrote:
> 
>> Josh,
>>
>> Yes, they require the use of the ztdummy driver in Zaptel as a timing
>> source.
>>
>> Steve Rodgers
>> WA6ZFT
>>
>>
>>
>>
>>
>> Josh Roberson wrote:
>>> I was wondering if the usb radio drivers require zaptel (now known as
>>> DAHDI) drivers/hardware or if the usb radio drivers can be used
>>> standalone?  I run Apple equipment here, and I would love to tie my
>>> asterisk server (running on my osx server) into my radio, but zaptel
>>> is out of the question on this platform.
>>>
>>> Any help is appreciated!
>>>
>>> -Josh
>>> WX4JRR
>>> _______________________________________________
>>> App_rpt mailing list
>>> App_rpt at lists.illiana.net
>>> http://lists.illiana.net/mailman/listinfo/app_rpt
>>>
>> _______________________________________________
>> App_rpt mailing list
>> App_rpt at lists.illiana.net
>> http://lists.illiana.net/mailman/listinfo/app_rpt
> 
> _______________________________________________
> App_rpt mailing list
> App_rpt at lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt
> 


From n9yty at n9yty.com  Sun Jul 20 16:28:34 2008
From: n9yty at n9yty.com (Steven Palm)
Date: Sun, 20 Jul 2008 16:28:34 -0500
Subject: [App_rpt] USB Radio for MAC??
In-Reply-To: <14E217CF-24D7-4BE1-85A4-86336C5010FD@comcast.net>
References: <14E217CF-24D7-4BE1-85A4-86336C5010FD@comcast.net>
Message-ID: <A268EE57-C71C-4C27-B7AC-54566A5FD988@n9yty.com>


On Jul 20, 2008, at 12:08 AM, Josh Roberson wrote:
> I was wondering if the usb radio drivers require zaptel (now known as
> DAHDI) drivers/hardware or if the usb radio drivers can be used
> standalone?  I run Apple equipment here, and I would love to tie my
> asterisk server (running on my osx server) into my radio, but zaptel
> is out of the question on this platform.

  The other issue is that the USB keyfob uses ALSA for it's sound,
so you'd have to port it to CoreAudio or use a library like portaudio.

  Steve

From kb4fxc at inttek.net  Mon Jul 21 00:08:11 2008
From: kb4fxc at inttek.net (David McGough)
Date: Mon, 21 Jul 2008 01:08:11 -0400 (EDT)
Subject: [App_rpt] URI configuration help
In-Reply-To: <Pine.LNX.4.44.0807201620480.8722-100000@goliath.inttek.net>
Message-ID: <Pine.LNX.4.44.0807210051270.27459-100000@goliath.inttek.net>



Hi Roger & Steve,

Well, I'm making progress. I've noticed a couple more things I thought I'd
mention. First, I've got a strange situation where I can only properly
access 2 of the 3 URI's I have attached to the PC....Initially, I only
plugged 1 URI in and couldn't get it to work at all (though the green LED
was blinking)....Then, when I plugged in a 2nd URI, the first started
working (with my TKR-850)....Today, I found that the second wasn't
functional....So, tonight, experimentally, I plugged in a 3rd URI and
both of the original 2 are now working. Strange.....Perhaps this has
something to do with udev? Anyway, this isn't holding me up at the moment.

The second issue is more troublesome. I can't get the repeater to link to
the remote base....When I issue the connect command: *2(node number), the
controller says it's linking both on the console and verbally. But, then
it seems to hang totally with the TX enabled from the end that received
the commands. I've tried this both ways--repeater to remote base (commands
from the repeater) and vice versa. I end up having to kill -9 the asterisk
process to regain control--"stop now" from the asterisk console
hangs...This should work, right?

Thanks in advance!

David KB4FXC


On Sun, 20 Jul 2008, David McGough wrote:

> 
> Hi Steve and Roger,
> 
> Thanks so much for the assistance. I'll give it a try today and report 
> back. I think most of my questions are now answered.
> 
> <snip>
> 
> 


From kb4fxc at inttek.net  Mon Jul 21 00:12:28 2008
From: kb4fxc at inttek.net (David McGough)
Date: Mon, 21 Jul 2008 01:12:28 -0400 (EDT)
Subject: [App_rpt] URI configuration help
In-Reply-To: <Pine.LNX.4.44.0807210051270.27459-100000@goliath.inttek.net>
Message-ID: <Pine.LNX.4.44.0807210110060.28807-100000@goliath.inttek.net>


Oops....In my previous message I meant to say I'm using the command:
*3(node number) to connect....See the functions table I'm using, below.

73, David KB4FXC

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

; function table
;
[functions]
1=ilink,1                               ; Specific link disconnect
2=ilink,2                               ; Specific Link connect -  monitor only
3=ilink,3                               ; Specific Link connect - transceive
4=ilink,4                               ; Enter command mode on a specific link
7=ilink,5                               ; Link status
                                                                                                                                                           
80=status,1                             ; System info
81=status,2                             ; Time
82=status,3                             ; app_rpt.c Version
87=ilink,15                             ; long range sensors
                                                                                                                                                           
;6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up
;0=autopatchdn                          ; Autopatch down
                                                                                                                                                           
99=cop,4                                ; Test tone
98=cop,6                                ; Phone TX key




From hwstar at rodgers.sdcoxmail.com  Mon Jul 21 20:50:34 2008
From: hwstar at rodgers.sdcoxmail.com (Stephen Rodgers)
Date: Mon, 21 Jul 2008 18:50:34 -0700
Subject: [App_rpt] URI configuration help
In-Reply-To: <Pine.LNX.4.44.0807210051270.27459-100000@goliath.inttek.net>
References: <Pine.LNX.4.44.0807210051270.27459-100000@goliath.inttek.net>
Message-ID: <48853CEA.6060605@rodgers.sdcoxmail.com>

David,

First off, I just learned something myself about adding extra radio
ports using USB fobs: They must be added one at a time.

Second, there should be no USB hubs between the FOB's and the PC's USB
ports.

Finally, what type if linux install is this? ACID, EVB, custom?


I'd suggest restoring the configuration back to one radio port get that
working, then add and tune the ports one at a time.


Steve,
WA6ZFT




David McGough wrote:
> 
> Hi Roger & Steve,
> 
> Well, I'm making progress. I've noticed a couple more things I thought I'd
> mention. First, I've got a strange situation where I can only properly
> access 2 of the 3 URI's I have attached to the PC....Initially, I only
> plugged 1 URI in and couldn't get it to work at all (though the green LED
> was blinking)....Then, when I plugged in a 2nd URI, the first started
> working (with my TKR-850)....Today, I found that the second wasn't
> functional....So, tonight, experimentally, I plugged in a 3rd URI and
> both of the original 2 are now working. Strange.....Perhaps this has
> something to do with udev? Anyway, this isn't holding me up at the moment.
> 
> The second issue is more troublesome. I can't get the repeater to link to
> the remote base....When I issue the connect command: *2(node number), the
> controller says it's linking both on the console and verbally. But, then
> it seems to hang totally with the TX enabled from the end that received
> the commands. I've tried this both ways--repeater to remote base (commands
> from the repeater) and vice versa. I end up having to kill -9 the asterisk
> process to regain control--"stop now" from the asterisk console
> hangs...This should work, right?
> 
> Thanks in advance!
> 
> David KB4FXC
> 
> 
> On Sun, 20 Jul 2008, David McGough wrote:
> 
>> Hi Steve and Roger,
>>
>> Thanks so much for the assistance. I'll give it a try today and report 
>> back. I think most of my questions are now answered.
>>
>> <snip>
>>
>>
> 
> _______________________________________________
> App_rpt mailing list
> App_rpt at lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt
> 


From kb4fxc at inttek.net  Mon Jul 21 21:14:19 2008
From: kb4fxc at inttek.net (David McGough)
Date: Mon, 21 Jul 2008 22:14:19 -0400 (EDT)
Subject: [App_rpt] URI configuration help
In-Reply-To: <48853CEA.6060605@rodgers.sdcoxmail.com>
Message-ID: <Pine.LNX.4.44.0807212152550.17923-100000@goliath.inttek.net>


Hi Steve,

I am running a EVB base system--centos 5 and 2.6.18-53.1.21.el5 kernel. I
updated asterisk to a hand-compiled version (1.4.21) using the latest
app_rpt and chan_usb code from Xelatek's SVN....Maybe I'll back down to 
the ACID release.

The URI's are plugged directly into the PC, and 2 of the 3 seem to be
working fine--other than I can't connect the extensions together. The
TKR-850 (set internally in duplex mode and is asterisk extension 111)  
works as a repeater, and accepts DTMF commands, etc....And, the remote
base (currently a IC-706mk2g, extension 222) also accepts DTMF commands,
etc....But, when I try to connect these units (using *3<node>), I get a
lock up....

I reduced my extensions.conf file to the below for testing:

---------------extensions.conf---------------------------------------
[general]
 
static=yes       ; These two lines prevent the command-line interface
writeprotect=yes ; from overwriting the config file. Leave them here.
 
[radio-secure]
exten => 111,1,rpt,111
exten => 222,1,rpt,222
 
[autopatch]
---------------------------------------------------------------------

And, here is my rpt.conf:
---------------rpt.conf---------------------------------------------
; Radio Repeater configuration file (for use with app_rpt)
;
 
 
[111]                           ; Change this to your assigned node number
 
rxchannel = Radio/usb                   ; Rx audio/signalling channel
controlstates=controlstates             ; system control state list
scheduler=schedule;                     ; scheduler entries
functions=functions                     ; Repeater Function Table
phone_functions=functions               ; Repeater Function Table
link_functions=link-functions           ; Link Function Table
telemetry=telemetry                     ; Telemetry descriptions
wait_times=wait-times                   ; Wait times
context = autopatch                     ; dialing context for phone
callerid = "Repeater" <0000000000> ; callerid for phone calls
;idrecording = |iid                     ; id recording or morse string
idrecording=|ikb4fxc/r                  ; id recording or morse string
accountcode=RADIO                       ; account code (optional)
hangtime=1000                           ; squelch tail hang time (in ms) 
(optional)
althangtime=4000                        ; longer squelch tail
totime=170000                           ; transmit time-out time (in ms) 
(optional)
totime=10000
idtime=540000                           ; id interval time (in ms) 
(optional)
; The default values for hangtime, time-out time, and id interval time are
; 5 seconds (5000 ms),  3 minutes (180000 ms), and 5 minutes (300000 ms)
; respectively
 
politeid=30000                          ; time in milliseconds before ID 
timer
 
                                        ; expires to try and ID in the 
tail.
                                        ; (optional, default is 30000).
idtalkover=|iid                         ; Talkover ID (optional) default 
is none
unlinkedct=ct2                          ; unlinked courtesy tone 
(optional) default is none
remotect=ct3
duplex=2
 
;////////////////////////////////////////////////////////////////////////////
[222]                           ; Change this to your assigned node number
 
rxchannel = Radio/usb1                  ; Rx audio/signalling channel
controlstates=controlstates             ; system control state list
scheduler=schedule;                     ; scheduler entries
functions=functions                     ; Repeater Function Table
phone_functions=functions               ; Repeater Function Table
link_functions=link-functions           ; Link Function Table
telemetry=telemetry                     ; Telemetry descriptions
wait_times=wait-times                   ; Wait times
context = autopatch                     ; dialing context for phone
callerid = "Repeater" <0000000000> ; callerid for phone calls
idrecording = |iid                      ; id recording or morse string
;idrecording=|ikb4fxc                   ; id recording or morse string
accountcode=RADIO                       ; account code (optional)
hangtime=1000                           ; squelch tail hang time (in ms) 
(optional)
althangtime=4000                        ; longer squelch tail
totime=170000                           ; transmit time-out time (in ms) 
(optional)
totime=10000
idtime=540000                           ; id interval time (in ms) 
(optional)
; The default values for hangtime, time-out time, and id interval time are
; 5 seconds (5000 ms),  3 minutes (180000 ms), and 5 minutes (300000 ms)
; respectively
 
politeid=30000                          ; time in milliseconds before ID timer
 
                                        ; expires to try and ID in the tail.
                                        ; (optional, default is 30000).
idtalkover=|iid                         ; Talkover ID (optional) default is none
unlinkedct=ct2                          ; unlinked courtesy tone (optional) default is none
remotect=ct3
duplex=0
 

;///////////////////////////////////////////////////////////////////////////////////////
;
; function table
;
[functions]
1=ilink,1                               ; Specific link disconnect
2=ilink,2                               ; Specific Link connect -  monitor 
only
3=ilink,3                               ; Specific Link connect - transceive
4=ilink,4                               ; Enter command mode on a specific link
7=ilink,5                               ; Link status
 
80=status,1                             ; System info
81=status,2                             ; Time
82=status,3                             ; app_rpt.c Version
87=ilink,15                             ; long range sensors
 
;6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up
;0=autopatchdn                          ; Autopatch down
 
99=cop,4                                ; Test tone
98=cop,6                                ; Phone TX key
 
 
;///////////////////////////////////////////////////////////////////////////////////////
;
; Link function table
;
; If this section is defined, then the remote user accessing our machine 
in command mode
; will only be able to do the functions defined in this section. If this 
section is
; omitted, then the link functions will be the same as the repeater 
functions.
;
 
 
[link-functions]
1=ilink,1                               ; Specific link disconnect
2=ilink,2                               ; Specific Link connect -  monitor 
only
3=ilink,3                               ; Specific Link connect - 
transceive
4=ilink,4                               ; Command mode
80=status,1                             ; System info
81=status,2                             ; Time
82=status,3                             ; app_rpt.c Version
87=ilink,15                             ; long range sensors
                                                                                                               
;6=autopatchup,farenddisconnect=1,noct=1,dialtime=20000 ; Autopatch up
;0=autopatchdn                           ; Autopatch down
 
99=cop,4                                ; Test tone
 
[telemetry]
 
; Telemetry entries can be shared across all repeaters, or defined for 
each repeater.
; Can be a tone sequence, morse string, or a file
;
; |t - Tone escape sequence
;
; Tone sequences consist of 1 or more 4-tuple entries (freq1, freq2, 
duration, amplitude)
; Single frequencies are created by setting freq1 or freq2 to zero.
;
; |m - Morse escape sequence
;
; Sends Morse code at the telemetry amplitude and telemetry frequency as 
defined in the
; [morse] section.
;
; Follow with an alphanumeric string
;
; |i - Morse ID escape sequence
;
; Sends Morse code at the ID amplitude and ID frequency as defined in the
; [morse] section.
;
; Follow with an alphanumeric string
 
 
ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048)
ct2=|t(660,880,150,2048)
ct3=|t(440,0,150,4096)
ct4=|t(550,0,150,2048)
ct5=|t(660,0,150,2048)
ct6=|t(880,0,150,2048)
ct7=|t(660,440,150,2048)
ct8=|t(700,1100,150,2048)
remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000);
remotemon=|t(1209,0,50,2048)
cmdmode=|t(900,903,200,2048)
functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048)
patchup=rpt/callproceeding
patchdown=rpt/callterminated
;idstr=|m('K','B','4','F','X','C')
 
;
; Morse code parameters, these are common to all repeaters.
;
 
[morse]
 
speed=13                ; Approximate speed in WPM
frequency=800           ; Morse Telemetry Frequency
amplitude=4096          ; Morse Telemetry Amplitude
idfrequency=1065        ; Morse ID Frequency
idamplitude=1024        ; Morse ID Amplitude
 
;
; This section allows wait times for telemetry events to be adjusted
; A section for wait times can be defined for every repeater
;
 
[wait-times]
telemwait=2000                          ; Time to wait before sending most telemetry
idwait=500                              ; Time to wait before starting ID
unkeywait=2000                          ; Time to wait after unkey before sending CT's and link telemetry
calltermwait=2000                       ; Time to wait before announcing "call terminated"
 
;
; This is where you define your nodes which can be connected to.
;
 
[nodes]
111 = radio at 127.0.0.1/111,NONE  ; Change this to your assigned node number
222 = radio at 127.0.0.1/222,NONE  ; Change this to your assigned node number
 
-------------------------------------------------------------------------------- 

Finally, here is the usbradio.conf:
------------------------------------------------------------------------
;
; Open Sound System Console Driver Configuration File
;
[general]
 
rxcpusaver=0
txcpusaver=0
debug=0x7
 
[usb]
; TKR-850
devicenum=0
 
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=0               ; 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=0.0      ; default tx ctcss freq, any frequency permitted
rxctcssfreqs=0.0        ; rx ctcss freqs in floating point. must be in 
table
txctcssfreqs=0.0        ; tx ctcss freqs, any frequency permitted
 
carrierfrom=usbinvert           ; 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
                        ; 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
 
txtoctype=notone        ; 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=1                ; Full Duplex
 
 
[usb1]
; IC-706mk2g 
devicenum=1
hdwtype=0
rxboost=0
rxctcssrelax=1
txctcssdefault=0.0
rxctcssfreqs=0.0
txctcssfreqs=0.0
carrierfrom=usbinvert   ; no,usb,usbinvert,dsp,vox
ctcssfrom=no            ; no,usb,dsp
rxdemod=speaker         ; input type from radio: no,speaker,flat
txprelim=no             ; Audio processing on left output channel: no,yes
txtoctype=notone        ; Transmit tone control type: no,phase,notone
txmixa=voice            ; Left channel output: 
no,voice,tone,composite,auxvoice
txmixb=no               ; Right channel output: no,voice,tone,composite, 
auxvoice
invertptt=0             ; Invert PTT 0 = ground to transmit, 1 = open to 
transmit
duplex=0                ; Simplex







On Mon, 21 Jul 2008, Stephen Rodgers wrote:

> David,
> 
> First off, I just learned something myself about adding extra radio
> ports using USB fobs: They must be added one at a time.
> 
> Second, there should be no USB hubs between the FOB's and the PC's USB
> ports.
> 
> Finally, what type if linux install is this? ACID, EVB, custom?
> 
> 
> I'd suggest restoring the configuration back to one radio port get that
> working, then add and tune the ports one at a time.
> 
> 
> Steve,
> WA6ZFT
> 
> 
> 
> 
> David McGough wrote:
> > 
> > Hi Roger & Steve,
> > 
> > Well, I'm making progress. I've noticed a couple more things I thought I'd
> > mention. First, I've got a strange situation where I can only properly
> > access 2 of the 3 URI's I have attached to the PC....Initially, I only
> > plugged 1 URI in and couldn't get it to work at all (though the green LED
> > was blinking)....Then, when I plugged in a 2nd URI, the first started
> > working (with my TKR-850)....Today, I found that the second wasn't
> > functional....So, tonight, experimentally, I plugged in a 3rd URI and
> > both of the original 2 are now working. Strange.....Perhaps this has
> > something to do with udev? Anyway, this isn't holding me up at the moment.
> > 
> > The second issue is more troublesome. I can't get the repeater to link to
> > the remote base....When I issue the connect command: *2(node number), the
> > controller says it's linking both on the console and verbally. But, then
> > it seems to hang totally with the TX enabled from the end that received
> > the commands. I've tried this both ways--repeater to remote base (commands
> > from the repeater) and vice versa. I end up having to kill -9 the asterisk
> > process to regain control--"stop now" from the asterisk console
> > hangs...This should work, right?
> > 
> > Thanks in advance!
> > 
> > David KB4FXC
> > 
> > 
> > On Sun, 20 Jul 2008, David McGough wrote:
> > 
> >> Hi Steve and Roger,
> >>
> >> Thanks so much for the assistance. I'll give it a try today and report 
> >> back. I think most of my questions are now answered.
> >>
> >> <snip>
> >>
> >>
> > 
> > _______________________________________________
> > App_rpt mailing list
> > App_rpt at lists.illiana.net
> > http://lists.illiana.net/mailman/listinfo/app_rpt
> > 
> 
> _______________________________________________
> App_rpt mailing list
> App_rpt at lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt
> 


From hwstar at rodgers.sdcoxmail.com  Mon Jul 21 22:07:24 2008
From: hwstar at rodgers.sdcoxmail.com (Stephen Rodgers)
Date: Mon, 21 Jul 2008 20:07:24 -0700
Subject: [App_rpt] URI configuration help
In-Reply-To: <Pine.LNX.4.44.0807212152550.17923-100000@goliath.inttek.net>
References: <Pine.LNX.4.44.0807212152550.17923-100000@goliath.inttek.net>
Message-ID: <48854EEC.6010105@rodgers.sdcoxmail.com>

David,

Using the latest version of Asterisk may be the cause of your problems.
Why did you feel the need to upgrade it from what comes with EVB?

Troubleshooting the lockup on an unproven system configuration will be a
complete waste of your time if you aren't a developer and able to fix
things yourself in the code and are willing to spend hours and hours
tracking down the root cause of the problem. If you want to get
something running quickly, you have to resist the urge to update code to
the latest and greatest and stick to that which has a track record of
working.

There are several people running plain vanilla multi-node EVB systems
(Roger W4RFJ and Will W4WWM). I'm running a two node ACID system on the
bench but it doesn't have all that much test time on it. (It doesn't
lock up when the two nodes are connected together though.) There is one
other person running ACID on a two node system (Randy KC6HUR) he might
be able to give some insight as to how well it works.


This is one of the few problems with open source, you just don't know in
advance which combinations of programs will play nice together without
doing extensive testing yourself and troubleshooting the problems
yourself. This is why EVB and ACID exist. There are just to many things
which can go terribly wrong when programs are updated to the latest and
greatest versions.

Steve


David McGough wrote:
> Hi Steve,
> 
> I am running a EVB base system--centos 5 and 2.6.18-53.1.21.el5 kernel. I
> updated asterisk to a hand-compiled version (1.4.21) using the latest
> app_rpt and chan_usb code from Xelatek's SVN....Maybe I'll back down to 
> the ACID release.
> 
> The URI's are plugged directly into the PC, and 2 of the 3 seem to be
> working fine--other than I can't connect the extensions together. The
> TKR-850 (set internally in duplex mode and is asterisk extension 111)  
> works as a repeater, and accepts DTMF commands, etc....And, the remote
> base (currently a IC-706mk2g, extension 222) also accepts DTMF commands,
> etc....But, when I try to connect these units (using *3<node>), I get a
> lock up....
> 
> I reduced my extensions.conf file to the below for testing:
> 
> ---------------extensions.conf---------------------------------------
> [general]
>  
> static=yes       ; These two lines prevent the command-line interface
> writeprotect=yes ; from overwriting the config file. Leave them here.
>  
> [radio-secure]
> exten => 111,1,rpt,111
> exten => 222,1,rpt,222
>  
> [autopatch]
> ---------------------------------------------------------------------
> 
> And, here is my rpt.conf:
> ---------------rpt.conf---------------------------------------------
> ; Radio Repeater configuration file (for use with app_rpt)
> ;
>  
>  
> [111]                           ; Change this to your assigned node number
>  
> rxchannel = Radio/usb                   ; Rx audio/signalling channel
> controlstates=controlstates             ; system control state list
> scheduler=schedule;                     ; scheduler entries
> functions=functions                     ; Repeater Function Table
> phone_functions=functions               ; Repeater Function Table
> link_functions=link-functions           ; Link Function Table
> telemetry=telemetry                     ; Telemetry descriptions
> wait_times=wait-times                   ; Wait times
> context = autopatch                     ; dialing context for phone
> callerid = "Repeater" <0000000000> ; callerid for phone calls
> ;idrecording = |iid                     ; id recording or morse string
> idrecording=|ikb4fxc/r                  ; id recording or morse string
> accountcode=RADIO                       ; account code (optional)
> hangtime=1000                           ; squelch tail hang time (in ms) 
> (optional)
> althangtime=4000                        ; longer squelch tail
> totime=170000                           ; transmit time-out time (in ms) 
> (optional)
> totime=10000
> idtime=540000                           ; id interval time (in ms) 
> (optional)
> ; The default values for hangtime, time-out time, and id interval time are
> ; 5 seconds (5000 ms),  3 minutes (180000 ms), and 5 minutes (300000 ms)
> ; respectively
>  
> politeid=30000                          ; time in milliseconds before ID 
> timer
>  
>                                         ; expires to try and ID in the 
> tail.
>                                         ; (optional, default is 30000).
> idtalkover=|iid                         ; Talkover ID (optional) default 
> is none
> unlinkedct=ct2                          ; unlinked courtesy tone 
> (optional) default is none
> remotect=ct3
> duplex=2
>  
> ;////////////////////////////////////////////////////////////////////////////
> [222]                           ; Change this to your assigned node number
>  
> rxchannel = Radio/usb1                  ; Rx audio/signalling channel
> controlstates=controlstates             ; system control state list
> scheduler=schedule;                     ; scheduler entries
> functions=functions                     ; Repeater Function Table
> phone_functions=functions               ; Repeater Function Table
> link_functions=link-functions           ; Link Function Table
> telemetry=telemetry                     ; Telemetry descriptions
> wait_times=wait-times                   ; Wait times
> context = autopatch                     ; dialing context for phone
> callerid = "Repeater" <0000000000> ; callerid for phone calls
> idrecording = |iid                      ; id recording or morse string
> ;idrecording=|ikb4fxc                   ; id recording or morse string
> accountcode=RADIO                       ; account code (optional)
> hangtime=1000                           ; squelch tail hang time (in ms) 
> (optional)
> althangtime=4000                        ; longer squelch tail
> totime=170000                           ; transmit time-out time (in ms) 
> (optional)
> totime=10000
> idtime=540000                           ; id interval time (in ms) 
> (optional)
> ; The default values for hangtime, time-out time, and id interval time are
> ; 5 seconds (5000 ms),  3 minutes (180000 ms), and 5 minutes (300000 ms)
> ; respectively
>  
> politeid=30000                          ; time in milliseconds before ID timer
>  
>                                         ; expires to try and ID in the tail.
>                                         ; (optional, default is 30000).
> idtalkover=|iid                         ; Talkover ID (optional) default is none
> unlinkedct=ct2                          ; unlinked courtesy tone (optional) default is none
> remotect=ct3
> duplex=0
>  
> 
> ;///////////////////////////////////////////////////////////////////////////////////////
> ;
> ; function table
> ;
> [functions]
> 1=ilink,1                               ; Specific link disconnect
> 2=ilink,2                               ; Specific Link connect -  monitor 
> only
> 3=ilink,3                               ; Specific Link connect - transceive
> 4=ilink,4                               ; Enter command mode on a specific link
> 7=ilink,5                               ; Link status
>  
> 80=status,1                             ; System info
> 81=status,2                             ; Time
> 82=status,3                             ; app_rpt.c Version
> 87=ilink,15                             ; long range sensors
>  
> ;6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up
> ;0=autopatchdn                          ; Autopatch down
>  
> 99=cop,4                                ; Test tone
> 98=cop,6                                ; Phone TX key
>  
>  
> ;///////////////////////////////////////////////////////////////////////////////////////
> ;
> ; Link function table
> ;
> ; If this section is defined, then the remote user accessing our machine 
> in command mode
> ; will only be able to do the functions defined in this section. If this 
> section is
> ; omitted, then the link functions will be the same as the repeater 
> functions.
> ;
>  
>  
> [link-functions]
> 1=ilink,1                               ; Specific link disconnect
> 2=ilink,2                               ; Specific Link connect -  monitor 
> only
> 3=ilink,3                               ; Specific Link connect - 
> transceive
> 4=ilink,4                               ; Command mode
> 80=status,1                             ; System info
> 81=status,2                             ; Time
> 82=status,3                             ; app_rpt.c Version
> 87=ilink,15                             ; long range sensors
>                                                                                                                
> ;6=autopatchup,farenddisconnect=1,noct=1,dialtime=20000 ; Autopatch up
> ;0=autopatchdn                           ; Autopatch down
>  
> 99=cop,4                                ; Test tone
>  
> [telemetry]
>  
> ; Telemetry entries can be shared across all repeaters, or defined for 
> each repeater.
> ; Can be a tone sequence, morse string, or a file
> ;
> ; |t - Tone escape sequence
> ;
> ; Tone sequences consist of 1 or more 4-tuple entries (freq1, freq2, 
> duration, amplitude)
> ; Single frequencies are created by setting freq1 or freq2 to zero.
> ;
> ; |m - Morse escape sequence
> ;
> ; Sends Morse code at the telemetry amplitude and telemetry frequency as 
> defined in the
> ; [morse] section.
> ;
> ; Follow with an alphanumeric string
> ;
> ; |i - Morse ID escape sequence
> ;
> ; Sends Morse code at the ID amplitude and ID frequency as defined in the
> ; [morse] section.
> ;
> ; Follow with an alphanumeric string
>  
>  
> ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048)
> ct2=|t(660,880,150,2048)
> ct3=|t(440,0,150,4096)
> ct4=|t(550,0,150,2048)
> ct5=|t(660,0,150,2048)
> ct6=|t(880,0,150,2048)
> ct7=|t(660,440,150,2048)
> ct8=|t(700,1100,150,2048)
> remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000);
> remotemon=|t(1209,0,50,2048)
> cmdmode=|t(900,903,200,2048)
> functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048)
> patchup=rpt/callproceeding
> patchdown=rpt/callterminated
> ;idstr=|m('K','B','4','F','X','C')
>  
> ;
> ; Morse code parameters, these are common to all repeaters.
> ;
>  
> [morse]
>  
> speed=13                ; Approximate speed in WPM
> frequency=800           ; Morse Telemetry Frequency
> amplitude=4096          ; Morse Telemetry Amplitude
> idfrequency=1065        ; Morse ID Frequency
> idamplitude=1024        ; Morse ID Amplitude
>  
> ;
> ; This section allows wait times for telemetry events to be adjusted
> ; A section for wait times can be defined for every repeater
> ;
>  
> [wait-times]
> telemwait=2000                          ; Time to wait before sending most telemetry
> idwait=500                              ; Time to wait before starting ID
> unkeywait=2000                          ; Time to wait after unkey before sending CT's and link telemetry
> calltermwait=2000                       ; Time to wait before announcing "call terminated"
>  
> ;
> ; This is where you define your nodes which can be connected to.
> ;
>  
> [nodes]
> 111 = radio at 127.0.0.1/111,NONE  ; Change this to your assigned node number
> 222 = radio at 127.0.0.1/222,NONE  ; Change this to your assigned node number
>  
> -------------------------------------------------------------------------------- 
> 
> Finally, here is the usbradio.conf:
> ------------------------------------------------------------------------
> ;
> ; Open Sound System Console Driver Configuration File
> ;
> [general]
>  
> rxcpusaver=0
> txcpusaver=0
> debug=0x7
>  
> [usb]
> ; TKR-850
> devicenum=0
>  
> 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=0               ; 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=0.0      ; default tx ctcss freq, any frequency permitted
> rxctcssfreqs=0.0        ; rx ctcss freqs in floating point. must be in 
> table
> txctcssfreqs=0.0        ; tx ctcss freqs, any frequency permitted
>  
> carrierfrom=usbinvert           ; 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
>                         ; 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
>  
> txtoctype=notone        ; 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=1                ; Full Duplex
>  
>  
> [usb1]
> ; IC-706mk2g 
> devicenum=1
> hdwtype=0
> rxboost=0
> rxctcssrelax=1
> txctcssdefault=0.0
> rxctcssfreqs=0.0
> txctcssfreqs=0.0
> carrierfrom=usbinvert   ; no,usb,usbinvert,dsp,vox
> ctcssfrom=no            ; no,usb,dsp
> rxdemod=speaker         ; input type from radio: no,speaker,flat
> txprelim=no             ; Audio processing on left output channel: no,yes
> txtoctype=notone        ; Transmit tone control type: no,phase,notone
> txmixa=voice            ; Left channel output: 
> no,voice,tone,composite,auxvoice
> txmixb=no               ; Right channel output: no,voice,tone,composite, 
> auxvoice
> invertptt=0             ; Invert PTT 0 = ground to transmit, 1 = open to 
> transmit
> duplex=0                ; Simplex
> 
> 
> 
> 
> 
> 
> 
> On Mon, 21 Jul 2008, Stephen Rodgers wrote:
> 
>> David,
>>
>> First off, I just learned something myself about adding extra radio
>> ports using USB fobs: They must be added one at a time.
>>
>> Second, there should be no USB hubs between the FOB's and the PC's USB
>> ports.
>>
>> Finally, what type if linux install is this? ACID, EVB, custom?
>>
>>
>> I'd suggest restoring the configuration back to one radio port get that
>> working, then add and tune the ports one at a time.
>>
>>
>> Steve,
>> WA6ZFT
>>
>>
>>
>>
>> David McGough wrote:
>>> Hi Roger & Steve,
>>>
>>> Well, I'm making progress. I've noticed a couple more things I thought I'd
>>> mention. First, I've got a strange situation where I can only properly
>>> access 2 of the 3 URI's I have attached to the PC....Initially, I only
>>> plugged 1 URI in and couldn't get it to work at all (though the green LED
>>> was blinking)....Then, when I plugged in a 2nd URI, the first started
>>> working (with my TKR-850)....Today, I found that the second wasn't
>>> functional....So, tonight, experimentally, I plugged in a 3rd URI and
>>> both of the original 2 are now working. Strange.....Perhaps this has
>>> something to do with udev? Anyway, this isn't holding me up at the moment.
>>>
>>> The second issue is more troublesome. I can't get the repeater to link to
>>> the remote base....When I issue the connect command: *2(node number), the
>>> controller says it's linking both on the console and verbally. But, then
>>> it seems to hang totally with the TX enabled from the end that received
>>> the commands. I've tried this both ways--repeater to remote base (commands
>>> from the repeater) and vice versa. I end up having to kill -9 the asterisk
>>> process to regain control--"stop now" from the asterisk console
>>> hangs...This should work, right?
>>>
>>> Thanks in advance!
>>>
>>> David KB4FXC
>>>
>>>
>>> On Sun, 20 Jul 2008, David McGough wrote:
>>>
>>>> Hi Steve and Roger,
>>>>
>>>> Thanks so much for the assistance. I'll give it a try today and report 
>>>> back. I think most of my questions are now answered.
>>>>
>>>> <snip>
>>>>
>>>>
>>> _______________________________________________
>>> App_rpt mailing list
>>> App_rpt at lists.illiana.net
>>> http://lists.illiana.net/mailman/listinfo/app_rpt
>>>
>> _______________________________________________
>> App_rpt mailing list
>> App_rpt at lists.illiana.net
>> http://lists.illiana.net/mailman/listinfo/app_rpt
>>
> 
> _______________________________________________
> App_rpt mailing list
> App_rpt at lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt
> 


From kb4fxc at inttek.net  Mon Jul 21 22:23:01 2008
From: kb4fxc at inttek.net (David McGough)
Date: Mon, 21 Jul 2008 23:23:01 -0400 (EDT)
Subject: [App_rpt] URI configuration help
In-Reply-To: <48854EEC.6010105@rodgers.sdcoxmail.com>
Message-ID: <Pine.LNX.4.44.0807212310140.17923-100000@goliath.inttek.net>


Hi Steve,

I guess I'm a glutton for punishment! I'm a systems programmer/developer 
and in the past haven't had much trouble with hand-compiling versions of 
asterisk....But, I know exactly what you're talking about!

The main reason I compiled it was to include the iLBC CODEC, etc.,--which
I have previously used exclusively for Internet-based links on our office
asterisk PBXs....I figured this would give me my best connectivity option 
from the road with the laptop.

But, for the moment, I'll back down to the ACID release and give it a try.

Thanks so much for all your help!

73, David KB4FXC




On Mon, 21 Jul 2008, Stephen Rodgers wrote:

> David,
> 
> Using the latest version of Asterisk may be the cause of your problems.
> Why did you feel the need to upgrade it from what comes with EVB?
> 
> Troubleshooting the lockup on an unproven system configuration will be a
> complete waste of your time if you aren't a developer and able to fix
> things yourself in the code and are willing to spend hours and hours
> tracking down the root cause of the problem. If you want to get
> something running quickly, you have to resist the urge to update code to
> the latest and greatest and stick to that which has a track record of
> working.
> 
> There are several people running plain vanilla multi-node EVB systems
> (Roger W4RFJ and Will W4WWM). I'm running a two node ACID system on the
> bench but it doesn't have all that much test time on it. (It doesn't
> lock up when the two nodes are connected together though.) There is one
> other person running ACID on a two node system (Randy KC6HUR) he might
> be able to give some insight as to how well it works.
> 
> 
> This is one of the few problems with open source, you just don't know in
> advance which combinations of programs will play nice together without
> doing extensive testing yourself and troubleshooting the problems
> yourself. This is why EVB and ACID exist. There are just to many things
> which can go terribly wrong when programs are updated to the latest and
> greatest versions.
> 
> Steve
> 
> 
> David McGough wrote:
> > Hi Steve,
> > 
> > I am running a EVB base system--centos 5 and 2.6.18-53.1.21.el5 kernel. I
> > updated asterisk to a hand-compiled version (1.4.21) using the latest
> > app_rpt and chan_usb code from Xelatek's SVN....Maybe I'll back down to 
> > the ACID release.
> > 
> > The URI's are plugged directly into the PC, and 2 of the 3 seem to be
> > working fine--other than I can't connect the extensions together. The
> > TKR-850 (set internally in duplex mode and is asterisk extension 111)  
> > works as a repeater, and accepts DTMF commands, etc....And, the remote
> > base (currently a IC-706mk2g, extension 222) also accepts DTMF commands,
> > etc....But, when I try to connect these units (using *3<node>), I get a
> > lock up....
> > 
> > I reduced my extensions.conf file to the below for testing:
> > 
> > ---------------extensions.conf---------------------------------------
> > [general]
> >  
> > static=yes       ; These two lines prevent the command-line interface
> > writeprotect=yes ; from overwriting the config file. Leave them here.
> >  
> > [radio-secure]
> > exten => 111,1,rpt,111
> > exten => 222,1,rpt,222
> >  
> > [autopatch]
> > ---------------------------------------------------------------------
> > 
> > And, here is my rpt.conf:
> > ---------------rpt.conf---------------------------------------------
> > ; Radio Repeater configuration file (for use with app_rpt)
> > ;
> >  
> >  
> > [111]                           ; Change this to your assigned node number
> >  
> > rxchannel = Radio/usb                   ; Rx audio/signalling channel
> > controlstates=controlstates             ; system control state list
> > scheduler=schedule;                     ; scheduler entries
> > functions=functions                     ; Repeater Function Table
> > phone_functions=functions               ; Repeater Function Table
> > link_functions=link-functions           ; Link Function Table
> > telemetry=telemetry                     ; Telemetry descriptions
> > wait_times=wait-times                   ; Wait times
> > context = autopatch                     ; dialing context for phone
> > callerid = "Repeater" <0000000000> ; callerid for phone calls
> > ;idrecording = |iid                     ; id recording or morse string
> > idrecording=|ikb4fxc/r                  ; id recording or morse string
> > accountcode=RADIO                       ; account code (optional)
> > hangtime=1000                           ; squelch tail hang time (in ms) 
> > (optional)
> > althangtime=4000                        ; longer squelch tail
> > totime=170000                           ; transmit time-out time (in ms) 
> > (optional)
> > totime=10000
> > idtime=540000                           ; id interval time (in ms) 
> > (optional)
> > ; The default values for hangtime, time-out time, and id interval time are
> > ; 5 seconds (5000 ms),  3 minutes (180000 ms), and 5 minutes (300000 ms)
> > ; respectively
> >  
> > politeid=30000                          ; time in milliseconds before ID 
> > timer
> >  
> >                                         ; expires to try and ID in the 
> > tail.
> >                                         ; (optional, default is 30000).
> > idtalkover=|iid                         ; Talkover ID (optional) default 
> > is none
> > unlinkedct=ct2                          ; unlinked courtesy tone 
> > (optional) default is none
> > remotect=ct3
> > duplex=2
> >  
> > ;////////////////////////////////////////////////////////////////////////////
> > [222]                           ; Change this to your assigned node number
> >  
> > rxchannel = Radio/usb1                  ; Rx audio/signalling channel
> > controlstates=controlstates             ; system control state list
> > scheduler=schedule;                     ; scheduler entries
> > functions=functions                     ; Repeater Function Table
> > phone_functions=functions               ; Repeater Function Table
> > link_functions=link-functions           ; Link Function Table
> > telemetry=telemetry                     ; Telemetry descriptions
> > wait_times=wait-times                   ; Wait times
> > context = autopatch                     ; dialing context for phone
> > callerid = "Repeater" <0000000000> ; callerid for phone calls
> > idrecording = |iid                      ; id recording or morse string
> > ;idrecording=|ikb4fxc                   ; id recording or morse string
> > accountcode=RADIO                       ; account code (optional)
> > hangtime=1000                           ; squelch tail hang time (in ms) 
> > (optional)
> > althangtime=4000                        ; longer squelch tail
> > totime=170000                           ; transmit time-out time (in ms) 
> > (optional)
> > totime=10000
> > idtime=540000                           ; id interval time (in ms) 
> > (optional)
> > ; The default values for hangtime, time-out time, and id interval time are
> > ; 5 seconds (5000 ms),  3 minutes (180000 ms), and 5 minutes (300000 ms)
> > ; respectively
> >  
> > politeid=30000                          ; time in milliseconds before ID timer
> >  
> >                                         ; expires to try and ID in the tail.
> >                                         ; (optional, default is 30000).
> > idtalkover=|iid                         ; Talkover ID (optional) default is none
> > unlinkedct=ct2                          ; unlinked courtesy tone (optional) default is none
> > remotect=ct3
> > duplex=0
> >  
> > 
> > ;///////////////////////////////////////////////////////////////////////////////////////
> > ;
> > ; function table
> > ;
> > [functions]
> > 1=ilink,1                               ; Specific link disconnect
> > 2=ilink,2                               ; Specific Link connect -  monitor 
> > only
> > 3=ilink,3                               ; Specific Link connect - transceive
> > 4=ilink,4                               ; Enter command mode on a specific link
> > 7=ilink,5                               ; Link status
> >  
> > 80=status,1                             ; System info
> > 81=status,2                             ; Time
> > 82=status,3                             ; app_rpt.c Version
> > 87=ilink,15                             ; long range sensors
> >  
> > ;6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up
> > ;0=autopatchdn                          ; Autopatch down
> >  
> > 99=cop,4                                ; Test tone
> > 98=cop,6                                ; Phone TX key
> >  
> >  
> > ;///////////////////////////////////////////////////////////////////////////////////////
> > ;
> > ; Link function table
> > ;
> > ; If this section is defined, then the remote user accessing our machine 
> > in command mode
> > ; will only be able to do the functions defined in this section. If this 
> > section is
> > ; omitted, then the link functions will be the same as the repeater 
> > functions.
> > ;
> >  
> >  
> > [link-functions]
> > 1=ilink,1                               ; Specific link disconnect
> > 2=ilink,2                               ; Specific Link connect -  monitor 
> > only
> > 3=ilink,3                               ; Specific Link connect - 
> > transceive
> > 4=ilink,4                               ; Command mode
> > 80=status,1                             ; System info
> > 81=status,2                             ; Time
> > 82=status,3                             ; app_rpt.c Version
> > 87=ilink,15                             ; long range sensors
> >                                                                                                                
> > ;6=autopatchup,farenddisconnect=1,noct=1,dialtime=20000 ; Autopatch up
> > ;0=autopatchdn                           ; Autopatch down
> >  
> > 99=cop,4                                ; Test tone
> >  
> > [telemetry]
> >  
> > ; Telemetry entries can be shared across all repeaters, or defined for 
> > each repeater.
> > ; Can be a tone sequence, morse string, or a file
> > ;
> > ; |t - Tone escape sequence
> > ;
> > ; Tone sequences consist of 1 or more 4-tuple entries (freq1, freq2, 
> > duration, amplitude)
> > ; Single frequencies are created by setting freq1 or freq2 to zero.
> > ;
> > ; |m - Morse escape sequence
> > ;
> > ; Sends Morse code at the telemetry amplitude and telemetry frequency as 
> > defined in the
> > ; [morse] section.
> > ;
> > ; Follow with an alphanumeric string
> > ;
> > ; |i - Morse ID escape sequence
> > ;
> > ; Sends Morse code at the ID amplitude and ID frequency as defined in the
> > ; [morse] section.
> > ;
> > ; Follow with an alphanumeric string
> >  
> >  
> > ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048)
> > ct2=|t(660,880,150,2048)
> > ct3=|t(440,0,150,4096)
> > ct4=|t(550,0,150,2048)
> > ct5=|t(660,0,150,2048)
> > ct6=|t(880,0,150,2048)
> > ct7=|t(660,440,150,2048)
> > ct8=|t(700,1100,150,2048)
> > remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000);
> > remotemon=|t(1209,0,50,2048)
> > cmdmode=|t(900,903,200,2048)
> > functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048)
> > patchup=rpt/callproceeding
> > patchdown=rpt/callterminated
> > ;idstr=|m('K','B','4','F','X','C')
> >  
> > ;
> > ; Morse code parameters, these are common to all repeaters.
> > ;
> >  
> > [morse]
> >  
> > speed=13                ; Approximate speed in WPM
> > frequency=800           ; Morse Telemetry Frequency
> > amplitude=4096          ; Morse Telemetry Amplitude
> > idfrequency=1065        ; Morse ID Frequency
> > idamplitude=1024        ; Morse ID Amplitude
> >  
> > ;
> > ; This section allows wait times for telemetry events to be adjusted
> > ; A section for wait times can be defined for every repeater
> > ;
> >  
> > [wait-times]
> > telemwait=2000                          ; Time to wait before sending most telemetry
> > idwait=500                              ; Time to wait before starting ID
> > unkeywait=2000                          ; Time to wait after unkey before sending CT's and link telemetry
> > calltermwait=2000                       ; Time to wait before announcing "call terminated"
> >  
> > ;
> > ; This is where you define your nodes which can be connected to.
> > ;
> >  
> > [nodes]
> > 111 = radio at 127.0.0.1/111,NONE  ; Change this to your assigned node number
> > 222 = radio at 127.0.0.1/222,NONE  ; Change this to your assigned node number
> >  
> > -------------------------------------------------------------------------------- 
> > 
> > Finally, here is the usbradio.conf:
> > ------------------------------------------------------------------------
> > ;
> > ; Open Sound System Console Driver Configuration File
> > ;
> > [general]
> >  
> > rxcpusaver=0
> > txcpusaver=0
> > debug=0x7
> >  
> > [usb]
> > ; TKR-850
> > devicenum=0
> >  
> > 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=0               ; 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=0.0      ; default tx ctcss freq, any frequency permitted
> > rxctcssfreqs=0.0        ; rx ctcss freqs in floating point. must be in 
> > table
> > txctcssfreqs=0.0        ; tx ctcss freqs, any frequency permitted
> >  
> > carrierfrom=usbinvert           ; 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
> >                         ; 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
> >  
> > txtoctype=notone        ; 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=1                ; Full Duplex
> >  
> >  
> > [usb1]
> > ; IC-706mk2g 
> > devicenum=1
> > hdwtype=0
> > rxboost=0
> > rxctcssrelax=1
> > txctcssdefault=0.0
> > rxctcssfreqs=0.0
> > txctcssfreqs=0.0
> > carrierfrom=usbinvert   ; no,usb,usbinvert,dsp,vox
> > ctcssfrom=no            ; no,usb,dsp
> > rxdemod=speaker         ; input type from radio: no,speaker,flat
> > txprelim=no             ; Audio processing on left output channel: no,yes
> > txtoctype=notone        ; Transmit tone control type: no,phase,notone
> > txmixa=voice            ; Left channel output: 
> > no,voice,tone,composite,auxvoice
> > txmixb=no               ; Right channel output: no,voice,tone,composite, 
> > auxvoice
> > invertptt=0             ; Invert PTT 0 = ground to transmit, 1 = open to 
> > transmit
> > duplex=0                ; Simplex
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > On Mon, 21 Jul 2008, Stephen Rodgers wrote:
> > 
> >> David,
> >>
> >> First off, I just learned something myself about adding extra radio
> >> ports using USB fobs: They must be added one at a time.
> >>
> >> Second, there should be no USB hubs between the FOB's and the PC's USB
> >> ports.
> >>
> >> Finally, what type if linux install is this? ACID, EVB, custom?
> >>
> >>
> >> I'd suggest restoring the configuration back to one radio port get that
> >> working, then add and tune the ports one at a time.
> >>
> >>
> >> Steve,
> >> WA6ZFT
> >>
> >>
> >>
> >>
> >> David McGough wrote:
> >>> Hi Roger & Steve,
> >>>
> >>> Well, I'm making progress. I've noticed a couple more things I thought I'd
> >>> mention. First, I've got a strange situation where I can only properly
> >>> access 2 of the 3 URI's I have attached to the PC....Initially, I only
> >>> plugged 1 URI in and couldn't get it to work at all (though the green LED
> >>> was blinking)....Then, when I plugged in a 2nd URI, the first started
> >>> working (with my TKR-850)....Today, I found that the second wasn't
> >>> functional....So, tonight, experimentally, I plugged in a 3rd URI and
> >>> both of the original 2 are now working. Strange.....Perhaps this has
> >>> something to do with udev? Anyway, this isn't holding me up at the moment.
> >>>
> >>> The second issue is more troublesome. I can't get the repeater to link to
> >>> the remote base....When I issue the connect command: *2(node number), the
> >>> controller says it's linking both on the console and verbally. But, then
> >>> it seems to hang totally with the TX enabled from the end that received
> >>> the commands. I've tried this both ways--repeater to remote base (commands
> >>> from the repeater) and vice versa. I end up having to kill -9 the asterisk
> >>> process to regain control--"stop now" from the asterisk console
> >>> hangs...This should work, right?
> >>>
> >>> Thanks in advance!
> >>>
> >>> David KB4FXC
> >>>
> >>>
> >>> On Sun, 20 Jul 2008, David McGough wrote:
> >>>
> >>>> Hi Steve and Roger,
> >>>>
> >>>> Thanks so much for the assistance. I'll give it a try today and report 
> >>>> back. I think most of my questions are now answered.
> >>>>
> >>>> <snip>
> >>>>
> >>>>
> >>> _______________________________________________
> >>> App_rpt mailing list
> >>> App_rpt at lists.illiana.net
> >>> http://lists.illiana.net/mailman/listinfo/app_rpt
> >>>
> >> _______________________________________________
> >> App_rpt mailing list
> >> App_rpt at lists.illiana.net
> >> http://lists.illiana.net/mailman/listinfo/app_rpt
> >>
> > 
> > _______________________________________________
> > App_rpt mailing list
> > App_rpt at lists.illiana.net
> > http://lists.illiana.net/mailman/listinfo/app_rpt
> > 
> 
> _______________________________________________
> App_rpt mailing list
> App_rpt at lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt
> 


From hwstar at rodgers.sdcoxmail.com  Mon Jul 21 23:06:39 2008
From: hwstar at rodgers.sdcoxmail.com (Stephen Rodgers)
Date: Mon, 21 Jul 2008 21:06:39 -0700
Subject: [App_rpt] URI configuration help
In-Reply-To: <Pine.LNX.4.44.0807212310140.17923-100000@goliath.inttek.net>
References: <Pine.LNX.4.44.0807212310140.17923-100000@goliath.inttek.net>
Message-ID: <48855CCF.6090804@rodgers.sdcoxmail.com>


David,

One thing I forgot to mention after I looked over your configs.

1. You mentioned the second radio was a remote base. You should have a
,y on the end of a remote base node like this:

222 = radio at 127.0.0.1/222,NONE,y  ; Change this to your assigned node number

2. As a starting point, a remote base node should have a node stanza
which looks like this:

[222]

;devicenum=1 				;  Not necessary, remove. Device
					; automatically assigned.

rxchannel = radio/usb1                  ; Rx audio/signalling channel

remote = ic706
functions = remote-functions

phone_functions = remote-functions
ioport = /dev/ttyS0			; Specify port for serial port
civaddr = 88				; Specify CIV address for IC706


And a function list like this:


[remote-functions]

0=remote,1                              ; Retrieve Memory

1=remote,2                              ; Set freq.

2=remote,3                              ; Set tx PL tone

3=remote,4                              ; Set rx PL tone

40=remote,100                           ; Rx PL off

41=remote,101                           ; Rx PL on

42=remote,102                           ; Tx PL off

43=remote,103                           ; Tx PL on

44=remote,104                           ; Low Power

45=remote,105                           ; Medium Power

46=remote,106                           ; High Power

711=remote,107                          ; Bump -20

714=remote,108                          ; Bump -100

717=remote,109                          ; Bump -500

713=remote,110                          ; Bump +20

716=remote,111                          ; Bump +100

719=remote,112                          ; Bump +500

721=remote,113                          ; Scan - slow

724=remote,114                          ; Scan - quick

727=remote,115                          ; Scan - fast

723=remote,116                          ; Scan + slow

726=remote,117                          ; Scan + quick

729=remote,118                          ; Scan + fast

79=remote,119                           ; Tune

51=remote,5                             ; Long status query

52=remote,140                           ; Short status query

6=remote,6                              ; Set mode
98=cop,6


Steve
WA6ZFT



David McGough wrote:
> Hi Steve,
> 
> I guess I'm a glutton for punishment! I'm a systems programmer/developer 
> and in the past haven't had much trouble with hand-compiling versions of 
> asterisk....But, I know exactly what you're talking about!
> 
> The main reason I compiled it was to include the iLBC CODEC, etc.,--which
> I have previously used exclusively for Internet-based links on our office
> asterisk PBXs....I figured this would give me my best connectivity option 
> from the road with the laptop.
> 
> But, for the moment, I'll back down to the ACID release and give it a try.
> 
> Thanks so much for all your help!
> 
> 73, David KB4FXC
> 
> 
> 
> 
> On Mon, 21 Jul 2008, Stephen Rodgers wrote:
> 
>> David,
>>
>> Using the latest version of Asterisk may be the cause of your problems.
>> Why did you feel the need to upgrade it from what comes with EVB?
>>
>> Troubleshooting the lockup on an unproven system configuration will be a
>> complete waste of your time if you aren't a developer and able to fix
>> things yourself in the code and are willing to spend hours and hours
>> tracking down the root cause of the problem. If you want to get
>> something running quickly, you have to resist the urge to update code to
>> the latest and greatest and stick to that which has a track record of
>> working.
>>
>> There are several people running plain vanilla multi-node EVB systems
>> (Roger W4RFJ and Will W4WWM). I'm running a two node ACID system on the
>> bench but it doesn't have all that much test time on it. (It doesn't
>> lock up when the two nodes are connected together though.) There is one
>> other person running ACID on a two node system (Randy KC6HUR) he might
>> be able to give some insight as to how well it works.
>>
>>
>> This is one of the few problems with open source, you just don't know in
>> advance which combinations of programs will play nice together without
>> doing extensive testing yourself and troubleshooting the problems
>> yourself. This is why EVB and ACID exist. There are just to many things
>> which can go terribly wrong when programs are updated to the latest and
>> greatest versions.
>>
>> Steve
>>
>>
>> David McGough wrote:
>>> Hi Steve,
>>>
>>> I am running a EVB base system--centos 5 and 2.6.18-53.1.21.el5 kernel. I
>>> updated asterisk to a hand-compiled version (1.4.21) using the latest
>>> app_rpt and chan_usb code from Xelatek's SVN....Maybe I'll back down to 
>>> the ACID release.
>>>
>>> The URI's are plugged directly into the PC, and 2 of the 3 seem to be
>>> working fine--other than I can't connect the extensions together. The
>>> TKR-850 (set internally in duplex mode and is asterisk extension 111)  
>>> works as a repeater, and accepts DTMF commands, etc....And, the remote
>>> base (currently a IC-706mk2g, extension 222) also accepts DTMF commands,
>>> etc....But, when I try to connect these units (using *3<node>), I get a
>>> lock up....
>>>
>>> I reduced my extensions.conf file to the below for testing:
>>>
>>> ---------------extensions.conf---------------------------------------
>>> [general]
>>>  
>>> static=yes       ; These two lines prevent the command-line interface
>>> writeprotect=yes ; from overwriting the config file. Leave them here.
>>>  
>>> [radio-secure]
>>> exten => 111,1,rpt,111
>>> exten => 222,1,rpt,222
>>>  
>>> [autopatch]
>>> ---------------------------------------------------------------------
>>>
>>> And, here is my rpt.conf:
>>> ---------------rpt.conf---------------------------------------------
>>> ; Radio Repeater configuration file (for use with app_rpt)
>>> ;
>>>  
>>>  
>>> [111]                           ; Change this to your assigned node number
>>>  
>>> rxchannel = Radio/usb                   ; Rx audio/signalling channel
>>> controlstates=controlstates             ; system control state list
>>> scheduler=schedule;                     ; scheduler entries
>>> functions=functions                     ; Repeater Function Table
>>> phone_functions=functions               ; Repeater Function Table
>>> link_functions=link-functions           ; Link Function Table
>>> telemetry=telemetry                     ; Telemetry descriptions
>>> wait_times=wait-times                   ; Wait times
>>> context = autopatch                     ; dialing context for phone
>>> callerid = "Repeater" <0000000000> ; callerid for phone calls
>>> ;idrecording = |iid                     ; id recording or morse string
>>> idrecording=|ikb4fxc/r                  ; id recording or morse string
>>> accountcode=RADIO                       ; account code (optional)
>>> hangtime=1000                           ; squelch tail hang time (in ms) 
>>> (optional)
>>> althangtime=4000                        ; longer squelch tail
>>> totime=170000                           ; transmit time-out time (in ms) 
>>> (optional)
>>> totime=10000
>>> idtime=540000                           ; id interval time (in ms) 
>>> (optional)
>>> ; The default values for hangtime, time-out time, and id interval time are
>>> ; 5 seconds (5000 ms),  3 minutes (180000 ms), and 5 minutes (300000 ms)
>>> ; respectively
>>>  
>>> politeid=30000                          ; time in milliseconds before ID 
>>> timer
>>>  
>>>                                         ; expires to try and ID in the 
>>> tail.
>>>                                         ; (optional, default is 30000).
>>> idtalkover=|iid                         ; Talkover ID (optional) default 
>>> is none
>>> unlinkedct=ct2                          ; unlinked courtesy tone 
>>> (optional) default is none
>>> remotect=ct3
>>> duplex=2
>>>  
>>> ;////////////////////////////////////////////////////////////////////////////
>>> [222]                           ; Change this to your assigned node number
>>>  
>>> rxchannel = Radio/usb1                  ; Rx audio/signalling channel
>>> controlstates=controlstates             ; system control state list
>>> scheduler=schedule;                     ; scheduler entries
>>> functions=functions                     ; Repeater Function Table
>>> phone_functions=functions               ; Repeater Function Table
>>> link_functions=link-functions           ; Link Function Table
>>> telemetry=telemetry                     ; Telemetry descriptions
>>> wait_times=wait-times                   ; Wait times
>>> context = autopatch                     ; dialing context for phone
>>> callerid = "Repeater" <0000000000> ; callerid for phone calls
>>> idrecording = |iid                      ; id recording or morse string
>>> ;idrecording=|ikb4fxc                   ; id recording or morse string
>>> accountcode=RADIO                       ; account code (optional)
>>> hangtime=1000                           ; squelch tail hang time (in ms) 
>>> (optional)
>>> althangtime=4000                        ; longer squelch tail
>>> totime=170000                           ; transmit time-out time (in ms) 
>>> (optional)
>>> totime=10000
>>> idtime=540000                           ; id interval time (in ms) 
>>> (optional)
>>> ; The default values for hangtime, time-out time, and id interval time are
>>> ; 5 seconds (5000 ms),  3 minutes (180000 ms), and 5 minutes (300000 ms)
>>> ; respectively
>>>  
>>> politeid=30000                          ; time in milliseconds before ID timer
>>>  
>>>                                         ; expires to try and ID in the tail.
>>>                                         ; (optional, default is 30000).
>>> idtalkover=|iid                         ; Talkover ID (optional) default is none
>>> unlinkedct=ct2                          ; unlinked courtesy tone (optional) default is none
>>> remotect=ct3
>>> duplex=0
>>>  
>>>
>>> ;///////////////////////////////////////////////////////////////////////////////////////
>>> ;
>>> ; function table
>>> ;
>>> [functions]
>>> 1=ilink,1                               ; Specific link disconnect
>>> 2=ilink,2                               ; Specific Link connect -  monitor 
>>> only
>>> 3=ilink,3                               ; Specific Link connect - transceive
>>> 4=ilink,4                               ; Enter command mode on a specific link
>>> 7=ilink,5                               ; Link status
>>>  
>>> 80=status,1                             ; System info
>>> 81=status,2                             ; Time
>>> 82=status,3                             ; app_rpt.c Version
>>> 87=ilink,15                             ; long range sensors
>>>  
>>> ;6=autopatchup,noct=1,farenddisconnect=1,dialtime=20000 ; Autopatch up
>>> ;0=autopatchdn                          ; Autopatch down
>>>  
>>> 99=cop,4                                ; Test tone
>>> 98=cop,6                                ; Phone TX key
>>>  
>>>  
>>> ;///////////////////////////////////////////////////////////////////////////////////////
>>> ;
>>> ; Link function table
>>> ;
>>> ; If this section is defined, then the remote user accessing our machine 
>>> in command mode
>>> ; will only be able to do the functions defined in this section. If this 
>>> section is
>>> ; omitted, then the link functions will be the same as the repeater 
>>> functions.
>>> ;
>>>  
>>>  
>>> [link-functions]
>>> 1=ilink,1                               ; Specific link disconnect
>>> 2=ilink,2                               ; Specific Link connect -  monitor 
>>> only
>>> 3=ilink,3                               ; Specific Link connect - 
>>> transceive
>>> 4=ilink,4                               ; Command mode
>>> 80=status,1                             ; System info
>>> 81=status,2                             ; Time
>>> 82=status,3                             ; app_rpt.c Version
>>> 87=ilink,15                             ; long range sensors
>>>                                                                                                                
>>> ;6=autopatchup,farenddisconnect=1,noct=1,dialtime=20000 ; Autopatch up
>>> ;0=autopatchdn                           ; Autopatch down
>>>  
>>> 99=cop,4                                ; Test tone
>>>  
>>> [telemetry]
>>>  
>>> ; Telemetry entries can be shared across all repeaters, or defined for 
>>> each repeater.
>>> ; Can be a tone sequence, morse string, or a file
>>> ;
>>> ; |t - Tone escape sequence
>>> ;
>>> ; Tone sequences consist of 1 or more 4-tuple entries (freq1, freq2, 
>>> duration, amplitude)
>>> ; Single frequencies are created by setting freq1 or freq2 to zero.
>>> ;
>>> ; |m - Morse escape sequence
>>> ;
>>> ; Sends Morse code at the telemetry amplitude and telemetry frequency as 
>>> defined in the
>>> ; [morse] section.
>>> ;
>>> ; Follow with an alphanumeric string
>>> ;
>>> ; |i - Morse ID escape sequence
>>> ;
>>> ; Sends Morse code at the ID amplitude and ID frequency as defined in the
>>> ; [morse] section.
>>> ;
>>> ; Follow with an alphanumeric string
>>>  
>>>  
>>> ct1=|t(350,0,100,2048)(500,0,100,2048)(660,0,100,2048)
>>> ct2=|t(660,880,150,2048)
>>> ct3=|t(440,0,150,4096)
>>> ct4=|t(550,0,150,2048)
>>> ct5=|t(660,0,150,2048)
>>> ct6=|t(880,0,150,2048)
>>> ct7=|t(660,440,150,2048)
>>> ct8=|t(700,1100,150,2048)
>>> remotetx=|t(1633,0,50,3000)(0,0,80,0)(1209,0,50,3000);
>>> remotemon=|t(1209,0,50,2048)
>>> cmdmode=|t(900,903,200,2048)
>>> functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048)
>>> patchup=rpt/callproceeding
>>> patchdown=rpt/callterminated
>>> ;idstr=|m('K','B','4','F','X','C')
>>>  
>>> ;
>>> ; Morse code parameters, these are common to all repeaters.
>>> ;
>>>  
>>> [morse]
>>>  
>>> speed=13                ; Approximate speed in WPM
>>> frequency=800           ; Morse Telemetry Frequency
>>> amplitude=4096          ; Morse Telemetry Amplitude
>>> idfrequency=1065        ; Morse ID Frequency
>>> idamplitude=1024        ; Morse ID Amplitude
>>>  
>>> ;
>>> ; This section allows wait times for telemetry events to be adjusted
>>> ; A section for wait times can be defined for every repeater
>>> ;
>>>  
>>> [wait-times]
>>> telemwait=2000                          ; Time to wait before sending most telemetry
>>> idwait=500                              ; Time to wait before starting ID
>>> unkeywait=2000                          ; Time to wait after unkey before sending CT's and link telemetry
>>> calltermwait=2000                       ; Time to wait before announcing "call terminated"
>>>  
>>> ;
>>> ; This is where you define your nodes which can be connected to.
>>> ;
>>>  
>>> [nodes]
>>> 111 = radio at 127.0.0.1/111,NONE  ; Change this to your assigned node number
>>> 222 = radio at 127.0.0.1/222,NONE  ; Change this to your assigned node number
>>>  
>>> -------------------------------------------------------------------------------- 
>>>
>>> Finally, here is the usbradio.conf:
>>> ------------------------------------------------------------------------
>>> ;
>>> ; Open Sound System Console Driver Configuration File
>>> ;
>>> [general]
>>>  
>>> rxcpusaver=0
>>> txcpusaver=0
>>> debug=0x7
>>>  
>>> [usb]
>>> ; TKR-850
>>> devicenum=0
>>>  
>>> 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=0               ; 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=0.0      ; default tx ctcss freq, any frequency permitted
>>> rxctcssfreqs=0.0        ; rx ctcss freqs in floating point. must be in 
>>> table
>>> txctcssfreqs=0.0        ; tx ctcss freqs, any frequency permitted
>>>  
>>> carrierfrom=usbinvert           ; 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
>>>                         ; 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
>>>  
>>> txtoctype=notone        ; 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=1                ; Full Duplex
>>>  
>>>  
>>> [usb1]
>>> ; IC-706mk2g 
>>> devicenum=1
>>> hdwtype=0
>>> rxboost=0
>>> rxctcssrelax=1
>>> txctcssdefault=0.0
>>> rxctcssfreqs=0.0
>>> txctcssfreqs=0.0
>>> carrierfrom=usbinvert   ; no,usb,usbinvert,dsp,vox
>>> ctcssfrom=no            ; no,usb,dsp
>>> rxdemod=speaker         ; input type from radio: no,speaker,flat
>>> txprelim=no             ; Audio processing on left output channel: no,yes
>>> txtoctype=notone        ; Transmit tone control type: no,phase,notone
>>> txmixa=voice            ; Left channel output: 
>>> no,voice,tone,composite,auxvoice
>>> txmixb=no               ; Right channel output: no,voice,tone,composite, 
>>> auxvoice
>>> invertptt=0             ; Invert PTT 0 = ground to transmit, 1 = open to 
>>> transmit
>>> duplex=0                ; Simplex
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Mon, 21 Jul 2008, Stephen Rodgers wrote:
>>>
>>>> David,
>>>>
>>>> First off, I just learned something myself about adding extra radio
>>>> ports using USB fobs: They must be added one at a time.
>>>>
>>>> Second, there should be no USB hubs between the FOB's and the PC's USB
>>>> ports.
>>>>
>>>> Finally, what type if linux install is this? ACID, EVB, custom?
>>>>
>>>>
>>>> I'd suggest restoring the configuration back to one radio port get that
>>>> working, then add and tune the ports one at a time.
>>>>
>>>>
>>>> Steve,
>>>> WA6ZFT
>>>>
>>>>
>>>>
>>>>
>>>> David McGough wrote:
>>>>> Hi Roger & Steve,
>>>>>
>>>>> Well, I'm making progress. I've noticed a couple more things I thought I'd
>>>>> mention. First, I've got a strange situation where I can only properly
>>>>> access 2 of the 3 URI's I have attached to the PC....Initially, I only
>>>>> plugged 1 URI in and couldn't get it to work at all (though the green LED
>>>>> was blinking)....Then, when I plugged in a 2nd URI, the first started
>>>>> working (with my TKR-850)....Today, I found that the second wasn't
>>>>> functional....So, tonight, experimentally, I plugged in a 3rd URI and
>>>>> both of the original 2 are now working. Strange.....Perhaps this has
>>>>> something to do with udev? Anyway, this isn't holding me up at the moment.
>>>>>
>>>>> The second issue is more troublesome. I can't get the repeater to link to
>>>>> the remote base....When I issue the connect command: *2(node number), the
>>>>> controller says it's linking both on the console and verbally. But, then
>>>>> it seems to hang totally with the TX enabled from the end that received
>>>>> the commands. I've tried this both ways--repeater to remote base (commands
>>>>> from the repeater) and vice versa. I end up having to kill -9 the asterisk
>>>>> process to regain control--"stop now" from the asterisk console
>>>>> hangs...This should work, right?
>>>>>
>>>>> Thanks in advance!
>>>>>
>>>>> David KB4FXC
>>>>>
>>>>>
>>>>> On Sun, 20 Jul 2008, David McGough wrote:
>>>>>
>>>>>> Hi Steve and Roger,
>>>>>>
>>>>>> Thanks so much for the assistance. I'll give it a try today and report 
>>>>>> back. I think most of my questions are now answered.
>>>>>>
>>>>>> <snip>
>>>>>>
>>>>>>
>>>>> _______________________________________________
>>>>> App_rpt mailing list
>>>>> App_rpt at lists.illiana.net
>>>>> http://lists.illiana.net/mailman/listinfo/app_rpt
>>>>>
>>>> _______________________________________________
>>>> App_rpt mailing list
>>>> App_rpt at lists.illiana.net
>>>> http://lists.illiana.net/mailman/listinfo/app_rpt
>>>>
>>> _______________________________________________
>>> App_rpt mailing list
>>> App_rpt at lists.illiana.net
>>> http://lists.illiana.net/mailman/listinfo/app_rpt
>>>
>> _______________________________________________
>> App_rpt mailing list
>> App_rpt at lists.illiana.net
>> http://lists.illiana.net/mailman/listinfo/app_rpt
>>
> 
> _______________________________________________
> App_rpt mailing list
> App_rpt at lists.illiana.net
> http://lists.illiana.net/mailman/listinfo/app_rpt
> 


From mcheavens at usa.net  Tue Jul 22 09:49:30 2008
From: mcheavens at usa.net (Mark Cheavens)
Date: Tue, 22 Jul 2008 09:49:30 -0500
Subject: [App_rpt] URI configuration help
In-Reply-To: <48853CEA.6060605@rodgers.sdcoxmail.com>
References: <Pine.LNX.4.44.0807210051270.27459-100000@goliath.inttek.net>
	<48853CEA.6060605@rodgers.sdcoxmail.com>
Message-ID: <7.0.1.0.2.20080722094600.03a254e0@usa.net>

Why can there be no USB Hubs?
I have two systems in development right now that will both require 
hubs to gain enough ports.

The adding one at a time and keeping them in the same location is the 
reason to use the URI's and add eeproms. Has anybody actually 
utilized the eprom functions using a URI and Asterisk?

Mark,
KC5EVE

At 08:50 PM 7/21/2008, you wrote:
>David,
>
>First off, I just learned something myself about adding extra radio
>ports using USB fobs: They must be added one at a time.
>
>Second, there should be no USB hubs between the FOB's and the PC's USB
>ports.
>
>Finally, what type if linux install is this? ACID, EVB, custom?
>
>
>I'd suggest restoring the configuration back to one radio port get that
>working, then add and tune the ports one at a time.
>
>
>Steve,
>WA6ZFT
>
>
>
>
>David McGough wrote:
> >
> > Hi Roger & Steve,
> >
> > Well, I'm making progress. I've noticed a couple more things I thought I'd
> > mention. First, I've got a strange situation where I can only properly
> > access 2 of the 3 URI's I have attached to the PC....Initially, I only
> > plugged 1 URI in and couldn't get it to work at all (though the green LED
> > was blinking)....Then, when I plugged in a 2nd URI, the first started
> > working (with my TKR-850)....Today, I found that the second wasn't
> > functional....So, tonight, experimentally, I plugged in a 3rd URI and
> > both of the original 2 are now working. Strange.....Perhaps this has
> > something to do with udev? Anyway, this isn't holding me up at the moment.
> >
> > The second issue is more troublesome. I can't get the repeater to link to
> > the remote base....When I issue the connect command: *2(node number), the
> > controller says it's linking both on the console and verbally. But, then
> > it seems to hang totally with the TX enabled from the end that received
> > the commands. I've tried this both ways--repeater to remote base (commands
> > from the repeater) and vice versa. I end up having to kill -9 the asterisk
> > process to regain control--"stop now" from the asterisk console
> > hangs...This should work, right?
> >
> > Thanks in advance!
> >
> > David KB4FXC
> >
> >
> > On Sun, 20 Jul 2008, David McGough wrote:
> >
> >> Hi Steve and Roger,
> >>
> >> Thanks so much for the assistance. I'll give it a try today and report
> >> back. I think most of my questions are now answered.
> >>
> >> <snip>
> >>
> >>
> >
> > _______________________________________________
> > App_rpt mailing list
> > App_rpt at lists.illiana.net
> > http://lists.illiana.net/mailman/listinfo/app_rpt
> >
>
>_______________________________________________
>App_rpt mailing list
>A