I suggested we remain with Psip, it appears lobster has agreed.gcmartin wrote:I have 2 questions which seem to be key for me
- Why are we trying to change the name of PSIP. Why aren't we just calling it SIP? What up?
It seems the name will remain as Psip.- If you do NOT have a server, where is the registration going to come from for the caller to contact the callee?
Apparently pjsua, the engine of Psip, is able to conduct peer to peer communications without a sip server. There are a number of people who would like this functionality including myself. I'm just having a few problems working out how to configure it. I understand if I was to put your IP address into my buddy's list I could see when you were online and I could call you. Of course this is more useful if you have a static IP address rather than dynamic one.gcmartin wrote: SIP is a protocol that is kinda similar to Internet. It relies on some authority who know where things are so that connections can traverse for an end to end tunnel for 2-way audio-video traffic.
For example: has this been used on a local LAN to get one telephony to connect to another? For a client to client operation, this will help anyone understand what is happening at which point you will begin to see why there is an Asterisk (and others that exist).
Neither do I yet but I'm working on it.gcmartin wrote: I do not have the skills for programing a STUN or any other NAT traversal techniques for getting past your router into the iNet to support audio communication connection services. But, before I step that far, I would most certainly insure that I can pick up a telephone on my LAN and talk to some other LAN user to insure that much of the system you envision is operating with the clarity you want.
With the current Psip I am able to communicate between my current network on 192.168.0.* without a sip server.
For example: on computer A, with an IP of 192.168.0.3, I can communicate with computer B, with an IP address of 192.168.0.4. This works very well. What I am trying to do is communicate with someone outside of my local network in the same manner.
The pjsua manual can be read from the existing Psip under the help menu item or here http://www.pjsip.org/pjsua.htmgcmartin wrote:
Trying to help with this posting by providing a starting point for a roadmap to successful implementation.
If need, and there is some document which points me to doing this on the local LAN using the product your reference, please steer me so that I can get the 1st step for direct SIP to SIP communication going.
Yes but they are all quite large. Psip is way under a Meg which fits better with the Puppy vision.gcmartin wrote: BTW aren't there some SIP to SIP or SIP to POTS implementations already available off-the-shelf?
Psip sound quality is also brilliant. It's probably better than all of the rest I have tried.
It can also be used on dialup, try that with Skype.
Register an ekiga account here. https://www.ekiga.net/?page=register
Here is the list of changes that I am currently working on:
- Tidy up the menu system
Remove and update redundant links
Include a username along with the sip address in the buddy list
Include the text-chat in main dialog instead of floating windows
Peer to Peer communications
If I was really skillful I would like build the entire GUI into the C code of pjsua.
It would be nice just to have two files, the main and the config file.
I hope that answers your questions.
Regards smokey