OP25 Question regarding whitelist/blacklist and multiple voice channels

Status
Not open for further replies.

jschmall

Member
Premium Subscriber
Joined
Jul 15, 2017
Messages
84
Location
Anderson, CA
Thanks.
Looking at the .json I would recommend moving the UDP ports further apart (i.e. 23456 and 23466) because internally op25 uses ports in pairs regardless of whether you are listening to single or dual channel. Separating them by 10 is easy and guarantees they won't conflict.



I think you might run into a problem there. Internally the talkgroups dictionary object is shared among all receivers; one of the checks performed prior to assigning a receiver to a call in progress is to make ensure no other receiver is already assigned to that call. This works fine as long as you don't duplicate tgids across multiple whitelist files but it's not going to work as intended where you genuinely do want the same call decoded simultaneously. I will have to figure out how to address that without breaking something else.
Ok good to know about the UDP ports, I’ll make those changes tonight.

Regarding the whitelists, that does make sense to me and I can see how that would be a conflict internally. Since that doesn’t seem to be a viable option right now, would I be able to do this with my .liq file instead? I would imagine I could create a mixer of sorts that includes both INPUT A and INPUT B that is streamed to my icecast server similarly to how the streams are mixed for my local audio output?
 

wgbecks

Active Member
Joined
Jan 17, 2005
Messages
1,113
Location
NE Wisconsin
In addition to spacing the UDP ports further apart as @ boatbod suggests, you can also drop the duplicate TGID 58762 from the rpd_whitelist_home.tsv to remove any internal conflicts. That said, as configured, your speaker output (multi.liq) is configured
for stereo that will play the audio from both voice channels.

Now in your streams directed to your local Icecast server, you can either retain separate mount points from both voice channels or you can
elect to create a single stereo stream similar to the local speaker output. If interested in the later option, send me a PM with your email contact and I'll send you a modified multi.liq arranged to create the stereo stream.

Bill
 

jschmall

Member
Premium Subscriber
Joined
Jul 15, 2017
Messages
84
Location
Anderson, CA
In addition to spacing the UDP ports further apart as @ boatbod suggests, you can also drop the duplicate TGID 58762 from the rpd_whitelist_home.tsv to remove any internal conflicts. That said, as configured, your speaker output (multi.liq) is configured
for stereo that will play the audio from both voice channels.

Now in your streams directed to your local Icecast server, you can either retain separate mount points from both voice channels or you can
elect to create a single stereo stream similar to the local speaker output. If interested in the later option, send me a PM with your email contact and I'll send you a modified multi.liq arranged to create the stereo stream.

Bill
Bill, the latter is exactly what I’m interested in. I will retain the local speaker mixed output and would like to implement the same to a single icecast mount point.

I will PM you my email, thanks.
 

boatbod

Member
Joined
Mar 3, 2007
Messages
3,532
Location
Talbot Co, MD
You can mix two (or more) sources in the liquidsoap script. The only problem would be the two streams talking over each other in the event of both being active simultaneously. Conceivably you could get more advanced and implement conditional mixing but I've never personally done that.
 

jschmall

Member
Premium Subscriber
Joined
Jul 15, 2017
Messages
84
Location
Anderson, CA
You can mix two (or more) sources in the liquidsoap script. The only problem would be the two streams talking over each other in the event of both being active simultaneously. Conceivably you could get more advanced and implement conditional mixing but I've never personally done that.
Bill was able to help me by creating a liquidsoap file that mixes both voice channels appropriately.

Thanks again for your help and insight.
 
Status
Not open for further replies.
Top