dragoncooler
Member
Greetings all,
I was wondering on the D-Star side of things how is callsign routing handled if you have a repeater/dedicated hotspot with your callsign?
Meaning, If I have a repeater my gateway is callsign__G. If I travel with my hotspot it will then register a new callsign_G, deeming it the new "primary" for my callsign.
Has anyone run into this situation yet? Id like to travel with my dvmega or hotspot and be able to route back and listen home to my repeater.
I notice in the IRCDDB logs when i turn the dvmega on, my callsign_G gets registered with a new IP address (essentially my phones IP address). I have tried using a different module for the hotspot, but the gateway __G cant change.
I was wondering on the D-Star side of things how is callsign routing handled if you have a repeater/dedicated hotspot with your callsign?
Meaning, If I have a repeater my gateway is callsign__G. If I travel with my hotspot it will then register a new callsign_G, deeming it the new "primary" for my callsign.
Has anyone run into this situation yet? Id like to travel with my dvmega or hotspot and be able to route back and listen home to my repeater.
I notice in the IRCDDB logs when i turn the dvmega on, my callsign_G gets registered with a new IP address (essentially my phones IP address). I have tried using a different module for the hotspot, but the gateway __G cant change.