[App_rpt-users] Clarifications Please: Parameters for iaxrpt contexts

[David Wilcox]

Carl 

 

Just for info

 

I figured out why that repeater at CATO was left behind, I was going to use parts for Baraboo

Well the repeater goes with  the antenna in the generator room  everything from the power plug (that was cut off)  to the N connector is smoked     

 

That means that the tuning cans are most likely junk  I will Ask Steve how to test them

 

 

 

From: App_rpt-users [mailto:app_rpt-users-bounces at lists.allstarlink.org] On Behalf Of Mike
Sent: Sunday, April 7, 2019 1:28 PM
To: app_rpt-users at lists.allstarlink.org
Subject: Re: [App_rpt-users] Clarifications Please: Parameters for iaxrpt contexts

 

Jim,

iaxrpt and 'dvswitch mobile' are two different animals.

One is connecting as a 'FRIEND' and the other as a 'USER' as seen/configured in iax.conf.

This is a asterisk thing. Documented with asterisk.

A 'FRIEND' is a bit less secure as you are assuming they are a known good security and not going to get announcements per our set-up. That could be changed.

You need to make your context 'match' between iax.conf and extensions.conf, NOT exactly by my following examples. Start with the iax configuration and follow that to your extensions configuration with the proper context.

IN IAX.conf

[iax-user]
type = user
context =iax-user
auth = md5
secret = px
host = dynamic
disallow = all
allow = ulaw
allow = adpcm
allow = gsm
notransfer = yes

[kb8jnm]
type = user
context =iax-user
auth = md5
secret = px
host = dynamic
disallow = all
allow = ulaw
allow = adpcm
allow = gsm
notransfer = yes

 

[iax-friend]                        
type = friend                         ; Notice is friend <--------------
context = iax-friend             ; Context in extensions.conf
auth = md5
secret = px
host = dynamic
disallow = all
allow = ulaw
allow = adpcm
allow = gsm
notransfer = yes

---ext

[iax-user]                ; for IAX VIOP clients/users - like a personal extension.                
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


[iax-friend]      ; iaxrpt-gui
exten => 1000,1,rpt(1000|X)
exten => 1999,1,rpt(1999|X)
exten => 29261,1,rpt(29261|X)
exten => 29283,1,rpt(29283|X)
exten => 29284,1,rpt(29284|X)
exten => 29285,1,rpt(29285|X)
exten => 48335,1,rpt(48335|X)

Your designated '|P' is phone mode and doubt you need that unless dialing in by phone to command and you have separate command list to enable for phone commands unless you lumped them all together and would require the phone command to key the transmitter. Should be well documented with app_rpt.

dvswitch mobile connects as a iax-client/user

Have you checked the wiki for in depth docs and groups.io. Hope my poor examples get you somewhere.

...mike/kb8jnm

 

On 4/7/2019 12:24 PM, Jim Aspinwall No1PC wrote:

I've had the 'phantom' node PTT issue when connecting from DVSwitch/iaxrpt on Android.  It took some digging to realize there are two different suggested solutions to apply to the context(s) in extensions.conf.

One says to apply:  exten=<node#>,1,rpt, <node#>|X   - which does not effect the desired solution  (for DVSwitch/iaxrpt on Android)

 

The other says to apply: exten=<node#>,1,rpt, <node#>|P    - which DOES effect the desired solution

I'm thinking you cannot have both an |X and a |P related statement in the same context... so I'd have to establish different contexts for different types of VoIP app users?  and of course accommodate them in iax.conf...

Is or can this be documented comprehensively?

And please - if a change is to be edited in some file - indicate which file... put the some 'x' statement in the wrong file and the node breaks or statement is useless... generates more back and forth clarifications. 

-----------

Further - interesting/compelling, would be great to have, the mention of perhaps having the connected node(s) announce the "callerID" of the connecting user - *great* - but not (yet?) implemented?   If it IS implemented - more detail please!  

exten=<node#>,1,rpt, <node#>|P|${CALLERID(name)}


Thanks!!

 





_______________________________________________
App_rpt-users mailing list
App_rpt-users at lists.allstarlink.org
http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users
 
To unsubscribe from this list please visit http://lists.allstarlink.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. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.keekles.org/pipermail/app_rpt-users/attachments/20190407/149597c4/attachment.html>