Forum Replies Created
-
AuthorPosts
-
Aaron, N3MBHForum AdministratorSent you and email.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorAllstar is something that’s been on our back burner. It will just take some time. Either we will need to incorporate it ourselves or wait until it’s incorporated into SVXLink. It uses an Asterisk backend so it is a different architecture. We would probably have to run that side by side with SVXLink and pipe the audio back and forth. A bit more involved than a standard module. It’s on the list once we have the time to devote to it.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorI am trying to get a better understanding of what you mean by ping ponging…or what exactly is happening. You mentioned a beep. I am trying to remember if this is a beep issued by echolink/module. Would need to try and recreate your setup. Can you send me an .orp file if I email you directly?
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorIf we can come up with a work around and build an ORP module, we will certainly update you here.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorHello Klaus,
I hope 2.1.1 is working well for you. This version is built with the SVXLink release 17.12.2 and not the trunk. We were having some other issues with the trunk version and it is much more consistent to base our builds off of a release than a trunk. The trunk version has the tendency to change.In talking with Dan, there appears to be changes to the Meta Info module that require the trunk build currently. The 17.12.2 release was put out over a year ago, so not sure if Tobias will be making an updated release in the near future. The only way around this is to use the build script located at https://github.com/OpenRepeater/scripts and do your own custom build and build with trunk. It will still require some hacking to get the module to activate and you’d need to manually edit your config for the module.
Sorry about the wait, but we are trying to work around some of the stalled development on SVXLink. That said, it does look like Tobias has been making some commits to it this year.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorKlaus…glad you got it figured out.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorHello Randy,
Yes they are ready to use. I would used the 2.1.1 image as it has a bug fix for the 2.1.0 image. The 2.1.0 image will likely be made unavailable in the near future. As of this writing, they are officially release…just in a soft release. Meaning I have not made the official announcement yet, wrote a blog article, sent out email newsletter, and post to social media as I typically do with new releases. That will be coming soon. Working on some new videos and I have some other that said they would help with some documentation. It’s not drastically different from 2.0.0.73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorThe way OpenRepeater works is the settings in the web UI are saved into a database, then those settings are used to construct the proper config files when changes are made. Generally speaking I would say it is not typically possible to upgrade the software as historically speaking with each progressive version there have been gradual changes to the database structure that could cause issues migrating the data.
It would likely be best to take screen shots of your setting and apply the same settings in the new version. If you have any custom sound files, be sure to make backups of those and upload those into the new version.
In the upcoming version 2.1.0 we have added a backup and restore feature. This will backup the database, modules, customs sound files, and ALSA settings. Going forward from here, you will be able to attempt to restore a backup to a newer version, but ORP will warn you if there is a version mismatch between the backup file and the current version. This will be a great feature for migrating installations to a different controller, recovering from a failure, or making restore points if you want to experiment.
The backup is a single file with ‘.orp’ extension. This is just an archive file and you can unzip it by changing the extension to ‘.tar.gz’.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorWell the DMK URI i think was development more for use with Asterisk and Allstar. The first thing would be able to get it working with a base install of SVXLink. From what I’ve read (which is not much) it sounds theoretically possible, but it might take some doing.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
Aaron, N3MBHForum AdministratorHello Randy, I would have to experiment with this some to see if I am able to recreated the same issue. But from your other post it seems that you have done some heavy modifications, so there could be something that is causing an undesired affect. I mentioned it the other post I just commented on about looking into doing a 2.1.0 build that will support simplex logic ideal for an echolink node.
73,
Aaron – N3MBH / WRFV871OpenRepeater is offered free of charge. Find out how you can support us.
-
AuthorPosts
