SDRTrunk Multiple Calls Nodes

[Deziel0495]

I been providing a single calls node for awhile using SDRTrunk. Applied and setup 2 more nodes, each with their own (but identical) alias list. The sites for the most part carry a lot of the same traffic, but not simulcast. However, it seems all traffic is being sent to BCFY through my original node.

Any suggestions on what I'm overlooking?

Thanks!

 

[jtwalker]

You have three separate streaming setups in SDRT, each using their own API key?

Then reference the streaming setup in alias list?

 

[DSheirer]

Are all three sites part of the same system and you're seeing the same talkgroup activity/calls? If so, then broadcastify only allows one provider to upload the call. Subsequent attempts to upload the same call that broadcastify knows that it's already getting from one provider get blocked.

 

[Deziel0495]

You have three separate streaming setups in SDRT, each using their own API key?

Ahhhhh! Looks like they're all using the same API. Maybe that's where I went wrong!

 

[Deziel0495]

Not an API issue. Through a help request Lindsay said multiple nodes can use the same API.

Perhaps it's just a fluke and these sites haven't had a unique talkgroup yet. SDRTrunk is firing away and showing activity for the 2 sites/nodes in question, but my original node is now showing a high number of duplicate calls. The nodes have been online just under 24 hours but still showing as "Never Active".

I'll monitor it and see what happens. Could be working perfectly fine 🤣

 

[Deziel0495]

Had a talkgroup key up earlier on one of the new nodes (sites), it registered under events in SDRTrunk but then on Broadcastify came out on my original node. The original node in SDRTrunk has no record of the traffic.

No idea why its happening. Top line is original node followed by the 2 new nodes.



Meanwhile on my management page (bottom is original node)

 

[Deziel0495]

Checking the logs from lastnight, an FD from the other side of the county responded to a call and all radio traffic was logged on one of the new nodes in SDRTrunk. However, on Broadcastify Calls, all traffic came through on my original local node.

All 3 nodes are using the same API key (see previous post)
Each node has their own (but identical) alias list
Each site/node is linked to their respective alias list
Each alias list is being sent to the correct calls stream

I'm not sure what else to rule out? It seems like SDRTrunk is working properly. I can see traffic being logged on each site separately but when it's sent to Broadcastify its all going under my original node.

 

[jtwalker]

I’m no expert (and you’ve been working with the experts) but how would Broadcastify know you are targeting second and third node if you are using same api key for all three? I think what you are seeing is a symptom of using one api key for all three feeds.

 

[mtindor]

I’m no expert (and you’ve been working with the experts) but how would Broadcastify know you are targeting second and third node if you are using same api key for all three? I think what you are seeing is a symptom of using one api key for all three feeds.

@Deziel0495 @jtwalker is absolutely correct. You need different API keys for each Calls platform feed. You might "get away with" using one for multiple, but at the very least it is frowned upon. I'm fairly certain Lindsay wants (and likely insists) that every Calls feed use its own API key. That's the only way you are going to see all three as separate nodes on BCFY anyway.

 

[Deziel0495]

You need different API keys for each Calls platform feed. You might "get away with" using one for multiple, but at the very least it is frowned upon. I'm fairly certain Lindsay wants (and likely insists) that every Calls feed use its own API key. That's the only way you are going to see all three as separate nodes on BCFY anyway.

I'm assuming that is the case, was a mistake on my part during the application submission. My help request is still open with Lindsay so I'll await his response. I appreciate everyone's feedback to troubleshoot.

 

[rhughes6]

I have 2 nodes on the same system and the manage pages for both show the same API key. Double check that the System IDs for each feed in SDRTrunk match the Node ID (SID) on your manage page for each node. They should be unique for each node.

 

[mtindor]

I have 2 nodes on the same system and the manage pages for both show the same API key. Double check that the System IDs for each feed in SDRTrunk match the Node ID (SID) on your manage page for each node. They should be unique for each node.

View attachment 161206View attachment 161207

Thanks for posting that. I probably gave erroneous info. I only feed one node from each system I monitor and just assumed it was the API key differentiating things. And of course I also didn't bother to look at my configuration in detail before chiming in.

Mike

 

[Deziel0495]

I have 2 nodes on the same system and the manage pages for both show the same API key. Double check that the System IDs for each feed in SDRTrunk match the Node ID (SID) on your manage page for each node. They should be unique for each node.

View attachment 161206View attachment 161207

This was exactly my problem. When I created a new calls stream, it carried over the system ID from my original node and I didn't notice. THANK YOU!

 

[GTR8000]

Just to be super clear, the API key is absolutely not the issue. Trust me, I'm feeding multiple nodes from different systems and/or sites using multiple geographically separate computers, and they are all using the identical API key.

The issue is the Node ID aka System ID in SDRTrunk. That must be unique for each instance of a Calls node, otherwise everything is going to get uploaded to the same node.