Drivers Auerswald Gmbh & Co. Kg Mobile Phones & Portable Devices

2009-03-12 23:59:44 UTC

Mar 25, 2004 David, finally, here is our RNDIS USB Gadget Driver - see the attached patch against the gadget-2.4 BK tree as of now. It shouldn't be too difficult to port this to 2.6. Auerswald Uni TAPI Treiber is a Shareware software in the category Miscellaneous developed by Auerswald GmbH & Co.KG. The latest version of Auerswald Uni TAPI Treiber is currently unknown. It was initially added to our database on. Auerswald Uni TAPI Treiber runs on the following operating systems: Windows. Auerswald also uses estos software itself (incl. Networking across locations and federation). Solution The LAN-TAPI interface is the basis for connecting ProCall Enterprise to telephone systems in the small office and business class of Auerswald. The USB ID Repository. The home of the usb.ids file. Main- USB Devices. 0 1 2 3 4 5 6 7 8 9 a b c d e f all. Operating System Driver Provider Driver Version; Download Driver: Windows XP (64 bit) Auerswald GmbH & Co. KG: (6/14/2013) Download Driver: Windows Server 2003 (64 bit).

I'm not a developer but I hope someone can help me. I'm runinng Gentoo Linux
using libusb-0.1.12.
I have a device that is not detected by libusb. It's a telephone switchboard
from German company Auerswald. The vendor ID is 0x09BF.
Drivers Auerswald Gmbh & Co. Kg Mobile Phones & Portable DevicesI found that 'lsusb -t' shows the device, lsusb with '-t' does not:
~ # lsusb -t
Bus# 0
`-Dev# 1 Vendor 0x1d6b Product 0x0001
`-Dev# 4 Vendor 0x09bf Product 0x00dbDrivers Auerswald Gmbh & Co. Kg Mobile Phones & Portable Devices
Bus# 7
`-Dev# 1 Vendor 0x1d6b Product 0x0001
~ # lsusb
Bus 002 Device 051: ID 0411:0098 MelCo., Inc.Drivers auerswald gmbh e
Bus 002 Device 003: ID 15a9:0004
Bus 002 Device 004: ID 0bda:0111 Realtek Semiconductor Corp. Card Reader
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 003: ID 046d:c03f Logitech, Inc. UltraX Optical Mouse
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
I also noticed that there's no device file for it in /proc/bus/usb/001
The software from Auerswald is mainly written in Java but they provided the
source code for the interface to libusb.
This is the part where they are scanning the USB bus for a device from
Auerswald (ID 09BF):
#define MAXDEVICES 16
#define MAXNAMELEN 100
#define MAXDEVLEN 20
#define ID_AUERSWALD 0x09BF // USB vendor ID of Auerswald
(JNIEnv *env, jclass classObj)
jobjectArray temp = NULL;
jstring s = NULL;
jclass stringClass = NULL;
struct usb_bus *bus;
unsigned int u;
unsigned int count;
int ret;
// Syncronized Teil 1
bus = usb_get_busses();
count = 0;
for (; bus; bus = bus->next) {
struct usb_device *dev;
for (dev = bus->devices; dev; dev = dev->next) {
dbg ('Vendor ID 0x%04x found', dev->descriptor.idVendor);
if (dev->descriptor.idVendor ID_AUERSWALD) {
usb_dev_handle *dev_handle;
u = 0;
switch (dev->descriptor.idProduct) {
case 0x00C0: /* COMpact 2104 USB/DSL */
case 0x00DB: /* COMpact 4410/2206 USB */
case 0x00DC: /* COMpact 4406 DSL */
case 0x00DD: /* COMpact 2204 USB */
case 0x00DE: /* COMpact 2104.2 USB */
case 0x00F1: /* Comfort 2000 System Telephone */
case 0x00F2: /* Comfort 1200 System Telephone */
case 0x00F5: /* Comfortel 2500 System Telephone */
// add more devices HERE
dev_handle = usb_open(dev);
I added the 'dbg' call after the second 'for'. When running the application I
get the following output:
Vendor ID 0x0411 found
Vendor ID 0x15a9 found
Drivers auerswald gmbh & co. kg mobile phones & portable devices installedVendor ID 0x0bda found
Vendor ID 0x1d6b found
Vendor ID 0x1d6b found
Vendor ID 0x1d6b found
Vendor ID 0x1d6b found
Vendor ID 0x1d6b found
Vendor ID 0x1d6b found
Vendor ID 0x1d6b found

Drivers Auerswald Gmbh E

Vendor ID 0x046d found
Vendor ID 0x1d6b found
Again the correct vendor ID isn't found and the application stops.
Any idea why 'lsusb -t' (and usbview, which doesn't use libusb) show the
device but lsusb (without -t) and the above code do not?
GPG Public Key available at
Key fingerprint = 3264 280C 05B1 572F 3F0B 42B8 1E7B 2D9D 063B D507
Chris Griffin: Hi, my name is Chris. Mom and dad said that I'm supposed to be
on my best behavior tonight and not mention poo. Oh god! What have I done?

Auerswald has attended the droidcon Berlin. „droidcon is a global developer conference series and a network focusing on the best of Android. The idea behind droidcon is to support the Android platform and create a strong network for developers and companies.” We made a session and invited the participants to stage for an open discussion.

The question was: „What can you do with an Android deskphone and what is required to be successful?” While mobile smartphones address every potential user (from the school kid to the executive) the usage of a deskphone has more of business angle. The discussion had two major discussion points: one was to identify use-case scenarios and integrated in this discussion was how to do it, which APIs and possibilities does Auerswald offer to get everything working?

Use-cases aka What does it mean to replace the dumb phone on your desk with a smartphone?

There were several other smart scenarios besides the standard use cases like synchronized address book (Exchange, Google, etc.) and calendar to talk about, which really show the power of smart devices compared to closed boxes normal phones and PBXs usually are. The power of APIs enables to integrate EASILY and cost efficient functionality.

In the group we found following useful scenarios:

CRM integration: Have an app to identify incoming callers: is it an important client or just the customer who is not paying his bills? Show up notes about the customer. After the call, the app could write back to the database that there has been a conversation with this specific customer.

Call Center scenarios: For inbound call centers the agent could immediately identify for which client the call is. Relevant information can be pushed directly to the display. For outbound calls the dialing can be made really easy. The call plan could be integrated into an app; the physical buttons on the phone could be used to enter multiple choice (yes/no) answers by the client.

Call a cab widget: Would ease the life of secretaries to call a cab. One press and the widget shows the secretary the time until the cab will arrive.

Nagios monitoring over buttons: An administrator in the group brought up the scenario in which the multicolor LEDs in the buttons could show server/network status. It’s immediately visible when the status changes from green to yellow or even red. A button press could retrieve exactly the affected system.

Fleet control: Another similar scenario to monitor the status of a fleet of trucks, delivery drivers, etc. With one glimpse of an eye the scheduler can see and react to delays or incidents.

How to get things going

Auerswald uses a standard Android open source package and only extended the stock Android where needed. The intention of Auerswald is to document and offer all required APIs for developers to access every part of the device. While the SIP phone app (from Auerswald) uses standard phone APIs, and the keypad (0,1,2,3,4,5,6,7,8,9,*,’) use standard input mechanisms, the phones also have additional function keys with tricolor LED (green, yellow, red) and different states (on, off, blinking) which are not available on other Android devices. To gain access to these keys, Auerswald implemented an API, with which a button can be assigned to a specific app. This API is documented on the website. The website also covers additional information about app provisioning, software updates in closed networks and central manageability.

Drivers Auerswald Gmbh Reviews

While most interfaces already rely on Android standards and may be used, the technical design of the phones required some modifications. The biggest modification concerns the audio processing, while the standard audio path through Android is not optimized for low latency, Auerswald implemented its own audio path with echo canceler and different audio optimizations for phone scenarios. Currently the engineers are working in enabling apps to gain access to these technologies so that apps can benefit from this low latency and phone optimized audio.

We were happy to figure out potential use cases and hope that companies and app developers see the potential our devices have to offer. We are looking forward to see the ideas and possibilities come true.

Über den Autor:
Tim Köhler, Leiter Produktmanagement, Auerswald GmbH & Co. KG