Page 15 of 16

Posted: Sun 02 Dec 2018, 17:06
by Mike Walsh
@ musher0:-
musher0 wrote:<snip>....I have added *.desktop file and icon from M_W's pet....</snip>
Oooooh....... :shock: :o :)

Nah, feel free, mate. Anything I post for Puppians to use, you do as you like with.

I picked that icon simply because it seemed a wee bit more 'modern', if you see what I mean.... :lol:

If any of my stuff helps somebody else out, I'm good with that. That's what the Linux ethos is all about, as far as I'm concerned. Share & share alike!


Mike. :wink:

Posted: Mon 03 Dec 2018, 02:02
by smokey01
I've started compiling psip-1.42 for various distributions. You can download a copy of the packages here: http://smokey01.com/psip/

Posted: Mon 03 Dec 2018, 06:15
by Pro
smokey01 wrote:I've started compiling psip-1.42 for various distributions. You can download a copy of the packages here: http://smokey01.com/psip/
thanks.
I see in packages empty /root and may be missing opencore-amr* library.

Posted: Mon 03 Dec 2018, 10:56
by smokey01
Pro wrote:
smokey01 wrote:I've started compiling psip-1.42 for various distributions. You can download a copy of the packages here: http://smokey01.com/psip/
thanks.
I see in packages empty /root and may be missing opencore-amr* library.
There is an empty /root. I meant to delete it but I forgot. It's harmless.

What distro are you running? Probably a good idea to mention that as there are many.

I've tested all of those distros on my psip site and they work.
http://smokey01.com/psip/

Posted: Mon 03 Dec 2018, 23:24
by Pro
smokey01 wrote: What distro are you running? Probably a good idea to mention that as there are many.
Arch linux based distro, not Puppy.

Ок, if libs present in system, no problem.

Posted: Tue 04 Dec 2018, 01:21
by smokey01
Pro wrote:
smokey01 wrote: What distro are you running? Probably a good idea to mention that as there are many.
Arch linux based distro, not Puppy.

Ок, if libs present in system, no problem.
They are except for a couple of symlinks which I included.

Did it run in Arch? If not run ldd on the binary to see what's missing.

Cheers

Posted: Tue 04 Dec 2018, 07:29
by Pro
smokey01 wrote: Did it run in Arch? If not run ldd on the binary to see what's missing.
no problem. yes i check psip with ldd.

x32_64 version coming soon?

Posted: Tue 04 Dec 2018, 07:37
by smokey01
Pro wrote:
smokey01 wrote: Did it run in Arch? If not run ldd on the binary to see what's missing.
no problem. yes i check psip with ldd.

x32_64 version coming soon?
Are you asking or providing?

@Pro, the 32bit version I posted will run in Fatdog64-800a providing the 32bit library SFS is loaded.

Posted: Tue 04 Dec 2018, 12:28
by watchdog
Repackaging psip-1.42 without the /lib dir it works in upupcc. Tested with sip.diamondcard.us. The symlinks in /lib break openssl and sylpheed in upupcc.

Posted: Tue 04 Dec 2018, 12:32
by smokey01
watchdog wrote:Repackaging psip-1.42 without the /lib dir it works in upupcc. Tested with sip.diamondcard.us. The symlinks in /lib break openssl and sylpheed in upupcc.
So once the /lib directory with the symlinks has been removed it works? Yes?

Posted: Tue 04 Dec 2018, 13:45
by watchdog
smokey01 wrote:
watchdog wrote:Repackaging psip-1.42 without the /lib dir it works in upupcc. Tested with sip.diamondcard.us. The symlinks in /lib break openssl and sylpheed in upupcc.
So once the /lib directory with the symlinks has been removed it works? Yes?
Yes, it works in upupcc. I have used the repackaged psip-1.42-xenial.pet.

LATER: I tried an encrypted call with "Secure voice call" and it does not work. What's the difference between "Secure Voice Call" and SRTP? Srtp can be enabled or disabled but with "Secure Voice Call" enabled I can't call.

LATER1: diamondcard.us is also known as ekiga call-out to call phone numbers. I searched with google and it seems that ekiga does not support encryption. If you login at your account at:

https://www.diamondcard.us/

