[arm-allstar] IAX Connections Locking Up on Connect

[Sean McCarthy]

I have, in fact that's where I picked up the line that was giving me fits.
Still no CID. Can someone send me theri working extensions and iax config
files, I'm sure I can figure it out from a known working conf.

Thanks,
Sean

On Wed, Mar 27, 2019 at 4:21 PM "Doug Crompton via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> Sean,
>
>  You do have both the extension.conf and iax.conf stanzas added for the
> dvswitch (Android iaxrpt) as per the howto at hamvoip?  This handles the
> CID.
>
>
> *73 Doug*
>
> *WA3DSP*
>
> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
>
> On Wed, Mar 27, 2019 at 3:58 PM "Sean McCarthy via ARM-allstar" <
> arm-allstar at hamvoip.org> wrote:
>
> > FIXED!!!
> >
> > So I did a search (AGAIN) and this time I found a post by our very own
> > David, which fixed the problem. Thank you David and I'm sorry I couldn't
> > find this earlier, been bugging me for months...
> >
> > Only problem now is I get "node no-cid connected" instead of the cid
> > entered in the program, my setup or dvswitch?
> >
> > Thanks!
> >
> >
> ---------------------------------------------------------------------------------------------------------------------------
> >
> > Everyone,
> >
> > This issue with PTT being initially keyed has been historically discussed
> > several times over on the app_rpt-users mailing list. For example, see
> > this thread:
> >
> http://lists.allstarlink.org/pipermail/app_rpt-users/2016-July/015560.html
> >
> > After looking through some discussion threads, the solution seems to be
> to
> > modify your /etc/asterisk/extensions.conf file, changing the following:
> >
> > ;original:
> > [radio-iaxrpt]
> > exten=1998,1,Rpt,1998|X
> > exten=1999,1,Rpt,1999|X
> >
> >
> > ;fixed:
> > [radio-iaxrpt]
> > exten=1998,1,Rpt,1998|P
> > exten=1999,1,Rpt,1999|P
> >
> >
> > ...You need to specify your node number(s) rather than 1998, 1999, of
> > course.
> >
> > Also, see this message from app_rpt-users for a more comprehensive
> > extensions.conf stanza for iaxrpt:
> >
> http://lists.allstarlink.org/pipermail/app_rpt-users/2016-July/015563.html
> >
> > Please try this and report back if this is a resolution. If this fixes
> the
> > problem, we'll update our base config files to reflect this change.
> >
> >
> > 73, David KB4FXC
> >
> >
> > On Sun, Mar 24, 2019 at 10:29 PM Sean McCarthy <smccarthy61 at gmail.com>
> > wrote:
> >
> > > It is the latest version of DVSwitch mobile (paid)
> > >
> > > I know it is neither the client or the device as I can log into 3 other
> > > hamvoip nodes with it and the problem DOES NOT follow.
> > >
> > > I also have half a dozen users that can use their DVSwitch client on
> > other
> > > nodes without issue, but the lock mine up on connect.
> > >
> > > It is no doubt something in MY node setup misconfigured or broken.
> > >
> > >
> > > On Sun, Mar 24, 2019 at 8:29 PM "Doug Crompton via ARM-allstar" <
> > > arm-allstar at hamvoip.org> wrote:
> > >
> > >> Sean,
> > >>
> > >>  Are you talking about Windows iaxrpt or dvswitch on Android (formerly
> > >> iaxrpt)
> > >>
> > >> I have never heard of windows iaxrpt doing that. Both programs are not
> > >> hamvoip related. the Windows iaxrpt is no longer support. I have seen
> > >> reports of dvswitch doing this. This is an application issue. dvswitch
> > has
> > >> its own support forum.
> > >>
> > >>
> > >> *73 Doug*
> > >>
> > >> *WA3DSP*
> > >>
> > >> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> > >>
> > >>
> > >> On Sun, Mar 24, 2019 at 7:45 PM "Sean McCarthy via ARM-allstar" <
> > >> arm-allstar at hamvoip.org> wrote:
> > >>
> > >> > I have an ongoing issue with incoming IAX connections to my node.
> > >> > When a connection is made, the node goes into TX until the connected
> > >> user
> > >> > hits the PTT one time, then it works perfectly. We've been working
> > >> around
> > >> > the issue for months, but as more folks are allowed IAX connection
> in,
> > >> it
> > >> > gets forgotten frequently.
> > >> >
> > >> > I know others have experienced this in the past, so I'm hoping
> someone
> > >> > knows a cure.
> > >> >
> > >> > I've tried it with multiple devices and they all do it, and those
> > >> devices
> > >> > do not do it on other nodes, so I know it's something in my setup...
> > >> >
> > >> > Thanks,
> > >> > Sean
> > >> > _______________________________________________
> > >> >
> > >> > ARM-allstar mailing list
> > >> > ARM-allstar at hamvoip.org
> > >> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >> >
> > >> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > >> >
> > >> _______________________________________________
> > >>
> > >> ARM-allstar mailing list
> > >> ARM-allstar at hamvoip.org
> > >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >>
> > >> Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > >>
> > >
> > _______________________________________________
> >
> > ARM-allstar mailing list
> > ARM-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> >
> _______________________________________________
>
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>