I'm looking to make a quick script that would allow any of my private nodes to have their node number "translated" when they make link requests to public nodes. The use case is I want local RF users who may be assigned to private nodes to prevent external users from accessing that link, to be able to connect outbound to public nodes to simplify the remote node side config. Basically I want something like this RFC 5876: Updates to Asserted Identity in the Session Initiation Protocol (SIP) | RFC Editor for app_rpt.
Anyone else already solve this? I think the current way forward is sed'ing some core app_rpt files and recompiling the module, this seems like a hammer to fix a leaky pipe solution and I don't want to have to maintain this to keep up with upstream allstarlink updates.
A node number is not a fungible thing that you can rename or "NAT". However, nothing beyond the "next hop" matters anyway. If you have a private node connected to a real node that then connects to another real node, the private node number is irrelevant.
Apologies, I was unclear . I want my local users to be able monitor and reply to multiple remote nodes over VoIP without bridging them all together and making the remote nodes RF paths noisy, I also want multiple people to be able to access my own RF linked nodes at a few different sites without bridging audio. I understand the current way is dynamically changing linked nodes and using DTMF, that doesn’t really work with how I want to do this.
Fundamentally, a node number is no different than an ip address or a unique SIP extension? Whether it’s publicly routable or not is irrelevant, NAT and Asserted Identity were designed exactly to handle this, I’m just looking to see if it’s been done with app_rpt? If not, what's the ASL3 compliant/approved way to run multiple isolated outbound links to public nodes from one user?
I guess I'm not clear on what you're really trying to accomplish here. What do you mean by "monitor and reply to multiple remote nodes over VoIP without bridging them" and "multiple isolated outbound links". app_rpt doesn't make arbitrary calls like a PBX, everything is a link.
I want my private nodes to be able to call out to remote public nodes, without going through my own public nodes can creating massive bridges of audio when they are in use or connected to physical radios.
That is not possible with ASL/app_rpt. Any private node like you describe has to go through a public node you control that identifies and brokers the private nodes. Your users need public nodes or your need to have a sufficiently-sized hub to do it.
. I want my local users to be able monitor and reply to multiple remote nodes over VoIP without bridging them all together and making the remote nodes RF paths noisy, I also want multiple people to be able to access my own RF linked nodes at a few different sites without bridging audio. I understand the current way is dynamically changing linked nodes and using DTMF, that doesn’t really work with how I want to do this.