you have the possibility of sending cheap international sms with your credit. So using psip and diamondcard.us is a basic alternative to skype and other heavy voip softwares.

Posted: Tue 04 Dec 2018, 20:18
by smokey01
smokey01 wrote:
watchdog wrote:Repackaging psip-1.42 without the /lib dir it works in upupcc. Tested with sip.diamondcard.us. The symlinks in /lib break openssl and sylpheed in upupcc.
So once the /lib directory with the symlinks has been removed it works? Yes?
watchdog wrote:Yes, it works in upupcc. I have used the repackaged psip-1.42-xenial.pet.
I have renamed it to psip-1.42.pet as it works on more than xenial. I may need to add a tooltip to upupcc when I add it to the list or add it's own .pet. Thanks for letting me know.

Posted: Tue 04 Dec 2018, 23:14
by Pro
smokey01 wrote:@Pro, the 32bit version I posted will run in Fatdog64-800a providing the 32bit library SFS is loaded.
multilib? this no best way, imho.

I suggest to look, as is done in my package. I posted the archive in the cloud.
https://cloud.mail.ru/public/9t5A/MFvZNQmyo
all optional lib and links may be used from /opt/psip/lib

Posted: Wed 05 Dec 2018, 04:06
by watchdog
Also tested psip-1.42-x86_64.pet in bionicpup64 7.9.7. Working fine with sip.diamondcard.us and the following psip.conf:

Code: Select all

{
	"accounts":	[{
			"name":	"New account",
			"sip-url":	"sip:xxxxxx@sip.diamondcard.us",
			"registrar":	"sip:sip.diamondcard.us",
			"realm":	"*",
			"user":	"xxxxxx",
			"password":	"xxxyyyzzz",
			"use-srtp":	0,
			"proxy":	"sip:sip.diamondcard.us",
			"active":	1
		}],
	"settings":	{
		"ring-command":	"aplay -Dplug:dmix /usr/share/sounds/2barks.au",
		"loglevel":	0,
		"help-command":	"defaultbrowser http://www.smokey01.com/help/psip/psip-help.html",
		"call-timeout":	"15",
		"minimise-tray":	0,
		"auto-register":	0,
		"ringtone-file":	"/usr/share/audio/beep_high.wav",
		"im-beep":	0,
		"im-command":	"",
		"activity-log":	0,
		"sampling-rate":	1,
		"quality":	5,
		"max-calls":	"4",
		"sip-port":	"5060",
		"public-ip":	"xx.yy.zz.aa",
		"stun-server":	"stunserver.org",
		"disable-vad":	0,
		"enable-ice":	0,
		"turn-server":	"",
		"turn-user":	"",
		"turn-password":	"",
		"turn-realm":	"",
		"turn-use-tcp":	0,
		"disable-tcp":	0,
		"disable-optional-srtp":	0,
		"audio-in":	"HDA Intel: CX20549 Analog (hw:0,0)",
		"audio-out":	"dmix"
	},
	"buddy-categories":	[{
			"category":	"iptel.org utilities",
			"buddies":	[{
					"nick":	"music",
					"address":	"sip:music@iptel.org"
				}, {
					"nick":	"echo",
					"address":	"sip:echo@iptel.org"
				}, {
					"nick":	"conference",
					"address":	"sip:conference@iptel.org"
				}, {
					"nick":	"voice mail",
					"address":	"sip:1000@iptel.org"
				}]
		}, {
			"category":	"ekiga.net utilities",
			"buddies":	[{
					"nick":	"echo",
					"address":	"sip:500@ekiga.net"
				}, {
					"nick":	"callback",
					"address":	"sip:520@ekiga.net"
				}, {
					"nick":	"conference",
					"address":	"sip:501@ekiga.net"
				}]
		}, {
			"category":	"personal",
			"buddies":	[{
					"nick":	"casa",
					"address":	"sip:0039xxxyyyzzz@sip.diamondcard.us"
				}]
		}]
}
If your network is under NAT then you have to use the public-ip and probably a stunserver. You can read for example your public-ip at:

http://www.indirizzo-ip.com/whois.php

