Jump to content

Java APIs for Bluetooth

From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by 131.231.226.100 (talk) at 18:54, 26 March 2009 (Delete contact details to commercial site). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

The Java APIs for Bluetooth is a Java ME specification for APIs that allow Java midlets to use Bluetooth on supporting devices. The specification was developed under the Java Community Process as JSR 82. The Specification, Reference Implementation, and TCK [1] are maintained at Motorola Open Source.

Java APIs described in the JSR-82 interface for following Bluetooth Protocols/Profiles:

  • SDAP - Service Discovery Application Profile
  • RFCOMM - Serial Cable Emulation Protocol
  • L2CAP - Logical Link Control and Adaptation Protocol
  • GOEP - Generic Object Exchange (OBEX) Profile

JSR 82 implementations for Java 2 Platform Standard Edition (J2SE) are also available.

Dear Friends:

Want to setup VoIP company, a business under your own brand name? We have complete solution to launche VoIP (Voice Over Internet Protocol) company. All support comes included. Features: PC2Phone, Device2Phone, Calling Card, Callback,sms callback solution, Ani Callback solution, DID callback solution, Cli Callback, Pin Callback, Wholesale Termination, Online Billing, Unlimited Resellers Creating, online shop, invoice generator, paypal integrated online shop, pin recharge modules, H323 and SIP. No ties to us, deal with the wholesalers you want and buy VoIP minutes from any one in the market without any expensive equipment.

[b]System[/b]

Single platform solution Rapid Service Rollout Pre-configured templates Scalability - phased investment Quick, flexible reporting Open database architecture allowing for extended reporting functions and use of external scripts

[b]Switching[/b]

Carrier-grade softswitch Gatekeeper, registrar and proxy functionality SIP and H323 protocol support Protocols transparent conversion Network protection capabilities Advanced routing Single entry point into VoIP infrastructure Flexible proxy methods

[b]Billing[/b]

Various authentication methods Prepaid/postpaid accounts Robust engine Fully integration with the softswitch Cooperation with MySQL or MSSQL

[b]Management interface[/b]

Real-time traffic and system's performance monitor Windows graphical interface Web-based interface

[b]Web interface for endusers[/b]

Customizable customer self care web interface Admin section with embedded html editors Ready to use design templates CDRs, payments, invoices, address book, user's profile and others/ Sending SMS, web callback

[b]IP IVR[/b]

Customizable IVR scenarios (XML) Ready to use templates Caller ID recognition One or two stage calling procedures Support for DIDs as access numbers

[b]Softphone[/b]

Based on SIP protocol Proprietary VOIP tunnel technology - making/receieving calls even behind voip blockades Fully integration with the web interface Quick access to voicemail Sending SMS

[b]Callback[/b]

Authentication by callerID or PIN Various methods of realizing callback Support for DIDs as callback service numbers SMS and Web triggered callback Embedded IVR system

[b]Resellers system (VSR)[/b]

Multilevel structure Web-based comprehensive interface Support for multi-currency Customizable web interface for end-users Integration with the E-Shop

[b]Callshop[/b]

Real-time monitoring and billing Booths visualisation Standalone and web based versions invoicing

[b]E-Shop[/b]

Various payments processors Credit cards, paypal, moneybookers Automatic sign-up procedure Recharge, also by vouchers/PINs Basket for selling products online

[b]SMS module[/b]

Support for http methods Extended routing plan with support for multiple SMS providers Integrated with the softphone and the end-users web interface Support for wholesale SMS traffic

[b]Capacity[/b]

Average result 1000 conncurent calls (full proxy) on one server (Dual Xeon CPU 2GB RAM*). For higher traffic recommended is cluster configuration with two or three servers with voipswitch software running on separate servers and connected to one, shared SQL database installed on a dedicated server. Web services running on a backup SQL server set in replication mode so that the load from web requests (for example browsing CDRs, statistics) does not affect the performance of the main SQL server.

  • tested and certified for SIP interoperatibility with Level3 (US based tier one carrier)

[b]Scalability[/b] Phased implementation of new services by enabling additional modules.

[b]Operating system[/b] Windows 2000, XP pro, Windows 2003 (both standard and web editions)

[b]Hardware requirements[/b] Recommended are servers based on Intel Xeon processors

dual core or quad core, in configuration of single or dual CPU, RAM minimum 1GB, HDD 100 GB or more

Devices

Devices supporting JSR 82:

Platform
40 series after 40 platform 2nd
s60 series after s60 platform 2nd
s80 series after s80 platform 2nd

Full list compiled based on publicly available resources

Devices not supporting JSR 82:

Stub icon

This computer science article is a stub. You can help Wikipedia by expanding it.

Retrieved from "https://en.wikipedia.org/w/index.php?title=Java_APIs_for_Bluetooth&oldid=279849214"