Puppy Phone - VOIP using SIP

[Lobster]

Smokey we are talking at cross purposes . . .
If you configure from the menu and have registered
with iptel you need to know that
registrar URL: sip.iptel.org
- so that is general info for others
that I was unaware of when I came to fill the info

I Have not altered the config file which you sent - that is something different and requires the settings you mention

[smokey01]

Smokey we are talking at cross purposes . . .
If you configure from the menu and have registered
with iptel you need to know that
registrar URL: sip.iptel.org
- so that is general info for others
that I was unaware of when I came to fill the info

I Have not altered the config file which you sent - that is something different and requires the settings you mention

Sorry. So is it working now?

[Lobster]

Sorry. So is it working now?

No

It does however run quite well in Wine except for two very important features, Sound and Video.

Que?
On that basis PSIP is working quite well . . .

[Caneri]

Hey..just had a lovely live voice chat with Smokey on psip...hooray

[Lobster]

Good news Eric

I have received voicemail (via email) which I will listen to soon
- thanks guys appreciate efforts
- once we get a few more people phoning we might be able to stage a conference call?

Theoretically the process of VOIP in Puppy should be:

1. Ensure working sound and Mic
2. Register Sip address
3. Configure PSIP with registered details
4. Use PSIP as soft phone

I am somewhere around 3 and 4 - Update - Was able to receive call from Eric - we have contact
We are getting there
- smokeys modified links (updated PSIP file is already an improvement)

Once we know the procedure works we can maybe set up a help wizard/tutorial/video to help the procedure . . .
Update I will be working on this next

there are programs for direct (non server communication) but
using PSIP would be the ideal
http://www.murga-linux.com/puppy/viewto ... 149#557149

[Caneri]

Hi Ed,

I confirm Fatdog does not work with psip.
The program (psip) will run with 32bit libs but there are no pop-up alerts to a phone call and calls (with the "m" command) produce a HUGE 50% cpu load....sadly so far nadda with FDog.

BUT....my old 409 install and Smokey's newer install co-operate and the call was crystal clear.

Very nice to speak with the pups again in live voice..Eric

[smokey01]

I know this is a bit adventurous of me but I'm going to try and figure out how to compile the source.

What I would really like is a GUI built into the source so there is only one file plus the config file of course.

I think this may be beyond my capabilities but it's nice to dream.

Maybe someone with the skills will offer to assist.

I wonder if BaCon would be useful to achieve this. Maybe vovchik is our man? http://www.murga-linux.com/puppy/profil ... ile&u=4077

[Lobster]

Just listened to Eric and Grants messages. Eric yours are clear - Grant yours are speaking too close to the mic - but message was fine Thanks guys

I wonder if BaCon would be useful to achieve this.

It would and we are likely to find the code easier (and kosher)

Eric thanks for confirming whether 64bit Puppy was PSIP compatible
Really PSIP should be working on all Puppys once pjsua had been compiled for that version . . .

[Lobster]

OK some more info:

In Slacko I can not input the password, when doing the configuration
I thought this was a security feature - not so, as I tried in Lucid.
Lucid was equally frustrating for me but the password could be added.

Grant has a new mic much clearer (still only able to receive voice messages)

