[arm-allstar] iaxrpt PTT keyed on start up (fix?) --was: iax rpt problem with hamvoip

[David Andreatta]

 Howdy, All;

I hadn't used either the Android app or Windows software for access for awhile. When I initially set up access, I was using the Windows application and, thus, used |X in the stanza. Having just tried access from the Android app, it appears I had the "PTT held on" problem as well! Changing the stanza to use "|P" has fixed the problem so that the Android app now works fine. (I don't have the Windows application installed here so I cannot try it with "|P" in the stanza.) So, this is yet another instance where the change to |P fixed the problem Re: access from the Android app. 

73,

Dave
WD0HXN
Erie, CO
 
    On Friday, May 4, 2018, 7:56:54 AM MDT, David McGough via arm-allstar <arm-allstar at hamvoip.org> wrote:  
 
 

Well took care of the problem for me..

Thanks
73 AA4II

On Fri, May 4, 2018 at 8:13 AM, David McGough <kb4fxc at inttek.net> wrote:

>
> 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
>
*** snip ***