- App_rpt-users - lists.keekles.org

Re: [App_rpt-users] Segmentation fault. Getting desperate.
by Ken Page 11 Oct '11

11 Oct '11

OK. I took a punt and did a make and then make install with the original Asterisk and radio sources. I still get the same segmentation fault a few seconds after the Asterisk server is starts. This happens straight after accessing the radio tune files. Everything works fine even the radio stuff just before it all bombs. I have no clue where to even start looking at this point. Everything else on the server still works fine. Apache, PHPbb, Minecraft server, and so on. So I have discounted an actual hardware memory issue etc. It's just Asterisk bombing out all of a sudden. Any idea's? ~Ken - vk4akp~ All_Star: 2134 (Off-Line). .-.-. On 10/11/2011 7:08 PM, app_rpt-users-request(a)ohnosec.org wrote: > Send App_rpt-users mailing list submissions to > app_rpt-users(a)ohnosec.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > or, via email, send a message with subject or body 'help' to > app_rpt-users-request(a)ohnosec.org > > You can reach the person managing the list at > app_rpt-users-owner(a)ohnosec.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of App_rpt-users digest..." > > > Today's Topics: > > 1. Re: Reverse autopatch immediately hanging up (Josh Freeman) > 2. Issues After Reboot (Travis Best) > 3. Re: Issues After Reboot (Jim Duuuude) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 10 Oct 2011 21:05:21 -0500 > From: Josh Freeman<cpe.jfreeman(a)gmail.com> > To: Jim Duuuude<telesistant(a)hotmail.com> > Cc: app_rpt mailing list<app_rpt-users(a)ohnosec.org> > Subject: Re: [App_rpt-users] Reverse autopatch immediately hanging up > Message-ID:<4E93A461.7080605(a)gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > OK. Well, darn. =) > > Originally, I had tried to connect directly from the Zap channel, and it > failed with the message > > Warning: We only accept links via IAX2, Echolink, TheLinkBox or Local!! > > I guess that's what got me thinking Local channels would be the way to > bridge over from Zap or SIP. > > Thanks again for your help! > > Josh > > On 10/10/2011 8:45 PM, Jim Duuuude wrote: >> dont use it at all... app_rpt cant deal with it. >> >> ------------------------------------------------------------------------ >> Date: Mon, 10 Oct 2011 19:53:14 -0500 >> From: cpe.jfreeman(a)gmail.com >> To: telesistant(a)hotmail.com >> Subject: Re: [App_rpt-users] Reverse autopatch immediately hanging up >> >> OK, I tried that... it looks like the reverse autopatch *does* work >> correctly when dialed into via pure IAX. Unfortunately, only being >> able to use native IAX clients doesn't meet the requirements for what >> I'm trying to do. I'll study up some more on how Local channels work, >> maybe I'm not using that mechanism correctly. >> >> Thanks, >> Josh >> >> On 10/10/2011 6:21 PM, Jim Duuuude wrote: >> >> okay, try calling it directly from your IAX client, rather then >> through a Local channel >> >> ------------------------------------------------------------------------ >> Date: Mon, 10 Oct 2011 18:05:16 -0500 >> From: cpe.jfreeman(a)gmail.com<mailto:cpe.jfreeman@gmail.com> >> To: APP_RPT-USERS(a)OHNOSEC.ORG<mailto:APP_RPT-USERS@OHNOSEC.ORG> >> Subject: Re: [App_rpt-users] Reverse autopatch immediately hanging up >> >> Jim, >> >> That would be correct, if I had left the [radio] context as it was >> in the bundled Allstar dialplan, where this line >> >> exten=_07XX,1,Goto(parkedcalls|${EXTEN:1}|1) >> >> makes it necessary to dial the leading "0." I created a different >> radio context, and simply added >> >> include => parkedcalls >> >> so that the pickup code *is* actually just '701'. >> >> Because I don't understand everything about this system, though, I >> tried reverting that part of my dialplan back to the Allstar >> configuration, just to see if that made a difference. It didn't - >> the autopatch still gets hung up within a second or two of >> connection. Dialing through the Local channel is the thing I'm >> doing that's significantly different than anything in the Allstar >> dialplan, so I'm guessing that's where the problem is - but I'm >> not smart enough to find it yet. >> >> Thanks, >> Josh >> >> On 10/10/2011 1:33 PM, Jim Duuuude wrote: >> >> Thats because youre missing a 'digits/0' between the incall >> and the PARKED, such as: >> >> Rpt(${EXTEN:1}|Rrpt/node:NODE:rpt/in-call:digits/0:PARKED|120) >> >> The code to pick that up should be '0701' *not* 701 >> >> JIM WB6NIL >> >> ------------------------------------------------------------------------ >> Date: Mon, 10 Oct 2011 11:06:52 -0500 >> From: cpe.jfreeman(a)gmail.com<mailto:cpe.jfreeman@gmail.com> >> To: APP_RPT-USERS(a)OHNOSEC.ORG<mailto:APP_RPT-USERS@OHNOSEC.ORG> >> Subject: [App_rpt-users] Reverse autopatch immediately hanging up >> >> Hello, >> >> I'm trying to set up a system that has a reverse autopatch as >> one of its features. The problem I'm having is that when a >> radio user dials the code to pick up an incoming call, the >> call gets disconnected almost immediately upon connecting. I'm >> certain the problem is that I've not set things up properly, >> but I'm still inexperienced enough that I could really use >> some help troubleshooting. >> >> My Asterisk system is running from a recent ACID image >> (downloaded maybe three weeks ago). The machine also has a >> TDM400P card with an FXS module connected to an analog >> telephone I'm using to originate incoming test calls to the >> repeater system. >> >> The relevant parts of my dialplan are as follows: >> >> In context *phones_local*: >> >> exten => 272727,1,Dial(Local/CQCQCQ@repeater) >> (Apparently, I can't directly connect to app_rpt from a Zap >> channel, so I dial through a Local channel instead.) >> >> Then, in context *repeater*: >> >> exten => CQCQCQ,1,Rpt(5674,Rrpt/in-call:PARKED,120) >> (This is an isolated system, so the node number is simply my >> name on a telephone keypad.) >> >> What happens is this: I dial 272727 from the analog telephone, >> and I hear the announcement over the radio just fine. I send >> *6701 from the radio, and hear "Connecting" from the repeater >> along with echoing audio from the analog phone (because it's >> right there next to the radio). Then, I immediately hear "Call >> terminated" and the autopatch drops. The analog phone doesn't >> get hung up, though. >> >> Here's what I see on the Asterisk console. For this trace, I >> was actually dialing in from an IAX softphone rather than the >> Zap channel, but the behavior is exactly the same. >> >> -- Executing [272727@phones_local:1] Dial("IAX2/josh-12630", >> "Local/CQCQCQ@repeater") in new stack >> -- Called CQCQCQ@repeater >> -- Executing [CQCQCQ@repeater:1] >> Rpt("Local/CQCQCQ@repeater-781b,2", >> "5674|Rrpt/in-call:PARKED|120") in new stack >> -- Return Context: (repeater,CQCQCQ,2) ID: 0 >> -- Warning: Return Context Invalid, call will return to >> default|s >> -- Music class default requested but no musiconhold loaded. >> == Parked Local/CQCQCQ@repeater-781b,2 on 701@parkedcalls. >> Will timeout back to extension [repeater] CQCQCQ, 2 in 45 seconds >> -- Added extension '701' priority 1 to parkedcalls >> -- Music class default requested but no musiconhold loaded. >> -- Music class default requested but no musiconhold loaded. >> -- Local/CQCQCQ@repeater-781b,1 answered IAX2/josh-12630 >> -- Call Parking Called, lot: 701, timeout: 0, context: (null) >> -- Music class default requested but no musiconhold loaded. >> --<Zap/pseudo-1800116975> Playing 'rpt/in-call' (language >> 'en') >> --<Zap/pseudo-1800116975> Playing 'digits/7' (language 'en') >> --<Zap/pseudo-1800116975> Playing 'digits/0' (language 'en') >> --<Zap/pseudo-1800116975> Playing 'digits/1' (language 'en') >> -- Hungup 'Zap/pseudo-1800116975' >> -- Hungup 'Zap/pseudo-1018949410' >> [Oct 9 19:44:18] NOTICE[2594]: chan_usbradio.c:3010 >> usbradio_read: Got DTMF char * duration 340 ms >> [Oct 9 19:44:19] NOTICE[2594]: chan_usbradio.c:3010 >> usbradio_read: Got DTMF char 6 duration 235 ms >> [Oct 9 19:44:20] NOTICE[2594]: chan_usbradio.c:3010 >> usbradio_read: Got DTMF char 7 duration 255 ms >> [Oct 9 19:44:20] NOTICE[2594]: chan_usbradio.c:3010 >> usbradio_read: Got DTMF char 0 duration 212 ms >> -- Hungup 'Zap/pseudo-1705936882' >> [Oct 9 19:44:21] NOTICE[2594]: chan_usbradio.c:3010 >> usbradio_read: Got DTMF char 1 duration 235 ms >> -- Executing [701@phones_radio:1] >> ParkedCall("Zap/pseudo-523589909", "701") in new stack >> -- Channel Zap/pseudo-523589909 connected to parked call 701 >> == Spawn extension (phones_radio, 701, 1) exited non-zero on >> 'Local/CQCQCQ@repeater-781b,1<ZOMBIE>' >> -- Hungup 'Zap/pseudo-1742992459' >> -- Hungup 'Zap/pseudo-1417902655' >> --<Zap/pseudo-1427730098> Playing 'rpt/callproceeding' >> (language 'en') >> -- Hungup 'Zap/pseudo-1427730098' >> --<Zap/pseudo-1938338821> Playing 'rpt/callterminated' >> (language 'en') >> -- Hungup 'Zap/pseudo-1938338821' >> -- Hungup 'Zap/pseudo-1525511763' >> >> I see some things about invalid return context and zombie >> channels, but I'm not sure what that means. Any idea what it >> is I'm missing? >> >> Thanks, >> Josh >> >> >> _______________________________________________ App_rpt-users >> mailing list App_rpt-users(a)ohnosec.org >> <mailto:App_rpt-users@ohnosec.org> >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> >> >> _______________________________________________ App_rpt-users >> mailing list App_rpt-users(a)ohnosec.org >> <mailto:App_rpt-users@ohnosec.org> >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users >> >> >

