![]() # sysop mailaddress and DMR 12:29:53.121 BM_United_States_3102, Opening DMR NetworkÄ®: 12:31:03.146 BM_United_States_3102, Connection to the master has timed out, retrying connection # hytera_mmdvm DMRGateway Config by OE1KBC Again, it works fine when using a hotspot id like 311372204, but times out using 311342. ![]() I am using repeater ID 311342 which was already under "My Repeaters" Any Ideas what difference it made once I changed the ID#? I am posting my configs and logs below, maybe someone could peek at it and figure out what I may change. I am pointing it to BM on port 62030 for MMDVM repeaters with passw0rd. The actual repeater is behind the Hytera DMR Gateway instance, so I will have IT log into BM as the old repeater ID." Once I changed this, it logged in and worked fine, but after awhile, it times out to BM and never comes back. Thinking about that, I figured "Hey, my repeater ID that is already affiliated would work. I had a conversation with one of the BM administrators and he said let him know and he would set the ID up for a repeater. It is setup to pass our local TG to the cluster only and everything else goes out across BM, using TGRewrite rules, so it logs into my HBLink3 instance and BM 3102. I burned it in a couple of weeks at home and then took it to he repeater site. The only issue was how TG's didn't disconnect after 15 mins. ![]() When I first deployed it, I set it up with just a hotspot ID and everything worked great from the test repeater at the house. It has worked very well so far, but I have a small issue and have not been able to find any info on it. I deployed this to connect my Hytera repeaters into my HBlink3 instance. I know this isn't a DV Switch product, but figure it works much the same. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |