<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Helvetica;
panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";
color:black;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:"Consolas","serif";
color:black;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Carl <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Just for info<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I figured out why that repeater at CATO was left behind, I was going to use parts for Baraboo<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>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 <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>That means that the tuning cans are most likely junk I will Ask Steve how to test them<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:windowtext'> App_rpt-users [mailto:app_rpt-users-bounces@lists.allstarlink.org] <b>On Behalf Of </b>Mike<br><b>Sent:</b> Sunday, April 7, 2019 1:28 PM<br><b>To:</b> app_rpt-users@lists.allstarlink.org<br><b>Subject:</b> Re: [App_rpt-users] Clarifications Please: Parameters for iaxrpt contexts<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p>Jim,<o:p></o:p></p><p>iaxrpt and 'dvswitch mobile' are two different animals.<o:p></o:p></p><p>One is connecting as a 'FRIEND' and the other as a 'USER' as seen/configured in iax.conf.<o:p></o:p></p><p>This is a asterisk thing. Documented with asterisk.<o:p></o:p></p><p>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.<o:p></o:p></p><p>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.<o:p></o:p></p><p>IN IAX.conf<o:p></o:p></p><p>[iax-user]<br>type = user<br>context =iax-user<br>auth = md5<br>secret = px<br>host = dynamic<br>disallow = all<br>allow = ulaw<br>allow = adpcm<br>allow = gsm<br>notransfer = yes<o:p></o:p></p><p>[kb8jnm]<br>type = user<br>context =iax-user<br>auth = md5<br>secret = px<br>host = dynamic<br>disallow = all<br>allow = ulaw<br>allow = adpcm<br>allow = gsm<br>notransfer = yes<o:p></o:p></p><p><o:p> </o:p></p><p>[iax-friend] <br>type = friend ; Notice is friend <--------------<br>context = iax-friend ; Context in extensions.conf<br>auth = md5<br>secret = px<br>host = dynamic<br>disallow = all<br>allow = ulaw<br>allow = adpcm<br>allow = gsm<br>notransfer = yes<o:p></o:p></p><p>---ext<o:p></o:p></p><p>[iax-user] ; for IAX VIOP clients/users - like a personal extension. <br>exten => ${NODE},1,Ringing<br>exten => ${NODE},n,Wait(3)<br>exten => ${NODE},n,Answer<br>exten => ${NODE},n,Set(NODENUM=${CALLERID(number)})<br>exten => ${NODE},n,Playback(rpt/node|noanswer)<br>exten => ${NODE},n,SayDigits(${EXTEN})<br>exten => ${NODE},n,Set(CALLERID(num)=0)<br>exten => ${NODE},n,Rpt,${NODE}|P|${CALLERID(name)}<br>exten => ${NODE},n,Hangup<br>exten => ${NODE},n(hangit),Answer<br>exten => ${NODE},n(hangit),Wait(1)<br>exten => ${NODE},n(hangit),Hangup<br><br><br>[iax-friend] ; iaxrpt-gui<br>exten => 1000,1,rpt(1000|X)<br>exten => 1999,1,rpt(1999|X)<br>exten => 29261,1,rpt(29261|X)<br>exten => 29283,1,rpt(29283|X)<br>exten => 29284,1,rpt(29284|X)<br>exten => 29285,1,rpt(29285|X)<br>exten => 48335,1,rpt(48335|X)<o:p></o:p></p><p class=MsoNormal>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.<o:p></o:p></p><p>dvswitch mobile connects as a iax-client/user<o:p></o:p></p><p>Have you checked the wiki for in depth docs and groups.io. Hope my poor examples get you somewhere.<o:p></o:p></p><p>...mike/kb8jnm<o:p></o:p></p><p><o:p> </o:p></p><div><p class=MsoNormal>On 4/7/2019 12:24 PM, Jim Aspinwall No1PC wrote:<o:p></o:p></p></div><blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'><div><div><p class=MsoNormal><span style='font-family:"Helvetica","sans-serif"'>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.<br><br>One says to apply: exten=<node#>,1,rpt, <node#>|X - which does not effect the desired solution (for DVSwitch/iaxrpt on Android)<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Helvetica","sans-serif"'><o:p> </o:p></span></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-family:"Helvetica","sans-serif"'>The other says to apply: exten=<node#>,1,rpt, <node#>|P - which DOES effect the desired solution<br><br>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...<br><br>Is or can this be documented comprehensively?<br><br>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. <br><br>-----------<br><br>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! <o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Helvetica","sans-serif"'>exten=<node#>,1,rpt, <node#>|P|${CALLERID(name)}<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Helvetica","sans-serif"'><br>Thanks!!<o:p></o:p></span></p></div><div><p class=MsoNormal><span style='font-family:"Helvetica","sans-serif"'><o:p> </o:p></span></p></div></div><p class=MsoNormal><br><br><o:p></o:p></p><pre>_______________________________________________<o:p></o:p></pre><pre>App_rpt-users mailing list<o:p></o:p></pre><pre><a href="mailto:App_rpt-users@lists.allstarlink.org">App_rpt-users@lists.allstarlink.org</a><o:p></o:p></pre><pre><a href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a><o:p></o:p></pre><pre><o:p> </o:p></pre><pre>To unsubscribe from this list please visit <a href="http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users">http://lists.allstarlink.org/cgi-bin/mailman/listinfo/app_rpt-users</a> and scroll down to the bottom of the page. Enter your email address and press the "Unsubscribe or edit options button"<o:p></o:p></pre><pre>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. <o:p></o:p></pre></blockquote></div></body></html>