wwwtpadcom
Site Admin
Joined: 09 Oct 2006
Posts: 1690
Location: UK, Lancashire, Burnley, BB12 7TW
|
 Posted: Thu Dec 04, 2008 3:51 pm Post subject: Tpad with the Free SIP Com. Softphone (SIP/VoIP/Jabber/MSN) |
 |
|
You can now use your Free Tpad VoIP Account and Free SIP Number with the new SIP Communicator Softphone.
SIP Communicator - the Java VoIP and Instant Messaging client.
SIP Communicator is an audio/video Internet phone and instant messenger that supports some of the most popular instant messaging and telephony protocols such as SIP, Jabber, AIM/ICQ, MSN, Yahoo! Messenger, Bonjour, IRC, RSS and soon others like IAX.
SIP Communicator is completely Open Source / Free Software, and is freely available under the terms of the GNU Lesser General Public License.
How to use the Tpad Global VoIP Network with SIP Communicator:
1. Download from http://www.sip-communicator.org/index.php/Main/Download
2. Pick the correct version for your operating system (Windows etc.)
3. Install and run the Softphone. (Run, accept T+C's etc..)
4. Select SIP from the list
5. Enter these details:
SIP ID: Your 7 digit Tpad Number
Password: Your Tpad password
SIP / Server Port:5060
Domain:sip.tpad.com
Outbound proxy = sip.tpad.com
Click NEXT.
How to make Calls with SIP Communicator and Tpad:
1. Dial in the correct Tpad format and press the Call Button
e.g
9+00+Country Code of destination your are dialling + area code + contact number
e.g 900441282777711
About SIP Communicator:
SIP Communicator is an audio/video Internet phone and instant messenger written in Java. It supports some of the most popular instant messaging and telephony protocols such as SIP, Jabber/XMPP (and hence GoogleTalk), AIM, ICQ, MSN, Yahoo! Messenger, IRC, Bonjour and soon others like IAX.
The development of SIP Communicator started at the Louis Pasteur University in Strasbourg, France. Throughout the years our community has grown to include members and contributors from Brazil, Bulgaria, Cameroon, China, France, Estonia, India, Germany, Japan, Romania, Spain, UK, USA, and others. Some of these contributors have joined the project after successfully participating in the 2007 edition of Google Summer of Code.
SIP Communicator is based on the OSGi architecture using the Felix implementation from Apache. This makes it very extensible and particularly developer friendly.
Some more history
SIP Communicator was originally called JsPhone and was one of the examples in the JAIN SIP reference implementation project. It then moved out to a life of its own as a separate project on java.net. At the time it was mostly doing audio/video calls through SIP and hence the name. It was one of the first to support IPv6 telephony.
Near the end of 2005 SIP Communicator was completely rearchitectured and a new OSGi based design was chosen so that plugins could be easily written for the project.
Acknowledgment:
The SIP Communicator and JAIN SIP projects, though administratively separate, are still in close collaboration.
SIP Communicator was originally created by Emil Ivov who was at the time a student at the Louis Pasteur University in Strasbourg, France. Today the core team has grown and counts developers and contributors from all over the world. A complete list of those may be found in the Team and Contributors section.
FAQs:
http://www.sip-communicator.org/index.php/Documentation/FAQ
How do I get the latest SIP Communicator source code?
You could either cvs checkout all of it from the SIP Communicator CVS repository (see Version Control for details) or use one of the nightly source snapshots (check the Download page).
§ How do I become an Observer of the project?
You can request the Observer project role here
§ I’ve discovered a bug, what can I do?
Please, report it to the developers!
Take a look at the Reporting bugs guidelines page describing the steps to report bugs effectively.
§ I’d like to see a new feature in SIP Communicator, can you do that for me?
Yes, developers take into account feature requests. First of all you’ll need to fill a new entry in java.net Issue Tracker or email directly the developers and describe in detail what new feature you want to see in SIP Communicator. We’ll examine its feasibility and decide whereas it can be included in SC distribution. Nevertheless you must know that treating feature requests is not our priority task and thus it is highly dependent of the developers’ availability.
§How do I subscribe to mailing lists?
To subscribe to one of the lists, you can either subscribe directly from java.net project page once logged in or send an email to listname-subscribe@sip-communicator.dev.java.net. Please visit Mailing Lists page to learn more about SIP Communicator’s mailing lists.
§ How do I contact the project developers?
You can ask questions concerning usage of the SIP Communicator on the users mailing list. In case you’d like to discuss anything having to do with the development please refer to the dev mailing list (Note that the mailing lists are moderated, so there may be a delay before your post shows up). For all urgent queries you could use IRC at irc.freenode.net, channel #sip-communicator.
§ How do I send a patch?
Mail patches to the dev mailing list, with a subject line that contains the word “PATCH” in all uppercase, for example
Subject: [PATCH] fix for SDP descriptor in INVITE message
A patch submission should contain one logical change; please don’t mix N unrelated changes in one submission, send N separate emails instead.
The patch itself should be generated from within the project root directory using unified diff format. The following example shows one way to generate it:
sip-communicator$ svn diff > myPatchfile.txt
You should give your patch files meaningful names. For instance if you fix a socket bug in the foo class do not call your patch file “patchfile.txt” but instead call it “foo-socket.txt”.
If the patch implements a new feature, make sure to describe the feature completely in your mail; if the patch fixes a bug, describe the bug in detail and give a reproduction recipe. An exception to these guidelines is when the patch addresses a specific issue in the issues database — in that case, just make sure to refer to the issue number in your log message.
§ I would like to update this wiki - what can I do?
Currently, only project developers are permitted to update the wiki. Please send your suggested changes to the dev mailing list.
A wiki page can be updated by appending the string ?action=edit to the current url and refreshing the page. The page will then be displayed with an extra menu line that includes a ‘Page Edit’ item.
If you click on the ‘Page Edit’ item, you will be redirected to a logon page. Enter your developer username and password and you should be redirected back to the original page. Click on ‘Page Edit’ again to access the source content of the page (a quick reference to wiki markup syntax is also displayed).
§ The cc-buildloop target of ant fails with the following error message: “Could not create task or type of type: junitreport”.
On some Linux distributions such as Debian, the ant package is actualy subdivided into multiple packages. So when you chose to install junit and ant with the distribution specific package system, don’t forget to install ant-optional too.
§ The cc-buildloop target of ant fails with the following error message: “No test with id=IcqProtocolProviderSlick”.
Have you created your own accounts.properties file in the lib directory? You’ll need to define two ICQ test accounts at least, and preferably some test accounts for the other supported protocols.
_________________
Tpad, Global ITSP VoIP Provider, Business Class IP PBX Hosted and Managed Telephony Solutions |
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
