Issues with patched TGs?

[krokus]

A couple hours ago, there was a vehicle pursuit along the county border, with multiple agencies involved. When the TG for initial agency was patched to this county's TG, the feed for this county stopped carrying the traffic. I could hear it on the G4, and it was on the archived traffic from the neighboring county's agency.

Is that a typical issue with systems like MPSCS, or is there a configuration conflict?

 

[RaleighGuy]

A couple hours ago, there was a vehicle pursuit along the county border, with multiple agencies involved. When the TG for initial agency was patched to this county's TG, the feed for this county stopped carrying the traffic. I could hear it on the G4, and it was on the archived traffic from the neighboring county's agency.

Is that a typical issue with systems like MPSCS, or is there a configuration conflict?

Depends which software the feeder uses, it isn't a Broadcastify/Calls Platform issue it is the feeder issue.

 

[tweiss3]

This is a known issue. SDRTrunk was attempting to address the issue in one of the current releases. If possible, I would prefer it uploads to all patched talkgroups, but that isn't always the case.

 

[IcomIcR20]

Is this on the Calls platform, or just a regular audio feed? If it is on Calls and the person providing the feed is running Trunk Recorder, they may have to contact Broadcastify directly in order for the patch to be handled correctly. I run a calls node for a system that has a patch between three TGs that is active 24/7. In order to get the traffic to appear on the TG that the transmissions typically originate from, I had to contact Broadcastify Support, and Lindsay did some magic on his end to make things work as desired (see: Handling Patched TGs with Trunk Recorder and Calls).

Regular feeds can also be created using Trunk Recorder, so there may be something the feed provider needs to change on their end. I believe SDRTrunk now has a way to work around this issue, but I have not tested it.

 

[krokus]

Is this on the Calls platform, or just a regular audio feed? If it is on Calls and the person providing the feed is running Trunk Recorder, they may have to contact Broadcastify directly in order for the patch to be handled correctly. I run a calls node for a system that has a patch between three TGs that is active 24/7. In order to get the traffic to appear on the TG that the transmissions typically originate from, I had to contact Broadcastify Support, and Lindsay did some magic on his end to make things work as desired (see: Handling Patched TGs with Trunk Recorder and Calls).

Regular feeds can also be created using Trunk Recorder, so there may be something the feed provider needs to change on their end. I believe SDRTrunk now has a way to work around this issue, but I have not tested it.

This was via the calls platform. I have no idea about the feed provider's configuration, or if it was assembled from more than one feed.