Flight-Hotel-Car Rental for AstriCon 2009: Support sip2sip.org Use our hot button to Expedia

Contact Us!
                                            sip2sip.org Clean Pipes, Free Triple Play and Wireless, Now!

Join us!

Private Members

Server Members

Hosting Members

Employee Area

Employer Area

Public


sip2sip.org

Official Home Page 





















The day would come eventually for Jeff and Dan to assess free long-distance calling with some objectivity. 

After all, peering requires lots of bells and whistles with many more tools.

The equipment of a node begins innocently enough. A sip-phone here and a PSTN gateway there.  And then there is the hop-on, hop-off configuration along with hours of learning SER, Asterisk and even SIPSimple.  In a few months a peer has spent $1,000 and a whole slice of life. And for what? So we all can dialup the world for free.

Here at sip2sip.org we wish to thank all of you who work to fulfill the promise. The world owes a special debt of gratitude to heroes like Jeff and Dan and the many unsung heroes of the DARPA/ARPANET. How can we sufficiently thank the Kahns, Cerfs and Metcalfes, Pulvers and Berningers? One way is to innovate. Seek out the Jonathan Rosenbergs and Stefan Chekanovs. Find the Darren Yeungs of this world and keep picking their brains. 

So! Where are we now?  Where is the "free" in calling the world for free.  It is really a simple configuration that takes complex knowledge of the setup routines.  You need a computer now, whereas before the onset of TigerJet and MagicJack USB you needed only a router and ATA and PSTN. We have always needed a phone and an ISP and public telephone system.  It is simple if you know what you are doing or someone else who does, otherwise you now must use your computer too, leaving it on all the time. 

Where are we going from here?  First we need to understand the lesson that we cannot do anything alone.  From our perspective at sip2sip.org there is but one approach to this problem of unity.  It is the approach we have advocated for many years, more than twenty years now.  This isn't our own idea, just an adaptation of a good one.  As our website works at advancing our approach, we expect the true believers will want to be a part of it.

A thumbnail of the approach is to identify and connect to the islands of underutilized capacity.  If a mutual benefit can be established beyond free worldwide data transmission then the approach will succeed.  A good example is a digital download product.  You just keep selling the permission to download. Everybody gets what they want.  These islands of underutilized capacity can support a worldwide mesh for free international calling. There just needs to be something in it for them. Exceeding the bandwidth allocation is where the first cost increment is experienced. Employee costs are naturally implied with any kind of growth.

sip2sip.org will look at the problem in a our own special way so all will benefit from the strength of membership.  Large numbers of people, yes. But we need large groups of people and many diverse groups of them, too. All peoples have much in common. We have more in common with each other than the elements of our makeup which sets us apart. Our world consists of more than advertising and commissions.  And our world is safer if we can communicate freely and free of charge.


Breaking News: Open XCAP Project solves non-dedicated XCAP server multiple realms naming with xcap-root url URL notation.





How to use multiple realms on the same server

If you run an OpenXCAP server for multiple domains you must inform the server under which domain you want to be authenticated otherwise the authentication will be performed under the default realm defined in the server configuration. The IETF has specified a special host name for the xcap server (xcap.example.com) in order to detect the domain name. In the real-world, for a multi domain environment it is likely that the same server using the same hostname will serve xcap documents for subscribers under multiple domains. Following the IETF recommandation, when using TLS one should purchase certificates for each domain it serves and should have in DNS for each domain it hosts an A record for the XCAP server address, which is not efficient.

We have solved this problem in the following way.

If the client is using user@domain notation in the XCAP URLs, OpenXCAP will work out of the box. We have noticed however that this functionality is not always available in today's clients. To fix the problem so that the server works for any client you must indicate in the client xcap-root url URL the domain your belong to as follows:

https://xcap.example.com/xcap-root@example.com/



Purchasing Page

Buy From Us



Carbon Credits That Work

















Contact Us!








BUY AN AMERICAN MADE ENCLOSURE AND GET FREE INSURANCE

FREE SERVER INSURANCE WILL SAVE YOU SUBSTANTIAL MONEY


 Click here for details









If you have any comments about our WEB page, you can e-mail us at xxxxxxxx@sip2sip.org.
However, due to the limited number of personnel in our corporate office, we may be unable to provide a direct response.


SIP2SIP HOSTING OPERATIONS INTERNATIONAL - http://sip2sip.xxxxxx.com or CALL 1-8XX-XXX-XXXX, 24 HOURS A DAY

Join us!

Private Members

Server Members

Hosting Members

Employee Area

Employer Area

Public



Legal Disclaimer:

Copyright 1988-2009 SIP2SIP.ORG.