Ask Your Question

I have a new ID, and am unable to transmit.

asked 2017-07-14 04:08:14 +0200

n5jlc gravatar image

I am capable of accepting my own answer. Please do not close my question on my behalf.

On July 10, I posted this question:

I have a new ID (issued two days ago). I can be heard on the local repeater, but I don't transmit across the Internet links. Why is this?

If it is because I have a new ID, how long will it take before I can use the system?

I received a few good questions and some logical answers. However, the problem was never solved and is ongoing. One of the previous answers to my post was:

I checked the Brandmeister database, and confirm that your ID 3105372 is there. Can you confirm this is the one you are using ?

I can also see that the Brandmeister network is accepting transmissions from you, which have been sent over the network. All transmissions have been made from repeater K5NSX. Do you have a hotspot that you could try on Brandmeister, and testing on different master servers ?

That is the correct ID, and yes the network will show that it is accepting transmissions. You can even look on my "last heard" page and see that I am shown to have transmitted several times. However, this information is misleading. If you were to look at Hoseline when I attempt to transmit, you will neither see my call sign listed nor hear my audio at all.

I have been working with some of the "people in the know" and it has been determined that there is a problem in the 3102 master. AE5AU confirmed the problem: "It seems that all Arkansas (3105) IDs 3105347 and later are not able to use BrandMeister. Their traffic doesn't traverse the master servers from one repeater to another nor to Hoseline."

If anyone knows how to reach any of the developers (this is closed-source or I would fix it myself) please let them know about this problem.

edit retag flag offensive close merge delete

2 answers

Sort by ยป oldest newest most voted

answered 2017-07-14 05:12:20 +0200

R3ABM gravatar image

updated 2017-07-14 05:18:45 +0200

First, developers know about this problem. Second is the problem is solved and it was due to operational support. In few words: each master node has its replica of data from the central DB that responsible for many thing including IDs. With a new software update several master nodes have not been configured properly to get updated data from the central DB. To be honest in addition there was another problem before with getting the data from MARC DB. It seems like someone in MARC doesn't like BM :)

edit flag offensive delete link more


Well, I don't mean to sound disagreeable, however if I can't transmit then the problem is not solved. If I understand you correctly, it sounds like the software has been patched but that patch has not been installed on the master server for this area. I would say that the problem is half-solved.

n5jlc gravatar imagen5jlc ( 2017-07-14 16:46:54 +0200 )edit

Not this way. Software was OK but configuration file wasn't. Please post here your ID to check.

R3ABM gravatar imageR3ABM ( 2017-07-14 18:55:45 +0200 )edit

answered 2017-07-14 18:00:32 +0200

n5jlc gravatar image

The software was updated with the correction on 3102 this morning, so this problem is solved.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2017-07-14 04:08:14 +0200

Seen: 46 times

Last updated: Jul 14