Been doing USB camera experiments. On a reasonably modern system a program that runs the video cam could be installed or suggested and run as a multitask option? Could not remember which is the best program for Puppy webcam support (I got the video working in the Skype from http://portablelinuxapps.org/Puppylinux - but not the sound)?

Also been looking at SIP on Android. Any recommendations if you use this over wifi?

[Lobster]

I think (fingers and claws crossed) I was able to send a voice mail to Smokey
- tried Eric several times but only iptel has voice messages . . .

So I think PSIP is working (yep) but needs some type of wizard
. . . rather complex to get working . . .

Once you have a SIP number
and configured your setup
you click on start pjsua
then refresh buddies
then click on a buddy and call

Grant
if you do a further update . . .
with regards the file /usr/local/psip/psip-gui

if you change line 89

Code: Select all

           <action>gxmessage "$(echo -e "Opening config file for editing. \nAfter editing you will need to stop and start pjsua\nusing the phone menu")"; Nicoedit '$PJCFG' &</action>

to

Code: Select all

           <action>gxmessage "$(echo -e "Opening config file for editing. \nAfter editing you will need to stop and start pjsua\nusing the phone menu")"; defaulttexteditor '$PJCFG' &</action>

that is one word Nicoedit to defaulttexteditor
It should then be possible to edit the config file (using geany) in most Puppy
Nicoedit is not in Slacko

. . . getting there . . .
thanks guys - sorry it has taken me so long . . .

[Lobster]

OK have chatted to Eric and Grant now
- managed a conference call with Grant
- that is something new and to use that you will need his
updated PSIP
http://www.murga-linux.com/puppy/viewto ... 750#555750

OK have created a quickstart section and will add more to
http://puppylinux.org/wikka/Psippy
'Use PSIP as soft phone' section soon . . .

Quickstart
Ensure working sound and Mic
Right click on the speaker icon (bottom right)
Ensure mic is turned on and working
Register Sip address
when putting in details:
sip URL: lobster@iptel.org (your iptel registered name replaces 'lobster')
registrar URL: sip.iptel.org
Configure PSIP with registered details
It is suggested you register and use iptel has this has a voicemail facility
Use the test call features Under the Iptel menu item Echo and music tests
Try a test call to one of the contact numbers
sip:smokey01@iptel.org, sip:lobster@iptel.org, sip:caneri@iptel.org
Use PSIP as soft phone

[smokey01]

I just had a nice, clear long chat with lobster on Psip.

In the revised GUI I have included a conference channel, no 528.

We both hung up and entered the conference channel and it worked brilliantly. It would be interesting to see how well this works with a number of callers.

On this weekend coming I might announce a time where we can have a conference so we can test.

Known issues at the moment are:
1. Can not hear the calling sound from the call initiator. The person receiving the call can hear the beep beeps ok though.

2. Has problem sharing the sound card. You might find that you don't get sound after using Psip. It doesn't seem to release control of the driver. Once you close Psip you get use the of your card sound back.

I will make the change from nicoedit to defaulteditor that lobster has suggested above.

I will create a pet package for both a GUI upgrade and the complete package, probably on the weekend.

[Lobster]

gcmartin wrote:
Did anyone ever get PSIP to Android going over your WiFi (P2P)?

You sent a couple of questions (this may have been one)
as a PM. My priority has been getting PSIP running
and using that as a means of communication whilst we develop . . .

I was not really in a position to answer questions until I had PSIP working in Slacko

Next will be Android to PSIP, conference call (as mentioned by Grant)
and starting some sort of wizard to integrate with Grants work.

So to answer your question - no not yet

[Lobster]

Enclosed my PSIP 2 wizard

Code: Select all

#!/bin/sh
#Lesser GPL licence v2 (/usr/share/doc/legal/lgpl-2.1.txt). 2007 www.puppylinux.com
#PSIP 2 Wizard written by Lobster Sept 2011 for Slacko Puppy 5.3

AUDIOICON='/usr/local/lib/X11/mini-icons/mini-speaker.xpm'

export PSIPPY="
 <window title=\"PSIP 2   S E T U P   WIZARD\" window_position=\"1\">
  <vbox>
  
   <frame 1: Ensure SOUND AND MIC settings are working>
    <hbox>
     <text><label>   Click button for mixer:</label></text>
     <vbox><button><input file>${AUDIOICON}</input><action>/usr/local/bin/defaultaudiomixer & </action></button></vbox>
     <text><label>Having adjusted the levels, click this button to play a test sound:</label></text>
     <vbox><button><input file>${AUDIOICON}</input><action>/usr/bin/aplay /usr/share/audio/2barks.wav &</action></button></vbox>
     </hbox>
   </frame>
  
   <frame 2: REGISTER SIP address>
     <text><label>Register with iptel for voicemail and conferencing using browser</label></text>
     <vbox><button><action>defaultbrowser http://serweb.iptel.org/user/reg/ &</action></button></vbox>
   </frame>
  
   <frame 3: CONFIGURE PSIP add SIP details to PSIP2 - Configure / Edit Account>
    <text><label>add details including password:</label></text>
    <text><label>sip URL: lobster@iptel.org (your iptel registered name replaces 'lobster')</label></text>
    <text><label>registrar URL: sip.iptel.org</label></text>
   </frame>
  
    <hbox>
     <button><label>Details</label>
        <action>defaultbrowser http://puppylinux.org/wikka/Psippy &</action>
     </button>
     <button>
       <label>EXIT</label>
       <action type=\"exit\">EXIT</action>
     </button>
    </hbox>

  </vbox>
</window>
"
 
 RETVAL="`gtkdialog3 --program=PSIPPY 2>/dev/null`"
 eval "$RETVAL"
 [ "$EXIT" != "RUNALSA" ] && exit

The last bit should be cleaned up as is not required but it seems to work as is . . .

Code: Select all

 RETVAL="`gtkdialog3 --program=PSIPPY 2>/dev/null`"
 eval "$RETVAL"
 [ "$EXIT" != "RUNALSA" ] && exit

[dogle]

A word of warning about a pjsua gotcha which has bitten me a couple of times.

A short time ago, in preparation for getting going with Psip, I put a music CD on pCD in order to check my audio setup (which I don't use regularly). I was alarmed to find that sound was being chopped at ~~10Hz, but fortunately memory was on my side for once.

The cause is pjsua trying to do something in the background - normal service was resumed as soon as pjsua was closed via the Psip GUI or killed from the CLI.

No big deal, perhaps, but it is a newbie-trap. When I was trying to use old-Psip many moons ago it had me looking for a replacement sound card before going any further (the effect is so like 'motorboating', as in, decoupling cap failure, I was quite convinced that I had a dud on my hands). :-))

