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