Android IAXRPT stuck PTT

App_rpt-users
1

All this talk of Android IAXRPT got me interested. I installed it
(v1.13). Sometimes when I connect to my node, the PTT on the node will
stick on. There is no indication of this in the app and no audio going
through, just dead air. (Luckily I had a radio monitoring and
discovered this issue quickly.) Other times I connect and it works
just fine--PTT follows the PTT button. What's going on here? Why does
it transmit without PTT pressed?

On IAXRPT for Windows (running in Wine on OS X), PTT behaves correctly.

I also have Zopier set up, but I configured this for VOX. I hit the
mute button when I don't want to transmit. It works just fine.

Relevant configuration stanzas below. (Let me know if you need more.)

Tom KD7LXL

iax.conf:

[iaxrpt]
username=iaxrpt
type=friend
context=radio-gui
auth=md5
secret=xxx
host=dynamic
disallow=all
allow=gsm
allow=ulaw
allow=g726aal2
notransfer=yes

[tomsphone] ; Zoiper Setup
username=tomsphone
type=friend
context=tomsphone
host=dynamic
auth=md5
secret=xxx
disallow=all
allow=ulaw
allow=g726aal2
allow=gsm
codecpriority=host
transfer=no
callerid="KD7LXL"

extensions.conf:

[radio-gui]
exten => 41702,1,rpt(41702|X)
exten => 1001,1,rpt(1001|X)

[tomsphone]
exten => 41702,1,answer()
exten => 41702,n,Playback(rpt/connected)
exten => 41702,n,rpt(41702|Pv)
exten => 1001,1,answer()
exten => 1001,n,Playback(rpt/connected)
exten => 1001,n,rpt(1001|Pv)

2

I’ve personally found, I had an old samsung galaxy phone, that leaving the app going all of the time in the background would cause things like that to happen. I would normally fire the app up to use it and then shut it down when down.

However I just got a new phone yesterday so I will have to reevaluate how it behaves on my new phone.

N1XBM

Apparare Scientor

Paratus Communicare

Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657

www.radioguysrepeaternetwork.com

3

For some reason I did not get Tom’s message from the list.

Tom,

Which context are you connecting to?
···

On 07/21/2016 07:41 PM, Robert Newberry
wrote:

    I've personally found, I had an old samsung galaxy

phone, that leaving the app going all of the time in the
background would cause things like that to happen. I would
normally fire the app up to use it and then shut it down when
down.

    However I just got a new phone yesterday so I will

have to reevaluate how it behaves on my new phone.

