Broadcastify Calls Support

[epersson]

@btt Any issue sending both Streams and Calls from the same instance? I'm heading down tomorrow to fix it and have requested both accounts. I figure Stream and Calls from the full Fire/Rescue simulcast then stream only from the second running a subset of just Pompano Beach.
Thanks.

 

[btt]

@btt Any issue sending both Streams and Calls from the same instance? I'm heading down tomorrow to fix it and have requested both accounts. I figure Stream and Calls from the full Fire/Rescue simulcast then stream only from the second running a subset of just Pompano Beach.
Thanks.

I don't think it will be an issue. The <Enable Broadcastify Output> option writes separate .wav files to a p25rx/broadcastify_calls directory. The streams should work for you as they were before.

 

[btt]

As of 07/11/22, the BTT BCalls application is now a choice when configuring Broadcastify Calls. If you choose this option, then it will show up in the system as "Trunking Recorder". Choosing "SDR Trunk" will also work. It will not show up in the Calls systems as BTT BCalls. There are currently P25RX systems configured as "Trunking Recorder" and "SDR Trunk" online. If you choose the first option "Trunk Recorder", it will not work. (Note difference between Trunking Recorder and Trunk Recorder).

 

[epersson]

@btt Hi, probably my screwup.. I have it set and supports mp3, OK.. I get the message wrong p25_sys_id for Tg### removing without send
Looking in the log the p25 sys ID is the source site ID which is 997 and is correct.

 

[FreqNout]

I get the message wrong p25_sys_id for Tg### removing without send
Looking in the log the p25 sys ID is the source site ID which is 997

997 may be a hex value. Try decimal 2455 for sys id.

 

[epersson]

997 may be a hex value. Try decimal 2455 for sys id.

Early morning, no coffee yet, and I've been away from hex for so long I didn't notice.. I will try, thanks!!! in advance if it works..

 

[epersson]

Early morning, no coffee yet, and I've been away from hex for so long I didn't notice.. I will try, thanks!!! in advance if it works..

Mea Culpa and I'm a dunce for the day.

 

[epersson]

Ok, Broward County Florida Fire/Rescue simulcast is up and running both on Stream and Calls platforms.

The issues with lockups were on my end and it appears when I shut off scrolling the system was running for 4 months without locking up. My router locked up but when I got here the P25 and BTConfig were humming away nicely.

 

[epersson]

Not sure where this is being done, but I am scanning 9 dispatches and 14 tacs. BTConfig and my SD100 showed Disp 9 then 1 ,4, 6 etc. the send to the Calls and the calls display all showed the TD and alias as Disp 9. then it 'reset' and started recording correctly. almost like the TX came so close together. I'll try to capture it doing it again.

 

[epersson]

@btt I think this is the same bug from a year ago when another call comes in before the delay period has ended it gets the call but doesn't realize its a different call. If you can look at the Broward county calls, this Dispatch 8 for 60 seconds, once you hear anything 263 and 24 or 22 those are actually on Dispatch 5 (Pompano) not Dispatch 8

 

[btt]

@btt I think this is the same bug from a year ago when another call comes in before the delay period has ended it gets the call but doesn't realize its a different call. If you can look at the Broward county calls, this Dispatch 8 for 60 seconds, once you hear anything 263 and 24 or 22 those are actually on Dispatch 5 (Pompano) not Dispatch 8

Must be a P2 issue with call termination. You are the first P25RX / P2 system using Calls. Let me look into it and see if I can get it fixed.

 

[epersson]

Must be a P2 issue with call termination. You are the first P25RX / P2 system using Calls. Let me look into it and see if I can get it fixed.

This sounds like something I reported a year ago where a call RIGHT on the end of another before the delay timer times out, you can hear the second call but BTConfig shows it as the same call TGID. Just guessing here. I originally had the timeout to 2 seconds but changed it to 100ms to stop it from happening. Just looked back in the p25Rx firmware thread search for 100ms and a couple relevenat entries come up

 

[btt]

This sounds like something I reported a year ago where a call RIGHT on the end of another before the delay timer times out, you can hear the second call but BTConfig shows it as the same call TGID. Just guessing here. I originally had the timeout to 2 seconds but changed it to 100ms to stop it from happening

The TG timeout is something different. Ideally the MAC_PTT_END control message would terminate the call. I don't think all P2 systems use this. I'm looking into it.

 

[epersson]

The TG timeout is something different. Ideally the MAC_PTT_END control message would terminate the call. I don't think all P2 systems use this. I'm looking into it.

Very good, just trying to give you all the info as I see it happening, relevant or not.. . ;-)

 

[btt]

@epersson, please give 2022-07-14_1137 a try. Thanks!

 

[epersson]

@epersson, please give 2022-07-14_1137 a try. Thanks!

On it
@btt Not a major issue, bot an unrelated thing I saw updating to the BTCalls version. I have two P25rx and it saw the first one then got real confused as to which one it was updating and resetting, so I unplugged one, let it update, then swapped. That solved it.

 

[epersson]

@btt done, it didn't ask to update the firmware on either? says running 1137
P.S. regardless, it does work great!!! Running 2 @ P25rx on streams, one of them also sending Calls.

 

[epersson]

The fact that it didn't ask... In the middle of this Rescue 89 is heard, that is a different dispatch.

 

[btt]

The fact that it didn't ask... In the middle of this Rescue 89 is heard, that is a different dispatch.

It isn't a firmware update, but a change to the Java firmware only. I will look and see what else we can try.

 

[btt]

@epersson,
Please try 07-14_1215. If this works, I may end up making a firmware change for both models.