1 0

Switch from usbradio to simpleusb - radio tune question
by Tony KT9AC 11 Oct '11

11 Oct '11

My node recently was experiencing some issues that I think were caused by a bad remote base sound fob interface (usb1), which locked the repeater in transmit until I could drive out to the site - no command in the world would work nor any audio passed (the repeater itself is attached using a URI on usb0 and always worked well). I have the logs from this looping event: [Sep 27 16:47:54] ERROR[15044] chan_usbradio.c: Not able to claim the USB device [Sep 27 16:47:55] WARNING[15006] chan_usbradio.c: Unable to re-open DSP device 0 (usb1): Device or resource busy I brought the PC back home and updated the code to latest level and decided to switch to simpleUSB since the Micor does all the PL work now. I created the simpleusb.conf file, changed rpt.conf to use it and seem to be back in business as it talks to the URI correctly. When I do a "radio tune" I get a message about "usb not active" and a device string of "-1". Is this anything to worry about, or how can I reset levels using simpleUSB? I want to get the repeater back into service without the remote base for now. The URI has the EEPROM and the simpleusb_tune_usb.conf file has the correct "4-1" for the device string in it. Thanks, Tony

2 1

URI For Sale
by Douglas Fitts 11 Oct '11

11 Oct '11

For you AllStar users, I have for sale the DMK Engineering URI device and associated interface cable. I purchased it [through PayPal] way back on November 2, 2010, I did download the program to the specific computer, logged onto the AllStar website as a System Op but never actually hooked up a radio to make the node play. I paid with shipping $79.90 and will sell the URI for $60 dollars plus $4.95 Priority Mail shipping. I am not sure if any documentation or CD came with the device but I am sure you can get the original factory DMK docs from their website. I will look to see if in fact I have an installation CD but I kind of doubt it. If you are interested please email me direct to my w7fdf(a)yahoo.com email address. Soon as I get the funds into my PayPal account I will create a shipping label, pack up the device and cable, include a photocopy of the original sales receipt for your records and off it goes to the new owner. If you do not have a PayPal account then its okay to mail me a money order. If you desire to mail a personal check I will not ship the URI until your check clears my banking institution. My address is good on the QRZ website shownhere. 73 Doug W7FDF Vail Arizona U.S.A. I

