Page 1 of 1

QSO Uploader and QRZ

Posted: Sat 4. Mar 2023, 18:33
by KE4OSL
I just installed QSO Uploader last night and I am not sure if I have it configured properly to upload contacts to QRZ in real time. I have had several QSOs that I've entered into Rumlog but they are not being sent to QRZ. Is there anything else that needs to be configured or used besides Rumlog and QSO Uploader in order to communicate with QRZ? Thanks.

Re: QSO Uploader and QRZ

Posted: Sat 4. Mar 2023, 18:44
by DL2RUM
Note the Help file in the application.
Monitor the application window for given information.
Without any further details it's hard to trouble shoot.

Re: QSO Uploader and QRZ

Posted: Sat 4. Mar 2023, 18:55
by KE4OSL
DL2RUM wrote: Sat 4. Mar 2023, 18:44 Note the Help file in the application.
Monitor the application window for given information.
Without any further details it's hard to trouble shoot.
Sorry I should have provided more. I believe I've set it up based on the suggestions in the help file and also based on some settings provided in the forum. The application window under QRZ.com says "Upload enabled" "Listening to N1MM on port 12070". However, after entering a contact in the log there is no upload.

Re: QSO Uploader and QRZ

Posted: Sat 4. Mar 2023, 19:59
by DL2RUM
This looks good.
Do you have made the corresponding settings in RUMlog?

Re: QSO Uploader and QRZ

Posted: Sat 4. Mar 2023, 22:35
by KE4OSL
DL2RUM wrote: Sat 4. Mar 2023, 19:59 This looks good.
Do you have made the corresponding settings in RUMlog?
I have my QRZ login info in Rumlog and then under UDP I have App info and contact info checked.

Re: QSO Uploader and QRZ

Posted: Sun 5. Mar 2023, 00:11
by DL2RUM
I don't know if the address is correct, but I don't think it's a good idea to receive and save QSO just sent out on the same port!

Re: QSO Uploader and QRZ

Posted: Sun 5. Mar 2023, 01:09
by KE4OSL
DL2RUM wrote: Sun 5. Mar 2023, 00:11 I don't know if the address is correct, but I don't think it's a good idea to receive and save QSO just sent out on the same port!
The host was the issue. It is working now. Thank you!