root/site/pages/faq.html
@
180
| Revision 177, 18.6 kB (checked in by nadya, 4 years ago) |
|---|
| Line | |
|---|---|
| 1 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> |
| 2 | <html> |
| 3 | <head> |
| 4 | <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"/> |
| 5 | <link rel="icon" href="/pages/images/favicon.ico" type="image"/> |
| 6 | <title>Telnic | FAQs </title> |
| 7 | <link rel="stylesheet" href="/pages/css/layout.css" type="text/css"/> |
| 8 | <link rel="stylesheet" href="/pages/css/print.css" type="text/css"/> |
| 9 | <link rel="stylesheet" href="/pages/css/nstyleupdates.css" type="text/css"/> |
| 10 | <link rel="stylesheet" href="/pages/css/faq.css" type="text/css"/> |
| 11 | <script src="/pages/js/jquery.pack.js"> |
| 12 | </script> |
| 13 | <script src="/pages/js/utils.js"> |
| 14 | </script> |
| 15 | <script src="/pages/js/swfobject.js"> |
| 16 | </script> |
| 17 | <script src="/pages/js/faq.js"> </script> |
| 18 | <meta name="author" value="Telnic Developer Community"/> |
| 19 | <meta name="email" value="general.AT.developer.DOT.telnic.DOT.org"/> |
| 20 | </head> |
| 21 | <body> |
| 22 | <!--PAGE HEADER--> |
| 23 | <!--TELNIC LOGO--> |
| 24 | <div id="header"> |
| 25 | <div class="logo"> |
| 26 | <a href="http://telnic.org/"> |
| 27 | <img src="/pages/images/TelnicLogo.gif" alt="The .tel Developer Community" border="0"/> |
| 28 | </a> |
| 29 | </div> |
| 30 | <div class="links"> |
| 31 | <a href="http://telnic.org/" class="normallink">Home</a> |
| 32 | <a href="http://telnic.org/aboutus.html" class="normallink">About Us</a> |
| 33 | <a href="/pages/sitemap.html" class="normallink">Developer Sitemap</a> |
| 34 | <a href="http://telnic.org/contact.html" class="lastlink">Contact Us</a> |
| 35 | </div> |
| 36 | </div> |
| 37 | <div id="wrapper"> |
| 38 | <div id="nsearchheader"> |
| 39 | <div id="nsearchformarea"> |
| 40 | <form action="http://www.google.com/search" method="get"> |
| 41 | <input value="telnic.org" name="sitesearch" type="hidden"/> |
| 42 | <input size="10" name="q" id="query" type="text"/> |
| 43 | <input name="Search" id="btnSubmit" value="Search" class="loginbtn" tabindex="3" type="submit"/> |
| 44 | </form> |
| 45 | </div> |
| 46 | </div> |
| 47 | <div class="clear"> </div> |
| 48 | <!--LEFT SIDE NAVIGATION--> |
| 49 | <div id="navcol"> |
| 50 | <ul class="first"> |
| 51 | <li> |
| 52 | <a href="/">Overview</a> |
| 53 | <ul class="navcolleveltwo"> |
| 54 | <li> |
| 55 | <a href="/pages/general_landing.html">Understanding .tel</a> |
| 56 | </li> |
| 57 | <li> |
| 58 | <a href="/pages/record_types.html">Record Types</a> |
| 59 | </li> |
| 60 | <li> |
| 61 | <a href="/pages/security.html">Privacy</a> |
| 62 | </li> |
| 63 | <li> |
| 64 | <a href="/pages/telhosting.html">TelHosting</a> |
| 65 | </li> |
| 66 | </ul> |
| 67 | </li> |
| 68 | <li> |
| 69 | <a href="/pages/downloads.html">.tel Applications</a> |
| 70 | <ul class="navcolleveltwo"> |
| 71 | <li> |
| 72 | <a href="/pages/blackberry/landing.html">Blackberry</a> |
| 73 | </li> |
| 74 | <li> |
| 75 | <a href="/pages/winmobile/landing.html">Windows Mobile</a> |
| 76 | </li> |
| 77 | <li> |
| 78 | <a href="/pages/winoutlook/landing.html">Outlook</a> |
| 79 | </li> |
| 80 | <li> |
| 81 | <a href="/pages/iphone/landing.html">iPhone</a> |
| 82 | </li> |
| 83 | <li> |
| 84 | <a href="/pages/more_apps.html">Softphone</a> |
| 85 | </li> |
| 86 | <li> |
| 87 | <a href="/pages/th/landing.html">TelHosting Software</a> |
| 88 | </li> |
| 89 | </ul> |
| 90 | </li> |
| 91 | <li> |
| 92 | <a href="/trac">Developer Area</a> |
| 93 | <ul class="navcolleveltwo"> |
| 94 | <li> |
| 95 | <a href="/trac/register">Sign up</a> |
| 96 | </li> |
| 97 | <li> |
| 98 | <a href="/trac/login">Log in</a> |
| 99 | </li> |
| 100 | <li> |
| 101 | <a href="/pages/discussion.html">Community</a> |
| 102 | <ul class="navcollevelthree"> |
| 103 | <li> |
| 104 | <a href="/trac/discussion">Forums</a> |
| 105 | </li> |
| 106 | <li> |
| 107 | <a href="/trac/wiki/TracWiki">Wiki</a> |
| 108 | </li> |
| 109 | <li> |
| 110 | <a href="/trac/wiki/RssFeed">RSS Feeds</a> |
| 111 | </li> |
| 112 | <li> |
| 113 | <a href="/trac/wiki/BugTracker">Submit a Bug / Patch</a> |
| 114 | </li> |
| 115 | </ul> |
| 116 | </li> |
| 117 | <li> |
| 118 | <a href="/trac/wiki/SourceCode">Source Code</a> |
| 119 | </li> |
| 120 | <li> |
| 121 | <a href="/pages/tools.html">Toolkits</a> |
| 122 | </li> |
| 123 | <li> |
| 124 | <a href="/pages/api_landing.html">APIs</a> |
| 125 | </li> |
| 126 | <li> |
| 127 | <a href="/pages/howtos.html">Howtos</a> |
| 128 | </li> |
| 129 | <li> |
| 130 | <a href="/pages/whitepapers.html">Whitepapers</a> |
| 131 | </li> |
| 132 | <li> |
| 133 | <a href="/pages/guidelines.html">Guidelines</a> |
| 134 | <ul class="navcollevelthree"> |
| 135 | <li> |
| 136 | <a href="/pages/maintain_code.html">Code Maintenance</a> |
| 137 | </li> |
| 138 | <li> |
| 139 | <a href="/pages/site.html">Website Updates</a> |
| 140 | </li> |
| 141 | </ul> |
| 142 | </li> |
| 143 | <li> |
| 144 | <a href="/pages/external_refs.html">External Links</a> |
| 145 | </li> |
| 146 | </ul> |
| 147 | </li> |
| 148 | <li> |
| 149 | <a href="/pages/faq.html">FAQ</a> |
| 150 | </li> |
| 151 | </ul> |
| 152 | </div> |
| 153 | <!--MAIN BODY--> |
| 154 | <div id="maincolfullwidth_withspace_more"> |
| 155 | <a name="FAQ"> |
| 156 | <h1>FAQ</h1> |
| 157 | </a> |
| 158 | <div class="click">Click the question to view the answer.</div> |
| 159 | <div class="expand"> |
| 160 | <a href="#" class="expandAll">Expand All</a> |
| 161 | | |
| 162 | <a href="#" class="collapseAll">Collapse All</a> |
| 163 | </div> |
| 164 | <div class="clear"> </div> |
| 165 | <div id="faq"> |
| 166 | |
| 167 | <div class="expander"> |
| 168 | <h3 class="label"> |
| 169 | <img src="/pages/images/faq_about_tech.gif" border="0" class="rollover"/> |
| 170 | </h3> |
| 171 | <ul class="faq"> |
| 172 | <li class="question">How is .tel different from other domains? |
| 173 | <div class="content"> |
| 174 | <p>A typical top-level domain (TLD) stores IP addresses in the DNS |
| 175 | and returns them when queried. The .tel DNS prohibits storage of A-records |
| 176 | (address records) and operates with other record types: NAPTR, |
| 177 | TXT and LOC to enable direct storage of contact data; |
| 178 | see <a href="/pages/record_types.html">Record Types</a>. </p> |
| 179 | </div> |
| 180 | </li> |
| 181 | <li class="question">What's a NAPTR record? What are the key benefits of a NAPTR record? |
| 182 | <div class="content"> |
| 183 | <p>Shortly and in connection with .tel domains: NAPTR records are communications-specific |
| 184 | type/value pairs that can be ordered. For example, you could have a phone number |
| 185 | (one NAPTR of type "voice:tel" with value "+13105551212"), followed by an email address |
| 186 | (another NAPTR of type "email:mailto" and value "a@b.com"). You can also label each |
| 187 | NAPTR record, for example the phone number could be labeled "my home".</p> |
| 188 | <p>Another key benefit of NAPTR records is their extensibility. New NAPTR types can be |
| 189 | created as new means of communications are developed, making the .tel solution |
| 190 | a very powerful long-term communications hub.</p> |
| 191 | <p>The full definition of a NAPTR record, in the |
| 192 | <a href="http://en.wikipedia.org/wiki/NAPTR" target="_blank">Wiki</a>.</p> |
| 193 | </div> |
| 194 | </li> |
| 195 | <li class="question">Do I need to understand DNS to use the .tel platform? |
| 196 | <div class="content"> |
| 197 | <p>No. All you need to know is how to interpret the DNS query results, |
| 198 | and we will provide you with libraries and sample code for that. |
| 199 | You surely do not to know the complexities of the DNS infrastructure, |
| 200 | but it may be generally a good idea to learn how things work at some |
| 201 | point, and that includes DNS basics. For a list of useful materials |
| 202 | about the DNS, see <a href="/pages/external_refs.html">External Links</a>. </p> |
| 203 | </div> |
| 204 | </li> |
| 205 | <li class="question">What DNS server software am I restricted to use? |
| 206 | <div class="content"> |
| 207 | <p>There is no restriction as to what DNS server software to use. However, some |
| 208 | older DNS servers may be incompatible with the EDNS0 standard necessary |
| 209 | for proper hosting of a .tel zone file. If your DNS server is relatively |
| 210 | up-to-date (within the past few years), it supports EDNS0. If your DNS |
| 211 | server is older than that, you probably have major security holes |
| 212 | that need patching!</p> |
| 213 | </div> |
| 214 | </li> |
| 215 | <li class="question">What about data security? |
| 216 | <div class="content"> |
| 217 | <p>Owners of .tel domains may not want to share their data with every Internet user; |
| 218 | to restrict data access, the .tel platform includes a "friending" mechanism based on |
| 219 | data encryption. Please see a high-level explanation at the |
| 220 | <a href="security.html">Security</a> page |
| 221 | and more in the <a href="http://rikkles.blogspot.com/2008/05/privacy-in-tel.html" target="_blank"> |
| 222 | blog entry</a> about the privacy model by Telnic Ltd. CTO, |
| 223 | Henri Asseily.</p> |
| 224 | </div> |
| 225 | </li> |
| 226 | <li class="question">Can I use .tel instead of OpenID? |
| 227 | <div class="content"> |
| 228 | <p>.tel puts you in control of your communications and allows you to centrally manage |
| 229 | and securely publish all your means of communications. |
| 230 | OpenID solves a totally different problem, which is cross-site authentication, |
| 231 | otherwise called "single sign-on". |
| 232 | See the <a href="http://en.wikipedia.org/wiki/OpenID" target="_blank">Wikipedia</a> article |
| 233 | on OpenID for more information. </p> |
| 234 | </div> |
| 235 | </li> |
| 236 | |
| 237 | </ul> |
| 238 | </div> |
| 239 | <div class="expander"> |
| 240 | <h3 class="label"> |
| 241 | <img src="/pages/images/faq_about_telhosting.gif" border="0" class="rollover"/> |
| 242 | </h3> |
| 243 | <ul class="faq"> |
| 244 | <li class="question">What's TelHosting Software? |
| 245 | <div class="content"> |
| 246 | <p>The TelHosting Software application is responsible for managing the content |
| 247 | of a user's domain. Registrars maintaining .tel domains need this application |
| 248 | to support additional .tel functionality.</p> |
| 249 | </div> |
| 250 | </li> |
| 251 | <li class="question">What Language is TelHosting Software in? |
| 252 | <div class="content"> |
| 253 | <p>The TelHosting Software is written in cross-platform Java |
| 254 | and uses Apache Tomcat application server, JAX-WS security module, |
| 255 | and other open-source Java components. The TelHosting Software is |
| 256 | provided in its entirety in an Open Source license as well.</p> |
| 257 | </div> |
| 258 | </li> |
| 259 | <li class="question">What interfaces does TelHosting Software provide? |
| 260 | <div class="content"> |
| 261 | <p>TelHosting Software has a web interface for accessing .tel |
| 262 | domain data directly via a web browser. Client applications |
| 263 | interact with the TelHosting software via a standardized SOAP API.</p> |
| 264 | </div> |
| 265 | </li> |
| 266 | <li class="question">Are full API specifications for TelHosting Software available? |
| 267 | <div class="content"> |
| 268 | <p>Yes, the API reference is available online and for download for all developer community members. </p> |
| 269 | </div> |
| 270 | </li> |
| 271 | </ul> |
| 272 | </div> |
| 273 | |
| 274 | <div class="expander"> |
| 275 | <h3 class="label"> |
| 276 | <img src="/pages/images/faq_apps.gif" border="0" class="rollover"/> |
| 277 | </h3> |
| 278 | <ul class="faq"> |
| 279 | |
| 280 | <li class="question">What applications for what platforms can I get now? |
| 281 | <div class="content"> |
| 282 | <p>For a complete list of currently available applications, please see the |
| 283 | <a href="/pages/downloads.html">.tel applications page</a>. To get a plug-in or client, |
| 284 | click the button at the bottom of the page describing the plug-in. Read the |
| 285 | description of the application for installation and configuration instructions. |
| 286 | <br/> |
| 287 | More applicaitons may be under development; please check the <a href="/trac/discussion">forum</a> |
| 288 | for latest news. |
| 289 | </p> |
| 290 | </div> |
| 291 | </li> |
| 292 | |
| 293 | <li class="question">Your application does not work (has a bug). How can I get support? |
| 294 | <div class="content"> |
| 295 | <p>Please use the services in the <a href="/trac">Developers Area</a> to report |
| 296 | the issue via the forum or as an issue ticket. The community will be glad to help you. |
| 297 | For questions on obtaining .tel domains, please refer to <a href="http://telnic.org/contact.html" target="_blank"> |
| 298 | Telnic Support Team</a>. |
| 299 | </p> |
| 300 | </div> |
| 301 | </li> |
| 302 | |
| 303 | <li class="question">What do I do if I need to change an application? |
| 304 | <div class="content"> |
| 305 | <p>You are very welcome to edit any client application you fancy, expand its functionality |
| 306 | or change the way it works. For that, check out the source code from our public SVN as |
| 307 | described on our <a href="/trac/wiki/SourceCode">wiki</a>. When you are ready to share |
| 308 | your code with us, please submit a ticket through the <a href="/trac/wiki/BugTracker">bug tracker</a>. |
| 309 | </p> |
| 310 | </div> |
| 311 | </li> |
| 312 | |
| 313 | <li class="question">Will all the source code be available? |
| 314 | <div class="content"> |
| 315 | <p>Yes, all client applications will be published in binary and source code format. |
| 316 | Some of the applications may not have reached the release stage, |
| 317 | but we plan to share whatever code and ideas we have for all our .tel applications. |
| 318 | In addition, SDKs, custom libs and other tools will be provided in binary |
| 319 | and source formats. |
| 320 | </p> |
| 321 | </div> |
| 322 | </li> |
| 323 | |
| 324 | <li class="question">There is no application for my device (software). Are you going |
| 325 | to make one? |
| 326 | <div class="content"> |
| 327 | <p>All available applications are supported by the developer community, and |
| 328 | new applications may become available as we progress with launching the .tel domain. |
| 329 | For the latest news on upcoming releases, please see the <a href="/trac/discussion"> |
| 330 | developer forums.</a> |
| 331 | </p> |
| 332 | </div> |
| 333 | </li> |
| 334 | |
| 335 | <li class="question">What languages can I write my .tel apps with? |
| 336 | <div class="content"> |
| 337 | <p>You can write your .tel apps in any language. |
| 338 | However, some of them are more suited to the network-centric environment |
| 339 | of .tel: your job will be much easier with a modern DNS library for |
| 340 | reading .tel info, and a HTTP(S) + SOAP library to access the |
| 341 | TelHosting API and friending system.</p> |
| 342 | <p>Our open-sourced applications are written in C#/.Net for the |
| 343 | Outlook plug-in and Windows Mobile, C++ for the Blackberry, |
| 344 | and Java for the TelHosting platform. Check back often in the |
| 345 | developer area for more sample code in other languages |
| 346 | (some iPhone Objective-C code is on the way).</p> |
| 347 | </div> |
| 348 | </li> |
| 349 | </ul> |
| 350 | </div> |
| 351 | |
| 352 | <div class="expander"> |
| 353 | <h3 class="label"> |
| 354 | <img src="/pages/images/faq_integrate.gif" border="0" class="rollover"/> |
| 355 | </h3> |
| 356 | <ul class="faq"> |
| 357 | <li class="question">How can .tel be integrated with web services? |
| 358 | <div class="content"> |
| 359 | <p>There are three main components to the .tel ecosystem:</p> |
| 360 | <ol> |
| 361 | <li class="noplus">A published .tel zone on the DNS cloud</li> |
| 362 | <li class="noplus">A TelHosting web service to edit .tel data</li> |
| 363 | <li class="noplus">A friending system web service to edit friend relationships</li> |
| 364 | </ol> |
| 365 | <p>The first component is accessed via DNS, while the other two via HTTP+SOAP. |
| 366 | You can integrate any one of those components independently with your own web services.</p> |
| 367 | </div> |
| 368 | </li> |
| 369 | <li class="question">So this is just for web services, right? |
| 370 | <div class="content"> |
| 371 | <p>No. Any application that has network access can take advantage of .tel. |
| 372 | </p> |
| 373 | </div> |
| 374 | </li> |
| 375 | <li class="question">How can .tel data be integrated into CRM systems to auto-update data? |
| 376 | <div class="content"> |
| 377 | <p>Simply store your customers' .tel domain names in your CRM. |
| 378 | Then whenever you need to contact them, have the CRM backend make |
| 379 | a DNS call to the .tel domain and grab the latest updated |
| 380 | contact information. You'll never have obsolete contact information again. |
| 381 | See the downloadable <a href="/pages/winoutlook/landing.html">Outlook plug-in</a> |
| 382 | for an in-depth integration example.</p> |
| 383 | <p>Another interesting integration point is to communicate via SOAP |
| 384 | with the TelHosting platform and friending system to have your |
| 385 | CRM users manage their own .tel from within the CRM software.</p> |
| 386 | </div> |
| 387 | </li> |
| 388 | <li class="question">How can .tel entries be managed from an internal CTI app? |
| 389 | <div class="content"> |
| 390 | <p>Computer telephony integration is similar to CRM applications: |
| 391 | since a DNS call is very quick, instead of retrieving someone's |
| 392 | potentially incorrect phone number from your internal database, |
| 393 | retrieve a correct one from his or her .tel.</p> |
| 394 | </div> |
| 395 | </li> |
| 396 | <li class="question">Do I have to pay royalties or GPL my code if I use .tel in my app? |
| 397 | <div class="content"> |
| 398 | <p>No, .tel client applications are released under the Telnic license, |
| 399 | which is not modeled after GPL. Please read the license agreement for details. |
| 400 | </p> |
| 401 | </div> |
| 402 | </li> |
| 403 | </ul> |
| 404 | </div> |
| 405 | <div class="expander"> |
| 406 | <h3 class="label"> |
| 407 | <img src="/pages/images/faq_community.gif" border="0" class="rollover"/> |
| 408 | </h3> |
| 409 | <ul class="faq"> |
| 410 | |
| 411 | <li class="question">Who can participate in the community? Can I join? |
| 412 | <div class="content"> |
| 413 | <p>Everybody is welcome to join the community. To sign up, fill in |
| 414 | the simple <a href="/trac/register">registration form</a>. Your account |
| 415 | is created immediately. You can specify an email address, time zone, and |
| 416 | other preferences for your account. |
| 417 | |
| 418 | </p> |
| 419 | </div> |
| 420 | </li> |
| 421 | |
| 422 | <li class="question">What are the benefits of participating the community? |
| 423 | <div class="content"> |
| 424 | <p>Signing up for the community is totally free and instantenous. An account |
| 425 | at the community website enables you to write to the forums, edit Wiki pages, and |
| 426 | submit tickets to the tracker. You can also create custom ticket reports |
| 427 | and subscribe to your customized RSS feeds. |
| 428 | </p> |
| 429 | </div> |
| 430 | </li> |
| 431 | |
| 432 | <li class="question">What's the difference between contributors and committers? |
| 433 | <div class="content"> |
| 434 | <p>All community members are contributors and have access to all |
| 435 | community resources, including source code, APIs, samples, and test harness.</p> |
| 436 | <p>Based on the principle of meritocracy, an active contributor who makes |
| 437 | stable and valuable contributions through the forum and bug tracker can be |
| 438 | elected <i>committer</i>. Committers are just like any other contributor, |
| 439 | but they have write access to SVN and are generally highly respected in the community.</p> |
| 440 | </div> |
| 441 | </li> |
| 442 | <li class="question">How do I become a committer? |
| 443 | <div class="content"> |
| 444 | <p>A committer is an honorary title, not an official job or role. If you have |
| 445 | been contributing to .tel application development, have demonstrated dedication to |
| 446 | the project and regularity of contributions, you are sure to be elected committer. |
| 447 | If you feel that despite your efforts, your contributions are not properly rewarded, |
| 448 | please speak up at the forum. The committers group is willing to see new members |
| 449 | join and can help you up your path.</p> |
| 450 | </div> |
| 451 | </li> |
| 452 | </ul> |
| 453 | </div> |
| 454 | </div> |
| 455 | </div> |
| 456 | <div class="clear"> </div> |
| 457 | </div> |
| 458 | <!--FOOTER SEPARATOR--> |
| 459 | <div id="footer"> |
| 460 | <div class="left"> |
| 461 | <a href="/pages/legal.html"> Legal & Privacy</a> © 2008 Telnic Limited.</div> |
| 462 | <div class="right"> |
| 463 | <p id="fplayer"> |
| 464 | <a href="http://www.macromedia.com/go/getflashplayer">Get the Flash Player</a> to see this movie.</p> |
| 465 | <script src="/pages/js/countdown.js"> </script> |
| 466 | </div> |
| 467 | </div> |
| 468 | </body> |
| 469 | </html> |
Note: See TracBrowser
for help on using the browser.
