hecatae
resident hecatae
- Joined
- Feb 7, 2014
- Messages
- 760
- Reaction score
- 199
I've tried those French instructions several times on an RPi3, but always end up with it failing due to 403 Forbidden and Not Found errors when accessing:If you want to test Xivo on a Raspberry Pi 2/3, you could test Raspivo.io
It's a packaging of Xivo for ARM platform.
The doc, in french (English outdated, I'll try to update during next week) http://www.raspivo.io/installation-depuis-nos-depots.html
Feel freeto test at home, office
I've tried those French instructions several times on an RPi3, but always end up with it failing due to 403 Forbidden and Not Found errors when accessing:
deb http://www.iris-network.fr/raspivo/raspberrypi3/latest jessie main
deb http://ftp.fr.debian.org/debian/ stable main contrib non-free
It's because you use latest, you have to use the version number, for the last version today, use :
deb http://www.iris-network.fr/raspivo/raspberrypi3/16.05 jessie main
deb http://ftp.fr.debian.org/debian/ stable main contrib non-free
After setting /etc/apt/sources.list.d/irisnetwork.list to:
deb http://www.iris-network.fr/raspivo/raspberrypi3/16.05 jessie main
deb http://ftp.fr.debian.org/debian/ stable main contrib non-free
[...]
E: Unable to locate package xivo
Oops! I did miss that.Do you 'apt-get update' after modifying /etc/apt/sources.list.d/irisnetwork.list ?
I now have a script that fully automates building a working XiVO system on a Raspberry Pi, but there are two issues:I didn't test with Internet Explorer the setup, but it should be working ... I just package the setup for ARM's processor, all the 'intelignce' is from Xivo devs.
I did exactly as you outlined, but no difference:Try this:
$ sudo -i
# apt-get clean
# cd /var/lib/apt
# mv lists lists.old
# mkdir -p lists/partial
# apt-get clean
# apt-get update
Did you work this out?
apt-get install debian-keyring
gpg --keyserver pgp.mit.edu --recv-keys 1F41B907
gpg --armor --export 1F41B907 | apt-key add -
arztde,@RPi-Fanyou should google the keywords and write in the normal help forum where are more that run debian.
TiJof,TiJof,
I noticed that the Raspberry Pi installation instructions were updated yesterday and tried them, but there are still problems remaining:
1. The PGP public key signature must be replaced with:
ClePowa=3FC6A9B2ACDD4CF3 && gpg --keyserver pgpkeys.mit.edu --recv-key $ClePowa && gpg -a --export $ClePowa | apt-key add -
in order to eliminate the following error:
W: GPG error: http://www.iris-network.fr jessie InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3FC6A9B2ACDD4CF3
2. When logging into the Raspberry Pi with any browser, the browser still complains of an invalid security certificate.
That's not a mystery really. Any self-signed cert will be complained about, unless created under a CA that you have imported as trusted.Now we just need to figure out what's causing browsers to complain about an invalid security certificate.
Do the non-Raspberry Pi builds have the same problem?That's not a mystery really. Any self-signed cert will be complained about, unless created under a CA that you have imported as trusted.
Yes.Do the non-Raspberry Pi builds have the same problem?
Why would anyone use a security certificate that is guaranteed to be flagged as invalid and suspicious?
Link up your team and customers Phone System Live Chat Video Conferencing
Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.
Check your inbox!
We’ve sent you an email. Click on the button in the email body to verify your email address – (if you can not find it, check your spam folder).
Upon verification you will be directed to the 3CX setup wizard.