PIONEERS Raspivo: XiVO for Raspberry Pi

hecatae

resident hecatae
Joined
Feb 7, 2014
Messages
760
Reaction score
199
http://raspivo.io/

http://raspivo.io/installation-depuis-nos-depots.html

FirstScreenRaspivoResize.png


off to play
 

RPi-Fan

Member
Joined
Jun 8, 2014
Messages
85
Reaction score
13
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
 

TiJof

New Member
Joined
May 10, 2016
Messages
4
Reaction score
0
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
 

RPi-Fan

Member
Joined
Jun 8, 2014
Messages
85
Reaction score
13
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

and running:

mkdir /var/lib/xivo/
touch /var/lib/xivo/disabled
apt-get install -y xivo --force-yes

The response is:

E: Unable to locate package xivo
 

RPi-Fan

Member
Joined
Jun 8, 2014
Messages
85
Reaction score
13
Do you 'apt-get update' after modifying /etc/apt/sources.list.d/irisnetwork.list ?
Oops! I did miss that.

Installation is now proceeding, but I do see:

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
W: GPG error: http://ftp.fr.debian.org stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY CBF8D6FD518E17E1

I'll report back whether the installation ultimately succeeds or fails.

Thanks for the help!
 

RPi-Fan

Member
Joined
Jun 8, 2014
Messages
85
Reaction score
13
Installation appears to have completed successfully.

When I access the Pi with Internet Explorer (11), I get a security certificate error. I proceeded anyway and went through the installation phase. When I got to the final step, clicking Validate didn't appear to do anything. After several refreshes and reattempts, it finally proceeded. It now presents a login screen, but entering the password I set doesn't get me in. There's no error message. It just sits there on the login screen. I also tried to accept/install your security certificate, but the warning doesn't go away.
 

RPi-Fan

Member
Joined
Jun 8, 2014
Messages
85
Reaction score
13
I did a fresh install and used Firefox this time. Firefox also complains about an invalid security certificate, so I had it make an exception so I could proceed.

Everything went smoothly this time all the way through the installation/validation process, but I'm still unable to log in at the authentication screen that follows. I used the password I set on the second line and tried numerous things on the first line, including leaving the word 'Login' there. There's a little browser activity each time, but I'm left on the authentication screen.
 

TiJof

New Member
Joined
May 10, 2016
Messages
4
Reaction score
0
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.
 

RPi-Fan

Member
Joined
Jun 8, 2014
Messages
85
Reaction score
13
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 now have a script that fully automates building a working XiVO system on a Raspberry Pi, but there are two issues:

1:
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
W: GPG error: http://ftp.fr.debian.org stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY CBF8D6FD518E17E1

2:
Browsers (IE and Firefox tested) complain of an invalid security certificate when XiVO is accessed. IE also does not seem to get along with the final step of installation when the Validate button is clicked and installation does not appear to complete. With Firefox, everything progresses normally when the Validate button is clicked.
 

RPi-Fan

Member
Joined
Jun 8, 2014
Messages
85
Reaction score
13
TiJof,

Using the following sequence:

echo "net.ipv6.conf.all.disable_ipv6=1" >> /etc/sysctl.conf
apt-get -y install ncurses-term git curl apt-transport-https
cat > /etc/apt/sources.list.d/irisnetwork.list << EOF
deb http://www.iris-network.fr/raspivo/raspberrypi3/16.05 jessie main
deb http://ftp.fr.debian.org/debian/ stable main contrib non-free
EOF
apt-get -y update
apt-get -y --force-yes install debian-archive-keyring
apt-get -y update
mkdir /var/lib/xivo/
touch /var/lib/xivo/disabled
apt-get -y --force-yes install xivo
sed -i 's/ status)/ status)\n\texit 0/g' /etc/init.d/dahdi

I have eliminated the following error:

W: GPG error: http://ftp.fr.debian.org stable Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8B48AD6246925553 NO_PUBKEY 7638D0442B90D010 NO_PUBKEY CBF8D6FD518E17E1

The browser certificate error and the following error still remain:

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

It appears there needs to be an apt-get of a missing iris-network.fr keyring to eliminate the remaining errors.

Any pointers?

Thanks,
Ron
 

RPi-Fan

Member
Joined
Jun 8, 2014
Messages
85
Reaction score
13
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 -
I did exactly as you outlined, but no difference:

apt-get update
...
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

and browsers complain about an invalid security certificate when connecting to the Raspberry Pi running XiVo. IOW, absolutely no change.

I've done dozens of fresh installs and the problem never changes.

Thanks for the suggestion,
Ron
 

RPi-Fan

Member
Joined
Jun 8, 2014
Messages
85
Reaction score
13
@RPi-Fanyou should google the keywords and write in the normal help forum where are more that run debian.
arztde,

I have Googled the problem extensively with no useful results. If you have a link to the 'normal help forum' where I could post the problem (in English), it would be greatly appreciated. My discussion here was directed more toward @TiJof who stated he was the packager of the setup for ARM processors.

Ron
 

RPi-Fan

Member
Joined
Jun 8, 2014
Messages
85
Reaction score
13
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.
 

RPi-Fan

Member
Joined
Jun 8, 2014
Messages
85
Reaction score
13
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.
TiJof,

Thank you for updating the Raspberry Pi installation instructions with the correct PGP public key signature.

Now we just need to figure out what's causing browsers to complain about an invalid security certificate.

Ron
 

jerrm

Guru
Joined
Sep 23, 2015
Messages
838
Reaction score
405
Now we just need to figure out what's causing browsers to complain about 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.
 

RPi-Fan

Member
Joined
Jun 8, 2014
Messages
85
Reaction score
13
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.
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?
 

jerrm

Guru
Joined
Sep 23, 2015
Messages
838
Reaction score
405
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?
Yes.

It's the way it works. The whole point of ssl/tls is to only trust known sources. Anyone can create a self-signed cert.

Either purchase a cert from a public trusted provider and install on the server, or import the generated CA cert as trusted into your clients.
 

Members online

No members online now.

Forum statistics

Threads
25,780
Messages
167,506
Members
19,199
Latest member
leocipriano
Get 3CX - Absolutely Free!

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.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Top