Correct me if I'm wrong. The radio system ID is different than the Braodcastify Calls System ID. If they were the same, the scanner protocol doesn't outputs the System ID and Site ID therefore ProScan has no way of knowing the IDs.
The Slot ID is for running multiple instances using the same System ID and API key.
Correct, the System ID Broadcastify Calls uses is not the same as the Trunking System ID (I wish Broadcastify would have called it something else).
The issue is when you apply for a Broadcastify Calls feed you have to tell them the Trunking System and Site you will upload (You choose it from a drop down list). If you are monitoring multiple Sites you need a different Broadcastify Calls application for each site.
This means Trunking Recorder needs to know what Site a call came from so it only uploads the correct calls to Broadcastify since you could be monitoring multiple sites on the same Trunked System.
Since the older Uniden scanners don't provide the true Trunked System ID or Site ID the calls out of ProScan don't include it (makes sense).
Trunking Recorder separates calls internally by SystemID so it must have a value, in this scenario since the true Trunked System ID isn't available Trunking Recorder makes a compromise by using the "System Name" string value in ProScan ("%S") and leaving the Site ID blank.
Since there is no Site ID Trunking Recorder can't upload the call to Broadcastify since it doesn't know enough about the call.
To solve this Trunking Recorder will start setting the "Site ID" value to the "System Name" from ProScan if it's a Trunked call. If it's a conventional call it will use the frequency. This will then allow Trunking Recorder to tie a call to a Broadcastify Calls "API key" and "SystemID".
It's not a great solution since you could possibly have the scanner picking up calls from multiple Trunked Sites under the same "System Name", but it's the only solution since the scanner doesn't provide the Trunked Site ID. (I believe the newer SDS scanner do send over a "Site Name" "%SI" so Trunking Recorder can use this for the "Site ID" and hopefully keep calls separated).
The "Slot ID" is another Broadcastify Calls unique thing.
When sending a Conventional non Trunked call you have to send a "Slot ID" value where you would normally send the "Talkgroup ID". From my limited understanding when you apply for a Conventional Calls feed you list out the Conventional frequencies you plan to upload and they give you a "Slot ID" value for each frequency.
That means Trunking Recorder will need to know this Frequency to "Slot ID" mapping and send the correct value when it uploads the conventional call.
I haven't gotten around to adding this logic yet to Trunking Recorder so I don't know the exact details for Conventional Calls.
These are the complications when you mix 4 different systems (Uniden scanner, ProScan, Trunking Recorder, Broadcastify Calls).
