The allstar-public dialplan contenxt in extensions.conf currently places "0" in CALLERID(num). While the dialplan sets CALLERID(name) to the WT callsign, that value is not published in "core show channels concise". The CALLERID(num) value is published in "core show channel concise", allowing that value to be used to match Allstar connections to channels.
Although CALLERID(num) is intended for numeric digits, alphanumeric characters may be used as long as spaces are avoided. The CALLSIGN value is being obtained from the Allstar authentication results. It seems putting that inCALLERID(num) would be acceptable use for Allstar. It would be helpful to script writers to have the WT callsign in CALLERID(num) so it can be found in Asterisk channel lists.
Could this line in the allstar-public dialplan context be changed?
from
same => n,Set(CALLERID(num)=0)
to
same => n,Set(CALLERID(num)=${CALLSIGN})
<EDIT)>
Also, the allstar-public dialplan sets the Asterisk channel dst / extension, to an 's'. The allstar-public dialplan must extract the local node number to connect from the CALLERID(num) value passed from the WT client. This leaves the Asterisk channel containing 's', which is also not consistent with channels for radio-secure, which have the local node number that is connected.
As far as I can determine, one cannot directly "Set" the Asterisk channel dst or src, values from a dialplan. But, another context can be used to set the Asterisk dst / extension value. I created another dialplan context named allstar-public-connect and used a Goto to transfer the WT connection process to that context to complete the Rpt() connection. Now, the Asterisk channel dst / extension values have the correct local node number.
Replace...
;same => n,Rpt(${NODENUM},X)
with...
same => n,Goto(allstar-public-connect,${NODENUM},1)
Add.to extensions.conf or custom/extensions.conf...
[allstar-public-connect]
; allstar-public context sets asterisk channel dst value to 's'. By jumping (goto) to this context, the channel dst value is reset.
; This allows asterisk channel listing to include the local node number instead of 's' in the dst field for scripts
exten => _XXXX!,1,NoOp(${EXTEN})
same => n,Rpt(${NODENUM},X)
same => n,Hangup()
In addition to the original CALLERID change, can something like this change be made for the local node number to be placed on the asterisk channel record in the dst / extension value? These changes would provide both the local node number and the WT callsign in the channel record for scripts to match and retrieve the Asterisk channel name.
David McAnally, WD5M
The allstar-public dialplan contenxt in extensions.conf currently places "0" in CALLERID(num). While the dialplan sets CALLERID(name) to the WT callsign, that value is not published in "core show channels concise". The CALLERID(num) value is published in "core show channel concise", allowing that value to be used to match Allstar connections to channels.
Although CALLERID(num) is intended for numeric digits, alphanumeric characters may be used as long as spaces are avoided. The CALLSIGN value is being obtained from the Allstar authentication results. It seems putting that inCALLERID(num) would be acceptable use for Allstar. It would be helpful to script writers to have the WT callsign in CALLERID(num) so it can be found in Asterisk channel lists.
Could this line in the allstar-public dialplan context be changed?
from
to
<EDIT)>
Also, the allstar-public dialplan sets the Asterisk channel dst / extension, to an 's'. The allstar-public dialplan must extract the local node number to connect from the CALLERID(num) value passed from the WT client. This leaves the Asterisk channel containing 's', which is also not consistent with channels for radio-secure, which have the local node number that is connected.
As far as I can determine, one cannot directly "Set" the Asterisk channel dst or src, values from a dialplan. But, another context can be used to set the Asterisk dst / extension value. I created another dialplan context named allstar-public-connect and used a Goto to transfer the WT connection process to that context to complete the Rpt() connection. Now, the Asterisk channel dst / extension values have the correct local node number.
Replace...
with...
Add.to extensions.conf or custom/extensions.conf...
In addition to the original CALLERID change, can something like this change be made for the local node number to be placed on the asterisk channel record in the dst / extension value? These changes would provide both the local node number and the WT callsign in the channel record for scripts to match and retrieve the Asterisk channel name.
David McAnally, WD5M