N1XBM

    Apparare Scientor

    Paratus Communicare

    Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657

    [www.radioguysrepeaternetwork.com](http://www.radioguysrepeaternetwork.com)




_______________________________________________
App_rpt-users mailing list
To unsubscribe from this list please visit and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

-- "Anything is possible if you don't know what you are talking about."
1st Law of Logic

App_rpt-users@ohnosec.orghttp://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-usershttp://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

4

In trying to confirm this, I exited (via the menu, not just returning
to home screen), reopened the app, and connected a couple times in a
row and experienced the behavior every time.

However, my goal is to leave this connected and monitoring the
repeater all day instead of carrying an HT, so I'd love if it were
stable enough for that. Auto-reconnect would be nice too.

Tom KD7LXL

···

On Thu, Jul 21, 2016 at 4:41 PM, Robert Newberry <N1XBM@amsat.org> wrote:

I've personally found, I had an old samsung galaxy phone, that leaving the
app going all of the time in the background would cause things like that to
happen. I would normally fire the app up to use it and then shut it down
when down.

5

This is the context I use for AndroidIAX

[iax-client]��� ��� ��� ��� ; for IAX VIOP clients.��� ��� ��� ���

exten => ${NODE},1,Ringing

exten => ${NODE},n,Wait(3)

exten => ${NODE},n,Answer

exten => ${NODE},n,Set(NODENUM=${CALLERID(number)})

exten => ${NODE},n,Playback(rpt/node|noanswer)

exten => ${NODE},n,SayDigits(${EXTEN})

exten => ${NODE},n,Set(CALLERID(num)=0)

exten => ${NODE},n,Rpt,${NODE}|P|${CALLERID(name)}

exten => ${NODE},n,Hangup

exten => ${NODE},n(hangit),Answer

exten => ${NODE},n(hangit),Wait(1)

exten => ${NODE},n(hangit),Hangup
···

On 07/21/2016 07:41 PM, Robert Newberry
wrote:

    I've personally found, I had an old samsung galaxy

phone, that leaving the app going all of the time in the
background would cause things like that to happen. I would
normally fire the app up to use it and then shut it down when
down.

    However I just got a new phone yesterday so I will

have to reevaluate how it behaves on my new phone.

N1XBM

    Apparare Scientor

    Paratus Communicare

    Allstar Node # 27086, 41540, 41812, 42086, 42658, 42657

    [www.radioguysrepeaternetwork.com](http://www.radioguysrepeaternetwork.com)




_______________________________________________
App_rpt-users mailing list
To unsubscribe from this list please visit and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"
You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

-- "Anything is possible if you don't know what you are talking about."
1st Law of Logic

App_rpt-users@ohnosec.orghttp://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-usershttp://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

6

Steve,

Good question. Sorry I wasn't clear on that. Android IAX and Windows
IAXRPT both connect to iaxrpt context. I only have the PTT issues with
Android IAX.

Reading the context you just posted, I'm trying to understand which
parts of it are critical. The telemetry drives me crazy so I cut that
out. Do I need to maybe add the Ringing, Wait, and Answer commands? (I
did try adding Answer at one point with no difference in behavior.)

Tom KD7LXL

···

On Thu, Jul 21, 2016 at 4:53 PM, Steve Zingman <szingman@msgstor.com> wrote:

For some reason I did not get Tom's message from the list.

Tom,
Which context are you connecting to?

7

Tom,
the relevant line is
exten => ${NODE},n,Rpt,${NODE}|P|${CALLERID(name)}

If you could try the complete context we can then prune it if it fixes the issue.

Steve

···

On 07/21/2016 07:58 PM, Tom Hayward wrote:

On Thu, Jul 21, 2016 at 4:53 PM, Steve Zingman <szingman@msgstor.com> wrote:

For some reason I did not get Tom's message from the list.

Tom,
Which context are you connecting to?

Steve,

Good question. Sorry I wasn't clear on that. Android IAX and Windows
IAXRPT both connect to iaxrpt context. I only have the PTT issues with
Android IAX.

Reading the context you just posted, I'm trying to understand which
parts of it are critical. The telemetry drives me crazy so I cut that
out. Do I need to maybe add the Ringing, Wait, and Answer commands? (I
did try adding Answer at one point with no difference in behavior.)

Tom KD7LXL

--
"Anything is possible if you don't know what you are talking about."
1st Law of Logic

8

I pasted this in verbatim and now connections fail:

[Jul 22 08:33:01] NOTICE[13402] chan_iax2.c: Rejected connect attempt
from 71.231.22.13, request '41702@iax-client' does not exist

Apparently the ${NODE} variable is never populated.

The big difference I notice is this one has P and my earlier config had an X:

exten => 41702,1,rpt(41702|X)

What does that mean? I know Pv sets VOX mode and I understood X to
mean DTMF to enable/disable PTT. How does Android IAX signal PTT?

Tom

···

On Thu, Jul 21, 2016 at 4:56 PM, Steve Zingman <szingman@msgstor.com> wrote:

This is the context I use for AndroidIAX

[iax-client] ; for IAX VIOP clients.
exten => ${NODE},1,Ringing
exten => ${NODE},n,Wait(3)
exten => ${NODE},n,Answer
exten => ${NODE},n,Set(NODENUM=${CALLERID(number)})
exten => ${NODE},n,Playback(rpt/node|noanswer)
exten => ${NODE},n,SayDigits(${EXTEN})
exten => ${NODE},n,Set(CALLERID(num)=0)
exten => ${NODE},n,Rpt,${NODE}|P|${CALLERID(name)}
exten => ${NODE},n,Hangup
exten => ${NODE},n(hangit),Answer
exten => ${NODE},n(hangit),Wait(1)
exten => ${NODE},n(hangit),Hangup

9

Opps, Sorry.
Add NODE = 41702 above it.

···

On 7/22/2016 11:41 AM, Tom Hayward wrote:

On Thu, Jul 21, 2016 at 4:56 PM, Steve Zingman <szingman@msgstor.com> wrote:

This is the context I use for AndroidIAX

[iax-client] ; for IAX VIOP clients.
exten => ${NODE},1,Ringing
exten => ${NODE},n,Wait(3)
exten => ${NODE},n,Answer
exten => ${NODE},n,Set(NODENUM=${CALLERID(number)})
exten => ${NODE},n,Playback(rpt/node|noanswer)
exten => ${NODE},n,SayDigits(${EXTEN})
exten => ${NODE},n,Set(CALLERID(num)=0)
exten => ${NODE},n,Rpt,${NODE}|P|${CALLERID(name)}
exten => ${NODE},n,Hangup
exten => ${NODE},n(hangit),Answer
exten => ${NODE},n(hangit),Wait(1)
exten => ${NODE},n(hangit),Hangup

I pasted this in verbatim and now connections fail:

[Jul 22 08:33:01] NOTICE[13402] chan_iax2.c: Rejected connect attempt
from 71.231.22.13, request '41702@iax-client' does not exist

Apparently the ${NODE} variable is never populated.

The big difference I notice is this one has P and my earlier config had an X:

exten => 41702,1,rpt(41702|X)

What does that mean? I know Pv sets VOX mode and I understood X to
mean DTMF to enable/disable PTT. How does Android IAX signal PTT?

Tom

--
"Anything is possible if you don't know what you are talking about."
1st Law of Logic

10

As you can tell, I'm very new to this and unfamiliar with the standard
variables, etc. Okay, added NODE = 41702 to the [globals] stanza and
now it works! I tried a few connects/disconnects and had no odd PTT
behavior.

Then I went back and removed the Playback commands as I prefer. It still works.

What is the difference between the P and X option in the Rpt command?
That seems to be the major difference here. All of the tutorials I found use X.
I have a hard time finding canon documentation for this stuff.

By the way, I was able to break (node graph was missing)
http://stats.allstarlink.org/getstatus.cgi?41702 by putting a space in
the CallerID. I guess that's not allowed.

Thanks for your help. The quick replies made for easy troubleshooting.

Tom KD7LXL

···

On Fri, Jul 22, 2016 at 8:44 AM, Steve Zingman <szingman@msgstor.com> wrote:

Opps, Sorry.
Add NODE = 41702 above it.

11

Tom,
Thanks for the feedback. Glad to know things are working. I have a pretty well commented set of config files atn <https://github.com/N4IRS/AllStar&gt;
We will also look into the CallerID issue. We are preparing to put AndroidIAX up on the Google PlayStore.

Steve

···

On 7/22/2016 12:10 PM, Tom Hayward wrote:

On Fri, Jul 22, 2016 at 8:44 AM, Steve Zingman <szingman@msgstor.com> wrote:

Opps, Sorry.
Add NODE = 41702 above it.

As you can tell, I'm very new to this and unfamiliar with the standard
variables, etc. Okay, added NODE = 41702 to the [globals] stanza and
now it works! I tried a few connects/disconnects and had no odd PTT
behavior.

Then I went back and removed the Playback commands as I prefer. It still works.

What is the difference between the P and X option in the Rpt command?
That seems to be the major difference here. All of the tutorials I found use X.
I have a hard time finding canon documentation for this stuff.

By the way, I was able to break (node graph was missing)
http://stats.allstarlink.org/getstatus.cgi?41702 by putting a space in
the CallerID. I guess that's not allowed.

Thanks for your help. The quick replies made for easy troubleshooting.

Tom KD7LXL

--
"Anything is possible if you don't know what you are talking about."
1st Law of Logic

12

As we all (obviously) know, VOIP protocols, such as IAX2, may be used for

transport of audio/signalling for uses other then phone calls, such as radio, in this case.

Therefore, an endpoint that accepts a VOIP connection processes/utilizes different

methodologies for a radio connection and a “traditional telephony” (like a phone call)

type of connection.

The “X” is used for a radio-style connection, and indicates to app_rpt that it is not to authenticate

the call (that is, authentication was done in the dialplan previous to “sending” it to app_rpt). This is

necessary for scenarios such as use with IAXRPT, where user authentication is done via means external

to app_rpt.

The “P” is used to make app_rpt accept a “traditional” telephony-style (VOIP SIP, IAX2, etc, or other telephony

interface, such as DAHDI) connection, and allow access to a node via a “telephone” call.

These are 2 very different operating environments.

Jim

···

From: app_rpt-users-bounces@ohnosec.org app_rpt-users-bounces@ohnosec.org on behalf of Tom Hayward tom@tomh.us
Sent: Friday, July 22, 2016 9:10 AM
To: Steve Zingman
Cc: app_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] Android IAXRPT stuck PTT

On Fri, Jul 22, 2016 at 8:44 AM, Steve Zingman szingman@msgstor.com wrote:

Opps, Sorry.

Add NODE = 41702 above it.

As you can tell, I’m very new to this and unfamiliar with the standard

variables, etc. Okay, added NODE = 41702 to the [globals] stanza and

now it works! I tried a few connects/disconnects and had no odd PTT

behavior.

Then I went back and removed the Playback commands as I prefer. It still works.

What is the difference between the P and X option in the Rpt command?

That seems to be the major difference here. All of the tutorials I found use X.

I have a hard time finding canon documentation for this stuff.

By the way, I was able to break (node graph was missing)

http://stats.allstarlink.org/getstatus.cgi?41702 by putting a space in

the CallerID. I guess that’s not allowed.

Thanks for your help. The quick replies made for easy troubleshooting.

Tom KD7LXL

App_rpt-users mailing list

App_rpt-users@ohnosec.org

http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users

To unsubscribe from this list please visit
http://ohnosec.org/cgi-bin/mailman/listinfo/app_rpt-users and scroll down to the bottom of the page. Enter your email address and press the “Unsubscribe or edit options button”

You do not need a password to unsubscribe, you can do it via email confirmation. If you have trouble unsubscribing, please send a message to the list detailing the problem.

13

Does this mean I need to be using two different contexts for IAXRPT
and Android IAX? As I said, I previously had "X" and now have "P" and
am using the same context for both Windows and Android app. From the
GUI, they appear to be very similar apps so I assumed they behaved the
same in terms of connection style. But as I reported, the X mode was
sometimes locking PTT on my node when connecting from Android. I never
experienced this from Windows IAXRPT.

Tom KD7LXL

···

On Fri, Jul 22, 2016 at 9:29 AM, Jim Duuuude <telesistant@hotmail.com> wrote:

The "X" is used for a radio-style connection, and indicates to app_rpt that
it is not to authenticate the call (that is, authentication was done in the dialplan previous to
"sending" it to app_rpt). This is necessary for scenarios such as use with
IAXRPT, where user authentication is done via means external to app_rpt.

The "P" is used to make app_rpt accept a "traditional" telephony-style (VOIP
SIP, IAX2, etc, or other telephony interface, such as DAHDI) connection, and
allow access to a node via a "telephone" call.

These are 2 very different operating environments.

14

Personally, I dont know anything about the Android version. I dont

even have a device that runs Android (or IOS either!!).

I think this definitely a question for someone that knows the Android stuff.

Jim

···

From: Tom Hayward tom@tomh.us
Sent: Friday, July 22, 2016 9:40 AM
To: Jim Duuuude
Cc: Steve Zingman; app_rpt-users@ohnosec.org
Subject: Re: [App_rpt-users] Android IAXRPT stuck PTT

On Fri, Jul 22, 2016 at 9:29 AM, Jim Duuuude telesistant@hotmail.com wrote:

The “X” is used for a radio-style connection, and indicates to app_rpt that

it is not to authenticate the call (that is, authentication was done in the dialplan previous to

“sending” it to app_rpt). This is necessary for scenarios such as use with

IAXRPT, where user authentication is done via means external to app_rpt.

The “P” is used to make app_rpt accept a “traditional” telephony-style (VOIP

SIP, IAX2, etc, or other telephony interface, such as DAHDI) connection, and

allow access to a node via a “telephone” call.

These are 2 very different operating environments.

Does this mean I need to be using two different contexts for IAXRPT

and Android IAX? As I said, I previously had “X” and now have “P” and

am using the same context for both Windows and Android app. From the

GUI, they appear to be very similar apps so I assumed they behaved the

same in terms of connection style. But as I reported, the X mode was

sometimes locking PTT on my node when connecting from Android. I never

experienced this from Windows IAXRPT.

Tom KD7LXL