There are a couple of different ways I can think of to
temporarily disable incoming connections. There’s a dtmf function cop,12
(and an lnkdis control state) that apparently disables user linking functions.
Now I’ve never used those before, so I’m not sure if it disables
all linking (incoming and outgoing) or just disables the local outgoing link
commands. I’m sure the devs could shed a little more light on that subject,
but hey, why not give it a shot?
Another real quick and easy way would be to comment out the entire
[radio] section in /etc/asterisk/iax.conf. This would literally make asterisk
stop listening for incoming connections. You could make a quick little shell
script that renames files to switch between two iax.conf files, your original
one and one with that section commented out, and even run it on an automatic
schedule if you wanted.
How are you playing these audio files? In other words, what do you do to
get the audio files to play?
I'm wondering if the connect message is the real culprit here.
LNKDIS only disables the linking functions it does not prevent incoming
connections from being accepted. Currently, the best way to do this is
to edit extensions.conf and comment our Rpt application like this:
[radio-secure]
;exten = 2010,1,rpt,2010
It seems strange to me that the audio file is being killed off and
I'd like to try out how you are playing files here to understand the
mechanism.
Thanks for the reply, here’s how I play the news over the repeater.
I record the files the night before and save them to the node as an .au file, then just use a root cron to call a bash script which contains the following:
/usr/sbin/asterisk -rx “rpt fun 2250 *6” ; disconnect all connections
sleep 6
/usr/sbin/asterisk -rx “rpt fun 2250 *947” ; reset the link activity timer flag
sleep 3
/usr/sbin/asterisk -rx “rpt playback 2250 gb2rs” ; plays the file
There is an almost identical script for the ARNewsline which plays out in the evening.
If there is an incoming connection during the playback, Alisson announces the incoming connection, and thats the end of the playback. I think that you could be right about the connect message causing the problem.
Perhaps I should be playing the files a different way which would alleviate the problem?
It would be nice though, to be able to script in something to prevent incoming connections during this time. I’m not sure how to script something that would comment out the line in extensions.conf - I’ll have to look into how to do that but it certainly looks like that will achieve whats needed.
Hi Stephen,
Thanks for the reply, here's how I play the news over the repeater.
I record the files the night before and save them to the node as an .au
file, then just use a root cron to call a bash script which contains the
following:
/usr/sbin/asterisk -rx "rpt fun 2250 *6" ; disconnect all connections
sleep 6
/usr/sbin/asterisk -rx "rpt fun 2250 *947" ; reset the link activity timer
flag
sleep 3
/usr/sbin/asterisk -rx "rpt playback 2250 gb2rs" ; plays the file
There is an almost identical script for the ARNewsline which plays out in
the evening.
If there is an incoming connection during the playback, Alisson announces
the incoming connection, and thats the end of the playback. I think that you
could be right about the connect message causing the problem.
Perhaps I should be playing the files a different way which would alleviate
the problem?
It would be nice though, to be able to script in something to prevent
incoming connections during this time. I'm not sure how to script something
that would comment out the line in extensions.conf - I'll have to look into
how to do that but it certainly looks like that will achieve whats needed.
Thanks everyone for the help so far.
Best wishes,
Matt
G4RKY
( currently listening to the latest Newsline )
Matt Beasant wrote:
Hi,
When I play the GB2RS news and ARnewsline audio files over my node, the
playback is killed off by an incoming connection.
How can I prevent an incoming connection during this time?
I thought I could disable the node but of course this kills the Tx
completely!
Didnt want to do anything as drastic as take down ETH0 if I could help it
How are you playing these audio files? In other words, what do you do to
get the audio files to play?
I'm wondering if the connect message is the real culprit here.
LNKDIS only disables the linking functions it does not prevent incoming
connections from being accepted. Currently, the best way to do this is
to edit extensions.conf and comment our Rpt application like this:
[radio-secure]
;exten = 2010,1,rpt,2010
It seems strange to me that the audio file is being killed off and
I'd like to try out how you are playing files here to understand the
mechanism.
With app_rpt.c version 0.186 the message does not get interrupted if I
do a connect in the middle of it while it is playing. I hear the connect
message after the audio file finishes playing.
So either app_rpt.c version 0.186 has resolved the issue, or there is a
missing piece of stimulus required to duplicate this issue.
What version of app_rpt.c are you using? (*82 should tell you if you
didn't change the function).