I didn't see this message make it to the list so I am re-sending it without the attachment but with a link to the attachment. http://www.midlandsnetworking.com/WB9UUS-Repeater.JPG <http://www.midlandsnetworking.com/WB9UUS-Repeater.JPG> I want to thank Jim and others who responded to help me make progress on this project. I have included a link to a simple drawing of my system (above) and my current configuration file modifications are listed below. In the past I have been running the repeater with a PAP2T at the receive site and an SPA-3102 at the transmit site. When there is receive signal the FXS port on the pap2t goes off hook and auto-IP-dials the SPA3102, which auto-answers on the FXO port and keys the transmitter via a little PIC microcontroller that I built and programed. The PIC takes care of hang time, time out time, friendly CWID, touch-tone control of basic enable/disable/timer-reset/temperature-status-of-final/high-low-power-control/etc. With the desire to add additional receive sites and to add linking such as AllStar and EchoLink, and maybe even phone patch, I began this project. I have no prior experience with Asterisk, App_Rpt, or Centos and I have still not got an understanding of how the configuration files really work. Even though I can write some pretty cool programs in PERL and in C, after spending several days and nights looking over the notes, configuration files and C programs of this I still don't understand it well enough to see why what I have now is doing what it is or how to modify it to do exactly what I want it to do. I have had the Linksys adapters working without a computer for a few years. The new receiver is connected to the USB-CM108-fob. The transmit side of the USB-fob is just connected to an LED and a local speaker, since there is no transmitter at the computers location. Here are my configuration file modifications so far. - - - - - - - - - - cut here - - - - - - - - - ; sip.conf file modifications ; 1000 is Linksys PAP2T number 1 registered (the repeater receiver site, auto-dials 1003) [1000] type=friend context=phones host=dynamic ; 1001 is Linksys PAP2T number 2 registered ( a test telephone, auto-dials 1003) [1001] type=friend context=phones host=dynamic ; 1002 is Linksys SPA-3102 not registered (at the transmitter, auto-answers) [1002] type=friend context=phones host=10.10.10.234 port=5061 - - - - - - - - - - cut here - - - - - - - - - ; extensions.conf file modifications [internal] exten => 1000,1,Verbose(1|Extension 1000) exten => 1000,n,Dial(SIP/1000,30) exten => 1000,n,Hangup() exten => 1001,1,Verbose(1|Extension 1001) exten => 1001,n,Dial(SIP/1001,30) exten => 1001,n,Hangup() exten => 1002,1,Verbose(1|Extension 1002) exten => 1002,n,Dial(SIP/1002,30) exten => 1002,n,Hangup() ;exten => 1003,1,Rpt(27360|D) ; sends primary receiver to app_rpt but only gets to transmitter if there is a local secondary-receiver signal on usb-fob exten => 1003,1,Dial(SIP/1002,30) ; sends primary receiver to transmitter without app_rpt [phones] include => internal [radio] exten=_X11,1,Goto(check_route|${EXTEN}|1); exten=_NXXXXXX,1,Goto(check_route|1${HOMENPA}${EXTEN}|1) exten=_1XXXXXXXXXX,1,Goto(check_route|${EXTEN}|1) exten=_07XX,1,Goto(parkedcalls|${EXTEN:1}|1) exten=00,1,Goto(my-ip|s|1) exten => 01,1,Dial,SIP/1002 ; sends local usb-fob secondary-receiver to transmitter exten => 01,2,Hangup - - - - - - - - - - cut here - - - - - - - - - ; rpt.conf file modifications [functions27360] 988=autopatchup,noct=1,farenddisconnect=1,quiet=1,nostar=1,exten=01 [events] *988 = f|T|RPT_RXKEYED ; This fires off '*988' when the RX is keyed (Dial Autopatch as above) *0 = f|F|RPT_RXKEYED ; This fires off '*0' when Rx is unkeyed (to hang up Autopatch) - - - - - - - - - - cut here - - - - - - - - - I think that is all I added to the configuration of the server so far. Currently the received signal from the pap2t passes through the asterisk server and then goes to the spa3102 without using the app_rpt program. This works as it did before the asterisk server was added. If a signal is detected by the receiver connected to the asterisk server then it gets connected to the spa3102 at the transmitter, but without the app_rpt generated ID, announcements, timers, or control. Which ever receiver connects to the transmitter first wins, the other one gets a busy signal. If I replace the "exten => 1003,1,Dial(SIP/1002,30)" line with the "exten => 1003,1,Rpt(27360|D)" line then the call from the pap2t feeds the app_rpt program but never gets out to the spa3102 at the transmitter unless there is also a signal from the local receiver, in which case the 2 audios mix and go to the transmitter. This is almost okay, but needs the pap2t connection to be able to get to the transmitter even if the local receiver does not have a signal. Also it would be desirable for the app_rpt IDs, announcements, timers, and controls to work. I do not yet know what will happen if another system links to my system. There is also a mysterious to me issue in that with the configuration using the "exten => 1003,1,Rpt(27360|D)" line, sometimes after several hours of operation, followed by a short idle time and then a kerchunk, the asterisk command line interface indicates a time-out but there was no input to cause a timeout. Every received signal after that induces another timeout message every three minutes. Exiting asterisk and restarting it clears the problem for several hours. I am still trying to find a way to make this work. I guess maybe I am the first one trying to do what I am doing with the split site repeater. If there is no way to make this work then I will consider building 2 more servers so that there is a server at each site, if that will allow it to work, but that will use a lot more power than the 5 watts that the Linksys devices use and may not survive the harsh environment of the transmit site. What I think I need is a way to designate that the transmitter, rather than being on the same usb device as the receiver, is instead on a sip device. That way the transmitter isn't using the autopatch function. Hopefully the picture http://www.midlandsnetworking.com/WB9UUS-Repeater.JPG will make it more clear what I am trying to do. Chuck