From harfija at auburn.edu Thu Mar 2 23:41:41 2006 From: harfija at auburn.edu (James Harfield) Date: Thu, 02 Mar 2006 17:41:41 -0600 Subject: [App_rpt] Radio Interface Question Message-ID: <44072E53020000D60000EFD9@TMIA1.AUBURN.EDU> Sorry for the delay, my list subscrption settings may be wrong. I was not receiving the digest or any other e-mails to reply to, or know that anyone had responded. . . moving on: > That assumption isn't correct. It is E&M for zaptel configuration only (not in > hardware). The card interface 4 wire audio even though only a single Zap > channel is specified. In zaptel.conf you should specify: > e&m = 1 > .... > And in zapata.conf you should specify: > signalling=em_txrx > channel = 1 > .... > And in rpt.conf you should specify only ONE zap channel: > [100] ; Name of First Repeater > rxchannel = Zap/1 ; Rx audio/signalling channel > ... Thank you Steve. We do have all of that setup or as you suggested. Went back and double checked after reading your post just to make sure. > Please elaborate on how you are trying to connect. When do you get the "Unable > to create channel Zap" error? Was it when you tried to run Asterisk with > app_rpt compiled in? I'll try to ASCII out how we're connecting to our radio: Radio PCI Side Card Ext Spkr => 1 RXA CVC Sense => 2 COR --not used-- => 3 UIOA --not used-- => 4 Subtone PTT => 5 PTT --not used-- => 6 UIOB Ext Mic => 7 TXA RF Ground => 8 GND With that attached, just through an RJ-45 cable, we load up Asterisk. Then after connecting to Asterisk via a Softphone we try to dial the radio. Our extensions.conf file looks like this for dialing the Zap channel: exten => 205,1,Dial(Zap/1/1999) 1999 was the channel name we gave it. It is at this point, when we dial it, that the "Unable to create channel type Zap" error. > Your concern is true. It isn't true E&M at the hardware level. COR is a input > which accepts voltages from 0 to 13.8V and PTT is an open drain output from a > power MOSFET. See the quadradio_pci_installation.pdf file on app-rpt.qrvc.com > for more information on how to interface to the board. > As stated above, It is E&M only at the software configuration level. > Hooking the signals of the Quad Radio Card to a real E&M interface could > damage the board as -48V exceeds the component ratings of the parts in the > input and output circuits. Hopefully you didn't do this?! That makes a lot of sense. I knew something was up and the -48V thing wouldn't pan out. That's why I wanted to make 100% sure before actually hooking up the base station we had laying around. Thanks again Steve. From hwstar at rodgers.sdcoxmail.com Fri Mar 3 02:59:08 2006 From: hwstar at rodgers.sdcoxmail.com (Steve Rodgers) Date: Thu, 2 Mar 2006 18:59:08 -0800 Subject: [App_rpt] Radio Interface Question In-Reply-To: <44072E53020000D60000EFD9@TMIA1.AUBURN.EDU> References: <44072E53020000D60000EFD9@TMIA1.AUBURN.EDU> Message-ID: <200603021859.08651.hwstar@rodgers.sdcoxmail.com> James, See my responses below.... On Thursday 02 March 2006 15:41, James Harfield wrote: > Sorry for the delay, my list subscrption settings may be wrong. I was > not receiving the digest or any other e-mails to reply to, or know that > > anyone had responded. . . moving on: > > That assumption isn't correct. It is E&M for zaptel configuration only > > (not in > > > hardware). The card interface 4 wire audio even though only a single > > Zap > > > channel is specified. In zaptel.conf you should specify: > > > > e&m = 1 > > .... > > > > And in zapata.conf you should specify: > > > > signalling=em_txrx > > channel = 1 > > .... > > > > And in rpt.conf you should specify only ONE zap channel: > > > > [100] ; Name of First Repeater > > > > rxchannel = Zap/1 ; Rx audio/signalling channel > > ... > > Thank you Steve. We do have all of that setup or as you suggested. > Went back and double checked after reading your post just to make sure. > > > Please elaborate on how you are trying to connect. When do you get the > > "Unable > > > to create channel Zap" error? Was it when you tried to run Asterisk > > with > > > app_rpt compiled in? > > I'll try to ASCII out how we're connecting to our radio: > > Radio PCI > Side Card > > Ext Spkr => 1 RXA > CVC Sense => 2 COR > --not used-- => 3 UIOA > --not used-- => 4 Subtone > PTT => 5 PTT > --not used-- => 6 UIOB > Ext Mic => 7 TXA > RF Ground => 8 GND A couple of things to note here: Tying speaker audio to RXA is not the preferred method. RXA should be tied to the receiver's discriminator output, or to a point where the audio levels are less than a couple of volts peak. Pin 8 should be tied to DC ground. If that is the same as RF ground, that's fine. Microphone inputs tend to be very sensitive. You might need to add some attenuation resistors to the microphone input to knock the audio level from the card down so that you can easily adjust the level. If there is a line level input to your transmitter you'd be better off using that. > > With that attached, just through an RJ-45 cable, we load up Asterisk. > Then after connecting to Asterisk via a Softphone we try to dial the > radio. Our extensions.conf file looks like this for dialing the Zap > channel: > > exten => 205,1,Dial(Zap/1/1999) Hmmmmm. The idea here is not to talk to the Zap channels directly. Instead of trying to talk to the zap radio channel directly, try something like this instead: exten => 205,1,Rpt,1999|D When your caller calls extension 205, the transmitter should key, and the caller's audio should be heard on a receiver tuned to the transmitter's frequency. This is what we call dumb phone control mode. There are other modes you can use and they are documented in app_rpt.c. Also me sure that app_rpt.so is loaded and running in asterisk before trying any of the above. Use the following asterisk CLI example to determine if app_rpt.so is loaded. linuxserver2*CLI> show modules like app_rpt Module Description Use app_rpt.so Radio Repeater / Remote Base version 0. 0 1 modules loaded Steve Rodgers, WA6ZFT QRV Communications From eric at lylix.net Fri Mar 3 05:40:59 2006 From: eric at lylix.net (Eric Tichansky) Date: Fri, 03 Mar 2006 00:40:59 -0500 Subject: [App_rpt] TDM400 Message-ID: <4407D6EB.1000805@lylix.net> I finally acquired all the RF components for my new 2M/440 crossband repeater, using app_rpt of course! Anyways, just wanted to get a better idea and perhaps more details concerning the problems surrounding the use of the TDM400 series cards with the Analog Radio Interface Board (ARIB). It seems to work fine as long as the system is active. Once idle for an extended period of time, an almost certain segfault results. Using the safe_asterisk script to respawn asterisk after a crash works OK to recover for continued RF communications, but is useless when an incoming phone patch call triggers the segfault -- the call is dumped and just simply annoying. Just wondering what debugging has been done and conclusions as to what aspect of the system seems to be the culprit (TDM 400 hardware, Asterisk, app_rpt)? Are there any other Zaptel compatible FXS cards available for a modest price? -- Eric Tichansky NI3S eric at lylix.net LYLIX.NET -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3485 bytes Desc: S/MIME Cryptographic Signature URL: From hwstar at rodgers.sdcoxmail.com Fri Mar 3 14:55:33 2006 From: hwstar at rodgers.sdcoxmail.com (Steve Rodgers) Date: Fri, 3 Mar 2006 06:55:33 -0800 Subject: [App_rpt] TDM400 In-Reply-To: <4407D6EB.1000805@lylix.net> References: <4407D6EB.1000805@lylix.net> Message-ID: <200603030655.33295.hwstar@rodgers.sdcoxmail.com> Eric, The segfault thing has to be something else in your asterisk configuration. The problem we experienced with the TDM400 was not a segfault issue. In a nutshell the problem is this: On-hook and off-hook voltage transients cause the TDM400 hardware to get into a strange state and then the whole system (including Linux) crashes or freezes. Not every card will do this though. Node 2060 (KE6UPI) on the allstar link uses a TDM400 and it seems to be working fine. If you asterisk configuration is segfaulting, then this has be something else in your asterisk configuration. (mixed versions of asterisk modules maybe?) follow the instructions posted on bugs.digium.com, or voip-info.org and prepare a backtrace file with GDB on the coredump. If you look at the backtrace file, you should be able to see exactly what was happening just before the segfault occurred. This will give you a clue as to what happened. Steve, WA6ZFT On Thursday 02 March 2006 21:40, Eric Tichansky wrote: > I finally acquired all the RF components for my new 2M/440 crossband > repeater, using app_rpt of course! > > Anyways, just wanted to get a better idea and perhaps more details > concerning the problems surrounding the use of the TDM400 series cards > with the Analog Radio Interface Board (ARIB). > > It seems to work fine as long as the system is active. Once idle for an > extended period of time, an almost certain segfault results. Using the > safe_asterisk script to respawn asterisk after a crash works OK to > recover for continued RF communications, but is useless when an incoming > phone patch call triggers the segfault -- the call is dumped and just > simply annoying. > > Just wondering what debugging has been done and conclusions as to what > aspect of the system seems to be the culprit (TDM 400 hardware, > Asterisk, app_rpt)? Are there any other Zaptel compatible FXS cards > available for a modest price? From eric at lylix.net Fri Mar 3 17:06:07 2006 From: eric at lylix.net (Eric Tichansky) Date: Fri, 03 Mar 2006 12:06:07 -0500 Subject: [App_rpt] TDM400 In-Reply-To: <200603030655.33295.hwstar@rodgers.sdcoxmail.com> References: <4407D6EB.1000805@lylix.net> <200603030655.33295.hwstar@rodgers.sdcoxmail.com> Message-ID: <4408777F.4020806@lylix.net> Steve Thanks for the info. I just "cleaned" out my asterisk installation. I was noticing some module compatibility notices when 'make install'ing from source... did find that I apparently had an older version of asterisk installed via my distribution (Gentoo). I'll do some further testing to see if the problems clear up and if not, do the debugging you suggested. I have not had any issues with a total system lockup, so hopefully if I get past the segfaults, I'll be able to enjoy the stability you are seeing on KE6UPI. More to follow after some testing. Eric NI3S Steve Rodgers wrote: > Eric, > > The segfault thing has to be something else in your asterisk configuration. > The problem we experienced with the TDM400 was not a segfault issue. In a > nutshell the problem is this: > > On-hook and off-hook voltage transients cause the TDM400 hardware to get into > a strange state and then the whole system (including Linux) crashes or > freezes. Not every card will do this though. Node 2060 (KE6UPI) on the > allstar link uses a TDM400 and it seems to be working fine. > > If you asterisk configuration is segfaulting, then this has be something else > in your asterisk configuration. (mixed versions of asterisk modules maybe?) > follow the instructions posted on bugs.digium.com, or voip-info.org and > prepare a backtrace file with GDB on the coredump. If you look at the > backtrace file, you should be able to see exactly what was happening just > before the segfault occurred. This will give you a clue as to what happened. > > > > > Steve, WA6ZFT > > > On Thursday 02 March 2006 21:40, Eric Tichansky wrote: >> I finally acquired all the RF components for my new 2M/440 crossband >> repeater, using app_rpt of course! >> >> Anyways, just wanted to get a better idea and perhaps more details >> concerning the problems surrounding the use of the TDM400 series cards >> with the Analog Radio Interface Board (ARIB). >> >> It seems to work fine as long as the system is active. Once idle for an >> extended period of time, an almost certain segfault results. Using the >> safe_asterisk script to respawn asterisk after a crash works OK to >> recover for continued RF communications, but is useless when an incoming >> phone patch call triggers the segfault -- the call is dumped and just >> simply annoying. >> >> Just wondering what debugging has been done and conclusions as to what >> aspect of the system seems to be the culprit (TDM 400 hardware, >> Asterisk, app_rpt)? Are there any other Zaptel compatible FXS cards >> available for a modest price? > _______________________________________________ > App_rpt mailing list > App_rpt at lists.illiana.net > http://lists.illiana.net/mailman/listinfo/app_rpt > -- Eric Tichansky eric at lylix.net LYLIX.NET -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3485 bytes Desc: S/MIME Cryptographic Signature URL: From eric at lylix.net Fri Mar 3 20:28:53 2006 From: eric at lylix.net (Eric Tichansky) Date: Fri, 03 Mar 2006 15:28:53 -0500 Subject: [App_rpt] TDM400 + Feature Requests Message-ID: <4408A705.4070801@lylix.net> Steve Awesome! After cleaning up the abondoned modules and other crud from the distribution install, stability seems to be solid. I'll know for sure after letting it set for a few hours and hitting it with an incoming autopatch. I was in contact with Jim Dixon a while back (Dec?) which basically resulted in the duplex=3 mode where incoming RF audio is never retransmitted. He had asked a question during our email exchange, <----- Do you want the audio (Rx->Tx) severed during all times, or just while in autopatch mode? (Obviously, severing it always does not make for a good repeater, but Im not sure thats what you want here). -----> and I attempted to respond, but the email must not have gone through... <----- I still havent gotten your response yet from the last question, but If what you want is to not repeat Rx audio EVER, then try this version with duplex=3. -----> Anyways, to build upon the duplex=3 mode and answer his inquiry... It would be more practical if this mode where modified to only block incoming RF audio during an autopatch. That way the system functions like a normal repeater most of the time, and a full-duplex compatible autopatching sytem during an autopatch (useful for full-duplex crossband autopatching, obviously not wanting to hear yourself). Last feature request: perhaps a way to integrate CallerID in CW during an incoming autopatch announcement. If you could push these upstream to Jim, that would be appreciated. -- Eric Tichansky NI3S eric at lylix.net LYLIX.NET -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3485 bytes Desc: S/MIME Cryptographic Signature URL: From hwstar at rodgers.sdcoxmail.com Sat Mar 4 03:47:56 2006 From: hwstar at rodgers.sdcoxmail.com (Steve Rodgers) Date: Fri, 3 Mar 2006 19:47:56 -0800 Subject: [App_rpt] TDM400 + Feature Requests In-Reply-To: <4408A705.4070801@lylix.net> References: <4408A705.4070801@lylix.net> Message-ID: <200603031947.56377.hwstar@rodgers.sdcoxmail.com> Eric, Glad to see you got it working. I forwarded your e-mail to Jim Dixon. Steve Rodgers, QRV Communications On Friday 03 March 2006 12:28, Eric Tichansky wrote: > Steve > > Awesome! After cleaning up the abondoned modules and other crud from > the distribution install, stability seems to be solid. I'll know for > sure after letting it set for a few hours and hitting it with an > incoming autopatch. > > I was in contact with Jim Dixon a while back (Dec?) which basically > resulted in the duplex=3 mode where incoming RF audio is never > retransmitted. He had asked a question during our email exchange, > > <----- > Do you want the audio (Rx->Tx) severed during all times, or just while > in autopatch mode? (Obviously, severing it always does not make for a > good repeater, but Im not sure thats what you want here). > -----> > > and I attempted to respond, but the email must not have gone through... > > <----- > I still havent gotten your response yet from the last question, but If > what you want is to not repeat Rx audio EVER, then try this version with > duplex=3. > -----> > > Anyways, to build upon the duplex=3 mode and answer his inquiry... It > would be more practical if this mode where modified to only block > incoming RF audio during an autopatch. That way the system functions > like a normal repeater most of the time, and a full-duplex compatible > autopatching sytem during an autopatch (useful for full-duplex crossband > autopatching, obviously not wanting to hear yourself). > > Last feature request: perhaps a way to integrate CallerID in CW during > an incoming autopatch announcement. > > If you could push these upstream to Jim, that would be appreciated. From K0SEY at ShaneYoung.com Fri Mar 3 13:58:03 2006 From: K0SEY at ShaneYoung.com (Shane Young =?iso-8859-1?b?S9hTRVk=?=) Date: Fri, 03 Mar 2006 07:58:03 -0600 Subject: [App_rpt] Radio Interface Question In-Reply-To: <44072E53020000D60000EFD9@TMIA1.AUBURN.EDU> References: <44072E53020000D60000EFD9@TMIA1.AUBURN.EDU> Message-ID: <1141394283.44084b6ba5fe3@mail.shaneyoung.com> It seems when we tried the TDM400, the TDM400 just sorta "stopped working" after a bit. I don't think Asterisk itself ever crapped out. It seems to me that I figured a T1 board was about $500 and a Carrier Access AB1 channel bank was about $125 on ebay. This is probably the most stable configuration (other than the PCI Radio board). The added bonus is 22 extra FXS stations ;) Quoting James Harfield : > Sorry for the delay, my list subscrption settings may be wrong. I was > not receiving the digest or any other e-mails to reply to, or know that > anyone had responded. . . moving on: > > > That assumption isn't correct. It is E&M for zaptel configuration only > (not in > > hardware). The card interface 4 wire audio even though only a single > Zap > > channel is specified. In zaptel.conf you should specify: > > > e&m = 1 > > .... > > > And in zapata.conf you should specify: > > > signalling=em_txrx > > channel = 1 > > .... > > > And in rpt.conf you should specify only ONE zap channel: > > > [100] ; Name of First Repeater > > > rxchannel = Zap/1 ; Rx audio/signalling channel > > ... > > Thank you Steve. We do have all of that setup or as you suggested. > Went back and double checked after reading your post just to make sure. > > > Please elaborate on how you are trying to connect. When do you get the > "Unable > > to create channel Zap" error? Was it when you tried to run Asterisk > with > > app_rpt compiled in? > > I'll try to ASCII out how we're connecting to our radio: > > Radio PCI > Side Card > > Ext Spkr => 1 RXA > CVC Sense => 2 COR > --not used-- => 3 UIOA > --not used-- => 4 Subtone > PTT => 5 PTT > --not used-- => 6 UIOB > Ext Mic => 7 TXA > RF Ground => 8 GND > > With that attached, just through an RJ-45 cable, we load up Asterisk. > Then after connecting to Asterisk via a Softphone we try to dial the > radio. Our extensions.conf file looks like this for dialing the Zap > channel: > > exten => 205,1,Dial(Zap/1/1999) > > 1999 was the channel name we gave it. It is at this point, when we dial > it, that the "Unable to create channel type Zap" error. > > > Your concern is true. It isn't true E&M at the hardware level. COR is > a input > > which accepts voltages from 0 to 13.8V and PTT is an open drain output > from a > > power MOSFET. See the quadradio_pci_installation.pdf file on > app-rpt.qrvc.com > > for more information on how to interface to the board. > > > As stated above, It is E&M only at the software configuration level. > > > Hooking the signals of the Quad Radio Card to a real E&M interface > could > > damage the board as -48V exceeds the component ratings of the parts in > the > > input and output circuits. Hopefully you didn't do this?! > > That makes a lot of sense. I knew something was up and the -48V thing > wouldn't pan out. That's why I wanted to make 100% sure before actually > hooking up the base station we had laying around. > > Thanks again Steve. > _______________________________________________ > App_rpt mailing list > App_rpt at lists.illiana.net > http://lists.illiana.net/mailman/listinfo/app_rpt > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From telesistant at hotmail.com Sat Mar 4 19:37:51 2006 From: telesistant at hotmail.com (Jim Duuuude) Date: Sat, 04 Mar 2006 11:37:51 -0800 Subject: [App_rpt] New version of app_rpt available In-Reply-To: <1141394283.44084b6ba5fe3@mail.shaneyoung.com> Message-ID: Check out the new version of app_rpt version 0.43. It now supports a duplex=4 mode, where (like duplex=3 mode) it mutes the path of main repeated audio (between main rx and tx, but not anywhere else), but only while the autopatch is in use. Also included documentation (in C file header) for all the duplex modes. It may be found at: http://www.zapatatelephony.org/app_rpt-0.43.c From hwstar at rodgers.sdcoxmail.com Sun Mar 5 20:25:14 2006 From: hwstar at rodgers.sdcoxmail.com (Steve Rodgers) Date: Sun, 5 Mar 2006 12:25:14 -0800 Subject: [App_rpt] Version 0.44 app_rpt available Message-ID: <200603051225.14765.hwstar@rodgers.sdcoxmail.com> There's a new version of app_rpt.c available on the zapatatelephony site. Version 0.44 Adds 2 CLI status commands-- rpt stats node and rpt lstats node The first command will list the state of the node and the second command will list the state of the links connected to the node. There is also a fix for the brief drop of the transmitter when a tail message is about to be played. Some systems did this while others were just fine. The new version of app_rpt is available here: http://www.zapatatelephony.org/app_rpt-0.44.c Steve, WA6ZFT From eric at lylix.net Mon Mar 6 02:03:15 2006 From: eric at lylix.net (Eric Tichansky) Date: Sun, 05 Mar 2006 21:03:15 -0500 Subject: [App_rpt] Iaxrpt In-Reply-To: <200603051225.14765.hwstar@rodgers.sdcoxmail.com> References: <200603051225.14765.hwstar@rodgers.sdcoxmail.com> Message-ID: <440B9863.5050006@lylix.net> Just testing iaxrpt... The Linux version is not appearing like the screenshot on the website. Instead of: [Connect][Hold][Speaker][Disconnect] I am seeing: [Dial][Hold][Transfer][Speaker][Hangup] Also, when inserting account information, and using Dail for connecting, my PBX spits out the follwoing: chan_iax2.c:7213 socket_read: Rejected connect attempt from 24.154.53.97, request 'NI3S at global' does not exist Any hints appreciated. Thanks! Eric NI3S -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3485 bytes Desc: S/MIME Cryptographic Signature URL: From hwstar at rodgers.sdcoxmail.com Mon Mar 6 06:23:59 2006 From: hwstar at rodgers.sdcoxmail.com (Steve Rodgers) Date: Sun, 5 Mar 2006 22:23:59 -0800 Subject: [App_rpt] Iaxrpt In-Reply-To: <440B9863.5050006@lylix.net> References: <200603051225.14765.hwstar@rodgers.sdcoxmail.com> <440B9863.5050006@lylix.net> Message-ID: <200603052223.59838.hwstar@rodgers.sdcoxmail.com> Yes, I noticed this as well. Looks like an older version was uploaded. The linux version will need to be updated and resubmitted. I can't say when this might be updated because I'm in the process of bringing up a new development system and the tools for the linux version aren't installed on the new box yet. The other problem is probably a configuration issue. You need to have a separate dial statement and context in extensions.conf for iaxrpt simlar to this: [radio-gui] exten => 2010,1,rpt(2010|X) Then in iax.conf add a stanza like this: ; Gui users [gui] type=user context=radio-gui auth=md5 secret=nunya host=dynamic disallow=all allow=gsm notransfer=yes Steve, WA6ZFT On Sunday 05 March 2006 18:03, Eric Tichansky wrote: > Just testing iaxrpt... > > The Linux version is not appearing like the screenshot on the website. > Instead of: > > [Connect][Hold][Speaker][Disconnect] > > I am seeing: > > [Dial][Hold][Transfer][Speaker][Hangup] > > Also, when inserting account information, and using Dail for connecting, > my PBX spits out the follwoing: > > chan_iax2.c:7213 socket_read: Rejected connect attempt from > 24.154.53.97, request 'NI3S at global' does not exist > > > Any hints appreciated. Thanks! > > Eric NI3S From hwstar at rodgers.sdcoxmail.com Mon Mar 6 15:00:22 2006 From: hwstar at rodgers.sdcoxmail.com (Steve Rodgers) Date: Mon, 6 Mar 2006 07:00:22 -0800 Subject: [App_rpt] Motorola MDC-1200 decode supported Message-ID: <200603060700.22586.hwstar@rodgers.sdcoxmail.com> Group, Jim and I added initial MDC-1200 decode support for app_rpt.c. To use, download the following files from zapatatelephony.org: app_rpt-0.45.c mdc-1200.tar.gz Copy app_rpt-0.45.c to your /usr/src/asterisk/apps directory untar the mdc-1200.tar.gz file and copy the files in the newly created mdc-1200 directory to your /usr/src/asterisk/apps directory Edit app_rpt-0.45.c and make sure the line containing "#include mdc_decode.c" is uncommented. Recompile and install asterisk. Now, when your radio sends a MDC1200 data burst, it's unot ID will be sent immediately following the courtesy tone. Obviously, this is just a start. There are other things we can do with this. Steve, WA6ZFT From Bryan at illiana.net Mon Mar 6 15:57:09 2006 From: Bryan at illiana.net (Bryan Fields) Date: Mon, 6 Mar 2006 09:57:09 -0600 Subject: [App_rpt] Voters In-Reply-To: <200601211957.48344.hwstar@rodgers.sdcoxmail.com> References: <006601c61d65$5b934b80$6401a8c0@CHARLESS> <00a701c61eb1$91f5af40$6401a8c0@CHARLESS> <200601211957.48344.hwstar@rodgers.sdcoxmail.com> Message-ID: <200603060957.11047.Bryan@illiana.net> On Saturday 21 January 2006 09:57 pm, Steve Rodgers wrote: > I'm not aware of any feature like this in GSM. With regard to DSP required, > it would probably involve measuring the noise content of a signal. The > problem is, that there's no easy way to determine noise from a valid signal > when measuring energy and spectrum in band. What this means is you would > probably have to get your signal quality from noise outside of the > bandwidth of the channel similar to what happens with noise squelch > circuits. Well S/N voters work with just the audio from a link rx and cor. They do this using op amps that only amp the high frequency componits of a signal. This can be done with two op-amps fed into a comparator. There must be some way to code an op amp function in a DSP/CPU and have it out put a value for a signal with more highfrequency content in it. > Also, there is something else I forgot to mention in the issue list under > Internet weather. There needs to be a way to adjust the delays dynamically > between all of the receive channels so that when ?the voter switches audio > channels, there is no repeated or dropped voice frames. This may not be a > trivial exercise. Well if you own the network and your running IPoATM or IP+QOS it's easy to route the traffic with low jitter. -- Bryan Fields Chief RF Engineer/Partner illiana.net 219-306-1805 From harfija at auburn.edu Tue Mar 7 23:28:06 2006 From: harfija at auburn.edu (James Harfield) Date: Tue, 07 Mar 2006 17:28:06 -0600 Subject: [App_rpt] Radio Interface Question In-Reply-To: References: Message-ID: <440DC2A6020000D60000F909@TMIA1.AUBURN.EDU> Steve Rodgers wrote: "A couple of things to note here: Tying speaker audio to RXA is not the preferred method. RXA should be tied to the receiver's discriminator output, or to a point where the audio levels are less than a couple of volts peak. Pin 8 should be tied to DC ground. If that is the same as RF ground, that's fine. Microphone inputs tend to be very sensitive. You might need to add some attenuation resistors to the microphone input to knock the audio level from the card down so that you can easily adjust the level. If there is a line level input to your transmitter you'd be better off using that." Measuring the levels of the speaker audio, regardless of volume level on the radio, the voltage does not break 1.5v. Looking at the documentation for the card I felt that this was appropriate. I'm using regular Ground as of now. Grounding PTT with "Ground" and not "RF Ground" keys the radio as it should. So I'll just move my ground pin to there and leave PTT where it is. What I'm doing now is making a small circuit to work as COR. I can't seem to find a working version of the COR in the radio pin out, so I've taken a MOSFET and 5v battery to switch the level from 5v to ground when a signal is present and stay at 5v when no signal is present. Unless I'm blindly missing something to pull off the radio that will work the same way. Something like: +5v | 10k _ |--------------to PCI card >from radio-- |_ | | gnd ASCII art may be butchered in the post though. The level from the radio should be enough to activate the FET and pull that output to ground, while allowing the 5v to pass to the card when there is no signal. Just for reference so you know where I'm coming from, I found a couple of Motorola HT600s on eBay with charger for pretty cheap and am playing with those since they seemed to have easy access to signals with the 13 pins on top. I thought this would be good to learn with while not investing tons of money in expensive radios to break. Thanks for the help while I struggle through this process. -JRH From hwstar at rodgers.sdcoxmail.com Wed Mar 8 05:10:29 2006 From: hwstar at rodgers.sdcoxmail.com (Steve Rodgers) Date: Tue, 7 Mar 2006 21:10:29 -0800 Subject: [App_rpt] Radio Interface Question In-Reply-To: <440DC2A6020000D60000F909@TMIA1.AUBURN.EDU> References: <440DC2A6020000D60000F909@TMIA1.AUBURN.EDU> Message-ID: <200603072110.29304.hwstar@rodgers.sdcoxmail.com> James, See below-- On Tuesday 07 March 2006 15:28, James Harfield wrote: > Measuring the levels of the speaker audio, regardless of volume level > on the radio, the voltage does not break 1.5v. Looking at the > documentation for the card I felt that this was appropriate. The potential problem here is that someone can mess with the receiver volume control and mess up the audio levels. > > I'm using regular Ground as of now. Grounding PTT with "Ground" and > not "RF Ground" keys the radio as it should. So I'll just move my > ground pin to there and leave PTT where it is. Sound like a good plan. > > What I'm doing now is making a small circuit to work as COR. I can't > seem to find a working version of the COR in the radio pin out, so I've > taken a MOSFET and 5v battery to switch the level from 5v to ground when > a signal is present and stay at 5v when no signal is present. Unless > I'm blindly missing something to pull off the radio that will work the > same way. Something like: > > +5v > > 10k > _ |--------------to PCI card > > >from radio-- |_ > > gnd May I suggest you get the schematic to the radio, and look for the transistor or electronic switch which is used to mute the audio? If you can find some point in the squelch circuit which swings from 5 volts or higher to ground, use this as your COR. The COR input as a 1 megohm input impedance. You should be able to find a point in the radio which will provide the signal for you. > > ASCII art may be butchered in the post though. The level from the > radio should be enough to activate the FET and pull that output to > ground, while allowing the 5v to pass to the card when there is no > signal. > > Just for reference so you know where I'm coming from, I found a couple > of Motorola HT600s on eBay with charger for pretty cheap and am playing > with those since they seemed to have easy access to signals with the 13 > pins on top. I thought this would be good to learn with while not > investing tons of money in expensive radios to break. Thanks for the > help while I struggle through this process. HT 600's should interface nicely. Take a look in the service manual to understand what I'm talking about. The way the speaker circuit works, also doubles nicely for COR. The audio output stage is powered down when there is no signal. > > -JRH > _______________________________________________ > App_rpt mailing list > App_rpt at lists.illiana.net > http://lists.illiana.net/mailman/listinfo/app_rpt From telesistant at hotmail.com Wed Mar 8 06:31:51 2006 From: telesistant at hotmail.com (Jim Duuuude) Date: Tue, 07 Mar 2006 22:31:51 -0800 Subject: [App_rpt] Radio Interface Question In-Reply-To: <200603072110.29304.hwstar@rodgers.sdcoxmail.com> Message-ID: Its a really easy thing. The two speaker outputs (which are a bridged audio out) stay at Gnd DC potential until there is something for the receiver to receive. So, if you do something like this: Keep Volume control about 9 o'clock on radio. ____________________________ Rx Audio | | | 47 .25W ---|--/\/\/\/\------| Spkr Lo | 47 .25W |_________________ COR ------/\/\/\/\------| Spkr Hi __|__ _____ .01uf | HT600 side | | Gnd The transmit audio just needs some sorta voltage divider (like maybe 5:1). >From: Steve Rodgers >Reply-To: Asterisk Repeater Controler >To: Asterisk Repeater Controler >Subject: Re: [App_rpt] Radio Interface Question >Date: Tue, 7 Mar 2006 21:10:29 -0800 >MIME-Version: 1.0 >Received: from lists.illiana.net ([207.227.243.140]) by >bay0-mc1-f2.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 7 >Mar 2006 21:10:37 -0800 >Received: (qmail 21709 invoked from network); 8 Mar 2006 05:10:36 -0000 >Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with SMTP; 8 >Mar 2006 05:10:36 -0000 >Received: (qmail 21684 invoked from network); 8 Mar 2006 05:10:33 -0000 >Received: from dukecmmtao02.coxmail.com (68.99.120.69)by 0 with SMTP; 8 Mar >2006 05:10:33 -0000 >Received: from steverod.sv.qrvc.com ([68.15.19.112])by >dukecmmtao02.coxmail.com(InterMail vM.6.01.05.02 201-2131-123-102-20050715) >with ESMTP >id<20060308051030.UCUW6953.dukecmmtao02.coxmail.com at steverod.sv.qrvc.com>for >; Wed, 8 Mar 2006 00:10:30 -0500 >X-Message-Info: JGTYoYF78jFOtBd3xYPhmA3Iazc+KvMicpT8V0kvhi8= >Return-Path: >Delivered-To: mailman-app_rpt at lists.illiana.net >User-Agent: KMail/1.9.1 >References: ><440DC2A6020000D60000F909 at TMIA1.AUBURN.EDU> >X-BeenThere: app_rpt at lists.illiana.net >X-Mailman-Version: 2.1.6 >Precedence: list >List-Id: Asterisk Repeater Controler >List-Unsubscribe: >, >List-Archive: >List-Post: >List-Help: >List-Subscribe: >, >Errors-To: app_rpt-bounces at lists.illiana.net >X-OriginalArrivalTime: 08 Mar 2006 05:10:37.0276 (UTC) >FILETIME=[A2DB61C0:01C6426E] > >James, > >See below-- > > >On Tuesday 07 March 2006 15:28, James Harfield wrote: > > > Measuring the levels of the speaker audio, regardless of volume level > > on the radio, the voltage does not break 1.5v. Looking at the > > documentation for the card I felt that this was appropriate. > >The potential problem here is that someone can mess with the receiver >volume >control and mess up the audio levels. > > > > > I'm using regular Ground as of now. Grounding PTT with "Ground" and > > not "RF Ground" keys the radio as it should. So I'll just move my > > ground pin to there and leave PTT where it is. > >Sound like a good plan. > > > > > What I'm doing now is making a small circuit to work as COR. I can't > > seem to find a working version of the COR in the radio pin out, so I've > > taken a MOSFET and 5v battery to switch the level from 5v to ground when > > a signal is present and stay at 5v when no signal is present. Unless > > I'm blindly missing something to pull off the radio that will work the > > same way. Something like: > > > > +5v > > > > 10k > > _ |--------------to PCI card > > > > >from radio-- |_ > > > > gnd > >May I suggest you get the schematic to the radio, and look for the >transistor >or electronic switch which is used to mute the audio? If you can find some >point in the squelch circuit which swings from 5 volts or higher to ground, >use this as your COR. The COR input as a 1 megohm input impedance. You >should >be able to find a point in the radio which will provide the signal for you. > > > > > ASCII art may be butchered in the post though. The level from the > > radio should be enough to activate the FET and pull that output to > > ground, while allowing the 5v to pass to the card when there is no > > signal. > > > > Just for reference so you know where I'm coming from, I found a couple > > of Motorola HT600s on eBay with charger for pretty cheap and am playing > > with those since they seemed to have easy access to signals with the 13 > > pins on top. I thought this would be good to learn with while not > > investing tons of money in expensive radios to break. Thanks for the > > help while I struggle through this process. > >HT 600's should interface nicely. Take a look in the service manual to >understand what I'm talking about. The way the speaker circuit works, also >doubles nicely for COR. The audio output stage is powered down when there >is >no signal. > > > > > > > > > -JRH > > _______________________________________________ > > 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 Thu Mar 9 05:23:20 2006 From: hwstar at rodgers.sdcoxmail.com (Steve Rodgers) Date: Wed, 8 Mar 2006 21:23:20 -0800 Subject: [App_rpt] Iaxrpt In-Reply-To: <440B9863.5050006@lylix.net> References: <200603051225.14765.hwstar@rodgers.sdcoxmail.com> <440B9863.5050006@lylix.net> Message-ID: <200603082123.20642.hwstar@rodgers.sdcoxmail.com> Eric, There's a new version of the iaxrpt binary for FC4 on iaxrpt.qrvc.com which fixes the issue you reported below. Also, I included some more setup information on the site which might be useful to you. Steve, WA6ZFT On Sunday 05 March 2006 18:03, Eric Tichansky wrote: > Just testing iaxrpt... > > The Linux version is not appearing like the screenshot on the website. > Instead of: > > [Connect][Hold][Speaker][Disconnect] > > I am seeing: > > [Dial][Hold][Transfer][Speaker][Hangup] > > Also, when inserting account information, and using Dail for connecting, > my PBX spits out the follwoing: > > chan_iax2.c:7213 socket_read: Rejected connect attempt from > 24.154.53.97, request 'NI3S at global' does not exist > > > Any hints appreciated. Thanks! > > Eric NI3S From eric at lylix.net Thu Mar 9 06:15:53 2006 From: eric at lylix.net (eric at lylix.net) Date: Thu, 09 Mar 2006 01:15:53 -0500 Subject: [App_rpt] Iaxrpt In-Reply-To: <200603082123.20642.hwstar@rodgers.sdcoxmail.com> References: <200603051225.14765.hwstar@rodgers.sdcoxmail.com> <440B9863.5050006@lylix.net> <200603082123.20642.hwstar@rodgers.sdcoxmail.com> Message-ID: <20060309011553.8veccxo7kcwcsokk@lylix.net> Steve I'll check it out. I did actually get the originally posted Iaxrpt program to work, just needed the extra setup info for extensions.conf :) I had it running under Gentoo Linux on an x86-64 system (under x86 emulation). Also, I'm happy to report that the TDM20B is working without any problems here. I've had the system up since fixing the segfault issues. Eric NI3S Quoting Steve Rodgers : > Eric, > > There's a new version of the iaxrpt binary for FC4 on iaxrpt.qrvc.com which > fixes the issue you reported below. Also, I included some more setup > information on the site which might be useful to you. > > Steve, > WA6ZFT > > On Sunday 05 March 2006 18:03, Eric Tichansky wrote: >> Just testing iaxrpt... >> >> The Linux version is not appearing like the screenshot on the website. >> Instead of: >> >> [Connect][Hold][Speaker][Disconnect] >> >> I am seeing: >> >> [Dial][Hold][Transfer][Speaker][Hangup] >> >> Also, when inserting account information, and using Dail for connecting, >> my PBX spits out the follwoing: >> >> chan_iax2.c:7213 socket_read: Rejected connect attempt from >> 24.154.53.97, request 'NI3S at global' does not exist >> >> >> Any hints appreciated. Thanks! >> >> Eric NI3S > _______________________________________________ > App_rpt mailing list > App_rpt at lists.illiana.net > http://lists.illiana.net/mailman/listinfo/app_rpt > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From harfija at auburn.edu Wed Mar 15 19:11:02 2006 From: harfija at auburn.edu (James Harfield) Date: Wed, 15 Mar 2006 13:11:02 -0600 Subject: [App_rpt] COP Functions Message-ID: <44181266020000D6000108C9@TMIA1.AUBURN.EDU> I'm having a problem getting cop,6 to function correctly in PTT'ing the radio. I have phone_functions = phone_functions defined in rpt.conf and within the phone_functions heading I have: 88 = cop,6 defined with the other cop, ilink, and status functions. When connecting to my base I use the |P option instead of |D for phone control. The problem I'm having is that cop,6 will not activate the base to transmit. All the status commands, System Info, Time, Version, and the test tone cop,4 command work fine. The radio keys up, the appropriate information is sent, and the radio is unkeyed. But cop,6 will not key it. What I can do is manually key the radio and then use *88 (for cop,6) to talk and # when I want to end talking. I've tried to dig through the code and look at the difference between cop,6 and cop,4 for activating the base, but I'm quite confused as to why one can work and one cannot. Thanks, JRH From f1shs at free.fr Wed Mar 15 19:50:21 2006 From: f1shs at free.fr (f1shs) Date: Wed, 15 Mar 2006 20:50:21 +0100 Subject: [App_rpt] Quad radio pci card Message-ID: <000101c64869$b1e79cf0$0a00a8c0@morpheus> Hi, I would like to know how simple testing my quad radio pci card. f1shs -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.2.4/282 - Release Date: 15/03/2006 From telesistant at hotmail.com Wed Mar 15 20:21:33 2006 From: telesistant at hotmail.com (Jim Duuuude) Date: Wed, 15 Mar 2006 12:21:33 -0800 Subject: [App_rpt] COP Functions In-Reply-To: <44181266020000D6000108C9@TMIA1.AUBURN.EDU> Message-ID: Well, if you have cop,6 defined as *88, and you are comming in with the P option, and you have phone_functions = phone_functions, then you definitely should be able to key the radio from the phone by dialing *88 (from the phone and only from the phone). Jim, WB6NIL >From: "James Harfield" >Reply-To: Asterisk Repeater Controler >To: >Subject: [App_rpt] COP Functions >Date: Wed, 15 Mar 2006 13:11:02 -0600 >MIME-Version: 1.0 >Received: from lists.illiana.net ([207.227.243.140]) by >bay0-mc12-f14.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, >15 Mar 2006 11:12:02 -0800 >Received: (qmail 25119 invoked from network); 15 Mar 2006 19:12:00 -0000 >Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with SMTP; 15 >Mar 2006 19:12:00 -0000 >Received: (qmail 25092 invoked from network); 15 Mar 2006 19:11:52 -0000 >Received: from d1.duc.auburn.edu (131.204.2.2)by 0 with SMTP; 15 Mar 2006 >19:11:52 -0000 >Received: from TMIA1.AUBURN.EDU (tmia1.auburn.edu [131.204.3.30])by >d1.duc.auburn.edu (8.13.4/8.13.4) with ESMTP id k2FJBjbE013830for >; Wed, 15 Mar 2006 13:11:49 -0600 (CST) >Received: from zTMIA1-MTA by TMIA1.AUBURN.EDUwith Novell_GroupWise; Wed, 15 >Mar 2006 13:11:45 -0600 >X-Message-Info: 6sSXyD95QpVMWPCRYsLAxQFjIgPjv7anT7L4spyjmhA= >Return-Path: >Delivered-To: mailman-app_rpt at lists.illiana.net >X-Mailer: Novell GroupWise Internet Agent 7.0 X-BeenThere: >app_rpt at lists.illiana.net >X-Mailman-Version: 2.1.6 >Precedence: list >List-Id: Asterisk Repeater Controler >List-Unsubscribe: >, >List-Archive: >List-Post: >List-Help: >List-Subscribe: >, >Errors-To: app_rpt-bounces at lists.illiana.net >X-OriginalArrivalTime: 15 Mar 2006 19:12:03.0471 (UTC) >FILETIME=[57DDA1F0:01C64864] > >I'm having a problem getting cop,6 to function correctly in PTT'ing the >radio. > >I have phone_functions = phone_functions defined in rpt.conf and within the >phone_functions heading I have: >88 = cop,6 >defined with the other cop, ilink, and status functions. When connecting >to my base I use the |P option instead of |D for phone control. > >The problem I'm having is that cop,6 will not activate the base to >transmit. All the status commands, System Info, Time, Version, and the >test tone cop,4 command work fine. The radio keys up, the appropriate >information is sent, and the radio is unkeyed. But cop,6 will not key it. >What I can do is manually key the radio and then use *88 (for cop,6) to >talk and # when I want to end talking. I've tried to dig through the code >and look at the difference between cop,6 and cop,4 for activating the base, >but I'm quite confused as to why one can work and one cannot. > >Thanks, > >JRH > >_______________________________________________ >App_rpt mailing list >App_rpt at lists.illiana.net >http://lists.illiana.net/mailman/listinfo/app_rpt From harfija at auburn.edu Wed Mar 15 20:29:28 2006 From: harfija at auburn.edu (James Harfield) Date: Wed, 15 Mar 2006 14:29:28 -0600 Subject: [App_rpt] COP Functions In-Reply-To: References: <44181266020000D6000108C9@TMIA1.AUBURN.EDU> Message-ID: <441824C8020000D6000108F9@TMIA1.AUBURN.EDU> That's what I figure as well. I've tried Softphone, Cell phone, land phone. All the default ilink and status functions work, along with cop,4 to initiate the test tone. But cop,6 won't key the radio. >>> telesistant at hotmail.com 3/15/2006 2:21 PM >>> Well, if you have cop,6 defined as *88, and you are comming in with the P option, and you have phone_functions = phone_functions, then you definitely should be able to key the radio from the phone by dialing *88 (from the phone and only from the phone). Jim, WB6NIL >From: "James Harfield" >Reply-To: Asterisk Repeater Controler >To: >Subject: [App_rpt] COP Functions >Date: Wed, 15 Mar 2006 13:11:02 -0600 >MIME-Version: 1.0 >Received: from lists.illiana.net ([207.227.243.140]) by >bay0-mc12-f14.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, >15 Mar 2006 11:12:02 -0800 >Received: (qmail 25119 invoked from network); 15 Mar 2006 19:12:00 -0000 >Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with SMTP; 15 >Mar 2006 19:12:00 -0000 >Received: (qmail 25092 invoked from network); 15 Mar 2006 19:11:52 -0000 >Received: from d1.duc.auburn.edu (131.204.2.2)by 0 with SMTP; 15 Mar 2006 >19:11:52 -0000 >Received: from TMIA1.AUBURN.EDU (tmia1.auburn.edu [131.204.3.30])by >d1.duc.auburn.edu (8.13.4/8.13.4) with ESMTP id k2FJBjbE013830for >; Wed, 15 Mar 2006 13:11:49 -0600 (CST) >Received: from zTMIA1-MTA by TMIA1.AUBURN.EDUwith Novell_GroupWise; Wed, 15 >Mar 2006 13:11:45 -0600 >X-Message-Info: 6sSXyD95QpVMWPCRYsLAxQFjIgPjv7anT7L4spyjmhA= >Return-Path: >Delivered-To: mailman-app_rpt at lists.illiana.net >X-Mailer: Novell GroupWise Internet Agent 7.0 X-BeenThere: >app_rpt at lists.illiana.net >X-Mailman-Version: 2.1.6 >Precedence: list >List-Id: Asterisk Repeater Controler >List-Unsubscribe: >, >List-Archive: >List-Post: >List-Help: >List-Subscribe: >, >Errors-To: app_rpt-bounces at lists.illiana.net >X-OriginalArrivalTime: 15 Mar 2006 19:12:03.0471 (UTC) >FILETIME=[57DDA1F0:01C64864] > >I'm having a problem getting cop,6 to function correctly in PTT'ing the >radio. > >I have phone_functions = phone_functions defined in rpt.conf and within the >phone_functions heading I have: >88 = cop,6 >defined with the other cop, ilink, and status functions. When connecting >to my base I use the |P option instead of |D for phone control. > >The problem I'm having is that cop,6 will not activate the base to >transmit. All the status commands, System Info, Time, Version, and the >test tone cop,4 command work fine. The radio keys up, the appropriate >information is sent, and the radio is unkeyed. But cop,6 will not key it. >What I can do is manually key the radio and then use *88 (for cop,6) to >talk and # when I want to end talking. I've tried to dig through the code >and look at the difference between cop,6 and cop,4 for activating the base, >but I'm quite confused as to why one can work and one cannot. > >Thanks, > >JRH > >_______________________________________________ >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 Wed Mar 15 20:57:01 2006 From: hwstar at rodgers.sdcoxmail.com (hwstar at rodgers.sdcoxmail.com) Date: Wed, 15 Mar 2006 12:57:01 -0800 Subject: [App_rpt] COP Functions Message-ID: <20060315205701.KEAI3326.dukecmmtao03.coxmail.com@dukecmmtao03> It probably would be a good idea to attach your rpt.conf file to the thread. Steve WA6ZFT > > From: "James Harfield" > Date: 2006/03/15 Wed PM 12:29:28 PST > To: > Subject: Re: [App_rpt] COP Functions > > That's what I figure as well. I've tried Softphone, Cell phone, land phone. All the default ilink and status functions work, along with cop,4 to initiate the test tone. But cop,6 won't key the radio. > > >>> telesistant at hotmail.com 3/15/2006 2:21 PM >>> > Well, if you have cop,6 defined as *88, and you are comming in with the P > option, and you > have phone_functions = phone_functions, then you definitely should be able > to key the > radio from the phone by dialing *88 (from the phone and only from the > phone). > > Jim, WB6NIL > > > >From: "James Harfield" > >Reply-To: Asterisk Repeater Controler > >To: > >Subject: [App_rpt] COP Functions > >Date: Wed, 15 Mar 2006 13:11:02 -0600 > >MIME-Version: 1.0 > >Received: from lists.illiana.net ([207.227.243.140]) by > >bay0-mc12-f14.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, > >15 Mar 2006 11:12:02 -0800 > >Received: (qmail 25119 invoked from network); 15 Mar 2006 19:12:00 -0000 > >Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with SMTP; 15 > >Mar 2006 19:12:00 -0000 > >Received: (qmail 25092 invoked from network); 15 Mar 2006 19:11:52 -0000 > >Received: from d1.duc.auburn.edu (131.204.2.2)by 0 with SMTP; 15 Mar 2006 > >19:11:52 -0000 > >Received: from TMIA1.AUBURN.EDU (tmia1.auburn.edu [131.204.3.30])by > >d1.duc.auburn.edu (8.13.4/8.13.4) with ESMTP id k2FJBjbE013830for > >; Wed, 15 Mar 2006 13:11:49 -0600 (CST) > >Received: from zTMIA1-MTA by TMIA1.AUBURN.EDUwith Novell_GroupWise; Wed, 15 > >Mar 2006 13:11:45 -0600 > >X-Message-Info: 6sSXyD95QpVMWPCRYsLAxQFjIgPjv7anT7L4spyjmhA= > >Return-Path: > >Delivered-To: mailman-app_rpt at lists.illiana.net > >X-Mailer: Novell GroupWise Internet Agent 7.0 X-BeenThere: > >app_rpt at lists.illiana.net > >X-Mailman-Version: 2.1.6 > >Precedence: list > >List-Id: Asterisk Repeater Controler > >List-Unsubscribe: > >, > >List-Archive: > >List-Post: > >List-Help: > >List-Subscribe: > >, > >Errors-To: app_rpt-bounces at lists.illiana.net > >X-OriginalArrivalTime: 15 Mar 2006 19:12:03.0471 (UTC) > >FILETIME=[57DDA1F0:01C64864] > > > >I'm having a problem getting cop,6 to function correctly in PTT'ing the > >radio. > > > >I have phone_functions = phone_functions defined in rpt.conf and within the > >phone_functions heading I have: > >88 = cop,6 > >defined with the other cop, ilink, and status functions. When connecting > >to my base I use the |P option instead of |D for phone control. > > > >The problem I'm having is that cop,6 will not activate the base to > >transmit. All the status commands, System Info, Time, Version, and the > >test tone cop,4 command work fine. The radio keys up, the appropriate > >information is sent, and the radio is unkeyed. But cop,6 will not key it. > >What I can do is manually key the radio and then use *88 (for cop,6) to > >talk and # when I want to end talking. I've tried to dig through the code > >and look at the difference between cop,6 and cop,4 for activating the base, > >but I'm quite confused as to why one can work and one cannot. > > > >Thanks, > > > >JRH > > > >_______________________________________________ > >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 Wed Mar 15 20:57:47 2006 From: hwstar at rodgers.sdcoxmail.com (hwstar at rodgers.sdcoxmail.com) Date: Wed, 15 Mar 2006 12:57:47 -0800 Subject: [App_rpt] Quad radio pci card Message-ID: <20060315205747.KFAD3326.dukecmmtao03.coxmail.com@dukecmmtao03> What do you need to test? Steve WA6ZFT > > From: "f1shs" > Date: 2006/03/15 Wed AM 11:50:21 PST > To: > Subject: [App_rpt] Quad radio pci card > > Hi, > > I would like to know how simple testing my quad radio pci card. > > f1shs > > -- > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.1.385 / Virus Database: 268.2.4/282 - Release Date: 15/03/2006 > > > > _______________________________________________ > App_rpt mailing list > App_rpt at lists.illiana.net > http://lists.illiana.net/mailman/listinfo/app_rpt > From harfija at auburn.edu Wed Mar 15 22:18:39 2006 From: harfija at auburn.edu (James Harfield) Date: Wed, 15 Mar 2006 16:18:39 -0600 Subject: [App_rpt] COP Functions Message-ID: <44183E5E020000D600010947@TMIA1.AUBURN.EDU> As requested rpt.conf: [1999] ; Name of First Repeater rxchannel = Zap/1 ; Rx audio/signalling channel ; Note: if you use a unified interface (tx/rx on one channel), only ; specify the rxchannel and the txchannel will be assumed from the rxchannel functions=functions ; Repeater Function Table ; ; Added phone_functions=phone_functions ; phone_functions = phone_functions ;phone functions table link_functions=link-functions ; Link Function Table telemetry=telemetry ; Telemetry descriptions wait_times=wait-times ; Wait times context = radio ; dialing context for phone callerid = "Your Repeater" <6198192562> ; callerid for phone calls idrecording = /etc/asterisk/id ; id recording accountcode=RADIO ; account code (optional) hangtime=1000 ; squelch tail hang time (in ms) (optional) totime=90000 ; transmit time-out time (in ms) (optional) idtime=180000 ; id interval time (in ms) (optional) ; ;Added duplex=2 ; ;duplex=2 ; 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/r ; Talkover ID (optional) default is none unlinkedct=ct2 ; unlinked courtesy tone (optional) default is none ; ; Repeater function table for node 010 ; [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 6=autopatchup ; Autopatch up 0=autopatchdn ; Autopatch down ; ;Added cop,6 in this context just to see if it would recognize cop,6 ; 88=cop,6 ; PTT Radio 99=cop,4 ; Audio test tone ; ;Added phone_functions table for the phone_functions=phone_functions ; [phone_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 ; ;Added cop,1 - cop,6 for testing purposes. ; 84=cop,1 ;warm boot 85=cop,2 ;system enable 86=cop,3 ;system disable 87=cop,5 ;debug mode 88=cop,6 ;system PTT 6=autopatchup ; Autopatch up 0=autopatchdn ; Autopatch down 99=cop,4 ; Audio test tone ; ; 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 7=ilink,5 ; Link status 80=status,1 ; System info 81=status,2 ; Time 82=status,3 ; app_rpt.c Version 6=autopatchup ; Autopatch up 0=autopatchdn ; Autopatch down 84=cop,1 ;warm boot 85=cop,2 ;system enable 86=cop,3 ;system disable 87=cop,5 ;debug mode 88=cop,6 ;system PTT 99=cop,4 ; Audio 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,2048) 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,75,2048)(0,0,75,0)(1209,0,75,2048); remotemon=|t(1209,0,75,2048) cmdmode=|t(900,903,200,2048) functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) ; ; Morse code parameters, these are common to all repeaters. ; [morse] speed=20 ; Approximate speed in WPM frequency=800 ; Morse Telemetry Frequency amplitude=4096 ; Morse Telemetry Amplitude idfrequency=1064 ; Morse ID Frequency idamplitude=3072 ; 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=1750 ; Time to wait before sending most telemetry idwait=500 ; Time to wait before starting ID unkeywait=1000 ; Time to wait after unkey before sending CT's and link telemetry calltermwait=1500 ; Time to wait before announcing "call terminated" ; ; This is where you define your nodes which cam be connected to. ; [nodes] 1999 = radio at 127.0.0.1/1999 ; This must be changed to your IP address We added cop,6 to the regular functions table and the link functions table just to test and see if it was picking up only those functions instead, since there was a comment that if link functions were enabled then the remote user would only have access to them. Here is the extensions.conf for connecting to the radio: exten => 305,1,Rpt,1999|P ulaw is allowed in both IAX.conf and SIP.conf that we are using to dial the radio. Does this need to be changed as well? Trying to add as much info I can think of. Thanks, JRH >>> hwstar at rodgers.sdcoxmail.com 03/15/06 2:57 PM >>> It probably would be a good idea to attach your rpt.conf file to the thread. Steve WA6ZFT > > From: "James Harfield" > Date: 2006/03/15 Wed PM 12:29:28 PST > To: > Subject: Re: [App_rpt] COP Functions > > That's what I figure as well. I've tried Softphone, Cell phone, land phone. All the default ilink and status functions work, along with cop,4 to initiate the test tone. But cop,6 won't key the radio. > > >>> telesistant at hotmail.com 3/15/2006 2:21 PM >>> > Well, if you have cop,6 defined as *88, and you are comming in with the P > option, and you > have phone_functions = phone_functions, then you definitely should be able > to key the > radio from the phone by dialing *88 (from the phone and only from the > phone). > > Jim, WB6NIL > > > >From: "James Harfield" > >Reply-To: Asterisk Repeater Controler > >To: > >Subject: [App_rpt] COP Functions > >Date: Wed, 15 Mar 2006 13:11:02 -0600 > >MIME-Version: 1.0 > >Received: from lists.illiana.net ([207.227.243.140]) by > >bay0-mc12-f14.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, > >15 Mar 2006 11:12:02 -0800 > >Received: (qmail 25119 invoked from network); 15 Mar 2006 19:12:00 -0000 > >Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with SMTP; 15 > >Mar 2006 19:12:00 -0000 > >Received: (qmail 25092 invoked from network); 15 Mar 2006 19:11:52 -0000 > >Received: from d1.duc.auburn.edu (131.204.2.2)by 0 with SMTP; 15 Mar 2006 > >19:11:52 -0000 > >Received: from TMIA1.AUBURN.EDU (tmia1.auburn.edu [131.204.3.30])by > >d1.duc.auburn.edu (8.13.4/8.13.4) with ESMTP id k2FJBjbE013830for > >; Wed, 15 Mar 2006 13:11:49 -0600 (CST) > >Received: from zTMIA1-MTA by TMIA1.AUBURN.EDUwith Novell_GroupWise; Wed, 15 > >Mar 2006 13:11:45 -0600 > >X-Message-Info: 6sSXyD95QpVMWPCRYsLAxQFjIgPjv7anT7L4spyjmhA= > >Return-Path: > >Delivered-To: mailman-app_rpt at lists.illiana.net > >X-Mailer: Novell GroupWise Internet Agent 7.0 X-BeenThere: > >app_rpt at lists.illiana.net > >X-Mailman-Version: 2.1.6 > >Precedence: list > >List-Id: Asterisk Repeater Controler > >List-Unsubscribe: > >, > >List-Archive: > >List-Post: > >List-Help: > >List-Subscribe: > >, > >Errors-To: app_rpt-bounces at lists.illiana.net > >X-OriginalArrivalTime: 15 Mar 2006 19:12:03.0471 (UTC) > >FILETIME=[57DDA1F0:01C64864] > > > >I'm having a problem getting cop,6 to function correctly in PTT'ing the > >radio. > > > >I have phone_functions = phone_functions defined in rpt.conf and within the > >phone_functions heading I have: > >88 = cop,6 > >defined with the other cop, ilink, and status functions. When connecting > >to my base I use the |P option instead of |D for phone control. > > > >The problem I'm having is that cop,6 will not activate the base to > >transmit. All the status commands, System Info, Time, Version, and the > >test tone cop,4 command work fine. The radio keys up, the appropriate > >information is sent, and the radio is unkeyed. But cop,6 will not key it. > >What I can do is manually key the radio and then use *88 (for cop,6) to > >talk and # when I want to end talking. I've tried to dig through the code > >and look at the difference between cop,6 and cop,4 for activating the base, > >but I'm quite confused as to why one can work and one cannot. > > > >Thanks, > > > >JRH > > > >_______________________________________________ > >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 Thu Mar 16 04:41:22 2006 From: hwstar at rodgers.sdcoxmail.com (Steve Rodgers) Date: Wed, 15 Mar 2006 20:41:22 -0800 Subject: [App_rpt] COP Functions In-Reply-To: <44183E5E020000D600010947@TMIA1.AUBURN.EDU> References: <44183E5E020000D600010947@TMIA1.AUBURN.EDU> Message-ID: <200603152041.22786.hwstar@rodgers.sdcoxmail.com> James, I tried your config file on my system (had to change the node and the zap channel, but everything else remained the same), and *88 keyed the transmitter over the phone as it should be. Now I'm scratching my head.... The next thing to try: Issue "rpt debug level 1" from the real asterisk console ( asterisk -vvvvvvc, and not asterisk -r) and see if you can see the DTMF digits being processed by app_rpt. You should see something like this: @@@@ Digits collected: 88, source: 0 @@@@ action: cop, param = 6 @@@@ table index i = 0 BTW: cop.6 has no effect when dialed on a radio or link channel. Cop,6 is for use on a phone dial-in only. I'd suggest removing these from your other function tables. Steve, WA6ZFT On Wednesday 15 March 2006 14:18, James Harfield wrote: > As requested rpt.conf: > > [1999] ; Name of First Repeater > > rxchannel = Zap/1 ; Rx audio/signalling channel > ; Note: if you use a unified interface (tx/rx on one channel), only > ; specify the rxchannel and the txchannel will be assumed from the > rxchannel > functions=functions ; Repeater Function Table > ; > ; Added phone_functions=phone_functions > ; > phone_functions = phone_functions ;phone functions table > link_functions=link-functions ; Link Function Table > telemetry=telemetry ; Telemetry descriptions > wait_times=wait-times ; Wait times > context = radio ; dialing context for phone > callerid = "Your Repeater" <6198192562> ; callerid for phone calls > idrecording = /etc/asterisk/id ; id recording > accountcode=RADIO ; account code (optional) > hangtime=1000 ; squelch tail hang time (in ms) > (optional) > totime=90000 ; transmit time-out time (in ms) > (optional) > idtime=180000 ; id interval time (in ms) > (optional) > ; > ;Added duplex=2 > ; > ;duplex=2 > > ; 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/r ; Talkover ID (optional) default > is none > unlinkedct=ct2 ; unlinked courtesy tone > (optional) default is none > > ; > ; Repeater function table for node 010 > ; > > [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 > > 6=autopatchup ; Autopatch up > 0=autopatchdn ; Autopatch down > > ; > ;Added cop,6 in this context just to see if it would recognize cop,6 > ; > 88=cop,6 ; PTT Radio > 99=cop,4 ; Audio test tone > > > ; > ;Added phone_functions table for the phone_functions=phone_functions > ; > [phone_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 > > > ; > ;Added cop,1 - cop,6 for testing purposes. > ; > 84=cop,1 ;warm boot > 85=cop,2 ;system enable > 86=cop,3 ;system disable > 87=cop,5 ;debug mode > 88=cop,6 ;system PTT > > 6=autopatchup ; Autopatch up > 0=autopatchdn ; Autopatch down > > 99=cop,4 ; Audio test tone > > > ; > ; 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 > 7=ilink,5 ; Link status > > > 80=status,1 ; System info > 81=status,2 ; Time > 82=status,3 ; app_rpt.c Version > > > 6=autopatchup ; Autopatch up > 0=autopatchdn ; Autopatch down > 84=cop,1 ;warm boot > 85=cop,2 ;system enable > 86=cop,3 ;system disable > 87=cop,5 ;debug mode > 88=cop,6 ;system PTT > > 99=cop,4 ; Audio 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,2048) > 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,75,2048)(0,0,75,0)(1209,0,75,2048); > remotemon=|t(1209,0,75,2048) > cmdmode=|t(900,903,200,2048) > functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > > ; > ; Morse code parameters, these are common to all repeaters. > ; > > [morse] > > speed=20 ; Approximate speed in WPM > frequency=800 ; Morse Telemetry Frequency > amplitude=4096 ; Morse Telemetry Amplitude > idfrequency=1064 ; Morse ID Frequency > idamplitude=3072 ; 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=1750 ; Time to wait before sending > most telemetry > idwait=500 ; Time to wait before starting > ID > unkeywait=1000 ; Time to wait after unkey > before sending CT's and link telemetry > calltermwait=1500 ; Time to wait before announcing > "call terminated" > > ; > ; This is where you define your nodes which cam be connected to. > ; > > [nodes] > 1999 = radio at 127.0.0.1/1999 ; This must be changed to your IP > address > > We added cop,6 to the regular functions table and the link functions > table just to test and see if it was picking up only those functions > instead, since there was a comment that if link functions were enabled > then the remote user would only have access to them. > > Here is the extensions.conf for connecting to the radio: > > exten => 305,1,Rpt,1999|P > > ulaw is allowed in both IAX.conf and SIP.conf that we are using to dial > the radio. Does this need to be changed as well? Trying to add as much > info I can think of. > > Thanks, > > JRH > > >>> hwstar at rodgers.sdcoxmail.com 03/15/06 2:57 PM >>> > > It probably would be a good idea to attach your rpt.conf file to the > thread. > > Steve > WA6ZFT > > > From: "James Harfield" > > Date: 2006/03/15 Wed PM 12:29:28 PST > > To: > > Subject: Re: [App_rpt] COP Functions > > > > That's what I figure as well. I've tried Softphone, Cell phone, land > > phone. All the default ilink and status functions work, along with > cop,4 to initiate the test tone. But cop,6 won't key the radio. > > > >>> telesistant at hotmail.com 3/15/2006 2:21 PM >>> > > > > Well, if you have cop,6 defined as *88, and you are comming in with > > the P > > > option, and you > > have phone_functions = phone_functions, then you definitely should be > > able > > > to key the > > radio from the phone by dialing *88 (from the phone and only from the > > phone). > > > > Jim, WB6NIL > > > > >From: "James Harfield" > > >Reply-To: Asterisk Repeater Controler > > >To: > > >Subject: [App_rpt] COP Functions > > >Date: Wed, 15 Mar 2006 13:11:02 -0600 > > >MIME-Version: 1.0 > > >Received: from lists.illiana.net ([207.227.243.140]) by > > >bay0-mc12-f14.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.1830); > > Wed, > > > >15 Mar 2006 11:12:02 -0800 > > >Received: (qmail 25119 invoked from network); 15 Mar 2006 19:12:00 > > -0000 > > > >Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with > > SMTP; 15 > > > >Mar 2006 19:12:00 -0000 > > >Received: (qmail 25092 invoked from network); 15 Mar 2006 19:11:52 > > -0000 > > > >Received: from d1.duc.auburn.edu (131.204.2.2)by 0 with SMTP; 15 Mar > > 2006 > > > >19:11:52 -0000 > > >Received: from TMIA1.AUBURN.EDU (tmia1.auburn.edu [131.204.3.30])by > > >d1.duc.auburn.edu (8.13.4/8.13.4) with ESMTP id k2FJBjbE013830for > > >; Wed, 15 Mar 2006 13:11:49 -0600 (CST) > > >Received: from zTMIA1-MTA by TMIA1.AUBURN.EDUwith Novell_GroupWise; > > Wed, 15 > > > >Mar 2006 13:11:45 -0600 > > >X-Message-Info: 6sSXyD95QpVMWPCRYsLAxQFjIgPjv7anT7L4spyjmhA= > > >Return-Path: > > >Delivered-To: mailman-app_rpt at lists.illiana.net > > >X-Mailer: Novell GroupWise Internet Agent 7.0 X-BeenThere: > > >app_rpt at lists.illiana.net > > >X-Mailman-Version: 2.1.6 > > >Precedence: list > > >List-Id: Asterisk Repeater Controler > > >List-Unsubscribe: > > > >, >t at lists.illiana.net?subject=unsubscribe> > > > > >List-Archive: > > >List-Post: > > >List-Help: > > >List-Subscribe: > > > >, >t at lists.illiana.net?subject=subscribe> > > > > >Errors-To: app_rpt-bounces at lists.illiana.net > > >X-OriginalArrivalTime: 15 Mar 2006 19:12:03.0471 (UTC) > > >FILETIME=[57DDA1F0:01C64864] > > > > > >I'm having a problem getting cop,6 to function correctly in PTT'ing > > the > > > >radio. > > > > > >I have phone_functions = phone_functions defined in rpt.conf and > > within the > > > >phone_functions heading I have: > > >88 = cop,6 > > >defined with the other cop, ilink, and status functions. When > > connecting > > > >to my base I use the |P option instead of |D for phone control. > > > > > >The problem I'm having is that cop,6 will not activate the base to > > >transmit. All the status commands, System Info, Time, Version, and > > the > > > >test tone cop,4 command work fine. The radio keys up, the > > appropriate > > > >information is sent, and the radio is unkeyed. But cop,6 will not > > key it. > > > >What I can do is manually key the radio and then use *88 (for cop,6) > > to > > > >talk and # when I want to end talking. I've tried to dig through the > > code > > > >and look at the difference between cop,6 and cop,4 for activating the > > base, > > > >but I'm quite confused as to why one can work and one cannot. > > > > > >Thanks, > > > > > >JRH > > > > > >_______________________________________________ > > >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 f1shs at free.fr Thu Mar 16 08:35:57 2006 From: f1shs at free.fr (f1shs at free.fr) Date: Thu, 16 Mar 2006 09:35:57 +0100 Subject: [App_rpt] App_rpt Digest, Vol 3, Issue 5 In-Reply-To: References: Message-ID: <1142498157.4419236d4674e@imp8-g19.free.fr> Selon app_rpt-request at lists.illiana.net: > Send App_rpt mailing list submissions to > app_rpt at lists.illiana.net > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.illiana.net/mailman/listinfo/app_rpt > or, via email, send a message with subject or body 'help' to > app_rpt-request at lists.illiana.net > > You can reach the person managing the list at > app_rpt-owner at lists.illiana.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of App_rpt digest..." > > > Today's Topics: > > 1. Re: COP Functions (hwstar at rodgers.sdcoxmail.com) > 2. Re: Quad radio pci card (hwstar at rodgers.sdcoxmail.com) > 3. Re: COP Functions (James Harfield) > 4. Re: COP Functions (Steve Rodgers) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 15 Mar 2006 12:57:01 -0800 > From: > Subject: Re: [App_rpt] COP Functions > To: Asterisk Repeater Controler > Message-ID: > <20060315205701.KEAI3326.dukecmmtao03.coxmail.com at dukecmmtao03> > Content-Type: text/plain; charset=ISO-8859-1 > > It probably would be a good idea to attach your rpt.conf file to the thread. > > Steve > WA6ZFT > > > > > From: "James Harfield" > > Date: 2006/03/15 Wed PM 12:29:28 PST > > To: > > Subject: Re: [App_rpt] COP Functions > > > > That's what I figure as well. I've tried Softphone, Cell phone, land > phone. All the default ilink and status functions work, along with cop,4 to > initiate the test tone. But cop,6 won't key the radio. > > > > >>> telesistant at hotmail.com 3/15/2006 2:21 PM >>> > > Well, if you have cop,6 defined as *88, and you are comming in with the P > > option, and you > > have phone_functions = phone_functions, then you definitely should be able > > to key the > > radio from the phone by dialing *88 (from the phone and only from the > > phone). > > > > Jim, WB6NIL > > > > > > >From: "James Harfield" > > >Reply-To: Asterisk Repeater Controler > > >To: > > >Subject: [App_rpt] COP Functions > > >Date: Wed, 15 Mar 2006 13:11:02 -0600 > > >MIME-Version: 1.0 > > >Received: from lists.illiana.net ([207.227.243.140]) by > > >bay0-mc12-f14.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, > > >15 Mar 2006 11:12:02 -0800 > > >Received: (qmail 25119 invoked from network); 15 Mar 2006 19:12:00 -0000 > > >Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with SMTP; > 15 > > >Mar 2006 19:12:00 -0000 > > >Received: (qmail 25092 invoked from network); 15 Mar 2006 19:11:52 -0000 > > >Received: from d1.duc.auburn.edu (131.204.2.2)by 0 with SMTP; 15 Mar 2006 > > >19:11:52 -0000 > > >Received: from TMIA1.AUBURN.EDU (tmia1.auburn.edu [131.204.3.30])by > > >d1.duc.auburn.edu (8.13.4/8.13.4) with ESMTP id k2FJBjbE013830for > > >; Wed, 15 Mar 2006 13:11:49 -0600 (CST) > > >Received: from zTMIA1-MTA by TMIA1.AUBURN.EDUwith Novell_GroupWise; Wed, > 15 > > >Mar 2006 13:11:45 -0600 > > >X-Message-Info: 6sSXyD95QpVMWPCRYsLAxQFjIgPjv7anT7L4spyjmhA= > > >Return-Path: > > >Delivered-To: mailman-app_rpt at lists.illiana.net > > >X-Mailer: Novell GroupWise Internet Agent 7.0 X-BeenThere: > > >app_rpt at lists.illiana.net > > >X-Mailman-Version: 2.1.6 > > >Precedence: list > > >List-Id: Asterisk Repeater Controler > > >List-Unsubscribe: > > > >, > > >List-Archive: > > >List-Post: > > >List-Help: > > >List-Subscribe: > > > >, > > >Errors-To: app_rpt-bounces at lists.illiana.net > > >X-OriginalArrivalTime: 15 Mar 2006 19:12:03.0471 (UTC) > > >FILETIME=[57DDA1F0:01C64864] > > > > > >I'm having a problem getting cop,6 to function correctly in PTT'ing the > > >radio. > > > > > >I have phone_functions = phone_functions defined in rpt.conf and within > the > > >phone_functions heading I have: > > >88 = cop,6 > > >defined with the other cop, ilink, and status functions. When connecting > > >to my base I use the |P option instead of |D for phone control. > > > > > >The problem I'm having is that cop,6 will not activate the base to > > >transmit. All the status commands, System Info, Time, Version, and the > > >test tone cop,4 command work fine. The radio keys up, the appropriate > > >information is sent, and the radio is unkeyed. But cop,6 will not key it. > > >What I can do is manually key the radio and then use *88 (for cop,6) to > > >talk and # when I want to end talking. I've tried to dig through the code > > >and look at the difference between cop,6 and cop,4 for activating the > base, > > >but I'm quite confused as to why one can work and one cannot. > > > > > >Thanks, > > > > > >JRH > > > > > >_______________________________________________ > > >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 > > > > > > ------------------------------ > > Message: 2 I've build a setup as describted in the installation procedure, but nothing work. I've used the exemples_conf files as a startup setup of asterisk + app_rpt... Is there some command to test if the pci card is functionning ? > Date: Wed, 15 Mar 2006 12:57:47 -0800 > From: > Subject: Re: [App_rpt] Quad radio pci card > To: Asterisk Repeater Controler > Message-ID: > <20060315205747.KFAD3326.dukecmmtao03.coxmail.com at dukecmmtao03> > Content-Type: text/plain; charset=ISO-8859-1 > > What do you need to test? > > Steve WA6ZFT > > > > > From: "f1shs" > > Date: 2006/03/15 Wed AM 11:50:21 PST > > To: > > Subject: [App_rpt] Quad radio pci card > > > > Hi, > > > > I would like to know how simple testing my quad radio pci card. > > > > f1shs > > > > -- > > No virus found in this outgoing message. > > Checked by AVG Free Edition. > > Version: 7.1.385 / Virus Database: 268.2.4/282 - Release Date: 15/03/2006 > > > > > > > > _______________________________________________ > > App_rpt mailing list > > App_rpt at lists.illiana.net > > http://lists.illiana.net/mailman/listinfo/app_rpt > > > > > > ------------------------------ > > Message: 3 > Date: Wed, 15 Mar 2006 16:18:39 -0600 > From: "James Harfield" > Subject: Re: [App_rpt] COP Functions > To: > Message-ID: <44183E5E020000D600010947 at TMIA1.AUBURN.EDU> > Content-Type: text/plain; charset=US-ASCII > > As requested rpt.conf: > > [1999] ; Name of First Repeater > > rxchannel = Zap/1 ; Rx audio/signalling channel > ; Note: if you use a unified interface (tx/rx on one channel), only > ; specify the rxchannel and the txchannel will be assumed from the > rxchannel > functions=functions ; Repeater Function Table > ; > ; Added phone_functions=phone_functions > ; > phone_functions = phone_functions ;phone functions table > link_functions=link-functions ; Link Function Table > telemetry=telemetry ; Telemetry descriptions > wait_times=wait-times ; Wait times > context = radio ; dialing context for phone > callerid = "Your Repeater" <6198192562> ; callerid for phone calls > idrecording = /etc/asterisk/id ; id recording > accountcode=RADIO ; account code (optional) > hangtime=1000 ; squelch tail hang time (in ms) > (optional) > totime=90000 ; transmit time-out time (in ms) > (optional) > idtime=180000 ; id interval time (in ms) > (optional) > ; > ;Added duplex=2 > ; > ;duplex=2 > > ; 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/r ; Talkover ID (optional) default > is none > unlinkedct=ct2 ; unlinked courtesy tone > (optional) default is none > > ; > ; Repeater function table for node 010 > ; > > [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 > > 6=autopatchup ; Autopatch up > 0=autopatchdn ; Autopatch down > > ; > ;Added cop,6 in this context just to see if it would recognize cop,6 > ; > 88=cop,6 ; PTT Radio > 99=cop,4 ; Audio test tone > > > ; > ;Added phone_functions table for the phone_functions=phone_functions > ; > [phone_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 > > > ; > ;Added cop,1 - cop,6 for testing purposes. > ; > 84=cop,1 ;warm boot > 85=cop,2 ;system enable > 86=cop,3 ;system disable > 87=cop,5 ;debug mode > 88=cop,6 ;system PTT > > 6=autopatchup ; Autopatch up > 0=autopatchdn ; Autopatch down > > 99=cop,4 ; Audio test tone > > > ; > ; 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 > 7=ilink,5 ; Link status > > > 80=status,1 ; System info > 81=status,2 ; Time > 82=status,3 ; app_rpt.c Version > > > 6=autopatchup ; Autopatch up > 0=autopatchdn ; Autopatch down > 84=cop,1 ;warm boot > 85=cop,2 ;system enable > 86=cop,3 ;system disable > 87=cop,5 ;debug mode > 88=cop,6 ;system PTT > > 99=cop,4 ; Audio 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,2048) > 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,75,2048)(0,0,75,0)(1209,0,75,2048); > remotemon=|t(1209,0,75,2048) > cmdmode=|t(900,903,200,2048) > functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > > ; > ; Morse code parameters, these are common to all repeaters. > ; > > [morse] > > speed=20 ; Approximate speed in WPM > frequency=800 ; Morse Telemetry Frequency > amplitude=4096 ; Morse Telemetry Amplitude > idfrequency=1064 ; Morse ID Frequency > idamplitude=3072 ; 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=1750 ; Time to wait before sending > most telemetry > idwait=500 ; Time to wait before starting > ID > unkeywait=1000 ; Time to wait after unkey > before sending CT's and link telemetry > calltermwait=1500 ; Time to wait before announcing > "call terminated" > > ; > ; This is where you define your nodes which cam be connected to. > ; > > [nodes] > 1999 = radio at 127.0.0.1/1999 ; This must be changed to your IP > address > > We added cop,6 to the regular functions table and the link functions > table just to test and see if it was picking up only those functions > instead, since there was a comment that if link functions were enabled > then the remote user would only have access to them. > > Here is the extensions.conf for connecting to the radio: > > exten => 305,1,Rpt,1999|P > > ulaw is allowed in both IAX.conf and SIP.conf that we are using to dial > the radio. Does this need to be changed as well? Trying to add as much > info I can think of. > > Thanks, > > JRH > > > >>> hwstar at rodgers.sdcoxmail.com 03/15/06 2:57 PM >>> > It probably would be a good idea to attach your rpt.conf file to the > thread. > > Steve > WA6ZFT > > > > > From: "James Harfield" > > Date: 2006/03/15 Wed PM 12:29:28 PST > > To: > > Subject: Re: [App_rpt] COP Functions > > > > That's what I figure as well. I've tried Softphone, Cell phone, land > phone. All the default ilink and status functions work, along with > cop,4 to initiate the test tone. But cop,6 won't key the radio. > > > > >>> telesistant at hotmail.com 3/15/2006 2:21 PM >>> > > Well, if you have cop,6 defined as *88, and you are comming in with > the P > > option, and you > > have phone_functions = phone_functions, then you definitely should be > able > > to key the > > radio from the phone by dialing *88 (from the phone and only from the > > phone). > > > > Jim, WB6NIL > > > > > > >From: "James Harfield" > > >Reply-To: Asterisk Repeater Controler > > >To: > > >Subject: [App_rpt] COP Functions > > >Date: Wed, 15 Mar 2006 13:11:02 -0600 > > >MIME-Version: 1.0 > > >Received: from lists.illiana.net ([207.227.243.140]) by > > >bay0-mc12-f14.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.1830); > Wed, > > >15 Mar 2006 11:12:02 -0800 > > >Received: (qmail 25119 invoked from network); 15 Mar 2006 19:12:00 > -0000 > > >Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with > SMTP; 15 > > >Mar 2006 19:12:00 -0000 > > >Received: (qmail 25092 invoked from network); 15 Mar 2006 19:11:52 > -0000 > > >Received: from d1.duc.auburn.edu (131.204.2.2)by 0 with SMTP; 15 Mar > 2006 > > >19:11:52 -0000 > > >Received: from TMIA1.AUBURN.EDU (tmia1.auburn.edu [131.204.3.30])by > > >d1.duc.auburn.edu (8.13.4/8.13.4) with ESMTP id k2FJBjbE013830for > > >; Wed, 15 Mar 2006 13:11:49 -0600 (CST) > > >Received: from zTMIA1-MTA by TMIA1.AUBURN.EDUwith Novell_GroupWise; > Wed, 15 > > >Mar 2006 13:11:45 -0600 > > >X-Message-Info: 6sSXyD95QpVMWPCRYsLAxQFjIgPjv7anT7L4spyjmhA= > > >Return-Path: > > >Delivered-To: mailman-app_rpt at lists.illiana.net > > >X-Mailer: Novell GroupWise Internet Agent 7.0 X-BeenThere: > > >app_rpt at lists.illiana.net > > >X-Mailman-Version: 2.1.6 > > >Precedence: list > > >List-Id: Asterisk Repeater Controler > > >List-Unsubscribe: > > > >, > > >List-Archive: > > >List-Post: > > >List-Help: > > >List-Subscribe: > > > >, > > >Errors-To: app_rpt-bounces at lists.illiana.net > > >X-OriginalArrivalTime: 15 Mar 2006 19:12:03.0471 (UTC) > > >FILETIME=[57DDA1F0:01C64864] > > > > > >I'm having a problem getting cop,6 to function correctly in PTT'ing > the > > >radio. > > > > > >I have phone_functions = phone_functions defined in rpt.conf and > within the > > >phone_functions heading I have: > > >88 = cop,6 > > >defined with the other cop, ilink, and status functions. When > connecting > > >to my base I use the |P option instead of |D for phone control. > > > > > >The problem I'm having is that cop,6 will not activate the base to > > >transmit. All the status commands, System Info, Time, Version, and > the > > >test tone cop,4 command work fine. The radio keys up, the > appropriate > > >information is sent, and the radio is unkeyed. But cop,6 will not > key it. > > >What I can do is manually key the radio and then use *88 (for cop,6) > to > > >talk and # when I want to end talking. I've tried to dig through the > code > > >and look at the difference between cop,6 and cop,4 for activating the > base, > > >but I'm quite confused as to why one can work and one cannot. > > > > > >Thanks, > > > > > >JRH > > > > > >_______________________________________________ > > >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 > > > > ------------------------------ > > Message: 4 > Date: Wed, 15 Mar 2006 20:41:22 -0800 > From: Steve Rodgers > Subject: Re: [App_rpt] COP Functions > To: Asterisk Repeater Controler > Message-ID: <200603152041.22786.hwstar at rodgers.sdcoxmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > James, > > I tried your config file on my system (had to change the node and the zap > channel, but everything else remained the same), and *88 keyed the > transmitter over the phone as it should be. Now I'm scratching my head.... > > The next thing to try: > > Issue "rpt debug level 1" from the real asterisk console ( asterisk > -vvvvvvc, > and not asterisk -r) and see if you can see the DTMF digits being processed > by app_rpt. > > You should see something like this: > > @@@@ Digits collected: 88, source: 0 > @@@@ action: cop, param = 6 > @@@@ table index i = 0 > > > BTW: cop.6 has no effect when dialed on a radio or link channel. Cop,6 is for > use on a phone dial-in only. I'd suggest removing these from your other > function tables. > > Steve, > WA6ZFT > > > > > On Wednesday 15 March 2006 14:18, James Harfield wrote: > > As requested rpt.conf: > > > > [1999] ; Name of First Repeater > > > > rxchannel = Zap/1 ; Rx audio/signalling channel > > ; Note: if you use a unified interface (tx/rx on one channel), only > > ; specify the rxchannel and the txchannel will be assumed from the > > rxchannel > > functions=functions ; Repeater Function Table > > ; > > ; Added phone_functions=phone_functions > > ; > > phone_functions = phone_functions ;phone functions table > > link_functions=link-functions ; Link Function Table > > telemetry=telemetry ; Telemetry descriptions > > wait_times=wait-times ; Wait times > > context = radio ; dialing context for phone > > callerid = "Your Repeater" <6198192562> ; callerid for phone calls > > idrecording = /etc/asterisk/id ; id recording > > accountcode=RADIO ; account code (optional) > > hangtime=1000 ; squelch tail hang time (in ms) > > (optional) > > totime=90000 ; transmit time-out time (in ms) > > (optional) > > idtime=180000 ; id interval time (in ms) > > (optional) > > ; > > ;Added duplex=2 > > ; > > ;duplex=2 > > > > ; 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/r ; Talkover ID (optional) default > > is none > > unlinkedct=ct2 ; unlinked courtesy tone > > (optional) default is none > > > > ; > > ; Repeater function table for node 010 > > ; > > > > [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 > > > > 6=autopatchup ; Autopatch up > > 0=autopatchdn ; Autopatch down > > > > ; > > ;Added cop,6 in this context just to see if it would recognize cop,6 > > ; > > 88=cop,6 ; PTT Radio > > 99=cop,4 ; Audio test tone > > > > > > ; > > ;Added phone_functions table for the phone_functions=phone_functions > > ; > > [phone_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 > > > > > > ; > > ;Added cop,1 - cop,6 for testing purposes. > > ; > > 84=cop,1 ;warm boot > > 85=cop,2 ;system enable > > 86=cop,3 ;system disable > > 87=cop,5 ;debug mode > > 88=cop,6 ;system PTT > > > > 6=autopatchup ; Autopatch up > > 0=autopatchdn ; Autopatch down > > > > 99=cop,4 ; Audio test tone > > > > > > ; > > ; 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 > > 7=ilink,5 ; Link status > > > > > > 80=status,1 ; System info > > 81=status,2 ; Time > > 82=status,3 ; app_rpt.c Version > > > > > > 6=autopatchup ; Autopatch up > > 0=autopatchdn ; Autopatch down > > 84=cop,1 ;warm boot > > 85=cop,2 ;system enable > > 86=cop,3 ;system disable > > 87=cop,5 ;debug mode > > 88=cop,6 ;system PTT > > > > 99=cop,4 ; Audio 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,2048) > > 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,75,2048)(0,0,75,0)(1209,0,75,2048); > > remotemon=|t(1209,0,75,2048) > > cmdmode=|t(900,903,200,2048) > > functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > > > > ; > > ; Morse code parameters, these are common to all repeaters. > > ; > > > > [morse] > > > > speed=20 ; Approximate speed in WPM > > frequency=800 ; Morse Telemetry Frequency > > amplitude=4096 ; Morse Telemetry Amplitude > > idfrequency=1064 ; Morse ID Frequency > > idamplitude=3072 ; 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=1750 ; Time to wait before sending > > most telemetry > > idwait=500 ; Time to wait before starting > > ID > > unkeywait=1000 ; Time to wait after unkey > > before sending CT's and link telemetry > > calltermwait=1500 ; Time to wait before announcing > > "call terminated" > > > > ; > > ; This is where you define your nodes which cam be connected to. > > ; > > > > [nodes] > > 1999 = radio at 127.0.0.1/1999 ; This must be changed to your IP > > address > > > > We added cop,6 to the regular functions table and the link functions > > table just to test and see if it was picking up only those functions > > instead, since there was a comment that if link functions were enabled > > then the remote user would only have access to them. > > > > Here is the extensions.conf for connecting to the radio: > > > > exten => 305,1,Rpt,1999|P > > > > ulaw is allowed in both IAX.conf and SIP.conf that we are using to dial > > the radio. Does this need to be changed as well? Trying to add as much > > info I can think of. > > > > Thanks, > > > > JRH > > > > >>> hwstar at rodgers.sdcoxmail.com 03/15/06 2:57 PM >>> > > > > It probably would be a good idea to attach your rpt.conf file to the > > thread. > > > > Steve > > WA6ZFT > > > > > From: "James Harfield" > > > Date: 2006/03/15 Wed PM 12:29:28 PST > > > To: > > > Subject: Re: [App_rpt] COP Functions > > > > > > That's what I figure as well. I've tried Softphone, Cell phone, land > > > > phone. All the default ilink and status functions work, along with > > cop,4 to initiate the test tone. But cop,6 won't key the radio. > > > > > >>> telesistant at hotmail.com 3/15/2006 2:21 PM >>> > > > > > > Well, if you have cop,6 defined as *88, and you are comming in with > > > > the P > > > > > option, and you > > > have phone_functions = phone_functions, then you definitely should be > > > > able > > > > > to key the > > > radio from the phone by dialing *88 (from the phone and only from the > > > phone). > > > > > > Jim, WB6NIL > > > > > > >From: "James Harfield" > > > >Reply-To: Asterisk Repeater Controler > > > >To: > > > >Subject: [App_rpt] COP Functions > > > >Date: Wed, 15 Mar 2006 13:11:02 -0600 > > > >MIME-Version: 1.0 > > > >Received: from lists.illiana.net ([207.227.243.140]) by > > > >bay0-mc12-f14.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.1830); > > > > Wed, > > > > > >15 Mar 2006 11:12:02 -0800 > > > >Received: (qmail 25119 invoked from network); 15 Mar 2006 19:12:00 > > > > -0000 > > > > > >Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with > > > > SMTP; 15 > > > > > >Mar 2006 19:12:00 -0000 > > > >Received: (qmail 25092 invoked from network); 15 Mar 2006 19:11:52 > > > > -0000 > > > > > >Received: from d1.duc.auburn.edu (131.204.2.2)by 0 with SMTP; 15 Mar > > > > 2006 > > > > > >19:11:52 -0000 > > > >Received: from TMIA1.AUBURN.EDU (tmia1.auburn.edu [131.204.3.30])by > > > >d1.duc.auburn.edu (8.13.4/8.13.4) with ESMTP id k2FJBjbE013830for > > > >; Wed, 15 Mar 2006 13:11:49 -0600 (CST) > > > >Received: from zTMIA1-MTA by TMIA1.AUBURN.EDUwith Novell_GroupWise; > > > > Wed, 15 > > > > > >Mar 2006 13:11:45 -0600 > > > >X-Message-Info: 6sSXyD95QpVMWPCRYsLAxQFjIgPjv7anT7L4spyjmhA= > > > >Return-Path: > > > >Delivered-To: mailman-app_rpt at lists.illiana.net > > > >X-Mailer: Novell GroupWise Internet Agent 7.0 X-BeenThere: > > > >app_rpt at lists.illiana.net > > > >X-Mailman-Version: 2.1.6 > > > >Precedence: list > > > >List-Id: Asterisk Repeater Controler > > > >List-Unsubscribe: > > > > > >, > >t at lists.illiana.net?subject=unsubscribe> > > > > > > >List-Archive: > > > >List-Post: > > > >List-Help: > > > >List-Subscribe: > > > > > >, > >t at lists.illiana.net?subject=subscribe> > > > > > > >Errors-To: app_rpt-bounces at lists.illiana.net > > > >X-OriginalArrivalTime: 15 Mar 2006 19:12:03.0471 (UTC) > > > >FILETIME=[57DDA1F0:01C64864] > > > > > > > >I'm having a problem getting cop,6 to function correctly in PTT'ing > > > > the > > > > > >radio. > > > > > > > >I have phone_functions = phone_functions defined in rpt.conf and > > > > within the > > > > > >phone_functions heading I have: > > > >88 = cop,6 > > > >defined with the other cop, ilink, and status functions. When > > > > connecting > > > > > >to my base I use the |P option instead of |D for phone control. > > > > > > > >The problem I'm having is that cop,6 will not activate the base to > > > >transmit. All the status commands, System Info, Time, Version, and > > > > the > > > > > >test tone cop,4 command work fine. The radio keys up, the > > > > appropriate > > > > > >information is sent, and the radio is unkeyed. But cop,6 will not > > > > key it. > > > > > >What I can do is manually key the radio and then use *88 (for cop,6) > > > > to > > > > > >talk and # when I want to end talking. I've tried to dig through the > > > > code > > > > > >and look at the difference between cop,6 and cop,4 for activating the > > > > base, > > > > > >but I'm quite confused as to why one can work and one cannot. > > > > > > > >Thanks, > > > > > > > >JRH > > > > > > > >_______________________________________________ > > > >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 > > > ------------------------------ > > _______________________________________________ > App_rpt mailing list > App_rpt at lists.illiana.net > http://lists.illiana.net/mailman/listinfo/app_rpt > > > End of App_rpt Digest, Vol 3, Issue 5 > ************************************* > From harfija at auburn.edu Thu Mar 16 15:15:28 2006 From: harfija at auburn.edu (James Harfield) Date: Thu, 16 Mar 2006 09:15:28 -0600 Subject: [App_rpt] COP Functions Message-ID: <44192CB0020000D600010A61@TMIA1.AUBURN.EDU> Steve, This is the output from the debug . . *CLI> @@@@ Digits collected: 8, source: 3 @@@@ Digits collected: 88, source: 3 @@@@ action: cop, param = 6 @@@@ table index i = 0 For *99 and the test tone, which does key the radio and works the output is.. *CLI> @@@@ Digits collected: 9, source: 3 @@@@ Digits collected: 99, source: 3 @@@@ action: cop, param = 4 @@@@ table index i = 0 Anything else you need? The debug looks as if it sees 88 and knows param = 6 is being executed. I'm at a loss as to what could be happening. Thanks, JRH >>> hwstar at rodgers.sdcoxmail.com 03/15/06 10:41 PM >>> James, I tried your config file on my system (had to change the node and the zap channel, but everything else remained the same), and *88 keyed the transmitter over the phone as it should be. Now I'm scratching my head.... The next thing to try: Issue "rpt debug level 1" from the real asterisk console ( asterisk -vvvvvvc, and not asterisk -r) and see if you can see the DTMF digits being processed by app_rpt. You should see something like this: @@@@ Digits collected: 88, source: 0 @@@@ action: cop, param = 6 @@@@ table index i = 0 BTW: cop.6 has no effect when dialed on a radio or link channel. Cop,6 is for use on a phone dial-in only. I'd suggest removing these from your other function tables. Steve, WA6ZFT On Wednesday 15 March 2006 14:18, James Harfield wrote: > As requested rpt.conf: > > [1999] ; Name of First Repeater > > rxchannel = Zap/1 ; Rx audio/signalling channel > ; Note: if you use a unified interface (tx/rx on one channel), only > ; specify the rxchannel and the txchannel will be assumed from the > rxchannel > functions=functions ; Repeater Function Table > ; > ; Added phone_functions=phone_functions > ; > phone_functions = phone_functions ;phone functions table > link_functions=link-functions ; Link Function Table > telemetry=telemetry ; Telemetry descriptions > wait_times=wait-times ; Wait times > context = radio ; dialing context for phone > callerid = "Your Repeater" <6198192562> ; callerid for phone calls > idrecording = /etc/asterisk/id ; id recording > accountcode=RADIO ; account code (optional) > hangtime=1000 ; squelch tail hang time (in ms) > (optional) > totime=90000 ; transmit time-out time (in ms) > (optional) > idtime=180000 ; id interval time (in ms) > (optional) > ; > ;Added duplex=2 > ; > ;duplex=2 > > ; 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/r ; Talkover ID (optional) default > is none > unlinkedct=ct2 ; unlinked courtesy tone > (optional) default is none > > ; > ; Repeater function table for node 010 > ; > > [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 > > 6=autopatchup ; Autopatch up > 0=autopatchdn ; Autopatch down > > ; > ;Added cop,6 in this context just to see if it would recognize cop,6 > ; > 88=cop,6 ; PTT Radio > 99=cop,4 ; Audio test tone > > > ; > ;Added phone_functions table for the phone_functions=phone_functions > ; > [phone_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 > > > ; > ;Added cop,1 - cop,6 for testing purposes. > ; > 84=cop,1 ;warm boot > 85=cop,2 ;system enable > 86=cop,3 ;system disable > 87=cop,5 ;debug mode > 88=cop,6 ;system PTT > > 6=autopatchup ; Autopatch up > 0=autopatchdn ; Autopatch down > > 99=cop,4 ; Audio test tone > > > ; > ; 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 > 7=ilink,5 ; Link status > > > 80=status,1 ; System info > 81=status,2 ; Time > 82=status,3 ; app_rpt.c Version > > > 6=autopatchup ; Autopatch up > 0=autopatchdn ; Autopatch down > 84=cop,1 ;warm boot > 85=cop,2 ;system enable > 86=cop,3 ;system disable > 87=cop,5 ;debug mode > 88=cop,6 ;system PTT > > 99=cop,4 ; Audio 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,2048) > 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,75,2048)(0,0,75,0)(1209,0,75,2048); > remotemon=|t(1209,0,75,2048) > cmdmode=|t(900,903,200,2048) > functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > > ; > ; Morse code parameters, these are common to all repeaters. > ; > > [morse] > > speed=20 ; Approximate speed in WPM > frequency=800 ; Morse Telemetry Frequency > amplitude=4096 ; Morse Telemetry Amplitude > idfrequency=1064 ; Morse ID Frequency > idamplitude=3072 ; 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=1750 ; Time to wait before sending > most telemetry > idwait=500 ; Time to wait before starting > ID > unkeywait=1000 ; Time to wait after unkey > before sending CT's and link telemetry > calltermwait=1500 ; Time to wait before announcing > "call terminated" > > ; > ; This is where you define your nodes which cam be connected to. > ; > > [nodes] > 1999 = radio at 127.0.0.1/1999 ; This must be changed to your IP > address > > We added cop,6 to the regular functions table and the link functions > table just to test and see if it was picking up only those functions > instead, since there was a comment that if link functions were enabled > then the remote user would only have access to them. > > Here is the extensions.conf for connecting to the radio: > > exten => 305,1,Rpt,1999|P > > ulaw is allowed in both IAX.conf and SIP.conf that we are using to dial > the radio. Does this need to be changed as well? Trying to add as much > info I can think of. > > Thanks, > > JRH > > >>> hwstar at rodgers.sdcoxmail.com 03/15/06 2:57 PM >>> > > It probably would be a good idea to attach your rpt.conf file to the > thread. > > Steve > WA6ZFT > > > From: "James Harfield" > > Date: 2006/03/15 Wed PM 12:29:28 PST > > To: > > Subject: Re: [App_rpt] COP Functions > > > > That's what I figure as well. I've tried Softphone, Cell phone, land > > phone. All the default ilink and status functions work, along with > cop,4 to initiate the test tone. But cop,6 won't key the radio. > > > >>> telesistant at hotmail.com 3/15/2006 2:21 PM >>> > > > > Well, if you have cop,6 defined as *88, and you are comming in with > > the P > > > option, and you > > have phone_functions = phone_functions, then you definitely should be > > able > > > to key the > > radio from the phone by dialing *88 (from the phone and only from the > > phone). > > > > Jim, WB6NIL > > > > >From: "James Harfield" > > >Reply-To: Asterisk Repeater Controler > > >To: > > >Subject: [App_rpt] COP Functions > > >Date: Wed, 15 Mar 2006 13:11:02 -0600 > > >MIME-Version: 1.0 > > >Received: from lists.illiana.net ([207.227.243.140]) by > > >bay0-mc12-f14.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.1830); > > Wed, > > > >15 Mar 2006 11:12:02 -0800 > > >Received: (qmail 25119 invoked from network); 15 Mar 2006 19:12:00 > > -0000 > > > >Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with > > SMTP; 15 > > > >Mar 2006 19:12:00 -0000 > > >Received: (qmail 25092 invoked from network); 15 Mar 2006 19:11:52 > > -0000 > > > >Received: from d1.duc.auburn.edu (131.204.2.2)by 0 with SMTP; 15 Mar > > 2006 > > > >19:11:52 -0000 > > >Received: from TMIA1.AUBURN.EDU (tmia1.auburn.edu [131.204.3.30])by > > >d1.duc.auburn.edu (8.13.4/8.13.4) with ESMTP id k2FJBjbE013830for > > >; Wed, 15 Mar 2006 13:11:49 -0600 (CST) > > >Received: from zTMIA1-MTA by TMIA1.AUBURN.EDUwith Novell_GroupWise; > > Wed, 15 > > > >Mar 2006 13:11:45 -0600 > > >X-Message-Info: 6sSXyD95QpVMWPCRYsLAxQFjIgPjv7anT7L4spyjmhA= > > >Return-Path: > > >Delivered-To: mailman-app_rpt at lists.illiana.net > > >X-Mailer: Novell GroupWise Internet Agent 7.0 X-BeenThere: > > >app_rpt at lists.illiana.net > > >X-Mailman-Version: 2.1.6 > > >Precedence: list > > >List-Id: Asterisk Repeater Controler > > >List-Unsubscribe: > > > >, >t at lists.illiana.net?subject=unsubscribe> > > > > >List-Archive: > > >List-Post: > > >List-Help: > > >List-Subscribe: > > > >, >t at lists.illiana.net?subject=subscribe> > > > > >Errors-To: app_rpt-bounces at lists.illiana.net > > >X-OriginalArrivalTime: 15 Mar 2006 19:12:03.0471 (UTC) > > >FILETIME=[57DDA1F0:01C64864] > > > > > >I'm having a problem getting cop,6 to function correctly in PTT'ing > > the > > > >radio. > > > > > >I have phone_functions = phone_functions defined in rpt.conf and > > within the > > > >phone_functions heading I have: > > >88 = cop,6 > > >defined with the other cop, ilink, and status functions. When > > connecting > > > >to my base I use the |P option instead of |D for phone control. > > > > > >The problem I'm having is that cop,6 will not activate the base to > > >transmit. All the status commands, System Info, Time, Version, and > > the > > > >test tone cop,4 command work fine. The radio keys up, the > > appropriate > > > >information is sent, and the radio is unkeyed. But cop,6 will not > > key it. > > > >What I can do is manually key the radio and then use *88 (for cop,6) > > to > > > >talk and # when I want to end talking. I've tried to dig through the > > code > > > >and look at the difference between cop,6 and cop,4 for activating the > > base, > > > >but I'm quite confused as to why one can work and one cannot. > > > > > >Thanks, > > > > > >JRH > > > > > >_______________________________________________ > > >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 _______________________________________________ App_rpt mailing list App_rpt at lists.illiana.net http://lists.illiana.net/mailman/listinfo/app_rpt From telesistant at hotmail.com Thu Mar 16 17:10:20 2006 From: telesistant at hotmail.com (Jim Duuuude) Date: Thu, 16 Mar 2006 09:10:20 -0800 Subject: [App_rpt] COP Functions In-Reply-To: <44192CB0020000D600010A61@TMIA1.AUBURN.EDU> Message-ID: James, I replied to you privately yesterday. Let me just talk to you, and have access to your system, and well see what the problem really is. Jim WB6NIL >From: "James Harfield" >Reply-To: Asterisk Repeater Controler >To: >Subject: Re: [App_rpt] COP Functions >Date: Thu, 16 Mar 2006 09:15:28 -0600 >MIME-Version: 1.0 >Received: from lists.illiana.net ([207.227.243.140]) by >bay0-mc12-f10.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, >16 Mar 2006 07:16:10 -0800 >Received: (qmail 21026 invoked from network); 16 Mar 2006 15:16:09 -0000 >Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with SMTP; 16 >Mar 2006 15:16:09 -0000 >Received: (qmail 21013 invoked from network); 16 Mar 2006 15:16:07 -0000 >Received: from d1.duc.auburn.edu (131.204.2.2)by 0 with SMTP; 16 Mar 2006 >15:16:07 -0000 >Received: from TMIA1.AUBURN.EDU (tmia1.auburn.edu [131.204.3.30])by >d1.duc.auburn.edu (8.13.4/8.13.4) with ESMTP id k2GFG6cq006547for >; Thu, 16 Mar 2006 09:16:06 -0600 (CST) >Received: from zTMIA1-MTA by TMIA1.AUBURN.EDUwith Novell_GroupWise; Thu, 16 >Mar 2006 09:16:06 -0600 >X-Message-Info: 6sSXyD95QpXnHStgs5f13BGoCTtHNMaxAIpI1fZkJMU= >Return-Path: >Delivered-To: mailman-app_rpt at lists.illiana.net >X-Mailer: Novell GroupWise Internet Agent 7.0 X-BeenThere: >app_rpt at lists.illiana.net >X-Mailman-Version: 2.1.6 >Precedence: list >List-Id: Asterisk Repeater Controler >List-Unsubscribe: >, >List-Archive: >List-Post: >List-Help: >List-Subscribe: >, >Errors-To: app_rpt-bounces at lists.illiana.net >X-OriginalArrivalTime: 16 Mar 2006 15:16:10.0257 (UTC) >FILETIME=[8E4E5010:01C6490C] > >Steve, > >This is the output from the debug . . > >*CLI> @@@@ Digits collected: 8, source: 3 >@@@@ Digits collected: 88, source: 3 >@@@@ action: cop, param = 6 >@@@@ table index i = 0 > >For *99 and the test tone, which does key the radio and works the output >is.. > >*CLI> @@@@ Digits collected: 9, source: 3 >@@@@ Digits collected: 99, source: 3 >@@@@ action: cop, param = 4 >@@@@ table index i = 0 > >Anything else you need? The debug looks as if it sees 88 and knows >param = 6 is being executed. I'm at a loss as to what could be >happening. > >Thanks, >JRH > > >>> hwstar at rodgers.sdcoxmail.com 03/15/06 10:41 PM >>> >James, > >I tried your config file on my system (had to change the node and the >zap >channel, but everything else remained the same), and *88 keyed the >transmitter over the phone as it should be. Now I'm scratching my >head.... > >The next thing to try: > >Issue "rpt debug level 1" from the real asterisk console ( asterisk >-vvvvvvc, >and not asterisk -r) and see if you can see the DTMF digits being >processed >by app_rpt. > >You should see something like this: > >@@@@ Digits collected: 88, source: 0 >@@@@ action: cop, param = 6 >@@@@ table index i = 0 > > >BTW: cop.6 has no effect when dialed on a radio or link channel. Cop,6 >is for >use on a phone dial-in only. I'd suggest removing these from your other >function tables. > >Steve, >WA6ZFT > > > > >On Wednesday 15 March 2006 14:18, James Harfield wrote: > > As requested rpt.conf: > > > > [1999] ; Name of First Repeater > > > > rxchannel = Zap/1 ; Rx audio/signalling channel > > ; Note: if you use a unified interface (tx/rx on one channel), only > > ; specify the rxchannel and the txchannel will be assumed from the > > rxchannel > > functions=functions ; Repeater Function Table > > ; > > ; Added phone_functions=phone_functions > > ; > > phone_functions = phone_functions ;phone functions table > > link_functions=link-functions ; Link Function Table > > telemetry=telemetry ; Telemetry descriptions > > wait_times=wait-times ; Wait times > > context = radio ; dialing context for >phone > > callerid = "Your Repeater" <6198192562> ; callerid for phone calls > > idrecording = /etc/asterisk/id ; id recording > > accountcode=RADIO ; account code (optional) > > hangtime=1000 ; squelch tail hang time (in ms) > > (optional) > > totime=90000 ; transmit time-out time (in ms) > > (optional) > > idtime=180000 ; id interval time (in ms) > > (optional) > > ; > > ;Added duplex=2 > > ; > > ;duplex=2 > > > > ; 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/r ; Talkover ID (optional) default > > is none > > unlinkedct=ct2 ; unlinked courtesy tone > > (optional) default is none > > > > ; > > ; Repeater function table for node 010 > > ; > > > > [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 > > > > 6=autopatchup ; Autopatch up > > 0=autopatchdn ; Autopatch down > > > > ; > > ;Added cop,6 in this context just to see if it would recognize cop,6 > > ; > > 88=cop,6 ; PTT Radio > > 99=cop,4 ; Audio test tone > > > > > > ; > > ;Added phone_functions table for the phone_functions=phone_functions > > ; > > [phone_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 > > > > > > ; > > ;Added cop,1 - cop,6 for testing purposes. > > ; > > 84=cop,1 ;warm boot > > 85=cop,2 ;system enable > > 86=cop,3 ;system disable > > 87=cop,5 ;debug mode > > 88=cop,6 ;system PTT > > > > 6=autopatchup ; Autopatch up > > 0=autopatchdn ; Autopatch down > > > > 99=cop,4 ; Audio test tone > > > > > > ; > > ; 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 > > 7=ilink,5 ; Link status > > > > > > 80=status,1 ; System info > > 81=status,2 ; Time > > 82=status,3 ; app_rpt.c Version > > > > > > 6=autopatchup ; Autopatch up > > 0=autopatchdn ; Autopatch down > > 84=cop,1 ;warm boot > > 85=cop,2 ;system enable > > 86=cop,3 ;system disable > > 87=cop,5 ;debug mode > > 88=cop,6 ;system PTT > > > > 99=cop,4 ; Audio 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,2048) > > 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,75,2048)(0,0,75,0)(1209,0,75,2048); > > remotemon=|t(1209,0,75,2048) > > cmdmode=|t(900,903,200,2048) > > functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > > > > ; > > ; Morse code parameters, these are common to all repeaters. > > ; > > > > [morse] > > > > speed=20 ; Approximate speed in WPM > > frequency=800 ; Morse Telemetry Frequency > > amplitude=4096 ; Morse Telemetry Amplitude > > idfrequency=1064 ; Morse ID Frequency > > idamplitude=3072 ; 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=1750 ; Time to wait before sending > > most telemetry > > idwait=500 ; Time to wait before starting > > ID > > unkeywait=1000 ; Time to wait after unkey > > before sending CT's and link telemetry > > calltermwait=1500 ; Time to wait before >announcing > > "call terminated" > > > > ; > > ; This is where you define your nodes which cam be connected to. > > ; > > > > [nodes] > > 1999 = radio at 127.0.0.1/1999 ; This must be changed to your IP > > address > > > > We added cop,6 to the regular functions table and the link functions > > table just to test and see if it was picking up only those functions > > instead, since there was a comment that if link functions were enabled > > then the remote user would only have access to them. > > > > Here is the extensions.conf for connecting to the radio: > > > > exten => 305,1,Rpt,1999|P > > > > ulaw is allowed in both IAX.conf and SIP.conf that we are using to >dial > > the radio. Does this need to be changed as well? Trying to add as >much > > info I can think of. > > > > Thanks, > > > > JRH > > > > >>> hwstar at rodgers.sdcoxmail.com 03/15/06 2:57 PM >>> > > > > It probably would be a good idea to attach your rpt.conf file to the > > thread. > > > > Steve > > WA6ZFT > > > > > From: "James Harfield" > > > Date: 2006/03/15 Wed PM 12:29:28 PST > > > To: > > > Subject: Re: [App_rpt] COP Functions > > > > > > That's what I figure as well. I've tried Softphone, Cell phone, >land > > > > phone. All the default ilink and status functions work, along with > > cop,4 to initiate the test tone. But cop,6 won't key the radio. > > > > > >>> telesistant at hotmail.com 3/15/2006 2:21 PM >>> > > > > > > Well, if you have cop,6 defined as *88, and you are comming in with > > > > the P > > > > > option, and you > > > have phone_functions = phone_functions, then you definitely should >be > > > > able > > > > > to key the > > > radio from the phone by dialing *88 (from the phone and only from >the > > > phone). > > > > > > Jim, WB6NIL > > > > > > >From: "James Harfield" > > > >Reply-To: Asterisk Repeater Controler > > > >To: > > > >Subject: [App_rpt] COP Functions > > > >Date: Wed, 15 Mar 2006 13:11:02 -0600 > > > >MIME-Version: 1.0 > > > >Received: from lists.illiana.net ([207.227.243.140]) by > > > >bay0-mc12-f14.bay0.hotmail.com with Microsoft >SMTPSVC(6.0.3790.1830); > > > > Wed, > > > > > >15 Mar 2006 11:12:02 -0800 > > > >Received: (qmail 25119 invoked from network); 15 Mar 2006 19:12:00 > > > > -0000 > > > > > >Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with > > > > SMTP; 15 > > > > > >Mar 2006 19:12:00 -0000 > > > >Received: (qmail 25092 invoked from network); 15 Mar 2006 19:11:52 > > > > -0000 > > > > > >Received: from d1.duc.auburn.edu (131.204.2.2)by 0 with SMTP; 15 >Mar > > > > 2006 > > > > > >19:11:52 -0000 > > > >Received: from TMIA1.AUBURN.EDU (tmia1.auburn.edu [131.204.3.30])by > > > >d1.duc.auburn.edu (8.13.4/8.13.4) with ESMTP id k2FJBjbE013830for > > > >; Wed, 15 Mar 2006 13:11:49 -0600 (CST) > > > >Received: from zTMIA1-MTA by TMIA1.AUBURN.EDUwith Novell_GroupWise; > > > > Wed, 15 > > > > > >Mar 2006 13:11:45 -0600 > > > >X-Message-Info: 6sSXyD95QpVMWPCRYsLAxQFjIgPjv7anT7L4spyjmhA= > > > >Return-Path: > > > >Delivered-To: mailman-app_rpt at lists.illiana.net > > > >X-Mailer: Novell GroupWise Internet Agent 7.0 X-BeenThere: > > > >app_rpt at lists.illiana.net > > > >X-Mailman-Version: 2.1.6 > > > >Precedence: list > > > >List-Id: Asterisk Repeater Controler > > > >List-Unsubscribe: > > > > > > >, > >t at lists.illiana.net?subject=unsubscribe> > > > > > > >List-Archive: > > > >List-Post: > > > >List-Help: > > > >List-Subscribe: > > > > > > >, > >t at lists.illiana.net?subject=subscribe> > > > > > > >Errors-To: app_rpt-bounces at lists.illiana.net > > > >X-OriginalArrivalTime: 15 Mar 2006 19:12:03.0471 (UTC) > > > >FILETIME=[57DDA1F0:01C64864] > > > > > > > >I'm having a problem getting cop,6 to function correctly in PTT'ing > > > > the > > > > > >radio. > > > > > > > >I have phone_functions = phone_functions defined in rpt.conf and > > > > within the > > > > > >phone_functions heading I have: > > > >88 = cop,6 > > > >defined with the other cop, ilink, and status functions. When > > > > connecting > > > > > >to my base I use the |P option instead of |D for phone control. > > > > > > > >The problem I'm having is that cop,6 will not activate the base to > > > >transmit. All the status commands, System Info, Time, Version, and > > > > the > > > > > >test tone cop,4 command work fine. The radio keys up, the > > > > appropriate > > > > > >information is sent, and the radio is unkeyed. But cop,6 will not > > > > key it. > > > > > >What I can do is manually key the radio and then use *88 (for >cop,6) > > > > to > > > > > >talk and # when I want to end talking. I've tried to dig through >the > > > > code > > > > > >and look at the difference between cop,6 and cop,4 for activating >the > > > > base, > > > > > >but I'm quite confused as to why one can work and one cannot. > > > > > > > >Thanks, > > > > > > > >JRH > > > > > > > >_______________________________________________ > > > >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 >_______________________________________________ >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 harfija at auburn.edu Fri Mar 17 03:54:30 2006 From: harfija at auburn.edu (James Harfield) Date: Thu, 16 Mar 2006 21:54:30 -0600 Subject: [App_rpt] COP Functions Message-ID: <4419DE95020000D600010B7C@TMIA1.AUBURN.EDU> Sent you an e-mail with some questions, Jim. Still no luck getting it working on our end but I'm trying different stuff day to day. JRH >>> telesistant at hotmail.com 03/16/06 11:10 AM >>> James, I replied to you privately yesterday. Let me just talk to you, and have access to your system, and well see what the problem really is. Jim WB6NIL >From: "James Harfield" >Reply-To: Asterisk Repeater Controler >To: >Subject: Re: [App_rpt] COP Functions >Date: Thu, 16 Mar 2006 09:15:28 -0600 >MIME-Version: 1.0 >Received: from lists.illiana.net ([207.227.243.140]) by >bay0-mc12-f10.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, >16 Mar 2006 07:16:10 -0800 >Received: (qmail 21026 invoked from network); 16 Mar 2006 15:16:09 -0000 >Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with SMTP; 16 >Mar 2006 15:16:09 -0000 >Received: (qmail 21013 invoked from network); 16 Mar 2006 15:16:07 -0000 >Received: from d1.duc.auburn.edu (131.204.2.2)by 0 with SMTP; 16 Mar 2006 >15:16:07 -0000 >Received: from TMIA1.AUBURN.EDU (tmia1.auburn.edu [131.204.3.30])by >d1.duc.auburn.edu (8.13.4/8.13.4) with ESMTP id k2GFG6cq006547for >; Thu, 16 Mar 2006 09:16:06 -0600 (CST) >Received: from zTMIA1-MTA by TMIA1.AUBURN.EDUwith Novell_GroupWise; Thu, 16 >Mar 2006 09:16:06 -0600 >X-Message-Info: 6sSXyD95QpXnHStgs5f13BGoCTtHNMaxAIpI1fZkJMU= >Return-Path: >Delivered-To: mailman-app_rpt at lists.illiana.net >X-Mailer: Novell GroupWise Internet Agent 7.0 X-BeenThere: >app_rpt at lists.illiana.net >X-Mailman-Version: 2.1.6 >Precedence: list >List-Id: Asterisk Repeater Controler >List-Unsubscribe: >, >List-Archive: >List-Post: >List-Help: >List-Subscribe: >, >Errors-To: app_rpt-bounces at lists.illiana.net >X-OriginalArrivalTime: 16 Mar 2006 15:16:10.0257 (UTC) >FILETIME=[8E4E5010:01C6490C] > >Steve, > >This is the output from the debug . . > >*CLI> @@@@ Digits collected: 8, source: 3 >@@@@ Digits collected: 88, source: 3 >@@@@ action: cop, param = 6 >@@@@ table index i = 0 > >For *99 and the test tone, which does key the radio and works the output >is.. > >*CLI> @@@@ Digits collected: 9, source: 3 >@@@@ Digits collected: 99, source: 3 >@@@@ action: cop, param = 4 >@@@@ table index i = 0 > >Anything else you need? The debug looks as if it sees 88 and knows >param = 6 is being executed. I'm at a loss as to what could be >happening. > >Thanks, >JRH > > >>> hwstar at rodgers.sdcoxmail.com 03/15/06 10:41 PM >>> >James, > >I tried your config file on my system (had to change the node and the >zap >channel, but everything else remained the same), and *88 keyed the >transmitter over the phone as it should be. Now I'm scratching my >head.... > >The next thing to try: > >Issue "rpt debug level 1" from the real asterisk console ( asterisk >-vvvvvvc, >and not asterisk -r) and see if you can see the DTMF digits being >processed >by app_rpt. > >You should see something like this: > >@@@@ Digits collected: 88, source: 0 >@@@@ action: cop, param = 6 >@@@@ table index i = 0 > > >BTW: cop.6 has no effect when dialed on a radio or link channel. Cop,6 >is for >use on a phone dial-in only. I'd suggest removing these from your other >function tables. > >Steve, >WA6ZFT > > > > >On Wednesday 15 March 2006 14:18, James Harfield wrote: > > As requested rpt.conf: > > > > [1999] ; Name of First Repeater > > > > rxchannel = Zap/1 ; Rx audio/signalling channel > > ; Note: if you use a unified interface (tx/rx on one channel), only > > ; specify the rxchannel and the txchannel will be assumed from the > > rxchannel > > functions=functions ; Repeater Function Table > > ; > > ; Added phone_functions=phone_functions > > ; > > phone_functions = phone_functions ;phone functions table > > link_functions=link-functions ; Link Function Table > > telemetry=telemetry ; Telemetry descriptions > > wait_times=wait-times ; Wait times > > context = radio ; dialing context for >phone > > callerid = "Your Repeater" <6198192562> ; callerid for phone calls > > idrecording = /etc/asterisk/id ; id recording > > accountcode=RADIO ; account code (optional) > > hangtime=1000 ; squelch tail hang time (in ms) > > (optional) > > totime=90000 ; transmit time-out time (in ms) > > (optional) > > idtime=180000 ; id interval time (in ms) > > (optional) > > ; > > ;Added duplex=2 > > ; > > ;duplex=2 > > > > ; 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/r ; Talkover ID (optional) default > > is none > > unlinkedct=ct2 ; unlinked courtesy tone > > (optional) default is none > > > > ; > > ; Repeater function table for node 010 > > ; > > > > [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 > > > > 6=autopatchup ; Autopatch up > > 0=autopatchdn ; Autopatch down > > > > ; > > ;Added cop,6 in this context just to see if it would recognize cop,6 > > ; > > 88=cop,6 ; PTT Radio > > 99=cop,4 ; Audio test tone > > > > > > ; > > ;Added phone_functions table for the phone_functions=phone_functions > > ; > > [phone_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 > > > > > > ; > > ;Added cop,1 - cop,6 for testing purposes. > > ; > > 84=cop,1 ;warm boot > > 85=cop,2 ;system enable > > 86=cop,3 ;system disable > > 87=cop,5 ;debug mode > > 88=cop,6 ;system PTT > > > > 6=autopatchup ; Autopatch up > > 0=autopatchdn ; Autopatch down > > > > 99=cop,4 ; Audio test tone > > > > > > ; > > ; 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 > > 7=ilink,5 ; Link status > > > > > > 80=status,1 ; System info > > 81=status,2 ; Time > > 82=status,3 ; app_rpt.c Version > > > > > > 6=autopatchup ; Autopatch up > > 0=autopatchdn ; Autopatch down > > 84=cop,1 ;warm boot > > 85=cop,2 ;system enable > > 86=cop,3 ;system disable > > 87=cop,5 ;debug mode > > 88=cop,6 ;system PTT > > > > 99=cop,4 ; Audio 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,2048) > > 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,75,2048)(0,0,75,0)(1209,0,75,2048); > > remotemon=|t(1209,0,75,2048) > > cmdmode=|t(900,903,200,2048) > > functcomplete=|t(1000,0,100,2048)(0,0,100,0)(1000,0,100,2048) > > > > ; > > ; Morse code parameters, these are common to all repeaters. > > ; > > > > [morse] > > > > speed=20 ; Approximate speed in WPM > > frequency=800 ; Morse Telemetry Frequency > > amplitude=4096 ; Morse Telemetry Amplitude > > idfrequency=1064 ; Morse ID Frequency > > idamplitude=3072 ; 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=1750 ; Time to wait before sending > > most telemetry > > idwait=500 ; Time to wait before starting > > ID > > unkeywait=1000 ; Time to wait after unkey > > before sending CT's and link telemetry > > calltermwait=1500 ; Time to wait before >announcing > > "call terminated" > > > > ; > > ; This is where you define your nodes which cam be connected to. > > ; > > > > [nodes] > > 1999 = radio at 127.0.0.1/1999 ; This must be changed to your IP > > address > > > > We added cop,6 to the regular functions table and the link functions > > table just to test and see if it was picking up only those functions > > instead, since there was a comment that if link functions were enabled > > then the remote user would only have access to them. > > > > Here is the extensions.conf for connecting to the radio: > > > > exten => 305,1,Rpt,1999|P > > > > ulaw is allowed in both IAX.conf and SIP.conf that we are using to >dial > > the radio. Does this need to be changed as well? Trying to add as >much > > info I can think of. > > > > Thanks, > > > > JRH > > > > >>> hwstar at rodgers.sdcoxmail.com 03/15/06 2:57 PM >>> > > > > It probably would be a good idea to attach your rpt.conf file to the > > thread. > > > > Steve > > WA6ZFT > > > > > From: "James Harfield" > > > Date: 2006/03/15 Wed PM 12:29:28 PST > > > To: > > > Subject: Re: [App_rpt] COP Functions > > > > > > That's what I figure as well. I've tried Softphone, Cell phone, >land > > > > phone. All the default ilink and status functions work, along with > > cop,4 to initiate the test tone. But cop,6 won't key the radio. > > > > > >>> telesistant at hotmail.com 3/15/2006 2:21 PM >>> > > > > > > Well, if you have cop,6 defined as *88, and you are comming in with > > > > the P > > > > > option, and you > > > have phone_functions = phone_functions, then you definitely should >be > > > > able > > > > > to key the > > > radio from the phone by dialing *88 (from the phone and only from >the > > > phone). > > > > > > Jim, WB6NIL > > > > > > >From: "James Harfield" > > > >Reply-To: Asterisk Repeater Controler > > > >To: > > > >Subject: [App_rpt] COP Functions > > > >Date: Wed, 15 Mar 2006 13:11:02 -0600 > > > >MIME-Version: 1.0 > > > >Received: from lists.illiana.net ([207.227.243.140]) by > > > >bay0-mc12-f14.bay0.hotmail.com with Microsoft >SMTPSVC(6.0.3790.1830); > > > > Wed, > > > > > >15 Mar 2006 11:12:02 -0800 > > > >Received: (qmail 25119 invoked from network); 15 Mar 2006 19:12:00 > > > > -0000 > > > > > >Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with > > > > SMTP; 15 > > > > > >Mar 2006 19:12:00 -0000 > > > >Received: (qmail 25092 invoked from network); 15 Mar 2006 19:11:52 > > > > -0000 > > > > > >Received: from d1.duc.auburn.edu (131.204.2.2)by 0 with SMTP; 15 >Mar > > > > 2006 > > > > > >19:11:52 -0000 > > > >Received: from TMIA1.AUBURN.EDU (tmia1.auburn.edu [131.204.3.30])by > > > >d1.duc.auburn.edu (8.13.4/8.13.4) with ESMTP id k2FJBjbE013830for > > > >; Wed, 15 Mar 2006 13:11:49 -0600 (CST) > > > >Received: from zTMIA1-MTA by TMIA1.AUBURN.EDUwith Novell_GroupWise; > > > > Wed, 15 > > > > > >Mar 2006 13:11:45 -0600 > > > >X-Message-Info: 6sSXyD95QpVMWPCRYsLAxQFjIgPjv7anT7L4spyjmhA= > > > >Return-Path: > > > >Delivered-To: mailman-app_rpt at lists.illiana.net > > > >X-Mailer: Novell GroupWise Internet Agent 7.0 X-BeenThere: > > > >app_rpt at lists.illiana.net > > > >X-Mailman-Version: 2.1.6 > > > >Precedence: list > > > >List-Id: Asterisk Repeater Controler > > > >List-Unsubscribe: > > > > > > >, > >t at lists.illiana.net?subject=unsubscribe> > > > > > > >List-Archive: > > > >List-Post: > > > >List-Help: > > > >List-Subscribe: > > > > > > >, > >t at lists.illiana.net?subject=subscribe> > > > > > > >Errors-To: app_rpt-bounces at lists.illiana.net > > > >X-OriginalArrivalTime: 15 Mar 2006 19:12:03.0471 (UTC) > > > >FILETIME=[57DDA1F0:01C64864] > > > > > > > >I'm having a problem getting cop,6 to function correctly in PTT'ing > > > > the > > > > > >radio. > > > > > > > >I have phone_functions = phone_functions defined in rpt.conf and > > > > within the > > > > > >phone_functions heading I have: > > > >88 = cop,6 > > > >defined with the other cop, ilink, and status functions. When > > > > connecting > > > > > >to my base I use the |P option instead of |D for phone control. > > > > > > > >The problem I'm having is that cop,6 will not activate the base to > > > >transmit. All the status commands, System Info, Time, Version, and > > > > the > > > > > >test tone cop,4 command work fine. The radio keys up, the > > > > appropriate > > > > > >information is sent, and the radio is unkeyed. But cop,6 will not > > > > key it. > > > > > >What I can do is manually key the radio and then use *88 (for >cop,6) > > > > to > > > > > >talk and # when I want to end talking. I've tried to dig through >the > > > > code > > > > > >and look at the difference between cop,6 and cop,4 for activating >the > > > > base, > > > > > >but I'm quite confused as to why one can work and one cannot. > > > > > > > >Thanks, > > > > > > > >JRH > > > > > > > >_______________________________________________ > > > >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 >_______________________________________________ >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 librettista at hotmail.com Wed Mar 22 15:19:39 2006 From: librettista at hotmail.com (Carlos .) Date: Wed, 22 Mar 2006 16:19:39 +0100 Subject: [App_rpt] Newbie question Message-ID: Hi. I am a newcomer to the app_rpt world. I bought a pciradio board some time ago and now I?m starting with the documents to install a remote radio system. I?ve installed an Asterisk at home and got it running now. Now I see in the "how-to" doc some guides about installing asterisk and some files. My question is: is necessary to perform all the described steps or is all of it included in the asterisk at home distribution ? I?ve tried "modprobe zaptel", "modprobe pciradio" and returned no error, so I suppose only have to edit the conf files. Is this correct ? And another one: has anyone the conf files to support both phone lines (digium boards) and pciradio in the same machine ? Thanks for all your help. Greetings from Spain Carlos From telesistant at hotmail.com Wed Mar 22 17:02:16 2006 From: telesistant at hotmail.com (Jim Duuuude) Date: Wed, 22 Mar 2006 09:02:16 -0800 Subject: [App_rpt] Newbie question In-Reply-To: Message-ID: Off hand, I can think of a couple of things that make your situation difficult: First off, the entire asterisk program needs to have a compile time flag (RADIO_RELAX) set for the DTMF decoders to work properly. This needs to be done to the entire build of asterisk, from the start. Asterisk at home is not built with app_rpt enabled (at least as far as I am aware). I have no idea of what version of asterisk comes with asterisk at home, but I can guarantee you that its not nearly the recent one. Running the recent version of app_rpt is important, since it usually has far more features then the ones included in releases. Also, the version of asterisk may not be modern enough for the latest version of app_rpt. We keep in sync with the latest version in SVN HEAD, so sometimes we find situations where the user needs to upgrade to SVN HEAD before app_rpt is usable on their systems. Other then these main issues, your config files need to be manually modified so that the stuff to make app_rpt work is included. First of all, the port numbers will have to be changed. Whichever card gets modprobed first will have the lowest port (channel) numbers. I suggest modprobing the pciradio card last, so that your 'normal' telephony interfaces will start a port 1, and your radio ones will start at like 5 or 25 or whatevers. Whatever the base may be, you need to put entries in /etc/zqptel.conf, /etc/asterisk/zapata.conf, /etc/asterisk/iax.conf, /etc/asterisk/extensions.conf, and change the port number in /etc/asterisk/rpt.conf. Dont also forget to put a system id message in as /etc/asterisk/id.[whatever-extension]. The next question, of course, is what does the Asterisk at home config system do with manual config file changes? Does it honor them, or does it poo right over them? Jim Dixon, WB6NIL >From: "Carlos ." >Reply-To: Asterisk Repeater Controler >To: app_rpt at lists.illiana.net >Subject: [App_rpt] Newbie question >Date: Wed, 22 Mar 2006 16:19:39 +0100 >MIME-Version: 1.0 >X-Originating-IP: [217.126.169.222] >X-Originating-Email: [librettista at hotmail.com] >X-Sender: librettista at hotmail.com >Received: from lists.illiana.net ([207.227.243.140]) by >bay0-mc10-f10.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, >22 Mar 2006 07:19:48 -0800 >Received: (qmail 13343 invoked from network); 22 Mar 2006 15:19:46 -0000 >Received: from localhost (HELO ?127.0.0.1?) (127.0.0.1) by 0 with SMTP; 22 >Mar 2006 15:19:46 -0000 >Received: (qmail 13325 invoked from network); 22 Mar 2006 15:19:43 -0000 >Received: from bay107-f4.bay107.hotmail.com (HELO hotmail.com) >(64.4.51.14)by 0 with SMTP; 22 Mar 2006 15:19:43 -0000 >Received: from mail pickup service by hotmail.com with Microsoft >SMTPSVC;Wed, 22 Mar 2006 07:19:40 -0800 >Received: from 64.4.51.220 by by107fd.bay107.hotmail.msn.com with HTTP;Wed, >22 Mar 2006 15:19:39 GMT >X-Message-Info: JGTYoYF78jE4oaiFylKnnDs8hHIqqAqn10N+eTIycsE= >Return-Path: >Delivered-To: mailman-app_rpt at lists.illiana.net >X-OriginalArrivalTime: 22 Mar 2006 15:19:40.0311 >(UTC)FILETIME=[09FC8270:01C64DC4] >X-BeenThere: app_rpt at lists.illiana.net >X-Mailman-Version: 2.1.6 >Precedence: list >List-Id: Asterisk Repeater Controler >List-Unsubscribe: >, >List-Archive: >List-Post: >List-Help: >List-Subscribe: >, >Errors-To: app_rpt-bounces at lists.illiana.net > >Hi. > >I am a newcomer to the app_rpt world. I bought a pciradio board some time >ago and now I?m starting with the documents to install a remote radio >system. >I?ve installed an Asterisk at home and got it running now. Now I see in the >"how-to" doc some guides about installing asterisk and some files. >My question is: is necessary to perform all the described steps or is all >of >it included in the asterisk at home distribution ? >I?ve tried "modprobe zaptel", "modprobe pciradio" and returned no error, so >I suppose only have to edit the conf files. Is this correct ? >And another one: has anyone the conf files to support both phone lines >(digium boards) and pciradio in the same machine ? >Thanks for all your help. > >Greetings from Spain >Carlos > > >_______________________________________________ >App_rpt mailing list >App_rpt at lists.illiana.net >http://lists.illiana.net/mailman/listinfo/app_rpt