1 0

Issues After Reboot
by Travis Best 11 Oct '11

11 Oct '11

After Rebooting Today I am now having the following issue /var/log/messages Oct 10 22:34:20 tbest kernel: asterisk[9571]: segfault at 1a4540b3 ip 08098f56 sp b6dc3140 error 6 in asterisk[8048000+101000] /var/log/asterisk/full [Oct 10 22:36:47] NOTICE[10142] cdr.c: CDR simple logging enabled. [Oct 10 22:36:47] NOTICE[10142] loader.c: 162 modules will be loaded. [Oct 10 22:36:47] WARNING[10142] res_smdi.c: No SMDI interfaces are available to listen on, not starting SMDI listener. Any Ideas???? Thanks Travis

2 1

Re: [App_rpt-users] Reverse autopatch immediately hanging up
by Josh Freeman 10 Oct '11

10 Oct '11

OK, I tried that... it looks like the reverse autopatch *does* work correctly when dialed into via pure IAX. Unfortunately, only being able to use native IAX clients doesn't meet the requirements for what I'm trying to do. I'll study up some more on how Local channels work, maybe I'm not using that mechanism correctly. Thanks, Josh On 10/10/2011 6:21 PM, Jim Duuuude wrote: > okay, try calling it directly from your IAX client, rather then > through a Local channel > > ------------------------------------------------------------------------ > Date: Mon, 10 Oct 2011 18:05:16 -0500 > From: cpe.jfreeman(a)gmail.com > To: APP_RPT-USERS(a)OHNOSEC.ORG > Subject: Re: [App_rpt-users] Reverse autopatch immediately hanging up > > Jim, > > That would be correct, if I had left the [radio] context as it was in > the bundled Allstar dialplan, where this line > > exten=_07XX,1,Goto(parkedcalls|${EXTEN:1}|1) > > makes it necessary to dial the leading "0." I created a different > radio context, and simply added > > include => parkedcalls > > so that the pickup code *is* actually just '701'. > > Because I don't understand everything about this system, though, I > tried reverting that part of my dialplan back to the Allstar > configuration, just to see if that made a difference. It didn't - the > autopatch still gets hung up within a second or two of connection. > Dialing through the Local channel is the thing I'm doing that's > significantly different than anything in the Allstar dialplan, so I'm > guessing that's where the problem is - but I'm not smart enough to > find it yet. > > Thanks, > Josh > > On 10/10/2011 1:33 PM, Jim Duuuude wrote: > > Thats because youre missing a 'digits/0' between the incall and > the PARKED, such as: > > Rpt(${EXTEN:1}|Rrpt/node:NODE:rpt/in-call:digits/0:PARKED|120) > > The code to pick that up should be '0701' *not* 701 > > JIM WB6NIL > > ------------------------------------------------------------------------ > Date: Mon, 10 Oct 2011 11:06:52 -0500 > From: cpe.jfreeman(a)gmail.com <mailto:cpe.jfreeman@gmail.com> > To: APP_RPT-USERS(a)OHNOSEC.ORG <mailto:APP_RPT-USERS@OHNOSEC.ORG> > Subject: [App_rpt-users] Reverse autopatch immediately hanging up > > Hello, > > I'm trying to set up a system that has a reverse autopatch as one > of its features. The problem I'm having is that when a radio user > dials the code to pick up an incoming call, the call gets > disconnected almost immediately upon connecting. I'm certain the > problem is that I've not set things up properly, but I'm still > inexperienced enough that I could really use some help > troubleshooting. > > My Asterisk system is running from a recent ACID image (downloaded > maybe three weeks ago). The machine also has a TDM400P card with > an FXS module connected to an analog telephone I'm using to > originate incoming test calls to the repeater system. > > The relevant parts of my dialplan are as follows: > > In context *phones_local*: > > exten => 272727,1,Dial(Local/CQCQCQ@repeater) > (Apparently, I can't directly connect to app_rpt from a Zap > channel, so I dial through a Local channel instead.) > > Then, in context *repeater*: > > exten => CQCQCQ,1,Rpt(5674,Rrpt/in-call:PARKED,120) > (This is an isolated system, so the node number is simply my name > on a telephone keypad.) > > What happens is this: I dial 272727 from the analog telephone, and > I hear the announcement over the radio just fine. I send *6701 > from the radio, and hear "Connecting" from the repeater along with > echoing audio from the analog phone (because it's right there next > to the radio). Then, I immediately hear "Call terminated" and the > autopatch drops. The analog phone doesn't get hung up, though. > > Here's what I see on the Asterisk console. For this trace, I was > actually dialing in from an IAX softphone rather than the Zap > channel, but the behavior is exactly the same. > > -- Executing [272727@phones_local:1] Dial("IAX2/josh-12630", > "Local/CQCQCQ@repeater") in new stack > -- Called CQCQCQ@repeater > -- Executing [CQCQCQ@repeater:1] > Rpt("Local/CQCQCQ@repeater-781b,2", > "5674|Rrpt/in-call:PARKED|120") in new stack > -- Return Context: (repeater,CQCQCQ,2) ID: 0 > -- Warning: Return Context Invalid, call will return to default|s > -- Music class default requested but no musiconhold loaded. > == Parked Local/CQCQCQ@repeater-781b,2 on 701@parkedcalls. Will > timeout back to extension [repeater] CQCQCQ, 2 in 45 seconds > -- Added extension '701' priority 1 to parkedcalls > -- Music class default requested but no musiconhold loaded. > -- Music class default requested but no musiconhold loaded. > -- Local/CQCQCQ@repeater-781b,1 answered IAX2/josh-12630 > -- Call Parking Called, lot: 701, timeout: 0, context: (null) > -- Music class default requested but no musiconhold loaded. > -- <Zap/pseudo-1800116975> Playing 'rpt/in-call' (language 'en') > -- <Zap/pseudo-1800116975> Playing 'digits/7' (language 'en') > -- <Zap/pseudo-1800116975> Playing 'digits/0' (language 'en') > -- <Zap/pseudo-1800116975> Playing 'digits/1' (language 'en') > -- Hungup 'Zap/pseudo-1800116975' > -- Hungup 'Zap/pseudo-1018949410' > [Oct 9 19:44:18] NOTICE[2594]: chan_usbradio.c:3010 > usbradio_read: Got DTMF char * duration 340 ms > [Oct 9 19:44:19] NOTICE[2594]: chan_usbradio.c:3010 > usbradio_read: Got DTMF char 6 duration 235 ms > [Oct 9 19:44:20] NOTICE[2594]: chan_usbradio.c:3010 > usbradio_read: Got DTMF char 7 duration 255 ms > [Oct 9 19:44:20] NOTICE[2594]: chan_usbradio.c:3010 > usbradio_read: Got DTMF char 0 duration 212 ms > -- Hungup 'Zap/pseudo-1705936882' > [Oct 9 19:44:21] NOTICE[2594]: chan_usbradio.c:3010 > usbradio_read: Got DTMF char 1 duration 235 ms > -- Executing [701@phones_radio:1] > ParkedCall("Zap/pseudo-523589909", "701") in new stack > -- Channel Zap/pseudo-523589909 connected to parked call 701 > == Spawn extension (phones_radio, 701, 1) exited non-zero on > 'Local/CQCQCQ@repeater-781b,1<ZOMBIE>' > -- Hungup 'Zap/pseudo-1742992459' > -- Hungup 'Zap/pseudo-1417902655' > -- <Zap/pseudo-1427730098> Playing 'rpt/callproceeding' > (language 'en') > -- Hungup 'Zap/pseudo-1427730098' > -- <Zap/pseudo-1938338821> Playing 'rpt/callterminated' > (language 'en') > -- Hungup 'Zap/pseudo-1938338821' > -- Hungup 'Zap/pseudo-1525511763' > > I see some things about invalid return context and zombie > channels, but I'm not sure what that means. Any idea what it is > I'm missing? > > Thanks, > Josh > > > _______________________________________________ App_rpt-users > mailing list App_rpt-users(a)ohnosec.org > <mailto:App_rpt-users@ohnosec.org> > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > > > > _______________________________________________ App_rpt-users mailing > list App_rpt-users(a)ohnosec.org > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

1 0

Reverse autopatch immediately hanging up
by Josh Freeman 10 Oct '11

10 Oct '11

Hello, I'm trying to set up a system that has a reverse autopatch as one of its features. The problem I'm having is that when a radio user dials the code to pick up an incoming call, the call gets disconnected almost immediately upon connecting. I'm certain the problem is that I've not set things up properly, but I'm still inexperienced enough that I could really use some help troubleshooting. My Asterisk system is running from a recent ACID image (downloaded maybe three weeks ago). The machine also has a TDM400P card with an FXS module connected to an analog telephone I'm using to originate incoming test calls to the repeater system. The relevant parts of my dialplan are as follows: In context *phones_local*: exten => 272727,1,Dial(Local/CQCQCQ@repeater) (Apparently, I can't directly connect to app_rpt from a Zap channel, so I dial through a Local channel instead.) Then, in context *repeater*: exten => CQCQCQ,1,Rpt(5674,Rrpt/in-call:PARKED,120) (This is an isolated system, so the node number is simply my name on a telephone keypad.) What happens is this: I dial 272727 from the analog telephone, and I hear the announcement over the radio just fine. I send *6701 from the radio, and hear "Connecting" from the repeater along with echoing audio from the analog phone (because it's right there next to the radio). Then, I immediately hear "Call terminated" and the autopatch drops. The analog phone doesn't get hung up, though. Here's what I see on the Asterisk console. For this trace, I was actually dialing in from an IAX softphone rather than the Zap channel, but the behavior is exactly the same. -- Executing [544484@phones_local:1] Dial("IAX2/josh-12630", "Local/CQCQCQ@repeater") in new stack -- Called CQCQCQ@repeater -- Executing [CQCQCQ@repeater:1] Rpt("Local/CQCQCQ@repeater-781b,2", "5674|Rrpt/in-call:PARKED|120") in new stack -- Return Context: (repeater,CQCQCQ,2) ID: 0 -- Warning: Return Context Invalid, call will return to default|s -- Music class default requested but no musiconhold loaded. == Parked Local/CQCQCQ@repeater-781b,2 on 701@parkedcalls. Will timeout back to extension [repeater] CQCQCQ, 2 in 45 seconds -- Added extension '701' priority 1 to parkedcalls -- Music class default requested but no musiconhold loaded. -- Music class default requested but no musiconhold loaded. -- Local/CQCQCQ@repeater-781b,1 answered IAX2/josh-12630 -- Call Parking Called, lot: 701, timeout: 0, context: (null) -- Music class default requested but no musiconhold loaded. -- <Zap/pseudo-1800116975> Playing 'rpt/in-call' (language 'en') -- <Zap/pseudo-1800116975> Playing 'digits/7' (language 'en') -- <Zap/pseudo-1800116975> Playing 'digits/0' (language 'en') -- <Zap/pseudo-1800116975> Playing 'digits/1' (language 'en') -- Hungup 'Zap/pseudo-1800116975' -- Hungup 'Zap/pseudo-1018949410' [Oct 9 19:44:18] NOTICE[2594]: chan_usbradio.c:3010 usbradio_read: Got DTMF char * duration 340 ms [Oct 9 19:44:19] NOTICE[2594]: chan_usbradio.c:3010 usbradio_read: Got DTMF char 6 duration 235 ms [Oct 9 19:44:20] NOTICE[2594]: chan_usbradio.c:3010 usbradio_read: Got DTMF char 7 duration 255 ms [Oct 9 19:44:20] NOTICE[2594]: chan_usbradio.c:3010 usbradio_read: Got DTMF char 0 duration 212 ms -- Hungup 'Zap/pseudo-1705936882' [Oct 9 19:44:21] NOTICE[2594]: chan_usbradio.c:3010 usbradio_read: Got DTMF char 1 duration 235 ms -- Executing [701@phones_radio:1] ParkedCall("Zap/pseudo-523589909", "701") in new stack -- Channel Zap/pseudo-523589909 connected to parked call 701 == Spawn extension (phones_radio, 701, 1) exited non-zero on 'Local/CQCQCQ@repeater-781b,1<ZOMBIE>' -- Hungup 'Zap/pseudo-1742992459' -- Hungup 'Zap/pseudo-1417902655' -- <Zap/pseudo-1427730098> Playing 'rpt/callproceeding' (language 'en') -- Hungup 'Zap/pseudo-1427730098' -- <Zap/pseudo-1938338821> Playing 'rpt/callterminated' (language 'en') -- Hungup 'Zap/pseudo-1938338821' -- Hungup 'Zap/pseudo-1525511763' I see some things about invalid return context and zombie channels, but I'm not sure what that means. Any idea what it is I'm missing? Thanks, Josh

2 3

Re: [App_rpt-users] Asterisk falls over soon after boot. (Segfault error)
by Ken Page 10 Oct '11

10 Oct '11

Hi Tony, I checked that config file but the CTCSS tone values either match or are remarked out on configs where the CTCSS is not used. We don't actually use any CTCSS on any of our radio's currently. However keep in mind that this fault (segmentation fault) has just come out of the blue. No config files or for that matter software has been changed or updated in weeks. One thing that sticks in my mind is that the server did freeze up a few days before this problem started and I did have to reset it. Once again I do wonder if it is simply a corrupt binary file maybe? I do wonder about maybe recompiling parts or all of the Asterisk and radio related stuff and re-installing the binaries. I don't really want to fiddle too much with that side of things without instruction though. The system here is run on a Gentoo Linux distro as we have other things on the go here as well with it. Originally getting the Asterisk Radio stuff totally up and running and bug free was only possible with the assistance of the magic touch of the GURU himself. Mr Jim Dude!. My recollection however is that in /usr/src/asterisk is the last installed version. So perhaps I can do a re-install from that without hopefully wiping any of our config files? Oh well. System has only been offline about a week or so now so I guess there is no rush yet. I can try to nut this out a bit further before I start playing with things I don't fully understand. Thanks for your input though. Much appreciated to get some feedback. Regards, Ken - vk4akp .-.-. > Message: 2 > Date: Mon, 10 Oct 2011 11:22:27 -0700 (PDT) > From: Tony KT9AC<kt9ac(a)ameritech.net> > To: app_rpt-users(a)ohnosec.org, Ken Page<vk4akp(a)yahoo.com.au> > Subject: Re: [App_rpt-users] Asterisk Bombs after startup. > Message-ID: > <1318270947.13182.YahooMailClassic(a)web81007.mail.mud.yahoo.com> > Content-Type: text/plain; charset=iso-8859-1 > > Hi Ken, > Check /etc/asterisk/usbradio.conf and look to see that your number count of CTCSS decode and encode tones match. That is what the error message is saying: > > ERROR: numrxcodes != numtxcodes > > Tony > > > --- On Mon, 10/10/11, Ken Page<vk4akp(a)yahoo.com.au> wrote: > >> From: Ken Page<vk4akp(a)yahoo.com.au> >> Subject: Re: [App_rpt-users] Asterisk Bombs after startup. >> To: app_rpt-users(a)ohnosec.org >> Date: Monday, October 10, 2011, 10:32 AM >> OK, I've found something else that >> might help diagnose the issue? >> >> I ran? asterisk -cvvvv???and got the >> following at the end before it bombs. >> >> ???"Segmentation fault" >> >> Could it be there is a corrupt file or something? >> >> Funny thing is everything works fine for about the first >> 10-20 seconds. >> >> The last thing it tries is some radio tune file. >> >> Maybe I should try downloading and recompiling the APP_RPT >> & USB_Radio >> modules? >> >> Any idea's? >> >> ~Ken~ >> vk4akp >> .-.-. >> >> >> [Oct 11 00:44:50] NOTICE[28167]: app_rpt.c:19094 >> rpt_master: Normal >> Repeater Init? 2134 >> ? ???-- Loading initial config for >> repeater 20040 >> ???== Parsing '/etc/asterisk/rpt.conf': >> Found >> ? ???-- Re-Loading config for repeater >> 2134 >> ???== Parsing '/etc/asterisk/rpt.conf': >> Found >> ERROR: numrxcodes != numtxcodes >> ? ???-- rpt (Rx) initiating call to >> Radio/usb on Radio/usb >> ???== Set device 1-2 to usb >> ERROR: numrxcodes != numtxcodes >> [Oct 11 00:44:50] NOTICE[28167]: app_rpt.c:19094 >> rpt_master: Normal >> Repeater Init? 20040 >> ? ???-- Re-Loading config for repeater >> 20040 >> ???== Parsing '/etc/asterisk/rpt.conf': >> Found >> ? ???-- rpt (Rx) initiating call to >> Radio/usb1 on Radio/usb1 >> ???== Parsing >> '/etc/asterisk/usbradio_tune_usb.conf': Found >> [Oct 11 00:44:50] WARNING[28171]: chan_usbradio.c:1449 >> hidthread: Loaded >> parameters from usbradio_tune_usb.conf for device usb . >> ???== Set device 1-1 to usb1 >> ???== Parsing >> '/etc/asterisk/usbradio_tune_usb1.conf': Found >> [Oct 11 00:44:50] WARNING[28173]: chan_usbradio.c:1449 >> hidthread: Loaded >> parameters from usbradio_tune_usb1.conf for device usb1 . >> ? ???-- Hungup 'Zap/pseudo-327798110' >> Segmentation fault >>

1 0

Re: [App_rpt-users] Asterisk Bombs after startup.
by Ken Page 10 Oct '11

10 Oct '11

OK, I've found something else that might help diagnose the issue? I ran asterisk -cvvvv and got the following at the end before it bombs. "Segmentation fault" Could it be there is a corrupt file or something? Funny thing is everything works fine for about the first 10-20 seconds. The last thing it tries is some radio tune file. Maybe I should try downloading and recompiling the APP_RPT & USB_Radio modules? Any idea's? ~Ken~ vk4akp .-.-. [Oct 11 00:44:50] NOTICE[28167]: app_rpt.c:19094 rpt_master: Normal Repeater Init 2134 -- Loading initial config for repeater 20040 == Parsing '/etc/asterisk/rpt.conf': Found -- Re-Loading config for repeater 2134 == Parsing '/etc/asterisk/rpt.conf': Found ERROR: numrxcodes != numtxcodes -- rpt (Rx) initiating call to Radio/usb on Radio/usb == Set device 1-2 to usb ERROR: numrxcodes != numtxcodes [Oct 11 00:44:50] NOTICE[28167]: app_rpt.c:19094 rpt_master: Normal Repeater Init 20040 -- Re-Loading config for repeater 20040 == Parsing '/etc/asterisk/rpt.conf': Found -- rpt (Rx) initiating call to Radio/usb1 on Radio/usb1 == Parsing '/etc/asterisk/usbradio_tune_usb.conf': Found [Oct 11 00:44:50] WARNING[28171]: chan_usbradio.c:1449 hidthread: Loaded parameters from usbradio_tune_usb.conf for device usb . == Set device 1-1 to usb1 == Parsing '/etc/asterisk/usbradio_tune_usb1.conf': Found [Oct 11 00:44:50] WARNING[28173]: chan_usbradio.c:1449 hidthread: Loaded parameters from usbradio_tune_usb1.conf for device usb1 . -- Hungup 'Zap/pseudo-327798110' Segmentation fault -- On 10/7/2011 2:00 AM, app_rpt-users-request(a)ohnosec.org wrote: > Send App_rpt-users mailing list submissions to > app_rpt-users(a)ohnosec.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > or, via email, send a message with subject or body 'help' to > app_rpt-users-request(a)ohnosec.org > > You can reach the person managing the list at > app_rpt-users-owner(a)ohnosec.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of App_rpt-users digest..." > > > Today's Topics: > > 1. Re: App_rpt-users Digest, Vol 32, Issue 6 (Ken Page) > 2. Re: for those Limey Linux and or D525MW users who are brave > enough (Ramesh Dhami (VA3UV)) > 3. Re: for those Limey Linux and or D525MW users who are brave > enough (Jim Duuuude) > 4. Re: for those Limey Linux and or D525MW users who are brave > enough (Ramesh Dhami (VA3UV)) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 07 Oct 2011 01:50:38 +1000 > From: Ken Page<vk4akp(a)yahoo.com.au> > To: app_rpt-users(a)ohnosec.org > Subject: Re: [App_rpt-users] App_rpt-users Digest, Vol 32, Issue 6 > Message-ID:<4E8DCE4E.7020900(a)yahoo.com.au> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi Mr Duuuude, > > Well. I am able to access the PBX via the phone that is plugged into the > TDM card and jump on the meetme conference. > > I can also bridge in another caller into the conference and talk for > about 10 seconds before Asterisk stops / falls over. > > The last thing in the log that Asterisk seems to try to do before it > crashes is read the radio tune stuff. > > The two URI interfaces do flash as per normal for a while before it all > crashes. > > If I just try rebooting the machine but not accessing Asterisk at all > via phone or anything it still falls over soon after boot. > > Weird. > > Am I right in guessing that because I can access meetme conference and > also the TDM card that the zaptel drivers are loaded OK? > > ~Ken - vk4akp~ > .-.-. > > > On 10/7/2011 1:30 AM, app_rpt-users-request(a)ohnosec.org wrote: >> Message: 3 >> Date: Thu, 6 Oct 2011 08:30:55 -0700 >> From: Jim Duuuude<telesistant(a)hotmail.com> >> To:<vk4akp(a)yahoo.com.au>, app_rpt mailing list >> <app_rpt-users(a)ohnosec.org> >> Subject: Re: [App_rpt-users] Asterisk service stopping minutes after >> boot constantly.. Help? >> Message-ID:<BLU155-W223FE76CA98B46CFDF40CEB1F90(a)phx.gbl> >> Content-Type: text/plain; charset="iso-8859-1" >> >> >> looks to me like maybe Zaptel isnt running >> >> JIM >> >>>> Date: Fri, 7 Oct 2011 01:29:32 +1000 >>>> From:vk4akp@yahoo.com.au >>>> To:app_rpt-users@ohnosec.org >>>> Subject: [App_rpt-users] Asterisk service stopping minutes after boot constantly.. Help? >>>> >>>> Hi, >>>> >>>> Last few days I have had a problem with Asterisk stopping for no reason. >>>> >>>> Asterisk service stops a couple of minutes after boot for no reason. >>>> >>>> Every time I reboot or restart Asterisk I get the same thing. Asterisk >>>> runs for a couple of minutes and then drops out. >>>> >>>> Nothing has been changed on the system in weeks. >>>> >>>> Any idea's? >>>> >>>> Tail of the log is included below. >>>> >>>> ~Ken - vk4akp~ >>>> .-.-. >>>> >>>> [Oct 7 00:29:41] NOTICE[7624] pbx_ael.c: Starting AEL load process. >>>> [Oct 7 00:29:41] NOTICE[7624] pbx_ael.c: AEL load process: calculated >>>> config file name '/etc/asterisk/extensions.ael'. >>>> [Oct 7 00:29:41] NOTICE[7624] pbx_ael.c: AEL load process: parsed >>>> config file name '/etc/asterisk/extensions.ael'. >>>> [Oct 7 00:29:41] NOTICE[7624] pbx_ael.c: AEL load process: checked >>>> config file name '/etc/asterisk/extensions.ael'. >>>> [Oct 7 00:29:41] NOTICE[7624] pbx_ael.c: AEL load process: compiled >>>> config file name '/etc/asterisk/extensions.ael'. >>>> [Oct 7 00:29:41] NOTICE[7624] pbx_ael.c: AEL load process: merged >>>> config file name '/etc/asterisk/extensions.ael'. >>>> [Oct 7 00:29:41] NOTICE[7624] pbx_ael.c: AEL load process: verified >>>> config file name '/etc/asterisk/extensions.ael'. >>>> [Oct 7 00:29:41] ERROR[7624] codec_dahdi.c: Failed to open >>>> /dev/zap/transcode: No such file or directory >>>> [Oct 7 00:29:41] NOTICE[7624] chan_irlp.c: Unable to load config irlp.conf >>>> [Oct 7 00:29:42] NOTICE[7624] app_gps.c: Unable to load config gps.conf >>>> [Oct 7 00:29:42] NOTICE[7665] app_rpt.c: Normal Repeater Init 2134 >>>> [Oct 7 00:29:42] NOTICE[7665] app_rpt.c: Normal Repeater Init 20040 >>>> [Oct 7 00:29:42] WARNING[7668] chan_usbradio.c: Loaded parameters from >>>> usbradio_tune_usb.conf for device usb . >>>> [Oct 7 00:29:42] WARNING[7672] chan_usbradio.c: Loaded parameters from >>>> usbradio_tune_usb1.conf for device usb1 . >>>> >>>> -- >>>> > > ------------------------------ > > Message: 2 > Date: Thu, 06 Oct 2011 11:54:11 -0400 > From: "Ramesh Dhami (VA3UV)"<Ramesh(a)va3uv.com> > To: app_rpt mailing list<app_rpt-users(a)ohnosec.org> > Subject: Re: [App_rpt-users] for those Limey Linux and or D525MW users > who are brave enough > Message-ID:<4E8DCF23.7050506(a)va3uv.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > On 06/10/2011 10:38 AM, Jim Duuuude wrote: >> Thin clients?? What do you think we are, and eating disorder clinic or >> something ?? :-) :-) >> >> First of all, Limey only supports VERY specific motherboard, of which >> that is not one. >> Also, since it runs entirely out of RAM, you need more then that for it >> to work in a reasonable >> manner. >> > <-- OK Jim; So I will save myself from those Limey's! > > Thin is good ... thin makes my hydro meter spin slowly. These things > run of 13.8V @ ~ 600mA. Me likes that :). > > Cheers! > > Ramesh. > > p.s., for all those than inquired last week - the ISO and install > scripts for my FREE STAR* project are now on my site: > > http://www.va3uv.com/iso.htm > > The install script will even allow you to install on top of an ACID > build - how's that for playing nice! > > > ------------------------------ > > Message: 3 > Date: Thu, 6 Oct 2011 08:55:38 -0700 > From: Jim Duuuude<telesistant(a)hotmail.com> > To: Ramesh Dhami<ramesh(a)va3uv.com>, app_rpt mailing list > <app_rpt-users(a)ohnosec.org> > Subject: Re: [App_rpt-users] for those Limey Linux and or D525MW users > who are brave enough > Message-ID:<BLU155-W16D3D603597EDFF11F559EB1F90(a)phx.gbl> > Content-Type: text/plain; charset="iso-8859-1" > > > Why dont you try a Beagleboard and LOX board.. It runs at 1/4 of that power! > > JIM > >> Date: Thu, 6 Oct 2011 11:54:11 -0400 >> From: Ramesh(a)va3uv.com >> To: app_rpt-users(a)ohnosec.org >> Subject: Re: [App_rpt-users] for those Limey Linux and or D525MW users who are brave enough >> >> On 06/10/2011 10:38 AM, Jim Duuuude wrote: >>> Thin clients?? What do you think we are, and eating disorder clinic or >>> something ?? :-) :-) >>> >>> First of all, Limey only supports VERY specific motherboard, of which >>> that is not one. >>> Also, since it runs entirely out of RAM, you need more then that for it >>> to work in a reasonable >>> manner. >>> >> <-- OK Jim; So I will save myself from those Limey's! >> >> Thin is good ... thin makes my hydro meter spin slowly. These things >> run of 13.8V @ ~ 600mA. Me likes that :). >> >> Cheers! >> >> Ramesh. >> >> p.s., for all those than inquired last week - the ISO and install >> scripts for my FREE STAR* project are now on my site: >> >> http://www.va3uv.com/iso.htm >> >> The install script will even allow you to install on top of an ACID >> build - how's that for playing nice! >> _______________________________________________ >> App_rpt-users mailing list >> App_rpt-users(a)ohnosec.org >> http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users > >

2 1

Motorola Astro
by Howard Small 10 Oct '11

10 Oct '11

I wish to use two Motorola Astro UHF sets as a repeater with a URI interface. The sets are model T99DX+144W and I am wondering if anyone has done this? If so can you share your experience please. Howard VK4BS

1 0

Serial/Parallel interface
by Carl Davies 07 Oct '11

07 Oct '11

Hi Andrew, thanks for the reply, yes the problem is Blobbed epoxy chips. Even when the vendor shows the chip type or even picture, there is no guarantee it will not be a blob, I have fallen foul of cheap Chinese imports on Ebay. I have since found the information relating to the parallel port here, http://ohnosec.org/drupal/node/177 Thanks, Regards Carl M1ELR ALLLSTAR node 27473. On Sun, 02 Oct 2011 22:09:18 Carl Davies wrote: >* Hi group,*>**>* Carl M1ELR here, I noticed in a post a few days ago there was mention of*>* using the Parallel port for PTT or COR, is this possible?*>**>* I currently run my node using the Centos install package from the Allstar*>* site but can change to the install version from Xipar if needed.*>**>* I have without success been buying sound fobs to build a new interface and*>* now have a drawer full of USB fobs that I can't mod, if the I/O wasn't via*>* the USB sound fob that would make life so much easier as the CM108 seems to*>* be getting harder to source.* Hello, What is the problem with those USB fobs? Is it that they are epoxy blobbed? If they are packaged chips, is it because they are not CM108? What chip are they? Please post the vendor ID/Product ID info. I have been working with CM108 compatible chips- maybe I can contribute something useful here. 73, Andrew ZL3AME

3 2