For the benefit of others, This was solved but if you are trying to do the same, you can make some example of this. In rpt.conf you need a line for the phone patch as a command... 6=autopatchup,noct=1,farenddisconnect=1,dialtime=40000 ; Autopatch up In extensions.conf the phone patch is the [radio] context [radio] exten => _5XXX,1,Dial(sip/${EXTEN},17);dial "SIP" ext on this box change to IAX if needed. Make it the first line as shown and you should not have to renumber anything. If correct and you have a sip extension on this box 5xxx you would dial... *65xxx Now this depends on where the extensions are with respect to where there are being dialed. On a remote box you need to point to the host of the extension via TRUNK That requires you route the call from each connected node to the node that hosts the extension. A scheme is required to separate extension numbers between connectable nodes. If you dial on a external iax trunk then something like this would be needed. This dials extensions 6xxx via iax2 trunk named PBX and could be the 2nd line of your [radio] stanza. [radio] exten => _5XXX,1,Dial(sip/${EXTEN},17);dial "SIP" ext on this box change to IAX if needed. exten=_6XXX,1,Dial,IAX2/PBX/${EXTEN} ;dial my ext/voicemail/functions on external trunk labeled PBX Note the rest of what you see in the radio stanza is a default scheme to check the number dialed and prevent toll numbers from being dialed on a external trunk. We don't really need that for internals if it matches a internal string. By placing it at the beginning, it will never see the rest of the stanza if true. We bypassed that by making it the first line and is so noted by having the "1"st instruction for a match. Notice all of the beginning strings are "1" because it is the first instruction only if "true", otherwise it continues until it finds the 1st matching instruction, and only then a second etc. (just so you can look at it and can see the program flow) The examples above are dialed for a radio connection to this node only 5xxx or ones on other trunked node in the case of the 6xxx. Each node must do it's own routing to destination. Hopefully I did not confuse anyone but the asterisk manual is a powerful tool when you want to know how it all works. Only minor adjustments are made for app_rpt here and there. ...mike/kb8jnm
-------- Original Message -------- Subject: [App_rpt-users] Subject: Autopatch type question From: Mike Lussier <mike.lussier@gmail.com> Date: Fri, January 09, 2015 10:43 am To: ALL STAR <app_rpt-users@ohnosec.org>
Mike,
Thanks ,
I put two line into extensions.conf exactly as you showed. these were using _5XXX & the other _6XXX I did an astres.sh and tried the radio 5000 & 6000 no good. Then I ran asterisk -vvvr and setup debug and verbose to level 9 keyed the radio I get a slew of node variable dumps for node 41470 8 variables and a hangup. Nothing in the debug showed the keys pressed on the radio.
MIke AE4ML
--
*"We must reject the idea that every time a law is broken, society is guilty rather than the law breaker.It is time to restore the American precept that each individual is accountable for his actions." ~ Ronald Regan*<hr>_______________________________________________ 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.
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.