AVM BlueFRITZ! » History » Version 4
laforge, 03/16/2022 01:52 PM
1 | 1 | roox | h1. AVM BlueFRITZ! |
---|---|---|---|
2 | |||
3 | {{toc}} |
||
4 | |||
5 | In the early 2000s (before WIFI was ubiquitous) "AVM":https://avm.de had a product line called BlueFRITZ! |
||
6 | Via Bluetooth one could access their supported ISDN- and DSL-routers without any cabling. |
||
7 | |||
8 | h2. Supported hardware |
||
9 | |||
10 | |_.Product|_.Description|_.Misc| |
||
11 | |_*USB Adapter*_|| |
||
12 | |BlueFRITZ! USB | USB Bluetooth Adapter | VID/PID 057c:2200 | |
||
13 | |BlueFRITZ! USB 2.0 | USB Bluetooth Adapter | VID/PID 057c:3800 | |
||
14 | |_*ISDN Product*_|| |
||
15 | |BlueFRITZ! AP-X|Bluetooth enabled ISDN router|| |
||
16 | |BlueFRITZ! AP-ISDN|ISDN-"Access Point" - small and powered via the ISDN bus|| |
||
17 | |BlueFRITZ! AP-DSL|DSL-/ISDN-router with Bluetooth|| |
||
18 | |_*OEM variants*_|| |
||
19 | |T-Com Eumex C 200|ariant of the BlueFRITZ! AP-X for the german Telekom|| |
||
20 | |Teledat C 120X|Another variant of the BlueFRITZ! AP-X for the german Telekom|| |
||
21 | |Teledat C 120data|USB Bluetooth adapter sold for the Teledat C 120X|| |
||
22 | |_*Product bundles*_|| |
||
23 | |BlueFRITZ! Startpaket v2.0|BlueFRITZ! USB v2.0 + BlueFRITZ! AP-X|| |
||
24 | |BlueFRITZ! ISDN Set v2.0|BlueFRITZ! USB v2.0 + BlueFRITZ! AP-ISDN|| |
||
25 | |BlueFRITZ! DSL Set v2.0|BlueFRITZ! USB v2.0 + BlueFRITZ! AP-DSL|| |
||
26 | |||
27 | These devices expose a CAPI 2.0 interface that can be used on Windows and Linux. |
||
28 | |||
29 | The _Common ISDN Bluetooth Access Profile_ (CIP) offers a uniform way to access the ISDN services of other devices via Bluetooth. This means that all features are made available in the B and D channels. CIP does not define a new ISDN interface, but uses the established Common ISDN API (CAPI 2.0). The CAPI Message Transport Protocol (CMTP) is used to enable CAPI Bluetooth. This protocol defines the uniform transport of CAPI messages over a Bluetooth L2CAP channel. |
||
30 | |||
31 | h2. Linux Support |
||
32 | |||
33 | Linux mainline support (CMTP/Kernel CAPI) and proper tooling for Bluez exists since 2003. |
||
34 | https://ftp.avm.de/archive/cardware/bluefritz.usb/linux/info.txt |
||
35 | https://web.archive.org/web/20080208063930/http://www.holtmann.org/linux/bluetooth/isdn.html (german only) |
||
36 | |||
37 | CMTP (CAPI Message Transport Protocol) is a transport layer for CAPI messages. |
||
38 | https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/tools/parser/cmtp.c |
||
39 | |||
40 | ciptool (used to set up, maintain, and inspect the CIP configuration) |
||
41 | https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/tools/ciptool.c |
||
42 | https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/tools/ciptool.rst |
||
43 | |||
44 | h2. BlueFRITZ! AP-ISDN |
||
45 | |||
46 | Small and lightweight (35g) ISDN Access Point. |
||
47 | 16-digit hardcoded Bluetooth PIN is printed on the back of the case. |
||
48 | |||
49 | 2 | laforge | h3. Hardware |
50 | |||
51 | 4 | laforge | The hardware is built around the following major functional blocks: |
52 | 2 | laforge | |
53 | |_.Chip|_.Function (expected)| |
||
54 | |AVM ARM VP22437-ZYA0YKN.Z1 03 tS0445 - AVM-UBIK 1.0|ARM based SoC| |
||
55 | |Infineon PSB3186F V1.1 0446|ISDN S/T Interface| |
||
56 | |AVM BLUEJOB.PV18 H2465-018 2CEA18146.1 0446 AA TWN|Bluetooth Interface| |
||
57 | 4 | laforge | |MX E044211 29LV800BTXBC-70 2K474300 TAIWAN|8Mbit NOR Flash Memory| |
58 | |Samsung K4S641632H-TC75|64Mbit SDRAM Memory| |
||
59 | 2 | laforge | |III S1W|RF LNA/PA?| |
60 | 3 | laforge | |Altera EPM3032A TC44-10|Glue Logic| |
61 | 2 | laforge | |
62 | 1 | roox | h3. Configuration example |
63 | |||
64 | * Kernel 4.12.14 |
||
65 | * BlueFRITZ! AP-ISDN (PIN: 1500750033515501) |
||
66 | * BlueFRITZ! USB 2.0 |
||
67 | |||
68 | lsusb |
||
69 | <pre> |
||
70 | Bus 001 Device 002: ID 057c:3800 AVM GmbH BlueFRITZ! Bluetooth Stick |
||
71 | </pre> |
||
72 | |||
73 | hciconfig/hcitool |
||
74 | <pre> |
||
75 | # hciconfig -a |
||
76 | hci0: Type: Primary Bus: USB |
||
77 | BD Address: 00:04:0E:8B:7A:95 ACL MTU: 120:20 SCO MTU: 24:5 |
||
78 | DOWN· |
||
79 | RX bytes:5101 acl:32 sco:0 events:172 errors:0 |
||
80 | TX bytes:1602 acl:32 sco:0 commands:90 errors:0 |
||
81 | Features: 0xff 0xff 0x05 0x00 0x00 0x00 0x00 0x00 |
||
82 | Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3· |
||
83 | Link policy:· |
||
84 | Link mode: SLAVE ACCEPT |
||
85 | |||
86 | # hcitool dev |
||
87 | Devices: |
||
88 | hci0 00:04:0E:8B:7A:95 |
||
89 | |||
90 | # hcitool -i hci0 scan |
||
91 | Scanning ... |
||
92 | 00:04:0E:8B:7E:8D Bluetooth ISDN Access Point |
||
93 | </pre> |
||
94 | |||
95 | |||
96 | bluetoothctl (pairing) |
||
97 | <pre> |
||
98 | [NEW] Controller 00:04:0E:8B:7A:95 leap151 [default] |
||
99 | Agent registered |
||
100 | [bluetooth]# scan on |
||
101 | Discovery started |
||
102 | [CHG] Controller 00:04:0E:8B:7A:95 Discovering: yes |
||
103 | [NEW] Device 00:04:0E:8B:7E:8D 00-04-0E-8B-7E-8D |
||
104 | [CHG] Device 00:04:0E:8B:7E:8D LegacyPairing: no |
||
105 | [CHG] Device 00:04:0E:8B:7E:8D Name: Bluetooth ISDN Access Point |
||
106 | [CHG] Device 00:04:0E:8B:7E:8D Alias: Bluetooth ISDN Access Point |
||
107 | [CHG] Device 00:04:0E:8B:7E:8D LegacyPairing: yes |
||
108 | ... |
||
109 | [bluetooth]# trust 00:04:0E:8B:7E:8D |
||
110 | [CHG] Device 00:04:0E:8B:7E:8D Trusted: yes |
||
111 | Changing 00:04:0E:8B:7E:8D trust succeeded |
||
112 | ... |
||
113 | [bluetooth]# pair 00:04:0E:8B:7E:8D |
||
114 | Attempting to pair with 00:04:0E:8B:7E:8D |
||
115 | [CHG] Device 00:04:0E:8B:7E:8D Connected: yes |
||
116 | Request PIN code |
||
117 | [Blue1m[agent] Enter PIN code: 1500750033515501 |
||
118 | [CHG] Device 00:04:0E:8B:7E:8D UUIDs: 00001101-0000-1000-8000-00805f9b34fb |
||
119 | [CHG] Device 00:04:0E:8B:7E:8D UUIDs: 00001103-0000-1000-8000-00805f9b34fb |
||
120 | [CHG] Device 00:04:0E:8B:7E:8D UUIDs: 00001109-0000-1000-8000-00805f9b34fb |
||
121 | [CHG] Device 00:04:0E:8B:7E:8D UUIDs: 00001116-0000-1000-8000-00805f9b34fb |
||
122 | [CHG] Device 00:04:0E:8B:7E:8D UUIDs: 00001128-0000-1000-8000-00805f9b34fb |
||
123 | [CHG] Device 00:04:0E:8B:7E:8D ServicesResolved: yes |
||
124 | [CHG] Device 00:04:0E:8B:7E:8D Paired: yes |
||
125 | Pairing successful |
||
126 | [CHG] Device 00:04:0E:8B:7E:8D ServicesResolved: no |
||
127 | [CHG] Device 00:04:0E:8B:7E:8D Connected: no |
||
128 | ... |
||
129 | [bluetooth]# connect 00:04:0E:8B:7E:8D |
||
130 | Attempting to connect to 00:04:0E:8B:7E:8D |
||
131 | [CHG] Device 00:04:0E:8B:7E:8D Connected: yes |
||
132 | [CHG] Device 00:04:0E:8B:7E:8D ServicesResolved: yes |
||
133 | [Bluetooth ISDN Access Point]# |
||
134 | ... |
||
135 | [Bluetooth ISDN Access Point]# info 00:04:0E:8B:7E:8D |
||
136 | Device 00:04:0E:8B:7E:8D (public) |
||
137 | Name: Bluetooth ISDN Access Point |
||
138 | Alias: Bluetooth ISDN Access Point |
||
139 | Class: 0x00420214 |
||
140 | Icon: phone |
||
141 | Paired: yes |
||
142 | Trusted: yes |
||
143 | Blocked: no |
||
144 | Connected: yes |
||
145 | LegacyPairing: yes |
||
146 | UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb) |
||
147 | UUID: Dialup Networking (00001103-0000-1000-8000-00805f9b34fb) |
||
148 | UUID: Cordless Telephony (00001109-0000-1000-8000-00805f9b34fb) |
||
149 | UUID: NAP (00001116-0000-1000-8000-00805f9b34fb) |
||
150 | UUID: Common ISDN Access (00001128-0000-1000-8000-00805f9b34fb) |
||
151 | RSSI: -20 |
||
152 | </pre> |
||
153 | |||
154 | |||
155 | ciptool |
||
156 | <pre> |
||
157 | # ciptool search |
||
158 | Searching ... |
||
159 | Checking service for 00:04:0E:8B:7E:8D |
||
160 | Connecting to device 00:04:0E:8B:7E:8D |
||
161 | Local device is not accepting role switch |
||
162 | |||
163 | # ciptool connect |
||
164 | # ciptool show |
||
165 | 1 00:04:0E:8B:7E:8D connected |
||
166 | </pre> |
||
167 | |||
168 | capiinfo |
||
169 | <pre> |
||
170 | # capiinfo |
||
171 | capi20.c: 164 CapiDebug():[capi20_isinstalled]: standard loop - module: standard |
||
172 | capi20.c: 164 CapiDebug():[capi20_isinstalled]: capi_fd: 4 |
||
173 | Number of Controllers : 1 |
||
174 | Controller 1: |
||
175 | Manufacturer: AVM Berlin |
||
176 | CAPI Version: 2.0 |
||
177 | Manufacturer Version: 3.11-04 (49.20) |
||
178 | Serial Number: 0753293 |
||
179 | BChannels: 2 |
||
180 | Global Options: 0x00000031 |
||
181 | internal controller supported |
||
182 | Supplementary Services supported |
||
183 | channel allocation supported (leased lines) |
||
184 | B1 protocols support: 0xc000000f |
||
185 | 64 kbit/s with HDLC framing |
||
186 | 64 kbit/s bit-transparent operation |
||
187 | V.110 asynconous operation with start/stop byte framing |
||
188 | V.110 synconous operation with HDLC framing |
||
189 | B2 protocols support: 0x00000b0b |
||
190 | ISO 7776 (X.75 SLP) |
||
191 | Transparent |
||
192 | LAPD with Q.921 for D channel X.25 (SAPI 16) |
||
193 | ISO 7776 (X.75 SLP) with V.42bis compression |
||
194 | V.120 asyncronous mode |
||
195 | V.120 bit-transparent mode |
||
196 | B3 protocols support: 0x8000000f |
||
197 | Transparent |
||
198 | T.90NL, T.70NL, T.90 |
||
199 | ISO 8208 (X.25 DTE-DTE) |
||
200 | X.25 DCE |
||
201 | |||
202 | 0100 |
||
203 | 0200 |
||
204 | 31000000 |
||
205 | 0f0000c0 |
||
206 | 0b0b0000 |
||
207 | 0f000080 |
||
208 | 00000000 00000000 00000000 00000000 00000000 00000000 |
||
209 | 01000001 00020000 00000000 00000000 00000000 |
||
210 | |||
211 | Supplementary services support: 0x000003ff |
||
212 | Hold / Retrieve |
||
213 | Terminal Portability |
||
214 | ECT |
||
215 | 3PTY |
||
216 | Call Forwarding |
||
217 | Call Deflection |
||
218 | MCID |
||
219 | CCBS |
||
220 | </pre> |
||
221 | |||
222 | |||
223 | dmesg |
||
224 | <pre> |
||
225 | usb 1-1: New USB device found, idVendor=057c, idProduct=3800 |
||
226 | usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 |
||
227 | usb 1-1: Product: Bluetooth Device |
||
228 | usb 1-1: Manufacturer: Bluetooth Device |
||
229 | usb 1-1: SerialNumber: 957A8B0E0400 |
||
230 | ... |
||
231 | Bluetooth: Core ver 2.22 |
||
232 | NET: Registered protocol family 31 |
||
233 | Bluetooth: HCI device and connection manager initialized |
||
234 | Bluetooth: HCI socket layer initialized |
||
235 | Bluetooth: L2CAP socket layer initialized |
||
236 | Bluetooth: SCO socket layer initialized |
||
237 | usbcore: registered new interface driver btusb |
||
238 | ... |
||
239 | ... // paired bluetooth |
||
240 | ... |
||
241 | Bluetooth: CMTP (CAPI Emulation) ver 1.0 |
||
242 | Bluetooth: CMTP socket layer initialized |
||
243 | Bluetooth: BNEP (Ethernet Emulation) ver 1.3 |
||
244 | Bluetooth: BNEP filters: protocol multicast |
||
245 | Bluetooth: BNEP socket layer initialized |
||
246 | ... |
||
247 | ... // ciptool connect |
||
248 | ... |
||
249 | Bluetooth: Found 1 CAPI controller(s) on device 00:04:0e:8b:7e:8d |
||
250 | kcapi: controller [001]: 00:04:0e:8b:7e:8d attached |
||
251 | kcapi: controller [001] "00:04:0e:8b:7e:8d" ready. |
||
252 | ... |
||
253 | ... // CAPI initialized (capiinit) |
||
254 | ... |
||
255 | CAPI 2.0 started up with major 68 (middleware) |
||
256 | ... |
||
257 | ... // ciptool release |
||
258 | ... |
||
259 | kcapi: controller [001]: 00:04:0e:8b:7e:8d unregistered |
||
260 | </pre> |