Bill, To expand on what @w6el mentioned,
Provided you have a valid phone patch string, (rpt.conf)
61=autopatchup,context=radio,noct=1,farenddisconnect=1,dialtime=20000,quiet=1
You need to have a route for that in extensions.conf
Think of that file as a router. Making the connections to a endpoint.
That endpoint must be a valid extension with authentication in sip,iax,rpt config files. Meaning it must be present and logged in to the system.
And many folks can get that far with some head scratching.
But often, they do not use the correct context in extensions.conf as described in that autopatch string. When you make a call with it, it goes to that context in extensions.conf and looks for a matching string dialed.
It may be necessary to change that context for specific purposes.
You might have the entry in there somewhere, but not in the proper context.
So, somewhere in [radio} in extensions.conf, you would then describe the route to that sip phone, for example...
[radio] ; example context
exten => _50X,1,SetMusicOnHold(default)
exten => _50X,n,Dial(sip/${EXTEN},20) ;dial ext/functions on this box
exten => _50X,n,VoiceMail(5000) ; common vm
exten => _50X,n,Hangup
This would dial any exact sip phone whos extension is 500 - 509
When you have more extensions, you will need to expand your learning on dialplan.
Yes, a few other things injected in there for you to think about.
Hope you get the gist of them without confusion.
exten => _50X,1,Dial(sip/${EXTEN},20) ;dial ext/functions on this box
exten => _50X,n,Hangup
The old default was [radio] and I'm not sure if that is the same with asl3 as I use my old config files and even those are not defaulted with recent versions.
So, just some more things to pay attention to.
Hope that helps some.