[smokey01]

dogle you are quite right.

I have identified this above at para 2 and some years ago.

It's one of the bugs I am going to try and fix as we never managed to last time. It's really not that much of an issue but it one all users should be aware of.

[smokey01]

Lobster your little setup wizard is quite good except there is a huge delay before you hear the 2barks, 15 - 30 seconds.

I must have press the test sound button many times as I was getting barks every now and then for up two three minutes.

[Lobster]

The sound bug may be related to the delay
I don't have it - but not good
Maybe a forced close of pjsua for this part of the wizard?
Micko says 'aplay' does play .au files - on my system it does not
Maybe a solution would be to use 'defaultmediaplayer' - assuming there is such a command?

I will do some more work on the wizard and let you have any results soon

Crash?
Run Puppy!

[smokey01]

I think I have found a solution to make the sound card play nice with Psip.

add the following line to /root/.psip/pjsua.cfg file:

Code: Select all

--snd-auto-close=0

This appears to release the sound card by Psip when not in use so you can play songs after using Psip without having to close it down.

More testing is required but this is how I tested it so far.

Test 1
Without the code inserted as above, check voice mail.
Now play a song with Psip running.
No sound

Test 2
Add the code to the pjsua.cfg file
Check voice mail
Now play a song
You should hear the song

Let me know if this works for you too.

[dogle]

maybe there's more than one ...

The 'motorboating' one - which seems to be provoked by asking pjsua to make an invalid call (eg to 'voicemail' when not registered with Iptel) is not relieved for me (I'm running 4.3.1 BTW) by addition of the code Smokey kindly suggests.

Note, it can be provoked by telling pjsua to make an invalid call using the CLI, so probably not Psip-dependent at all.

If so this could be tough on the newcomer who has at present no indicator that pjsua is still running when he thinks his VoIP application has been shut down. (Tray anyone?).