Posted: Wed 05 Dec 2018, 06:40
by Pro
watchdog wrote:Also tested psip-1.42-x86_64.pet
i download file http://smokey01.com/software/internet/p ... x86_64.pet and my archiver say "archive damaged". may be have new link?

Posted: Wed 05 Dec 2018, 07:21
by jamesbond
watchdog wrote:If your network is under NAT then you have to use the public-ip and probably a stunserver. You can read for example your public-ip at:

http://www.indirizzo-ip.com/whois.php
I would say http://icanhazip.com but I know so many people get very nervous about it for reasons I can't fathom, so I'd better not say anything about it :lol:

By the way, I have a new tarball for psip: http://distro.ibiblio.org/fatdog/source ... 05.tar.bz2. Nothing big, I just fixed a few compile errors and added "--help" and added "--expand-buddies" which will expand the buddy list by defaults (this is CatDude's request). Version number stays at 1.42.

Posted: Wed 05 Dec 2018, 13:02
by smokey01
Pro wrote:
watchdog wrote:Also tested psip-1.42-x86_64.pet
i download file http://smokey01.com/software/internet/p ... x86_64.pet and my archiver say "archive damaged". may be have new link?
Try this:

Code: Select all

tar -xvJf psip-1.42-x86_64.pet
This will extract it but will display a few errors that are harmless like:
xz: (stdin): Compressed data is corrupt
tar: Child returned status 1
tar: Error is not recoverable: exiting now
Now you can repackage it for your distro.

Posted: Wed 05 Dec 2018, 16:03
by CatDude
jamesbond wrote:By the way, I have a new tarball for psip: http://distro.ibiblio.org/fatdog/source ... 05.tar.bz2. Nothing big, I just fixed a few compile errors and added "--help" and added "--expand-buddies" which will expand the buddy list by defaults (this is CatDude's request). Version number stays at 1.42.
@ jamesbond
Nice one mate. 8)

Posted: Sat 08 Dec 2018, 02:11
by OscarTalks
I am able to compile PSIP 1.42 in Dpup Wheezy and Dpup Stretch.
Each required one tweak of the CFLAGS in Makefile
Wheezy does not like "-Wno-error=misleading-indentation"
Using pjproject 2.7.2 and osxcart 1.2.0

Audio device names look different in the Preferences window
Compared to my PSIP 1.41 builds which used pjproject 1.14.2 and osxcart 1.1.0

For anyone testing, try making a call to:-
sip:904@mouselike.org
This service has several tests which you can select via the DTMF number keypad, including requesting a text message to be sent to your PSIP client.

Posted: Sat 08 Dec 2018, 22:05
by Mike Walsh
Evening, all.

Now; this may seem like a daft thing to say.....but you may, perhaps, wish to utilise multiple psip.conf files with PSIP. Not multiple accounts; PSIP is already capable of that. I'm talking about the settings for PSIP itself.

I've found it advantageous to use multiple psip.conf files myself. I had it demonstrated to me a couple or three weeks ago that you can, for example, run PSIP thru a VPN tunnel.....which requires a totally different set of configurations to that in use by PSIP when it's operating 'normally'.

You might wish to keep different config files for different groups of contacts, perhaps. Whatever the reasons, it's a PITA to have to keep swapping the files around in /root. PSIP can only make use of one .conf file at a time, otherwise it gets confused!

-------------------------------------

Anyway, I've thrown together a wee utility that permits this to be be carried out easily, via a YAD-powered GUI. It makes use of a hidden folder in /root, containing a number of sub-directories.

You manually place each of your psip.conf files into one of each of these numbered sub-directories (making sure you know which is which, naturally.) You select the utility from Menu->Network->PSIP Config Select, which looks like this:-


Image


Prior to starting PSIP, just select the appropriate psip.conf file with the corresponding button. All this does is to delete the psip.conf file currently resident in /root, and to copy across the one you've selected. Nowt to it, really....it just makes an additional operation a bit easier to handle, that's all. Wait till the 'Success!' message pops up, and you're good to go.

The .pet for this is attached below. If you don't have YAD on your system (check to see if /usr/bin/yad exists), you can get the current version here.

Perhaps it'll be useful for some of you. I built it to fulfill a personal need.....as always, I don't mind sharing.


Mike. :wink: