- linux-dect - lists.osmocom.org

libnl compile error: "usr/bin/ld: cannot find -lnl-route"
by komkon555 26 Jun '17

26 Jun '17

Hallo. So I experienced an issue with libnl-compilation. The error is: make[2]: Entering directory `/usr/src/libnl/src' CCLD nl-pktloc-lookup /usr/bin/ld: cannot find -lnl-route collect2: error: ld returned 1 exit status make[2]: *** [nl-pktloc-lookup] Error 1 make[2]: Leaving directory `/usr/src/libnl/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/libnl/src' make: *** [all-recursive] Error 1 The compilation is tried on Debian Wheezy. The osmocom-linux-kernel/headers (kernel:git://dect.osmocom.org/git/linux-2.6.git) are successfully compiled and installed as in manual. I have tried also all native libnl debian-packages with source. Unfortunately they are not suitable for libdect. Please help. Best regards.

1 1

Dect Kernel Stack for Kernel 4.9
by Newsy Paper 17 Mar '17

17 Mar '17

Hi! I tried to port the kernel stack provided by Patrick McHardy to Kernel 4.9 It is compiling for me and the module also loads, however I'm unable to getthe netlink device working. So there is still no way to get the dectmon working again using a modern linux kernel :( Anyone able to help? I put my patch here: https://paste2.org/F9CImF8x kind regards Newspaperman

1 0

osmocom dect PP-mode
by Pavel Nakonechny 09 May '16

09 May '16

Hello, I am currently playing with Osmocom DECT software stack using COM-ON-AIR PCI card. What I am trying to achieve is to configure test PC as portable part and connect it to DECT base station. I have cloned and successfully compiled the following repos: git://dect.osmocom.org/linux-2.6.git git://dect.osmocom.org/libnl.git git://dect.osmocom.org/libdect.git Following instructions on dect.osmocom.org/wiki/Configuration page I configured PP. However, the example app dect-llme-scan was able to work only after uncommenting line: //nl_dect_llme_mac_info_set_pari(lmsg, pari); With the line above uncommented, dect-llme-scan returns the list of available base stations. So I assume, that hardware and most part of software works. Then I tried to use example pp-access-rights to connect to the test base station. This app fails immediately after launch for the same reason as dect-llme-scan. Thus, I have added nl_dect_llme_mac_info_set_pari(lmsg, pari); with empty PARI to dect_netlink_mac_me_info_req(struct dect_handle *dh) function. With this modification, the example moves farther, but fails anyway with "No such file or directory" message on this line: if (connect(ddl->dfd->fd, (struct sockaddr *)&ddl->dlei, sizeof(ddl->dlei)) < 0 && errno != EAGAIN) goto err3; in file lce.c All in all. May I at first ask about how to properly configure portable part? Here I have to specify EMC and FPN of the base station? # dect-cluster-add --name cluster0 --mode fp --emc 0x1182 --fpn 0x0fac3 # dect-cell-add --name cell0 --cluster cluster0 # dect-transceiver-bind --transceiver trx0 --cell cell0 What should I use here as IPUI? Some random identifier of my PP? # pp-access-rights --cluster cluster0 --pin 0000 --ipui 0x11830fac4 And, in general, are the sources in repos I listed previously were tested in PP mode or they are not fully functional yet? Thanks in advance. :) -- WBR, Pavel

1 1

OsmocomDECT for Fritzbox router
by Thomas Schmiedl 13 Mar '15

13 Mar '15

Hello, would it be possible to use OsmocomDECT with the Fritzbox router? I try to extend my router Fritzbox 7312 with an application called "Callmonitor" (http://freetz.org/wiki/packages/callmonitor; sorry german only), which has a reverse-search (via internet-telephone-books) to query the name of the caller (query by caller's phone number). I want to transfer this name to my DECT cordless phone. Unfortunately, the manufacturer of the router, AVM in Berlin, does not provide any information about DECT (closed-source). Or could someone help me tracing the software dect_manager (http://www.wehavemorefun.de/fritzbox/Dect_manager) or libdect (http://www.wehavemorefun.de/fritzbox/Libdect.so), because I am not a developer. Best regards, Thomas

1 0

OsmocomDECT for Fritzbox router
by Thomas Schmiedl 11 Mar '15

11 Mar '15

Hello, would it be possible to use OsmocomDECT with the Fritzbox router? I try to extend my router Fritzbox 7312 with an application called "Callmonitor" (http://freetz.org/wiki/packages/callmonitor; sorry german only), which has a reverse-search (via internet-telephone-books) to query the name of the caller (query by caller's phone number). I want to transfer this name to my DECT cordless phone. Unfortunately, the manufacturer of the router, AVM in Berlin, does not provide any information about DECT (closed-source). Thanks for the reply. Best regards, Thomas

1 0

Announcing OsmoDevCon 2015
by Harald Welte 13 Feb '15

13 Feb '15

Dear Osmocom.org project members, I'm happy to be able to announce the annual incarnation of OsmoDevCon. The Date is set for March 27 through 30. Venue: As usual, IN-Berlin e.V. in Berlin, Germany. Further details can be obtained from http://openbsc.osmocom.org/trac/wiki/OsmoDevCon2015 Attendance, as usual, is restricted to people with an active history in the Project by contributions in terms of code, patches, discussions, documentation or in other form. = Registration = If you have wiki access, please add yourself to the #Requested section. Alternatively, you can send me private e-mail about it. After review, your (nick)name will be listed in the #Confirmed section. Looking forward to meeting all of you again soon! -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

DECT MitM Attack
by Tobias XY 09 Jan '15

09 Jan '15

Hello, how can i start a "Man in the middle attack", to decrypt encrypted phone calls of the DECT standard? I read something about it on the internet. Here, however, I lack the software and I do not know what hardware do I need to do so. The normal DECT Sniff attack I have already stated. However, one can hereby decode only unencrypted packets. Anyone have an idea? Greetings. Tobi

1 0

error trying to make module under kernel 3.11.7 / gcc-4.7.3
by Atom2 10 Mar '14

10 Mar '14

Hi List, I am trying to compile the kernel driver module for 3.11.7 (gentoo hardened sources) using gcc-4.7.3. The card I am planning to use is a Dosch&Amnand Com-On-Air PCI. So far I have been able to change the patch file provided for the 3.0 kernels (http://dect.osmocom.org/attachment/wiki/Patches/linux-3.0.diff) to apply to my kernel sources. There were a few changes required, but nothing too drastic. However, when I start the 'make' for the kernel the compiler issues an error as follows: [... snip ...] CC kernel/module.o In file included from include/net/dect/mac_ccf.h:12:0, from include/net/dect/dect.h:148, from drivers/dect/coa/sc1442x.c:19: include/net/dect/mac.h:622:8: error: duplicate member ‘lbn’ include/net/dect/mac.h:624:9: error: duplicate member ‘pmid’ CC arch/x86/pci/bus_numa.o CC fs/ext4/super.o CC arch/x86/pci/amd_bus.o make[3]: *** [drivers/dect/coa/sc1442x.o] Error 1 make[2]: *** [drivers/dect/coa] Error 2 make[1]: *** [drivers/dect] Error 2 make: *** [drivers] Error 2 make: *** Waiting for unfinished jobs.... CC arch/x86/power/cpu.o [... snip ...] Given that the related code within include/net/dect/mac.h looks as follows (comments added by me), this seems to be a valid complaint of the compiler: [... snip ...] struct dect_cctrl { enum dect_cctrl_cmds cmd; union { struct { u16 fmid; u32 pmid; /* <=== pmid */ }; struct { u8 lbn; /* <=== lbn */ u8 ecn; u8 type; u8 service; u8 slot; bool cf; u8 a_mod; u8 bz_mod; u8 bz_ext_mod; u8 acr; }; struct { u8 lbn; /* <=== lbn */ u8 reason; u32 pmid; /* <=== pmid */ }; }; }; [... snip ...] lbn and pmid are indeed defined twice. A research on the internet for similar errors suggested that those constructs were tolerated (I don't know how) by gcc versions prior to 4.5, but are no longer valid. Is there any patch available or a suggestion on what I need to change in order to successfully compile the driver. Many thanks and regards, KK

1 0

dect.osmocom.org back up
by Patrick McHardy 08 Mar '14

08 Mar '14

Just FYI: thanks to Holger dect.osmocom.org is back up again (and hopefully will stay up). I might merge the code with the 3.13 kernel during the next days.

1 0

[RFC] [ADMIN] Making lists subscriber-only?
by Harald Welte 12 Jan '14

12 Jan '14

Dear all, so far the osmocom.org mailing lists have always been in a 'non-members are manually moderated' mode. This has created a lot of work for manual list moderation, where a lot of the messages caught are simply spam, and only the occasional valid message is being received. I'd like to thank the list moderators for taking care of this. However, in more recent discussions, we were considering to move the lists to a completely closed mode, i.e. postings would automatically be rejected from non-members. The automatic response would contain a description of how to subscribe in 'nomail' mode, i.e. to subscribe in a way to be able to post to the list, while still not receiving any incoming traffic. The latter should be fine for occasional posters who don't want the bulk e-mail that goes with a full/regular subscription. Please provide feedback in case you disagree with that change. Unless there is major opposition, we will likely transition to the 'closed' mode within one month. Thanks, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

Osmo/DECT unreachable
by mario phoenix 15 Oct '13

15 Oct '13

http://dect.osmocom.org/ Any clue ? Mario

3 2

Buy COM-ON-AIR PCMCIA Type 2
by Blago Blagoev 10 Sep '13

10 Sep '13

Buy COM-ON-AIR PCMCIA Type 2. Suggestions are welcome to e-mail.

1 0

Compile of libdect fails
by Stephan Meier 10 Jul '13

10 Jul '13

Hi, sorry to be a bit of a nag, but libdect fails, too. The configure script fails while trying to find libnl. The fix is to replace "nl" with "nl-3" in configure.ac:36 (the first param of the AC_CHECK_LIB macro). Cheers, Stephan

2 1

Compile of libnl failed
by Stephan Meier 03 Jul '13

03 Jul '13

Hi, after cloning libnl from git://dect.osmocom.org/git/libnl.git, I tried to compile it. It breaks while trying to compile the "nl-pktloc-lookup" binary. It seems to be caused by line 131 in src/Makefile.am (LDADD statement that overwrites the linker flags set before). Removing this line and thus using the "old" linker flags works. Is this the desired behavior or did anybody just forget to delete this line? Cheers, Stephan

4 12

New version of libnl
by C470IP 01 Jun '13

01 Jun '13

Hello! Has anyone succeeded in compiling the latest version of libnl? After executing 'sh autogen.sh' it takes quite a while, then the following messages appear: Killed autom4te: /usr/bin/m4 failed with exit status: 137 aclocal: /usr/bin/autom4te failed with exit status: 137 autoreconf: aclocal failed with exit status: 137 Killed autom4te: /usr/bin/m4 failed with exit status: 137 aclocal: /usr/bin/autom4te failed with exit status: 137 autoreconf: aclocal failed with exit status: 137 (yes they are double). Am I doing something wrong? Or maybe there are some new installation instructions regarding the latest version of OsmocomDECT software? With best regards, C470IP. E-mail: c470ip(a)yandex.ru

1 0

Linux 3.8 merged but some wishes...
by Blago Blagoev 01 Apr '13

01 Apr '13

Hi! Good news http://dect.osmocom.org/trac/dect/blog/kaber-2013/03/31/linux_38_merged But: Asterisk wideband support is still unfinished. Asterisk do not work in PP-mode. How about working to bring to the state? It seems these problems are much more interesting and important. Anyone agree with me?

4 5

[ANNOUNCE] OsmoDevCon 2013-04-04 till 2013-04-07, Berlin
by Harald Welte 26 Feb '13

26 Feb '13

Dear fellow Osmcoom developers, it is my pleasure to finally announce the date + venue of OsmoDevCon 2013: Date: April 04 through April 07, 2013 Place: IN-Berlin, Lehrter Str. 53, Berlin Like last year, this is an event for developers of the various Osmocom proejects. Reservation and confirmation of reservation is required. The event is free of charge. The Room is made available by IN-Berlin e.V., an Internet related non-profit organization. Lunch catering will be sponsored (so far by sysmocom GmbH, but if any other sponsors come up, we are happy to share the cost). So all you have to cover is your own travel + accomodation costs, as well as breakfast and dinner. If you are an active developer and cannot afford travel/accomodation, please let me know and I'll see if we can do something about it. If you would like to attend, please send a message to laforge(a)gnumonks.org applying for registration of the event. The registration deadline is March 5, i.e. one week from now. There is no detailed schedule of talks yet. I will start a separate discussion suggesting / collecting topics in the next couple of days. More information is (and will be made) available at http://openbsc.osmocom.org/trac/wiki/OsmoDevCon2013 Further discussion regarding the event should be directed at the osmocom-event-orga(a)lists.osmocom.org mailing list, to avoid cross-posting over the various project-specific lists. Best regards and happy hacking, Harald -- - Harald Welte <laforge(a)gnumonks.org> http://laforge.gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6)

1 0

Unable to load module chan_dect.so in Asterisk
by Blago Blagoev 01 Nov '12

01 Nov '12

Hi! I do all instructions of http://dect.osmocom.org/trac/dect/wiki/Build%20instructions#kernel with last versions kernel, libnl, libdect, dectmon. When finish all configurations I got a dect-stack of hard-working But chan_dect.so module asterisk would not load correctly. Here http://dect.osmocom.org/trac/dect/blog/kaber-2011/11/04/linux_31_merged I read that the module is still not should work for P640j (Wideband) So I went back to version kernel 2.6.39-DECT and older versions of the libnl and libdect. As far as I understand, these versions do not support P640j (Wideband) and an asterisk to them should work fine? I have successfully created DECT cluster, cell, transceiver on the old-version soft: root@debian:~/dect/old/work# ./dect-cluster-list 1: DECT Cluster cluster0: Mode: FP PARI: class A (residential) EMC: 045d FPN: 00d1c root@debian:~/dect/old/work# ./dect-cell-list 1: DECT Cell cell0@cluster0: root@debian:~/dect/old/work# ./dect-transceiver-list DECT Transceiver trx0@cell0: Type: sc1442x RF-band: 00008 Events: busy: 0 late: 0 root@debian:~/dect/old/work# When I start the daemon Asterix in debug mode i can see the next: root@debian:/var/log/asterisk# asterisk -vvvc . .. . == Registered channel type 'DECT' (Digital Enhanced Cordless Telecommunications (DECT)) == Registered application 'DectUserAuth' == Parsing '/etc/asterisk/dect.conf': == Found -- Registered extension context 'dect_register'; registrar: DECT dect_netlink_init: Protocol mismatch [Nov 1 13:55:45] ERROR[1734]: chan_dect.c:2336 dect_load_module: Unable to initialize DECT handle == Unregistered channel type 'DECT' Who can help?

1 0

Unable to load module chan_dect in Asterisk
by Blago Blagoev 01 Nov '12

01 Nov '12

Hi! I do all instructions of http://dect.osmocom.org/trac/dect/wiki/Build%20instructions#kernel with last versions kernel, libnl, libdect, dectmon. When finish all configurations I got a dect-stack of hard-working But chan_dect.so module asterisk would not load correctly. Here http://dect.osmocom.org/trac/dect/blog/kaber-2011/11/04/linux_31_merged I read that the module is still not should work for P640j (Wideband) So I went back to version kernel 2.6.39-DECT and older versions of the libnl and libdect. As far as I understand, these versions do not support P640j (Wideband) and an asterisk to them should work fine? I have successfully created DECT cluster, cell, transceiver on the old-version soft: root@debian:~/dect/old/work# ./dect-cluster-list 1: DECT Cluster cluster0: Mode: FP PARI: class A (residential) EMC: 045d FPN: 00d1c root@debian:~/dect/old/work# ./dect-cell-list 1: DECT Cell cell0@cluster0: root@debian:~/dect/old/work# ./dect-transceiver-list DECT Transceiver trx0@cell0: Type: sc1442x RF-band: 00008 Events: busy: 0 late: 0 root@debian:~/dect/old/work# When I start the daemon Asterix in debug mode i can see the next: root@debian:/var/log/asterisk# asterisk -vvvc . .. . == Registered channel type 'DECT' (Digital Enhanced Cordless Telecommunications (DECT)) == Registered application 'DectUserAuth' == Parsing '/etc/asterisk/dect.conf': == Found -- Registered extension context 'dect_register'; registrar: DECT dect_netlink_init: Protocol mismatch [Nov 1 13:55:45] ERROR[1734]: chan_dect.c:2336 dect_load_module: Unable to initialize DECT handle == Unregistered channel type 'DECT' Who can help?

1 0

Re: DECT + GNU Radio?
by Patrick McHardy 31 Oct '12

31 Oct '12

Patrick McHardy <kaber(a)trash.net> schrieb: > > >Joel Mayer <joelm_armillary(a)msn.com> schrieb: > >>Dear Mister Patrick McHardy- >> >>Here is a link to the EZTV 668 dongle. I have an EZTV 666 dongle >>working in windows >>(Ubuntu is in the near future on my lap top). I cannot vouch for the >>668 dongle in >>any personal way, but I have read comments in the various forums >>testifying to >>the utility of the 668. >> >>http://www.nooelec.com/store/software-defined-radio/eztv668-dvb-t-usb-set-f…<http://www.nooelec.com/store/software-defined-radio/eztv668-dvb-t-usb-set-f…> >> >>The install script I mentioned beneath these lines only works in >>Windows. To install >>the GNU radio software in Ubuntu you need to use a script written by a >>certain Mister >>Marcus Leech (he is a radio astronomer). See: >> >>http://gnuradio.org/redmine/projects/gnuradio/wiki/InstallingGR<http://gnuradio.org/redmine/projects/gnuradio/wiki/InstallingGR> >> >>Make certain you use Mister Leech's script! The GNU radio people have >>pulled >>their packages out of the repositories. The only way to get a fresh >new >>GNU >>radio is from the GNU radio people! >> >>My suggestion is, you install the SDR# radio in windows using the >>script I mentioned >>at the bottom of this note. Then install the SDR# scanner radio built >>by k5dev >>(below). Here is a link to a useful quick start guide for windows: >>http://www.atouk.com/SDRSharpQuickStart.html<http://www.atouk.com/SDRSharpQuickStart.html> >> >>To install the SDR# radio in Ubuntu on top of your GNU radio go here: >>http://rtlsdr.org/<http://rtlsdr.org/> Scroll down to the bottom of >the >>first page and visit: >>http://rtlsdr.org/softwarelinux<http://rtlsdr.org/softwarelinux> >> >>I'm going to journey to my pay pal account and try to send forty >>dollars to you at "kaber" at "trash dot net" without the quotes. >> >>Have A Nice Day! > >Thanks a lot, didn't expect that :-) I'll order one of these devices >and will give it a shot. Dropped CC, sorry.

3 3

Trying to fill some gaps in documentation
by C470IP 30 Oct '12

30 Oct '12

Hello! Recently I've managed to install all Osmocom-DECT components (except Asterisk, which will be installed later). Everything seem to be working fine, at least I could try examples from the website without any error. Many thanks to the authors for this extraordinary job. Now I want to go further and to configure some useful system using these tools, but I feel some gaps in documentation/description which need to be clarified. I would be very thankful to anybody who would bother to answer the following questions: 1) When a DECT cluster is configured in FP mode (like first example here: http://dect.osmocom.org/trac/dect/wiki/Configuration ), how can we use it to attach handsets? Or for what this mode is for? Also I've found that in this mode beacon frames are sent very seldom and with minimal power, is this normal? 2) Where one can find the list of keywords for dectmon command line? Or if not keywords, what is dectmon awaiting after its > character? 3) In which program can we open raw dump files created by dectmon? Is it possible to dump pcap from dectmon? 4) How can we extract audio from the monitored stream? For example I created a cluster in PP mode locked to my unencrypted phone, then created a cell and bound the transceiver, then ran dectmon with '-a yes' keys. No success at all. 5) Is it possible to extract audio from raw dumps of dectmon with some ready-to use software? 6) BTW does dectmon support seamless channel hopping to make smooth audio streams without noise interrupts like those happening in dect_cli software? Would be grateful for any response. With best regards, C470IP. E-mail: c470ip(a)yandex.ru

2 1

Unable to load module chan_dect in Asterisk
by Blago Blagoev 22 Oct '12

22 Oct '12

*Hi!** Asterisk got a problem with load the chan_dect module.** in my /var/log/asterisk/messages i see: [Oct 22 17:17:52] WARNING[1049] loader.c: Error loading module 'chan_dect.so': /usr/lib/asterisk/modules/chan_dect.so: undefined symbol: dect_mm_endpoint_get [Oct 22 17:17:52] WARNING[1049] loader.c: Module 'chan_dect.so' could not be loaded. * Who can recommend? **

1 0

Cannot make libnl
by C470IP 17 Oct '12

17 Oct '12

Hello! While compiling libnl I get the following errors: route/cls/ematch_grammar.c:773:5: error: unknown type name 'YYSTYPE' route/cls/ematch_grammar.c:816:1: error: unknown type name 'YYSTYPE' route/cls/ematch_grammar.c:818:23: error: unknown type name 'YYSTYPE' route/cls/ematch_grammar.c:931:17: error: unknown type name 'YYSTYPE' route/cls/ematch_grammar.c:954:1: error: unknown type name 'YYSTYPE' route/cls/ematch_grammar.c:2433:1: error: unknown type name 'YYSTYPE' route/cls/ematch_grammar.c:2439:23: error: unknown type name 'YYSTYPE' route/cls/ematch_grammar.c:1766:26: warning: 'yy_get_previous_state' defined but not used [-Wunused-function] route/cls/ematch_grammar.c:1799:26: warning: 'yy_try_NUL_trans' defined but not used [-Wunused-function] route/cls/ematch_grammar.c:1631:12: warning: 'yy_get_next_buffer' defined but not used [-Wunused-function] make[2]: *** [route/cls/ematch_grammar.lo] Error 1 make[2]: Exiting `/libnl/lib' make[1]: *** [all] Error 2 make[1]: Exiting `/libnl/lib' make: *** [all-recursive] Error 1 I've tried bison 2.2, 2.3 and 2.6.2 with no success. Byacc and flex are also installed. Is it possible to fix these errors somehow? Unfortunately my knowledge of source syntax is not sufficient. With best regards, C470IP.

1 0

How to use the audio-option in dektmon?
by Blago Blagoev 28 Sep '12

28 Sep '12

Hi! Computer with dektmon must have a sound card and installed drivers for it? When i run dectmon with option "audio" and loke to the FP, (which is a conversation) I need to hear the sound on the computer on-line? Is it possible to record the sound in a file?

1 0

Anyone using dect in production?
by henrik hansen 23 Sep '12

23 Sep '12

Hey folks, Is anyone out there who is using xom-on-air cards in productional environment? Von meinem iPhone gesendet

2 1

DECT + GNU Radio?
by Joel Mayer 23 Sep '12

23 Sep '12

Dear Fans of DECT- What about the GNU Radio Project? Is anyone working on a version of DECT as an element of, say the SDR# radio? How about the SDR# scanner radio? (1) http://sdrsharp.com/<http://sdrsharp.com/> (2) http://www.k5dev.com/<http://www.k5dev.com/> If you want to try this flavor of radio all you need is a suitable USB Dongle. For easy install with a script use: http://rtlsdr.org/softwarewindows<http://rtlsdr.org/softwarewindows> (The Automated method mentioned at the top of the page, specifically sdr-install.zip) Have A Nice Day! ----- Original Message ----- From: linux-dect-request(a)lists.osmocom.org<mailto:linux-dect-request@lists.osmocom.org> To: linux-dect(a)lists.osmocom.org<mailto:linux-dect@lists.osmocom.org> Sent: Friday, September 21, 2012 5:00 AM Subject: linux-dect Digest, Vol 40, Issue 1 Send linux-dect mailing list submissions to linux-dect(a)lists.osmocom.org<mailto:linux-dect@lists.osmocom.org> To subscribe or unsubscribe via the World Wide Web, visit https://lists.osmocom.org/mailman/listinfo/linux-dect<https://lists.osmocom.org/mailman/listinfo/linux-dect> or, via email, send a message with subject or body 'help' to linux-dect-request(a)lists.osmocom.org<mailto:linux-dect-request@lists.osmocom.org> You can reach the person managing the list at linux-dect-owner(a)lists.osmocom.org<mailto:linux-dect-owner@lists.osmocom.org> When replying, please edit your Subject line so it is more specific than "Re: Contents of linux-dect digest..."

2 1

Problems building libdect
by Blago Blagoev 21 Sep '12

21 Sep '12

Hi I have Problem: When I try to Build libdect: root@debian:~/dect/libdect# ~~~~~~~~~~ bash: ~~~~~~~~~~: command not found root@debian:~/dect/libdect# ./configure checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for a thread-safe mkdir -p... /bin/mkdir -p checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for a sed that does not truncate output... /bin/sed configure: Documentation build disabled checking for nl_socket_alloc in -lnl... yes checking for nl_dect_cluster_alloc in -lnl-dect... yes checking for event_init in -lev... yes checking for bfd_init in -lbfd... yes checking how to run the C preprocessor... gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking whether to enable assertions... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking fcntl.h usability... yes checking fcntl.h presence... yes checking for fcntl.h... yes checking for inttypes.h... (cached) yes checking limits.h usability... yes checking limits.h presence... yes checking for limits.h... yes checking malloc.h usability... yes checking malloc.h presence... yes checking for malloc.h... yes checking stddef.h usability... yes checking stddef.h presence... yes checking for stddef.h... yes checking for stdint.h... (cached) yes checking for stdlib.h... (cached) yes checking for string.h... (cached) yes checking for unistd.h... (cached) yes checking sys/socket.h usability... yes checking sys/socket.h presence... yes checking for sys/socket.h... yes checking for linux/dect.h... yes checking for linux/dect_netlink.h... yes checking event.h usability... yes checking event.h presence... yes checking for event.h... yes checking bfd.h usability... yes checking bfd.h presence... yes checking for bfd.h... yes checking checking whether event.h is compatible with libev... configure: error: incompatible event.h header for libev root@debian:~/dect/libdect#

2 3

"incompatible event.h header" message when configure libdect
by Blago Blagoev 04 Sep '12

04 Sep '12

Good day! When i run the configure script from libdect, i obtain the following. error: configure: error: incompatible event.h header for libev installed: libev 4.11-1 libevent 2.0.20-1 on last version ArchLinux Also tested library libevent 2.0.19 and libevent 2.0.10 and OpenSUSE 12.1 But the error still remains :( Who can recommend?

1 0

US DECT 6.0
by Frédéric LECAILLE 16 Aug '12

16 Aug '12

Hello Patrick, I had a look at the net/dect/mac_csf.c file source code. dect_bc_si_cycle_complete() often returns false with "incomplete: SSI" kernel logs: Aug 15 15:33:25 amanda kernel: [18609.133852] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:25 amanda kernel: [18609.143816] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:25 amanda kernel: [18609.153819] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:25 amanda kernel: [18609.163822] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:25 amanda kernel: [18609.173820] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:25 amanda kernel: [18609.183821] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.193820] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.203820] page: RFPI: d7ce8 bearer description: bt: 50000000 sn: 2 sp: 0 cn: 23 Aug 15 15:33:26 amanda kernel: [18609.213817] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.233819] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.243822] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.253821] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.263822] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.273818] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.283820] extended fixed part capabilities: fpc: 01000 hlc: 000000 Aug 15 15:33:26 amanda kernel: [18609.283826] incomplete: SSI Aug 15 15:33:26 amanda kernel: [18609.293831] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.303818] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.323822] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.333823] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.343819] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.353817] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.363819] page: RFPI: d7ce8 blind full slots: 8aa Aug 15 15:33:26 amanda kernel: [18609.373820] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.383816] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.393842] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.403823] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.413822] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.433816] identities information: e: 0 class: 0 emc: 2284 fpn: 1af9d rpn: 0 Aug 15 15:33:26 amanda kernel: [18609.443818] multi-frame number: 4282678 Aug 15 15:33:26 amanda kernel: [18609.443825] incomplete: SSI As far as I understand the code, in this case, the driver never locks, this would be the reason why dectmon never displays any message… The driver never logs any DBC message. This was the case before patching for US DECT. It seems there are EU DECT stations where I am testing this driver. [ 1112.263021] DBC slot 4 carrier 8: quality control: confirm quality [ 1112.267631] DBC slot 4 carrier 8: RSSI: selection: 60 now: 64 [ 1112.272821] DBC slot 4 carrier 8: quality control: wait [ 1112.272884] TX 17.00.04: FT T-MUX: N-channel [ 1112.272890] TX 17.00.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 2 [ 1112.283008] RX 17.00.16: trx0: Q1: 0 Q2: 0 A/B: 2a carrier: 2 A-CRC: 0 X-CRC: 0 Z-CRC: 0 TX 17.01.04: FT T-MUX: N-channel [ 1112.283017] TX 17.01.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 3 [ 1112.292781] TX 17.02.04: FT T-MUX: N-channel [ 1112.292786] TX 17.02.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 4 [ 1112.302781] TX 17.03.04: FT T-MUX: N-channel [ 1112.302785] TX 17.03.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 5 [ 1112.312813] TX 17.04.04: FT T-MUX: N-channel [ 1112.312817] TX 17.04.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 6 [ 1112.322783] TX 17.05.04: FT T-MUX: N-channel [ 1112.322789] TX 17.05.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 7 [ 1112.332781] TX 17.06.04: FT T-MUX: N-channel [ 1112.332785] TX 17.06.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 8 [ 1112.342780] TX 17.07.04: FT T-MUX: N-channel [ 1112.342784] TX 17.07.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 9 [ 1112.352813] TX 17.08.04: FT T-MUX: Q-channel [ 1112.352817] TX 17.08.04: trx0: Q1: 0 Q2: 0 A/B: 8e carrier: 8 PSCN: 0 [ 1112.362797] TX 17.09.04: FT T-MUX: N-channel [ 1112.362803] TX 17.09.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 1 [ 1112.372794] TX 17.10.04: FT T-MUX: N-channel[ 1112.372800] TX 17.10.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 2 [ 1112.382788] TX 17.11.04: FT T-MUX: N-channel [ 1112.382794] TX 17.11.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 3 [ 1112.392821] TX 17.12.04: FT T-MUX: N-channel [ 1112.392827] TX 17.12.04: trx0: Q1: 0 Q2: 0 A/B: 6e carrier: 8 PSCN: 4 [ 1112.395383] RX 17.11.20: trx0: Q1: 0 Q2: 0 A/B: a0 carrier: 3 A-CRC: 0 X-CRC: 0 Z-CRC: 0 On Aug 14, 2012, at 12:00 PM, linux-dect-request(a)lists.osmocom.org wrote: > Send linux-dect mailing list submissions to > linux-dect(a)lists.osmocom.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.osmocom.org/mailman/listinfo/linux-dect > or, via email, send a message with subject or body 'help' to > linux-dect-request(a)lists.osmocom.org > > You can reach the person managing the list at > linux-dect-owner(a)lists.osmocom.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of linux-dect digest..." > Today's Topics: > > 1. Re: linux-dect Digest, Vol 37, Issue 6 (Fr?d?ric LECAILLE) > 2. Re: linux-dect Digest, Vol 37, Issue 6 (henrik hansen) > > From: Frédéric LECAILLE <frednews78(a)free.fr> > Subject: Re: linux-dect Digest, Vol 37, Issue 6 > Date: August 13, 2012 9:53:23 PM GMT+02:00 > To: linux-dect(a)lists.osmocom.org > > > Hello Henrik, > > If you type this command in a terminal this will give you an idea about your issue: > > ldd /usr/lib/asterisk/modules/chan_dect.so > > > On Aug 11, 2012, at 12:00 PM, linux-dect-request(a)lists.osmocom.org wrote: > >> Send linux-dect mailing list submissions to >> linux-dect(a)lists.osmocom.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.osmocom.org/mailman/listinfo/linux-dect >> or, via email, send a message with subject or body 'help' to >> linux-dect-request(a)lists.osmocom.org >> >> You can reach the person managing the list at >> linux-dect-owner(a)lists.osmocom.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of linux-dect digest..." >> Today's Topics: >> >> 1. undefined symbol: dect_mm_endpoint_get (henrik hansen) >> 2. Re: undefined symbol: dect_mm_endpoint_get (Patrick McHardy) >> >> From: henrik hansen <hhansen06(a)googlemail.com> >> Subject: undefined symbol: dect_mm_endpoint_get >> Date: August 10, 2012 4:35:09 PM GMT+02:00 >> To: linux-dect(a)lists.osmocom.org >> >> >> Hey, >> my Asterisk got a problem with the chan_dect module. >> I build it like it's written here: http://dect.osmocom.org/trac/dect/wiki/Build%20instructions >> >> debian*CLI> module load chan_dect >> Unable to load module chan_dect >> Command 'module load chan_dect' failed. >> [Aug 10 14:23:41] WARNING[19284]: loader.c:449 load_dynamic_module: Error loading module 'chan_dect': /usr/lib/asterisk/modules/chan_dect.so: undefined symbol: dect_mm_endpoint_get >> [Aug 10 14:23:41] WARNING[19284]: loader.c:839 load_resource: Module 'chan_dect' could not be loaded. >> >> Could someone help me, getting this fixed? >> >> -- >> -- >> Mit freundlichen Grüßen >> Henrik Hansen >> >> >> >> >> From: Patrick McHardy <kaber(a)trash.net> >> Subject: Re: undefined symbol: dect_mm_endpoint_get >> Date: August 10, 2012 4:37:12 PM GMT+02:00 >> To: henrik hansen <hhansen06(a)googlemail.com> >> Cc: linux-dect(a)lists.osmocom.org >> >> >> On Fri, 10 Aug 2012, henrik hansen wrote: >> >>> Hey, >>> my Asterisk got a problem with the chan_dect module. >>> I build it like it's written here: >>> http://dect.osmocom.org/trac/dect/wiki/Build%20instructions >>> >>> debian*CLI> module load chan_dect >>> Unable to load module chan_dect >>> Command 'module load chan_dect' failed. >>> [Aug 10 14:23:41] WARNING[19284]: loader.c:449 load_dynamic_module: Error >>> loading module 'chan_dect': /usr/lib/asterisk/modules/chan_dect.so: >>> undefined symbol: dect_mm_endpoint_get >>> [Aug 10 14:23:41] WARNING[19284]: loader.c:839 load_resource: Module >>> 'chan_dect' could not be loaded. >>> >>> Could someone help me, getting this fixed? >> >> Its basically that chan_dect hasn't been converted to use the new API >> for wideband audio support yet. Just fixing this problem without actually adding wideband support should be relatively easy, I'll try to have a look during the weekend. >> >> >> >> >> _______________________________________________ >> linux-dect mailing list >> linux-dect(a)lists.osmocom.org >> https://lists.osmocom.org/mailman/listinfo/linux-dect > > > > > From: henrik hansen <hhansen06(a)googlemail.com> > Subject: Re: linux-dect Digest, Vol 37, Issue 6 > Date: August 13, 2012 10:50:52 PM GMT+02:00 > To: Frédéric LECAILLE <frednews78(a)free.fr> > Cc: linux-dect(a)lists.osmocom.org > > > Hey Frédéric, > for me it looks like there are no problems: > > root@debian:~# ldd /usr/lib/asterisk/modules/chan_dect.so > linux-gate.so.1 => (0xb77a6000) > libdect.so.0 => /usr/lib/libdect.so.0 (0xb7765000) > libpthread.so.0 => /lib/i686/cmov/libpthread.so.0 (0xb774c000) > libc.so.6 => /lib/i686/cmov/libc.so.6 (0xb7604000) > libdl.so.2 => /lib/i686/cmov/libdl.so.2 (0xb7600000) > libnl-dect.so.3 => /usr/local/lib/libnl-dect.so.3 (0xb75f5000) > libnl.so.3 => /usr/local/lib/libnl.so.3 (0xb75e1000) > /lib/ld-linux.so.2 (0xb77a7000) > libm.so.6 => /lib/i686/cmov/libm.so.6 (0xb75bb000) > > My System is a Debian 6.0 x86 > > > 2012/8/13 Frédéric LECAILLE <frednews78(a)free.fr> > Hello Henrik, > > If you type this command in a terminal this will give you an idea about your issue: > > ldd /usr/lib/asterisk/modules/chan_dect.so > > > On Aug 11, 2012, at 12:00 PM, linux-dect-request(a)lists.osmocom.org wrote: > >> Send linux-dect mailing list submissions to >> linux-dect(a)lists.osmocom.org >> >> To subscribe or unsubscribe via the World Wide Web, visit >> https://lists.osmocom.org/mailman/listinfo/linux-dect >> or, via email, send a message with subject or body 'help' to >> linux-dect-request(a)lists.osmocom.org >> >> You can reach the person managing the list at >> linux-dect-owner(a)lists.osmocom.org >> >> When replying, please edit your Subject line so it is more specific >> than "Re: Contents of linux-dect digest..." >> Today's Topics: >> >> 1. undefined symbol: dect_mm_endpoint_get (henrik hansen) >> 2. Re: undefined symbol: dect_mm_endpoint_get (Patrick McHardy) >> >> From: henrik hansen <hhansen06(a)googlemail.com> >> Subject: undefined symbol: dect_mm_endpoint_get >> Date: August 10, 2012 4:35:09 PM GMT+02:00 >> To: linux-dect(a)lists.osmocom.org >> >> >> Hey, >> my Asterisk got a problem with the chan_dect module. >> I build it like it's written here: http://dect.osmocom.org/trac/dect/wiki/Build%20instructions >> >> debian*CLI> module load chan_dect >> Unable to load module chan_dect >> Command 'module load chan_dect' failed. >> [Aug 10 14:23:41] WARNING[19284]: loader.c:449 load_dynamic_module: Error loading module 'chan_dect': /usr/lib/asterisk/modules/chan_dect.so: undefined symbol: dect_mm_endpoint_get >> [Aug 10 14:23:41] WARNING[19284]: loader.c:839 load_resource: Module 'chan_dect' could not be loaded. >> >> Could someone help me, getting this fixed? >> >> -- >> -- >> Mit freundlichen Grüßen >> Henrik Hansen >> >> >> >> >> From: Patrick McHardy <kaber(a)trash.net> >> Subject: Re: undefined symbol: dect_mm_endpoint_get >> Date: August 10, 2012 4:37:12 PM GMT+02:00 >> To: henrik hansen <hhansen06(a)googlemail.com> >> Cc: linux-dect(a)lists.osmocom.org >> >> >> On Fri, 10 Aug 2012, henrik hansen wrote: >> >>> Hey, >>> my Asterisk got a problem with the chan_dect module. >>> I build it like it's written here: >>> http://dect.osmocom.org/trac/dect/wiki/Build%20instructions >>> >>> debian*CLI> module load chan_dect >>> Unable to load module chan_dect >>> Command 'module load chan_dect' failed. >>> [Aug 10 14:23:41] WARNING[19284]: loader.c:449 load_dynamic_module: Error >>> loading module 'chan_dect': /usr/lib/asterisk/modules/chan_dect.so: >>> undefined symbol: dect_mm_endpoint_get >>> [Aug 10 14:23:41] WARNING[19284]: loader.c:839 load_resource: Module >>> 'chan_dect' could not be loaded. >>> >>> Could someone help me, getting this fixed? >> >> Its basically that chan_dect hasn't been converted to use the new API >> for wideband audio support yet. Just fixing this problem without actually adding wideband support should be relatively easy, I'll try to have a look during the weekend. >> >> >> >> >> _______________________________________________ >> linux-dect mailing list >> linux-dect(a)lists.osmocom.org >> https://lists.osmocom.org/mailman/listinfo/linux-dect > > > > > -- > -- > Mit freundlichen Grüßen > Henrik Hansen > > Waldstr 29 > 28816 Stuhr > > Tel.: 04206 6698 > Mobil: 0170 2350 222 > Mail: hhansen06(a)googlemail.com > > > > _______________________________________________ > linux-dect mailing list > linux-dect(a)lists.osmocom.org > https://lists.osmocom.org/mailman/listinfo/linux-dect

2 5

Re: linux-dect Digest, Vol 37, Issue 6
by Frédéric LECAILLE 15 Aug '12

15 Aug '12

Hello Henrik, If you type this command in a terminal this will give you an idea about your issue: ldd /usr/lib/asterisk/modules/chan_dect.so On Aug 11, 2012, at 12:00 PM, linux-dect-request(a)lists.osmocom.org wrote: > Send linux-dect mailing list submissions to > linux-dect(a)lists.osmocom.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.osmocom.org/mailman/listinfo/linux-dect > or, via email, send a message with subject or body 'help' to > linux-dect-request(a)lists.osmocom.org > > You can reach the person managing the list at > linux-dect-owner(a)lists.osmocom.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of linux-dect digest..." > Today's Topics: > > 1. undefined symbol: dect_mm_endpoint_get (henrik hansen) > 2. Re: undefined symbol: dect_mm_endpoint_get (Patrick McHardy) > > From: henrik hansen <hhansen06(a)googlemail.com> > Subject: undefined symbol: dect_mm_endpoint_get > Date: August 10, 2012 4:35:09 PM GMT+02:00 > To: linux-dect(a)lists.osmocom.org > > > Hey, > my Asterisk got a problem with the chan_dect module. > I build it like it's written here: http://dect.osmocom.org/trac/dect/wiki/Build%20instructions > > debian*CLI> module load chan_dect > Unable to load module chan_dect > Command 'module load chan_dect' failed. > [Aug 10 14:23:41] WARNING[19284]: loader.c:449 load_dynamic_module: Error loading module 'chan_dect': /usr/lib/asterisk/modules/chan_dect.so: undefined symbol: dect_mm_endpoint_get > [Aug 10 14:23:41] WARNING[19284]: loader.c:839 load_resource: Module 'chan_dect' could not be loaded. > > Could someone help me, getting this fixed? > > -- > -- > Mit freundlichen Grüßen > Henrik Hansen > > > > > From: Patrick McHardy <kaber(a)trash.net> > Subject: Re: undefined symbol: dect_mm_endpoint_get > Date: August 10, 2012 4:37:12 PM GMT+02:00 > To: henrik hansen <hhansen06(a)googlemail.com> > Cc: linux-dect(a)lists.osmocom.org > > > On Fri, 10 Aug 2012, henrik hansen wrote: > >> Hey, >> my Asterisk got a problem with the chan_dect module. >> I build it like it's written here: >> http://dect.osmocom.org/trac/dect/wiki/Build%20instructions >> >> debian*CLI> module load chan_dect >> Unable to load module chan_dect >> Command 'module load chan_dect' failed. >> [Aug 10 14:23:41] WARNING[19284]: loader.c:449 load_dynamic_module: Error >> loading module 'chan_dect': /usr/lib/asterisk/modules/chan_dect.so: >> undefined symbol: dect_mm_endpoint_get >> [Aug 10 14:23:41] WARNING[19284]: loader.c:839 load_resource: Module >> 'chan_dect' could not be loaded. >> >> Could someone help me, getting this fixed? > > Its basically that chan_dect hasn't been converted to use the new API > for wideband audio support yet. Just fixing this problem without actually adding wideband support should be relatively easy, I'll try to have a look during the weekend. > > > > > _______________________________________________ > linux-dect mailing list > linux-dect(a)lists.osmocom.org > https://lists.osmocom.org/mailman/listinfo/linux-dect

2 2

undefined symbol: dect_mm_endpoint_get
by henrik hansen 10 Aug '12

10 Aug '12

Hey, my Asterisk got a problem with the chan_dect module. I build it like it's written here: http://dect.osmocom.org/trac/dect/wiki/Build%20instructions debian*CLI> module load chan_dect Unable to load module chan_dect Command 'module load chan_dect' failed. [Aug 10 14:23:41] WARNING[19284]: loader.c:449 load_dynamic_module: Error loading module 'chan_dect': /usr/lib/asterisk/modules/chan_dect.so: undefined symbol: dect_mm_endpoint_get [Aug 10 14:23:41] WARNING[19284]: loader.c:839 load_resource: Module 'chan_dect' could not be loaded. Could someone help me, getting this fixed? -- -- Mit freundlichen Grüßen Henrik Hansen

2 1

Re: debt 6.0 rf band
by Frédéric LECAILLE 09 Aug '12

09 Aug '12

On Aug 9, 2012, at 12:20 AM, Patrick McHardy wrote: > Updated patch attached > <usdect.diff> Ok thank you a lot Patrick. Here are the results: with your last patch: dect-transceiver-list --name trx0 DECT Transceiver trx0@cell0: Type: vtrx RF-band: 00000 Events: busy: 0 late: 0 slot 0: <scanning> packet: P00 carrier: 27 (0.000 MHz) RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0 *The frequency is always 0 MHz* The kernel logs seems to be OK: [15122.889144] vtrx trx0: set carrier: slot: 0 carrier: 23 [15122.899150] vtrx trx0: set carrier: slot: 0 carrier: 24 [15122.909150] vtrx trx0: set carrier: slot: 0 carrier: 25 [15122.919151] vtrx trx0: set carrier: slot: 0 carrier: 26 [15122.929150] vtrx trx0: set carrier: slot: 0 carrier: 27 So I have tried your last patch with mine to force the rf_band to 1: dect-transceiver-list --name trx0 DECT Transceiver trx0@cell0: Type: vtrx RF-band: 00001 Events: busy: 0 late: 0 slot 0: <scanning> packet: P00 carrier: 23 (1921.536 MHz) RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0 The channel seems to be ok, but no station are visible during scanning… My contact in USA is not present, perhaps he is not at home… do not know if its station is on... About trx2: dect-transceiver-list --name trx2 DECT Transceiver trx2: Type: sc1442x Features: slow-hopping,p64 RF-band: 00001 Events: busy: 0 late: 0 slot 0: <idle> RX: bytes 0 packets 0 a-crc-errors 0 x-crc-errors 0 z-crc-errors 0 TX: bytes 0 packets 0 (no a-crc-errors) If I remember well, with only my patch which forces the rf_band to 3 we got for trx2: dect-transceiver-list --name trx2 I see that slot0 is scanning: DECT Transceiver trx2@cell0: Type: sc1442x Features: slow-hopping,p64 RF-band: 00003 Events: busy: 0 late: 0 slot 0: <scanning> packet: P00 carrier: 5 (1888.704 MHz) RX: bytes 0 packets 0 a-crc-errors 1629 x-crc-errors 0 z-crc-errors 0

2 7

debt 6.0 rf band
by Frédéric LECAILLE 08 Aug '12

08 Aug '12

Hello, I am trying to use a dosh&amand PCI card… this one: 01:03.0 Communication controller: Quicklogic Corporation COM-ON-AIR Dosch&Amand DECT (rev 32) Subsystem: Device 1786:0001 Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Interrupt: pin A routed to IRQ 20 Region 0: Memory at ddefe000 (32-bit, non-prefetchable) [size=8K] Kernel driver in use: com_on_air_pci with the dect kernel stack… I have managed to compile the kernel 3.2.0 with this config: CONFIG_DECT=m CONFIG_DECT_DEBUG=y CONFIG_DECT_CSF=m CONFIG_DECT_RAW=m CONFIG_DECT_CCF=m CONFIG_DECT_LU1_SAP=m CONFIG_DECTDEVICES=y CONFIG_DECT_VTRX=m CONFIG_DECT_COA_PCI=m CONFIG_DECT_COA=m CONFIG_DECT_COA_U2785=y CONFIG_DECT_COA_FIRMWARE=y CONFIG_DECT_COA_P64=y The driver seems to work but the issue is that I am trying to use it in USA for an American client, and I did not managed to make this card use the 1.9Mhz band (rf band 3 I guess). When I run this command: dect-transceiver-list --name trx2 I see that slot0 is scanning: DECT Transceiver trx2@cell0: Type: sc1442x Features: slow-hopping,p64 RF-band: 00003 Events: busy: 0 late: 0 slot 0: <scanning> packet: P00 carrier: 5 (1888.704 MHz) RX: bytes 0 packets 0 a-crc-errors 1629 x-crc-errors 0 z-crc-errors 0 but it nevers uses RF band 3 channel. For you information I have patch the driver this way to set the default debt rf band to 3: [root@localhost linux-2.6]# git diff diff --git a/drivers/dect/coa/sc1442x.c b/drivers/dect/coa/sc1442x.c index 73b9869..89b0a55 100644 --- a/drivers/dect/coa/sc1442x.c +++ b/drivers/dect/coa/sc1442x.c @@ -698,6 +698,7 @@ static u64 sc1442x_set_band(const struct dect_transceiver *t { struct coa_device *dev = dect_transceiver_priv(trx); +printk("setting band %d\n", band->band); return dev->radio_ops->map_band(dev, band); } diff --git a/net/dect/transceiver.c b/net/dect/transceiver.c index 706899d..25278af 100644 --- a/net/dect/transceiver.c +++ b/net/dect/transceiver.c @@ -19,6 +19,8 @@ #include <net/dect/mac_csf.h> #include <net/dect/transceiver.h> +static int rf_band = 3; +module_param(rf_band, int, 0); static LIST_HEAD(dect_transceiver_list); static int dect_transceiver_notify(struct dect_transceiver *trx, unsigned long event); @@ -651,7 +653,7 @@ int dect_register_transceiver(struct dect_transceiver *trx) if (err < 0) goto out; - err = dect_transceiver_set_band(trx, DECT_DEFAULT_BAND); + err = dect_transceiver_set_band(trx, rf_band); if (err < 0) goto out; Thank you in advance for any help. Fred

2 3

anyone for hire for dedected install and config for PCI card?
by Jeff Doucette 05 Aug '12

05 Aug '12

Is there anyone available for hire to help me get Dedected like CLI tools working with OcmocomDECT. I have the Com on Air PCI card and can't figure out how to get the driver to work. I need some guidence and willing to pay for it. Please advise, J BODY { font-family:Arial, Helvetica, sans-serif;font-size:12px; }

1 0

State of Work?
by henrik hansen 02 Aug '12

02 Aug '12

Hello List, I'm new to the osmocomDECT project and just bought 2 com-on-air PCI Cards. After reading the list archive, i have some questions about the state of the project. What features do we suport at the moment? Can i build a dect cell with asterisk support? is handover within a cell about multiple basestations supported? if i can help, test or support the project with hardware, so please tell ;) -- -- Mit freundlichen Grüßen Henrik Hansen

1 0

The LMX3161 still not supported ?
by ol ol 23 Jul '12

23 Jul '12

Hi! Is there any news on the chipset support LMX3161? COA card III-type of still does not work with osmocom soft? Thanks, Blago.

1 0

How to build Wireshark-1.6.7 against patched libpcap
by chiccus2003＠libero.it 22 Jun '12

22 Jun '12

Hi, I do not know how to build Wireshark-1.6.7 against patched libpcap. The Kernel 3.2.0+ is built and installed in directory: umberto@umberto-desktop:/usr/src The patched libpcap + libnl +libdect are built and installed in directory: umberto@umberto-desktop:/usr/src/tools Also the source directory wireshark-1.6.7 is in directory: umberto@umberto-desktop:/usr/src/tools I do: cd wireshark-1.6.7$ sudo ./configure --with-pcap=/usr/local/lib and I get the error: ........ checking for connect... yes checking whether to use libpcap for packet capture... yes checking pcap.h usability... yes checking pcap.h presence... yes checking for pcap.h... yes checking for pcap_open_live in -lpcap... no checking for pcap_open_live in -lpcap with -lcfg -lodm... no checking for pcap_open_live in -lpcap with -lpfring... no configure: error: Can't link with library libpcap. andrea@andrea-desktop:/usr/src/tools/wireshark-1.6.7$ What should I do? (Pci card installed) With best regards, Umberto

4 19

How to build Wireshark-1.6.7 against patched libpcap
by chiccus2003＠libero.it 06 May '12

06 May '12

Hi, I do not know how to build Wireshark-1.6.7 against patched libpcap. The Kernel 3.2.0+ is built and installed in directory: umberto@umberto-desktop:/usr/src The patched libpcap + libnl +libdect are built and installed in directory: umberto@umberto-desktop:/usr/src/tools Also the source directory wireshark-1.6.7 is in directory: umberto@umberto-desktop:/usr/src/tools I do: cd wireshark-1.6.7$ sudo ./configure --with-pcap=/usr/local/lib and I get the following error: ........ checking for connect... yes checking whether to use libpcap for packet capture... yes checking pcap.h usability... yes checking pcap.h presence... yes checking for pcap.h... yes checking for pcap_open_live in -lpcap... no checking for pcap_open_live in -lpcap with -lcfg -lodm... no checking for pcap_open_live in -lpcap with -lpfring... no configure: error: Can't link with library libpcap. andrea@andrea-desktop:/usr/src/tools/wireshark-1.6.7$ But if I run “./configure”, then when I run “sudo wireshark” can not find the interface dect. There are only interfaces: "any" - "lo" - "usb0". What should I do? (Pci card installed) With best regards, Umberto

2 1

Problems Building DECT Stack
by Sebastian --- 24 Apr '12

24 Apr '12

Hi First Problem: When I try to Build libdect (libnl was build and Installed without any critical errors): root@bt:/home/libdect# sh configure checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for a thread-safe mkdir -p... /bin/mkdir -p checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for a sed that does not truncate output... /bin/sed configure: Documentation build disabled checking for nl_socket_alloc in -lnl... no configure: error: No suitable version of libnl found Second Problem: When I Put in my com-on-air PCMCIA Card, and look in Kern.log: Apr 19 19:06:26 bt kernel: [ 13.847922] com_on_air_cs 0.0: DECTDataDevice PCMCIA F22 Apr 19 19:06:26 bt kernel: [ 13.888290] com_on_air_cs 0.0: Radio type U2785B Apr 19 19:06:26 bt kernel: [ 13.901784] com_on_air_cs 0.0: Loading firmware ... Apr 19 19:06:26 bt kernel: [ 13.996529] pcmcia 0.1: pcmcia: registering new device pcmcia0.1 (IRQ: 3) Apr 19 19:06:26 bt kernel: [ 13.996740] com_on_air_cs 0.1: DECTDataDevice PCMCIA F22 Apr 19 19:06:26 bt kernel: [ 13.996818] com_on_air_cs 0.1: failed to enable PCMCIA device Apr 19 19:06:26 bt kernel: [ 13.996880] com_on_air_cs: probe of 0.1 failed with error -13

4 9

Protocol mismatch error
by Tasha 14 Mar '12

14 Mar '12

Hello Patrick, I am currently working on my master thesis in computer science in which I'm trying to exploit you great open source software linux DECT-Stack. I plan to use it for controlling a Com-On-Air PCI ISDN card (Dosch&Amand). However, I'm facing problems with operating libdect, dectmon. To be more precise, after installing software and trying to run it I always get the following error message: dect_netlink_init: Protocol mismatch dect_init: Bad file descriptor root@dect:~/dectmon# valgrind src/dectmon ==4479== Memcheck, a memory error detector ==4479== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. ==4479== Using Valgrind-3.6.1-Debian and LibVEX; rerun with -h for copyright info ==4479== Command: src/dectmon ==4479== dectmon > ==4479== Warning: invalid file descriptor -1 in syscall close() dect_netlink_init: Protocol mismatch dectmon > dect_open_handle: Bad file descriptor ==4479== ==4479== HEAP SUMMARY: ==4479== in use at exit: 65,329 bytes in 189 blocks ==4479== total heap usage: 305 allocs, 116 frees, 74,326 bytes allocated ==4479== ==4479== LEAK SUMMARY: ==4479== definitely lost: 0 bytes in 0 blocks ==4479== indirectly lost: 0 bytes in 0 blocks ==4479== possibly lost: 0 bytes in 0 blocks ==4479== still reachable: 65,329 bytes in 189 blocks ==4479== suppressed: 0 bytes in 0 blocks ==4479== Rerun with --leak-check=full to see details of leaked memory ==4479== ==4479== For counts of detected and suppressed errors, rerun with: -v ==4479== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 39 from 6) root@dect:~/dectmon# and for any dect-command in asterisk: No such command 'dect show portables' Since my master degree depends highly on successful usage of your software I want to ask you for help and would very appreciate it. It would be very nice if you could give me an advise on how the problem can be solved. Please let me know if you need additional info, esp. in case the error text is not enough for you to be able to analyze the error. Thank you in advance! Best Regards, Tasha

2 3

libnl 'make' fails
by DeDecTed 06 Mar '12

06 Mar '12

Hi, I've been trying to compile 'libnl' on my Ubuntu 11.10 and I got the error: CC route/cls/ematch_grammar.lo route/cls/ematch_grammar.c:773:5: error: unknown type name 'YYSTYPE' The needed libs like byacc, bison or flex had been previously installed. Any clue what might cause the problem?

1 0

Using the DECT stack in PP mode
by Matthew Hess 14 Feb '12

14 Feb '12

Hi there, I would appreciate it if you could post this question to the linux-dect mailing list. I've been playing with the Osmocom DECT stack for a while now, trying to make it work in PP mode against a base station I've got. My goal right now is just to be able to run the pp-location-update example in libdect. So far, I've managed to compile, run and configure everything (I'm using the COA PCI card). dect-llme-scan shows my base station, and it has the "location_registration" higher layer capability. However, running the pp-location-update example results in the following output: "FP does not support location registration". The debug output from the kernel shows the following (apparently) interesting things: 1. "incomplete:SARI" is repeated a few times. 2. After a while, "timeout" 3. This repeats forever, with lots of seemingly "redundant" (and uninteresting) debug output in between. I'm guessing that the MAC layer doesn't want to lock on to the base station for some reason. I found the code that does this in mac_csf.c, but I'm clueless as to what I can actually do about it. I wonder if you could help me with this somehow. Perhaps you could point me to the right direction as to what could be changed in order for this to work? Or why does the stack not lock onto the base station? The base station does work with commercial DECT PPs, so some changes to the mac_csf code should probably make it work. I'm pretty good at playing with kernel code, I'm just not sure what is the right thing to do. I appreciate the help. Matt Hess

1 0

can we please make spammers harder to post new tickets?
by Allard Dijk 08 Sep '11

08 Sep '11

Hi, On avg. we get 2 spam tickets a day on Trac. Can you add some level of spam protection to add a ticket? *CAPTCHA *login required < this barrier is the quickest... (and is the same as other osmocom tracs) *changed ticket flow ( ticket not visible before approval) Best, Allard

3 4

compile failure
by Joe Freeman 08 Sep '11

08 Sep '11

Greetings- I'm trying to compile from the git sources, based on the 2.6 kernel included on the website. This is an an x86_64 install (originally CentOS 6, but I've got kernel 3.0.4 running on it now)... I'm having a heck of a time getting the DECT stuff to compile in the kernel. my make keeps failing- In file included from /home/jfreeman/linux-2.6/include/net/dect/dect.h:147, from /home/jfreeman/linux-2.6/drivers/dect/coa/sc1442x.c:19: /home/jfreeman/linux-2.6/include/net/dect/identities.h:55: error: field âarcâ has incomplete type make[4]: *** [drivers/dect/coa/sc1442x.o] Error 1 make[3]: *** [drivers/dect/coa] Error 2 make[2]: *** [drivers/dect] Error 2 make[1]: *** [drivers] Error 2 make: *** [sub-make] Error 2 That's the most recent failure, after I removed the enum dect_ari_classes from dect_netlink.h Anyone have any thoughts or suggestions? Thanks- Joe

2 1

Will the LMX3161 be supported in the future?
by luca bongiorni 23 Aug '11

23 Aug '11

Hi guys, have you find a solution for LMX3161 to be fully supported? Regards Luca

5 14

dect.osmocom.org Wiki accounts
by Patrick McHardy 13 Aug '11

13 Aug '11

Since Romain already asked for it, if someone wants Wiki accounts on dect.osmocom.org for adding new content, just send me an email.

1 0

Siemens proprietary protocol
by Romain Fliedel 13 Aug '11

13 Aug '11

Hi, I'm trying to understand siemens proprietary protocol and I'd like to add some data on the wiki (add new pcap, and dumps). How do I create an account on the wiki ? (it asks for a login/password) Does someone have pcaps for other siemens phones ? Thanks

2 1

dectmon how to ?
by Fliedel Romain 03 Aug '11

03 Aug '11

Hi again, Since I got the pcap to work with dect I'm trying to capture traffic between a handset and its base. I've been able to find my FP with dect-llme-scan (as specified here http://dect.osmocom.org/trac/dect/wiki/Configuration), but now I'd like to lock to this FP and capture the traffic with wireshark. I've used the dectmon utility but it's locking to other FP. Is there a way to lock to a specific FP ? Is there a how to somewhere for capturing traffic ? Thanks again, Romain

2 1

pairing problem
by Tobias Seufert 03 Aug '11

03 Aug '11

2 1

problem building kernel
by Fliedel Romain 29 Jul '11

29 Jul '11

Hi, I'm trying to build a kernel from the git repository with dect stack enabled but i get this error : net/dect/ccp.c:25:27: fatal error: net/tipc/tipc.h: it appears that this file has been removed in kernel 2.6.36 Do you have any idea to solve this problem ? Thanks

3 9

USB DECT devices
by Simon Kowalewski 29 Jul '11

29 Jul '11

Hi! I'd like to play around with OsmocomDECT a bit, but my prehistoric laptop with PCMCIA (my Pismo) has given up on me and all desktop computers I have are PCIe, none has PCI (the oldest being a PowerMac G5). But they all do have USB, and I have a Sinus 702 data, also known as Gigaset M34, a USB DECT adapter. Here are the details as seen from the PC side: DECT Data Device: Produkt-ID: 0x0026 Hersteller-ID: 0x0681 (Siemens Information and Communication Products) Version: 1,00 Seriennummer: 00045ABF42 Geschwindigkeit: Bis zu 12 MBit/s Hersteller: Siemens AG Standort-ID: 0x04100000 / 5 Verfügbare Stromstärke (mA): 500 Erforderliche Stromstärke (mA): 90 I couldn't find too much information on the chipset in these things, but if anyone is interested in hacking around with this, I could bring it to the camp. Cheers, Simon -- ATOM-STROM-AUSSTIEG JETZT! Noch heute zum günstigsten Ökostromanbieter wechseln! Naturstrom: 22,5 Cent/kWh, Preisgarantie bis Jahresende! Einfach anmelden unter http://naturstrom-jetzt.de/

3 2

Linux 3.0 merged
by Patrick McHardy 22 Jul '11

22 Jul '11

I've merged the DECT tree with the Linux 3.0 release. Due to some recent firmware changes, I'd appreciate feedback whether things are still working properly for everyone.

1 0

DECT hardware for linux
by Joe Freeman 29 Jun '11

29 Jun '11

Greetings- I've been banging my head against a wall today trying to identify hardware and a source of supply. What I'm trying to do is implement a an Asterisk solution that uses DECT headsets. The headset endpoints have no requirement to dial out, only to participate in a conference bridge. I haven't been able to identify a DECT interface that will allow this. I'd also entertain a SIP-DECT interface that would be SIP to the asterisk box. Range for this solution needs to be about 40-50m. Does anyone have any suggestions or thoughts?

2 1

Git problems fixed
by Patrick McHardy 09 Jun '11

09 Jun '11

To anyone who has had problems cloning the git kernel tree from dect.osmocom.org, thanks to Harald the problem should be fixed now. Please retry and report any problems.

1 0

is it possbile to use osmocom com_on_air_pci driver with dedected dect_cli ?
by Maba 24 May '11

24 May '11

It's seems the osmocom kernel is the only one who have a driver for the pci quicklogic dosh armand card . is it possible to use this drivers with the dump pcap tool of dedected (dect_cli) ?? Or, is it possible to dump pcap files with commands in libnl + dectmon ??? Thx for your answers and have nice days ;)

2 1

DECT Call drops after approx. 2 seconds
by Johannes Graser 12 Apr '11

12 Apr '11

Hi, I successfully managed to compile the DECT kernel, the libs and asterisk. I also can register PPs in asterisk, call them and place outbound calls from these PPs, but as soon as the connection is established, it takes about 2 seconds until the call drops, the PP loses connectivity and re-registers at asterisk. Whithin these 2 seconds the connection works in both directions correctly. I use the PCI Com-on-Air Card a Gigaset A58H PP and an older Gigaset 4000 Comfort. Does anyone know what the reason for this behaviour is? See the asterisk-log below... Thanks in advance, Johannes Graser *CLI> LCE: link -1 (RELEASED): alloc LCE: link 42 (ESTABLISHED): start <LCE.05>: SDU timer LCE: link 42 (ESTABLISHED): new link: PMID: bb600 LCN: 0 LLN: 1 SAPI: 0 LCE: RX: 03 05 05 07 80 a8 00 a4 41 3a 28 06 07 a0 a5 01 |........A:(.....| LCE: RX: 18 27 d6 18 e0 80 7b 06 81 00 02 18 01 42 |.'....{......B| LCE: link 42 (ESTABLISHED): stop <LCE.05>: SDU timer LCE: link 42 (ESTABLISHED): new transaction: protocol: Call Control F: 0 TV: 0 CC: unknown transaction: msg type: 5 CC-SETUP parse {CC-SETUP} message IE: <<PORTABLE-IDENTITY>> id: 5 len: 9 dst: 0x2115ff0 type: IPUI (0) PUT: N (IPEI) EMC: 0a44 PSN: 13a28 IE: <<FIXED-IDENTITY>> id: 6 len: 9 dst: 0x2112700 type: PARK (20) class: A EMC: 1182 FPN: 0fac3 IE: <<BASIC-SERVICE>> id: e0 len: 2 dst: 0x2112b50 call class: normal call (8) service: basic speech default attributes (0) IE: <<ESCAPE-TO-PROPRIETARY>> id: 7b len: 8 dst: 0x2119d60 EMC: 2 Content: 18 01 42 |..B| LCE: link 42 (ESTABLISHED): set IPUI: N EMC: 0a44 PSN: 13a28 LCE: link 42 (ESTABLISHED): confirm transaction: Call Control TV: 0 Role: 1 CC: call 0x2112620 (CALL INITIATED): new call CC: call 0x2112620 (CALL INITIATED): MNCC_SETUP-ind MM: link 42 (none): MM_AUTHENTICATE-req MM: link 42 (none): initiate procedure: authentication priority: 2 timeout: 10s LCE: link 42 (ESTABLISHED): open transaction: Mobility Management TV: 0 build {MM-AUTHENTICATION-REQUEST} message IE: <<AUTH-TYPE>> id: a 0x7f6c82671860 [Mar 17 16:22:43] NOTICE[1426]: chan_dect.c:1051 dect_mncc_setup_ind: PT 'DECT-PT-600': incoming call authentication algorithm: DSAA (1) authentication key type: User authentication key (1) authentication key number: 8 cipher key number: 0 INC: 0 DEF: 0 TXC: 0 UPC: 1 IE: <<RAND>> id: c 0x7f6c82671840 value: 13c93f577c813bcc IE: <<RS>> id: e 0x7f6c82671820 value: 4d90028926449990 LCE: TX: 05 40 0a 03 01 18 10 0c 08 cc 3b 81 7c 57 3f c9 |.@........;.|W?.| LCE: TX: 13 0e 08 90 99 44 26 89 02 90 4d |.....D&...M| LCE: RX: 85 41 0d 04 4d 1b d3 7f |.A..M...| MM: link 42 (authentication): AUTHENTICATION-REPLY parse {MM-AUTHENTICATION-REPLY} message IE: <<RES>> id: d len: 6 dst: 0x2116050 value: 7fd31b4d MM: link 42 (authentication): complete authentication procedure LCE: link 42 (ESTABLISHED): close transaction: Mobility Management TV: 0 Role: 0 LCE: link 42 (ESTABLISHED): partial release MM: link 42 (none): MM_AUTHENTICATE-cfm: accept: 1 MM: link 42 (none): MM_CIPHER-req MM: link 42 (none): initiate procedure: ciphering priority: 2 timeout: 10s LCE: link 42 (ESTABLISHED): open transaction: Mobility Management TV: 0 LCE: link 42 (ESTABLISHED): DL_ENC_KEY-req: 99dac9d705411edf build {MM-CIPHER-REQUEST} message IE: <<CIPHER-INFO>> id: 19 0x7f6c82671770 enable: 1 cipher algorithm: DECT Standard Cipher 1 (1) cipher key type: derived (9) cipher key num: 0 LCE: link 42 (ESTABLISHED): stop <LCE.05>: SDU timer [Mar 17 16:22:43] NOTICE[1426]: chan_dect.c:1327 dect_mm_authenticate_cfm: PT 'DECT-PT-600': authentication succeeded LCE: TX: 05 4c 19 02 81 98 |.L....| LCE: link 42 (ESTABLISHED): DL_ENCRYPT-ind MM: link 42 (ciphering): CIPHER-cfm MM: link 42 (ciphering): complete ciphering procedure LCE: link 42 (ESTABLISHED): close transaction: Mobility Management TV: 0 Role: 0 LCE: link 42 (ESTABLISHED): partial release MM: link 42 (none): MM_CIPHER-cfm: accept: 1 CC: call 0x2112620 (CALL INITIATED): MNCC_CALL_PROC-req build {CC-CALL-PROC} message LCE: link 42 (ESTABLISHED): stop <LCE.05>: SDU timer LCE: TX: 83 02 |..| -- Executing [s@default:1] Wait("DECT/DECT-PT-600-02112698", "1") in new stack LCE: RX: 03 7b 2c 03 31 32 33 |.{,.123| CC: call 0x2112620 (CALL PROCEEDING): receive msg type 7b CC: call 0x2112620 (CALL PROCEEDING): CC-INFO parse {CC-INFO} message IE: <<MULTI-KEYPAD>> id: 2c len: 5 dst: 0x211a370 Info: 31 32 33 |123| CC: call 0x2112620 (CALL PROCEEDING): MNCC_INFO-ind keypad: '1' (31) keypad: '2' (32) keypad: '3' (33) LCE: RX: 03 7b 7b 05 81 00 02 30 00 |.{{....0.| CC: call 0x2112620 (CALL PROCEEDING): receive msg type 7b CC: call 0x2112620 (CALL PROCEEDING): CC-INFO parse {CC-INFO} message IE: <<ESCAPE-TO-PROPRIETARY>> id: 7b len: 7 dst: 0x2119900 EMC: 2 Content: 30 00 |0.| CC: call 0x2112620 (CALL PROCEEDING): MNCC_INFO-ind CC: call 0x2112620 (CALL PROCEEDING): MNCC_CONNECT-req -- Executing [s@default:2] Answer("DECT/DECT-PT-600-02112698", "") in new stack CC: call 0x2112620 (CALL PROCEEDING): U-Plane connected build {CC-CONNECT} message LCE: TX: 83 07 |..| [Mar 17 16:22:45] NOTICE[1442]: chan_dect.c:665 dect_answer: PT 'DECT-PT-600': answer call state 4 [Mar 17 16:22:45] NOTICE[1442]: chan_dect.c:844 dect_indicate: PT 'DECT-PT-600': indicate condition -1 -- Executing [s@default:3] Set("DECT/DECT-PT-600-02112698", "TIMEOUT(digit)=5") in new stack -- Digit timeout set to 5.000 -- Executing [s@default:4] Set("DECT/DECT-PT-600-02112698", "TIMEOUT(response)=10") in new stack -- Response timeout set to 10.000 -- Executing [s@default:5] BackGround("DECT/DECT-PT-600-02112698", "demo-congrats") in new stack -- <DECT/DECT-PT-600-02112698> Playing 'demo-congrats.gsm' (language 'en') -- Executing [3@default:1] Set("DECT/DECT-PT-600-02112698", "LANGUAGE()=fr") in new stack [Mar 17 16:22:45] ERROR[1442]: pbx.c:3683 ast_func_write: Function LANGUAGE not registered -- Executing [3@default:2] Goto("DECT/DECT-PT-600-02112698", "s,restart") in new stack -- Goto (default,s,5) -- Executing [s@default:5] BackGround("DECT/DECT-PT-600-02112698", "demo-congrats") in new stack -- <DECT/DECT-PT-600-02112698> Playing 'demo-congrats.gsm' (language 'en') CC: call 0x2112620 (ACTIVE): LU1 Queue-Statistic: CC: call 0x2112620 (ACTIVE): RX-Bytes: 0 CC: call 0x2112620 (ACTIVE): RX-Underflow: 0 CC: call 0x2112620 (ACTIVE): TX-Bytes: 400 CC: call 0x2112620 (ACTIVE): TX-Underflow: 0 CC: call 0x2112620 (ACTIVE): LU1 Queue-Statistic: CC: call 0x2112620 (ACTIVE): RX-Bytes: 0 CC: call 0x2112620 (ACTIVE): RX-Underflow: 0 CC: call 0x2112620 (ACTIVE): TX-Bytes: 400 CC: call 0x2112620 (ACTIVE): TX-Underflow: 0 CC: call 0x2112620 (ACTIVE): LU1 Queue-Statistic: CC: call 0x2112620 (ACTIVE): RX-Bytes: 0 CC: call 0x2112620 (ACTIVE): RX-Underflow: 0 CC: call 0x2112620 (ACTIVE): TX-Bytes: 400 CC: call 0x2112620 (ACTIVE): TX-Underflow: 0 LCE: recvmsg: Connection timed out LCE: link 42 (ESTABLISHED): shutdown CC: call 0x2112620 (ACTIVE): shutdown CC: call 0x2112620 (ACTIVE): MNCC_REJECT-ind CC: call 0x2112620 (ACTIVE): LU1 Queue-Statistic: CC: call 0x2112620 (ACTIVE): RX-Bytes: 0 CC: call 0x2112620 (ACTIVE): RX-Underflow: 0 CC: call 0x2112620 (ACTIVE): TX-Bytes: 440 CC: call 0x2112620 (ACTIVE): TX-Underflow: 0 CC: call 0x2112620 (ACTIVE): U-Plane disconnected LCE: link 42 (RELEASED): close transaction: Call Control TV: 0 Role: 1 LCE: link 42 (RELEASED): destroy == Spawn extension (default, s, 5) exited non-zero on 'DECT/DECT-PT-600-02112698'

2 4

Patches for setting the MFN from userspace
by Erik Tews 19 Mar '11

19 Mar '11

Hi With help from Patrick, I developed a small set of patches, so that you can change the MFN of an FP from userspace. You can pull these patches from branch upstream from: http://www.cdc.informatik.tu-darmstadt.de/~e_tews/linux-2.6/ http://www.cdc.informatik.tu-darmstadt.de/~e_tews/libnl/

2 1

Fehler beim Kernel bauen
by Jens Zerban 15 Jan '11

15 Jan '11

unter Kanotix 2.6.30-10-generic habe ich nun folgenden Fehler bei make: CC [M] net/dect/mac_ccf.o net/dect/mac_ccf.c:65: warning: ‘dect_slotnum’ defined but not used net/dect/mac_ccf.c:75: warning: ‘dect_mfn’ defined but not used net/dect/mac_ccf.c:211: warning: ‘dect_mbc_tb_get_by_lbn’ defined but not used CC [M] net/dect/dsc.o CC [M] net/dect/dlc.o CC [M] net/dect/dlc_cplane.o CC [M] net/dect/dlc_b_sap.o CC [M] net/dect/dlc_s_sap.o CC [M] net/dect/dlc_uplane.o CC [M] net/dect/ccp.o net/dect/ccp.c: In function ‘dect_ccp_send_to_cell’: net/dect/ccp.c:55: error: implicit declaration of function ‘tipc_send_buf’ make[2]: *** [net/dect/ccp.o] Fehler 1 make[1]: *** [net/dect] Fehler 2 make: *** [net] Fehler 2 Kann jemand helfen? ___________________________________________________________ NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://produkte.web.de/go/webdefreephone

2 1

Kernel oops
by Barry Myles 11 Jan '11

11 Jan '11

I'm using the linux-dect code and experimenting with dectmon and the libdect examples. Mostly, I think they are working well. I have a com-on-air type II card and it's in an aging P4 laptop. However, I'm having some kernel stability problems. The machine runs stabily forever before the card is configured with the netlink utilities. However, once the card is configured then a few minutes later the kernel will oops. I'm configuring the card something like: dect-cluster-add --name cluster0 --emc 0xABCD --fpn 0x12345 --mode PP dect-cell-add --name cell0 --cluster cluster0 --flags monitor dect-transceiver-bind --transceiver trx0 --cell cell0 Until the kernel oops then everything seems to work fine and dectmon, for example will happily log what it sees. I've attached two kernel logs which seem fairly typical of what is happening. Can anyone help? -- Barry Myles

2 1

Fehler beim Bauen des Kernels unter verschiedenen Linux-BS
by Jens Zerban 11 Jan '11

11 Jan '11

drivers/dect/coa/com_on_air_cs.o drivers/dect/coa/com_on_air_cs.c:22:23: Fehler: pcmcia/cs.h: Datei oder Verzeichnis nicht gefunden drivers/dect/coa/com_on_air_cs.c: In Funktion »com_on_air_probe«: drivers/dect/coa/com_on_air_cs.c:41: Fehler: »win_req_t« nicht deklariert (erste Benutzung in dieser Funktion) drivers/dect/coa/com_on_air_cs.c:41: Fehler: (Jeder nicht deklarierte Bezeichner wird nur einmal aufgeführt drivers/dect/coa/com_on_air_cs.c:41: Fehler: für jede Funktion in der er auftritt.) drivers/dect/coa/com_on_air_cs.c:41: Fehler: expected »;« before »req« drivers/dect/coa/com_on_air_cs.c:42: Warnung: ISO C90 forbids mixed declarations and code drivers/dect/coa/com_on_air_cs.c:67: Fehler: »struct pcmcia_device« hat kein Element namens »conf« drivers/dect/coa/com_on_air_cs.c:68: Fehler: »struct pcmcia_device« hat kein Element namens »conf« drivers/dect/coa/com_on_air_cs.c:68: Fehler: »INT_MEMORY_AND_IO« nicht deklariert (erste Benutzung in dieser Funktion) drivers/dect/coa/com_on_air_cs.c:69: Fehler: »struct pcmcia_device« hat kein Element namens »conf« drivers/dect/coa/com_on_air_cs.c:70: Fehler: »struct pcmcia_device« hat kein Element namens »conf« drivers/dect/coa/com_on_air_cs.c:71: Fehler: »struct pcmcia_device« hat kein Element namens »conf« drivers/dect/coa/com_on_air_cs.c:73: Fehler: »req« nicht deklariert (erste Benutzung in dieser Funktion) drivers/dect/coa/com_on_air_cs.c:78: Fehler: »struct pcmcia_device« hat kein Element namens »win« drivers/dect/coa/com_on_air_cs.c:91: Fehler: »struct pcmcia_device« hat kein Element namens »conf« drivers/dect/coa/com_on_air_cs.c:100: Fehler: Implizite Deklaration der Funktion »pcmcia_request_configuration« drivers/dect/coa/com_on_air_cs.c:100: Fehler: »struct pcmcia_device« hat kein Element namens »conf« drivers/dect/coa/com_on_air_cs.c:106: Fehler: »struct pcmcia_device« hat kein Element namens »conf« drivers/dect/coa/com_on_air_cs.c:109: Fehler: »struct pcmcia_device« hat kein Element namens »conf« drivers/dect/coa/com_on_air_cs.c:110: Fehler: »struct pcmcia_device« hat kein Element namens »conf« drivers/dect/coa/com_on_air_cs.c:111: Fehler: »struct pcmcia_device« hat kein Element namens »conf« drivers/dect/coa/com_on_air_cs.c:112: Fehler: »struct pcmcia_device« hat kein Element namens »conf« Fehler habe ich unter Kanotix,Ubuntu 10.04,Mandriva 2010. Normalen Kernel kann ich bauen, aber dieser will nicht. drivers/dect/coa/com_on_air_cs.c:112: Fehler: »struct pcmcia_device« hat kein Element namens »conf« drivers/dect/coa/com_on_air_cs.c:112: Fehler: »struct pcmcia_device« hat kein Element namens »conf« drivers/dect/coa/com_on_air_cs.c:112: Fehler: »struct pcmcia_device« hat kein Element namens »conf« drivers/dect/coa/com_on_air_cs.c:116: Fehler: »struct pcmcia_device« hat kein Element namens »conf« drivers/dect/coa/com_on_air_cs.c:118: Warnung: format »%llx« erwartet Typ »long long unsigned int«, aber Argument 4 hat Typ »resource_size_t« drivers/dect/coa/com_on_air_cs.c:119: Warnung: format »%llx« erwartet Typ »long long unsigned int«, aber Argument 4 hat Typ »resource_size_t« drivers/dect/coa/com_on_air_cs.c:121: Warnung: format »%llx« erwartet Typ »long long unsigned int«, aber Argument 4 hat Typ »resource_size_t« drivers/dect/coa/com_on_air_cs.c:122: Warnung: format »%llx« erwartet Typ »long long unsigned int«, aber Argument 4 hat Typ »resource_size_t« drivers/dect/coa/com_on_air_cs.c:146: Fehler: »struct pcmcia_device« hat kein Element namens »conf« drivers/dect/coa/com_on_air_cs.c:164: Fehler: »struct pcmcia_device« hat kein Element namens »win« make[3]: *** [drivers/dect/coa/com_on_air_cs.o] Fehler 1 make[2]: *** [drivers/dect/coa] Fehler 2 make[1]: *** [drivers/dect] Fehler 2 make: *** [drivers] Fehler 2 [root@localhost linux-2.6]# ___________________________________________________________ NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://produkte.web.de/go/webdefreephone

2 1

Kernel oops
by Barry Myles 09 Jan '11

09 Jan '11

I'm using the linux-dect code and experimenting with dectmon and the libdect examples. Mostly, I think they are working well. I have a com-on-air type II card and it's in an aging P4 laptop. However, I'm having some kernel stability problems. The machine runs stabily forever before the card is configured with the netlink utilities. However, once the card is configured then a few minutes later the kernel will oops. I'm configuring the card something like: dect-cluster-add --name cluster0 --emc 0xABCD --fpn 0x12345 --mode PP dect-cell-add --name cell0 --cluster cluster0 --flags monitor dect-transceiver-bind --transceiver trx0 --cell cell0 Until the kernel oops then everything seems to work fine and dectmon, for example will happily log what it sees. I've attached two kernel logs which seem fairly typical of what is happening. Can anyone help? -- Barry Myles

1 0

New experimental patch for dectmon
by Erik Tews 13 Dec '10

13 Dec '10

Hi I tried to write some code, which checks all possible pins in a handshake, so that you don't need to specify the pin. However, I am currently not able to put my system into a proper monitoring-mode, so I could not test this patch so far. Could someone check the patch available at: http://www.cdc.informatik.tu-darmstadt.de/~e_tews/dectmon/ in branch "pin-bf", that it really works? The code there is completely untested.

1 0

Two small problems with libpcap
by Erik Tews 24 Nov '10

24 Nov '10

Hi I spotted two small problems with libpcap: * Preables for received PP frames are missing, the dedected.org tools used to include the preamble as well. This can easily be fixed by adding a default preamble if the kernel doesn't report the preamble to the userspace. * The slottime wraps around at 2^12 and not at 2^11 as it used to wrap around with the dedected.org tools. I am not sure about the best solution here, one could also use the full 16 bits for the time which are available in the header.

2 6

tcpdump build problems / new tcpdump tree?
by Erik Tews 15 Nov '10

15 Nov '10

Hi Building the libpcap tree works fine, but because libpcap depends on libnl for dect monitoring, every programm using libpcap.a needs to be linked with libnl and libnl-dect. Just trying to build tcpdump from git fails because of that. What would be the best solution for this problem? Starting a new tcpdump tree or trying to fix it in the libpcap tree?

2 1

Dectmon only recording data partially?
by Erik Tews 15 Nov '10

15 Nov '10

Hi I have a strange problem with dectmon. I would like to monitor the conversations between a Siemens AS150 and it's base station. I started the cluster in monitoring mode with the same emc and fpn as the original base station in pp mode: dect-cluster-add --name cluster0 --emc $EMC --fpn $FPN --mode pp --monitor dect-cell-add --name cell0 --cluster cluster0 dect-transceiver-bind --transceiver trx0 --cell cell0 Now, when I launch dectmon, I get these messages: # ./dectmon -n yes netlink: cluster0: mode PP ARI: class A: EMC: 0ff6 FPN: 0deb7 LCE: set default pmid e94bd LCE: registered protocol 0 (Link Control) LCE: registered protocol 3 (Call Control) LCE: registered protocol 4 (Call Independant Supplementary Services) LCE: registered protocol 6 (ConnectionLess Message Service) LCE: registered protocol 5 (Mobility Management) netlink: message group: 4 netlink: FPC: full_slot,page_repetition,basic_a_field_setup,in_min_delay netlink: HLC: adpcm_g721_voice,gap_pap_basic_speech,standard_authentication,location_registration unknown unknown netlink: message group: 4 Should't there be more output? I am sure that at least some location registration or authentication messages are exchanged here. I am running 2.6.36, but I did not update to the latest version in the git tree yet.

2 20

dectmon deciphering
by Patrick McHardy 13 Nov '10

13 Nov '10

Just in case someone is interested - I've just pushed out changes to allow dectmon to decipher connections if it was able to track the initial key allocation (and thus knows the UAK). The PIN it uses is currently hardcoded to "0000" in src/nwk.c, so make sure to change it to use your own PIN or add brute forcing :) If someone wants to play with this, I'm still looking for traces of Siemens phones during pairing, location updates etc :) ... NWK: 05 40 0a 03 01 18 18 0c 08 23 b1 0e 03 7d 0d 3f |.@.......#...}.?| NWK: ee 0e 08 77 1c 1c 5f aa a6 06 33 |...w.._...3| {MM-AUTHENTICATION-REQUEST} message: IE: <<AUTH-TYPE>> id: a len: 5 dst: 0x60c2e0 authentication algorithm: DSAA (1) authentication key type: User authentication key (1) authentication key number: 8 cipher key number: 8 INC: 0 DEF: 0 TXC: 0 UPC: 1 IE: <<RAND>> id: c len: 10 dst: 0x60c4c0 value: ee3f0d7d030eb123 IE: <<RS>> id: e len: 10 dst: 0x60c4e0 value: 3306a6aa5f1c1c77 NWK: 85 41 0d 04 ba 5b b8 af |.A...[..| {MM-AUTHENTICATION-REPLY} message: IE: <<RES>> id: d len: 6 dst: 0x60c660 value: afb85bba authentication successful DCK: 30 e5 60 b3 b9 f6 ee e8 |0.`.....| NWK: 05 4c 19 02 81 98 |.L....| {MM-CIPHER-REQUEST} message: IE: <<CIPHER-INFO>> id: 19 len: 4 dst: 0x60c2b0 enable: 1 cipher algorithm: DECT Standard Cipher 1 (1) cipher key type: derived (9) cipher key num: 8 ciphering enabled: FP->PP ciphering enabled: PP->FP NWK: 83 0d 1e 02 80 88 7c 04 90 02 00 84 |......|.....| {CC-SETUP-ACK} message: IE: <<PROGRESS-INDICATOR>> id: 1e len: 4 dst: 0x60c660 Location: user (0) Progress description: In-band information or appropriate pattern now available (8) IE: <<CODEC-LIST>> id: 7c len: 6 dst: 0x60c940 Negotiation Indicator: codec negotiation (1) Codec 1: Codec: G.726 (32kbit) (2) MAC/DLC Service: DLC service: LU1, MAC service: I_NA (0) Slot size: full slot (4) C-Plane routing: C_S only (0)

2 3

Dectmon problems on malloc function
by Oscar Soriano Riera 12 Nov '10

12 Nov '10

Hello Everyone for Spain I have some problems in the startup or running Dectmon. I use the lasted drivers (today 20101008) packets on http://dect.osmocom.org. This is my runbook: 1) I compile dectmon with this: #sh autogen.sh #sh configure #make #make install 2)I getup the interface: #dect-cluster-add --name cluster0 --emc 0x12f5 --fpn 0x0be9f --mode PP #dect-cell-add --name cell0 --cluster cluster0 --flags monitor #dect-transceiver-bind --transceiver trx0 --cell cell0 Added: 0: DECT Cluster cluster0: Mode: PP PARI: class A (residential) EMC: 12f5 FPN: 0be9f Added: 0: DECT Cell cell0@cluster0: Bound: DECT Transceiver trx0@cell0: RF-band: 00000 Events: busy: 0 late: 0 3)I can see in the log that the device is correct getup (some fragment): [ 3709.832225] extended fixed part capabilities: fpc: 00022 hlc: 000000 [ 3710.099164] extended fixed part capabilities: fpc: 00020 hlc: 000000 [ 3710.914148] identities information: e: 0 class: 0 emc: 1106 fpn: 08f71 rpn: 0 [ 3711.382176] identities information: e: 0 class: 0 emc: 065f fpn: 1d9d8 rpn: 0 [ 3712.039334] identities information: e: 0 class: 0 emc: 0f73 fpn: 1066a rpn: 0 [ 3712.120434] identities information: e: 0 class: 0 emc: 0d24 fpn: 04834 rpn: 0 [ 3713.079207] identities information: e: 0 class: 0 emc: 1056 fpn: 158ee rpn: 0 [ 3713.345455] identities information: e: 0 class: 0 emc: 1133 fpn: 1e399 rpn: 0 [ 3713.467939] identities information: e: 0 class: 0 emc: 0de9 fpn: 1bc8c rpn: 0 [ 3713.550437] page: RFPI: 241a0 bearer description: bt: 5000000000 sn: 2 sp: 0 cn: 4 [ 3713.632170] identities information: e: 0 class: 0 emc: 065f fpn: 1d9d8 rpn: 0 [ 3713.877937] identities information: e: 0 class: 0 emc: 0de9 fpn: 1bc8c rpn: 0 [ 3714.736021] identities information: e: 0 class: 0 emc: 0726 fpn: 16bc9 rpn: 0 [ 3714.960698] page: RFPI: cf0b0 blind full slots: 2aa [ 3715.329202] identities information: e: 0 class: 0 emc: 1056 fpn: 158ee rpn: 0 [ 3715.390439] static system information: nr: 0 sn: 2 cn: 4 pscn: 4 [ 3716.044455] identities information: e: 0 class: 0 emc: 12fd fpn: 1b11b rpn: 0 [ 3716.166016] identities information: e: 0 class: 0 emc: 0726 fpn: 16bc9 rpn: 0 [ 3716.576015] full/long page: extend: 0 length: 4000000000000000 [ 3716.986016] identities information: e: 0 class: 0 emc: 0726 fpn: 16bc9 rpn: 0 [ 3717.230442] page: RFPI: 241a0 bearer description: bt: 5000000000 sn: 2 sp: 0 cn: 4 [ 3717.392245] identities information: e: 0 class: 0 emc: 101b fpn: 13012 rpn: 0 [ 3717.432942] identities information: e: 0 class: 0 emc: 1133 fpn: 1e399 rpn: 0 [ 3717.757908] identities information: e: 0 class: 0 emc: 0de9 fpn: 1bc8c rpn: 0 [ 3718.023878] identities information: e: 0 class: 0 emc: 14d4 fpn: 18fc7 rpn: 0 [ 3718.779329] identities information: e: 0 class: 0 emc: 0f73 fpn: 1066a rpn: 0 [ 3719.086319] identities information: e: 0 class: 0 emc: 0747 fpn: 06960 rpn: 0 [ 3719.433269] identities information: e: 0 class: 0 emc: 0a6d fpn: 061c7 rpn: 0 [ 3719.494174] identities information: e: 0 class: 0 emc: 1106 fpn: 08f71 rpn: 0 [ 3719.657595] identities information: e: 0 class: 0 emc: 07ef fpn: 17322 rpn: 0 4) Launch Dectmon return a segment fault root@DECT:/usr/src/dectmon# src/dectmon *** glibc detected *** ./dectmon: free(): invalid next size (normal): 0x084d15c8 *** ======= Backtrace: ========= /lib/i686/cmov/libc.so.6(+0x6b281)[0xb772d281] /lib/i686/cmov/libc.so.6(+0x6cad8)[0xb772ead8] /lib/i686/cmov/libc.so.6(cfree+0x6d)[0xb7731bbd] /usr/local/lib/libnl.so.3(nlmsg_free+0x83)[0xb784a1d3] /usr/local/lib/libnl-dect.so.3(nl_dect_cluster_query+0x50)[0xb78570b0] /usr/lib/libdect.so.0(+0x1cc9d)[0xb7830c9d] /usr/lib/libdect.so.0(dect_open_handle+0xbd)[0xb7818e5d] ./dectmon[0x804cbec] /lib/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0xb76d8c76] ./dectmon[0x8049021] ======= Memory map: ======== 08048000-0804e000 r-xp 00000000 03:01 794829 /usr/src/dectmon/src/dectmon 0804e000-0804f000 rw-p 00006000 03:01 794829 /usr/src/dectmon/src/dectmon 084d1000-084f2000 rw-p 00000000 00:00 0 [heap] b7500000-b7521000 rw-p 00000000 00:00 0 b7521000-b7600000 ---p 00000000 00:00 0 b7669000-b7686000 r-xp 00000000 03:01 2154538 /lib/libgcc_s.so.1 b7686000-b7687000 rw-p 0001c000 03:01 2154538 /lib/libgcc_s.so.1 b769b000-b769c000 rw-p 00000000 00:00 0 b769c000-b76c0000 r-xp 00000000 03:01 2171097 /lib/i686/cmov/libm-2.11.2.so b76c0000-b76c1000 r--p 00023000 03:01 2171097 /lib/i686/cmov/libm-2.11.2.so b76c1000-b76c2000 rw-p 00024000 03:01 2171097 /lib/i686/cmov/libm-2.11.2.so b76c2000-b7802000 r-xp 00000000 03:01 2171331 /lib/i686/cmov/libc-2.11.2.so b7802000-b7804000 r--p 0013f000 03:01 2171331 /lib/i686/cmov/libc-2.11.2.so b7804000-b7805000 rw-p 00141000 03:01 2171331 /lib/i686/cmov/libc-2.11.2.so b7805000-b7808000 rw-p 00000000 00:00 0 b7808000-b7813000 r-xp 00000000 03:01 2048785 /usr/lib/libev.so.3.0.0 b7813000-b7814000 rw-p 0000b000 03:01 2048785 /usr/lib/libev.so.3.0.0 b7814000-b783a000 r-xp 00000000 03:01 2048792 /usr/lib/libdect.so.0.0.1 b783a000-b783e000 rw-p 00025000 03:01 2048792 /usr/lib/libdect.so.0.0.1 b783e000-b783f000 rw-p 00000000 00:00 0 b783f000-b7851000 r-xp 00000000 03:01 762960 /usr/local/lib/libnl.so.3.0.0 b7851000-b7852000 rw-p 00012000 03:01 762960 /usr/local/lib/libnl.so.3.0.0 b7852000-b785b000 r-xp 00000000 03:01 762976 /usr/local/lib/libnl-dect.so.3.0.0 b785b000-b785c000 rw-p 00009000 03:01 762976 /usr/local/lib/libnl-dect.so.3.0.0 b7870000-b7872000 rw-p 00000000 00:00 0 b7872000-b7873000 r-xp 00000000 00:00 0 [vdso] b7873000-b788e000 r-xp 00000000 03:01 2155169 /lib/ld-2.11.2.so b788e000-b788f000 r--p 0001a000 03:01 2155169 /lib/ld-2.11.2.so b788f000-b7890000 rw-p 0001b000 03:01 2155169 /lib/ld-2.11.2.so bfcae000-bfccf000 rw-p 00000000 00:00 0 [stack] 5) I use Valgrid to see a problem, but valgrid fails, i think that is a problem with the malloc when it get memory for the stack: root@DECT:/usr/src/dectmon# valgrind src/dectmon ==10731== Memcheck, a memory error detector ==10731== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et al. ==10731== Using Valgrind-3.6.0 and LibVEX; rerun with -h for copyright info ==10731== Command: src/dectmon ==10731== ==10731== Invalid write of size 2 ==10731== at 0x408E568: event_set (in /usr/lib/libev.so.3.0.0) ==10731== by 0x804940E: register_fd (event_ops.c:35) ==10731== by 0x4078361: dect_fd_register (io.c:103) ==10731== by 0x4077C14: dect_netlink_init (netlink.c:358) ==10731== by 0x405FE5C: dect_open_handle (libdect.c:66) ==10731== by 0x804CBEB: main (main.c:108) ==10731== Address 0x41ff7d8 is not stack'd, malloc'd or (recently) free'd ==10731== ==10731== Invalid write of size 4 ==10731== at 0x408E57C: event_set (in /usr/lib/libev.so.3.0.0) ==10731== by 0x804940E: register_fd (event_ops.c:35) ==10731== by 0x4078361: dect_fd_register (io.c:103) ==10731== by 0x4077C14: dect_netlink_init (netlink.c:358) ==10731== by 0x405FE5C: dect_open_handle (libdect.c:66) ==10731== by 0x804CBEB: main (main.c:108) ==10731== Address 0x41ff7c0 is 0 bytes after a block of size 88 alloc'd ==10731== at 0x4023FE0: malloc (vg_replace_malloc.c:236) ==10731== by 0x407897D: dect_malloc (utils.c:21) ==10731== by 0x4078486: dect_fd_alloc (io.c:56) ==10731== by 0x4077BBF: dect_netlink_init (netlink.c:352) ==10731== by 0x405FE5C: dect_open_handle (libdect.c:66) ==10731== by 0x804CBEB: main (main.c:108) ==10731== ==10731== Invalid write of size 4 ==10731== at 0x408E582: event_set (in /usr/lib/libev.so.3.0.0) ==10731== by 0x804940E: register_fd (event_ops.c:35) ==10731== by 0x4078361: dect_fd_register (io.c:103) ==10731== by 0x4077C14: dect_netlink_init (netlink.c:358) ==10731== by 0x405FE5C: dect_open_handle (libdect.c:66) ==10731== by 0x804CBEB: main (main.c:108) ==10731== Address 0x41ff7cc is 12 bytes after a block of size 88 alloc'd ==10731== at 0x4023FE0: malloc (vg_replace_malloc.c:236) ==10731== by 0x407897D: dect_malloc (utils.c:21) ==10731== by 0x4078486: dect_fd_alloc (io.c:56) ==10731== by 0x4077BBF: dect_netlink_init (netlink.c:352) ==10731== by 0x405FE5C: dect_open_handle (libdect.c:66) ==10731== by 0x804CBEB: main (main.c:108) ==10731== ==10731== Invalid write of size 4 ==10731== at 0x408E589: event_set (in /usr/lib/libev.so.3.0.0) ==10731== by 0x804940E: register_fd (event_ops.c:35) ==10731== by 0x4078361: dect_fd_register (io.c:103) ==10731== by 0x4077C14: dect_netlink_init (netlink.c:358) ==10731== by 0x405FE5C: dect_open_handle (libdect.c:66) ==10731== by 0x804CBEB: main (main.c:108) ==10731== Address 0x41ff7d0 is not stack'd, malloc'd or (recently) free'd ==10731== ==10731== Invalid write of size 4 ==10731== at 0x408E590: event_set (in /usr/lib/libev.so.3.0.0) ==10731== by 0x804940E: register_fd (event_ops.c:35) ==10731== by 0x4078361: dect_fd_register (io.c:103) ==10731== by 0x4077C14: dect_netlink_init (netlink.c:358) ==10731== by 0x405FE5C: dect_open_handle (libdect.c:66) ==10731== by 0x804CBEB: main (main.c:108) ==10731== Address 0x41ff7c8 is 8 bytes after a block of size 88 alloc'd ==10731== at 0x4023FE0: malloc (vg_replace_malloc.c:236) ==10731== by 0x407897D: dect_malloc (utils.c:21) ==10731== by 0x4078486: dect_fd_alloc (io.c:56) ==10731== by 0x4077BBF: dect_netlink_init (netlink.c:352) ==10731== by 0x405FE5C: dect_open_handle (libdect.c:66) ==10731== by 0x804CBEB: main (main.c:108) ==10731== ==10731== Invalid write of size 4 ==10731== at 0x408E593: event_set (in /usr/lib/libev.so.3.0.0) ==10731== by 0x804940E: register_fd (event_ops.c:35) ==10731== by 0x4078361: dect_fd_register (io.c:103) ==10731== by 0x4077C14: dect_netlink_init (netlink.c:358) ==10731== by 0x405FE5C: dect_open_handle (libdect.c:66) ==10731== by 0x804CBEB: main (main.c:108) ==10731== Address 0x41ff7c4 is 4 bytes after a block of size 88 alloc'd ==10731== at 0x4023FE0: malloc (vg_replace_malloc.c:236) ==10731== by 0x407897D: dect_malloc (utils.c:21) ==10731== by 0x4078486: dect_fd_alloc (io.c:56) ==10731== by 0x4077BBF: dect_netlink_init (netlink.c:352) ==10731== by 0x405FE5C: dect_open_handle (libdect.c:66) ==10731== by 0x804CBEB: main (main.c:108) ==10731== ==10731== Invalid write of size 4 ==10731== at 0x408E596: event_set (in /usr/lib/libev.so.3.0.0) ==10731== by 0x804940E: register_fd (event_ops.c:35) ==10731== by 0x4078361: dect_fd_register (io.c:103) ==10731== by 0x4077C14: dect_netlink_init (netlink.c:358) ==10731== by 0x405FE5C: dect_open_handle (libdect.c:66) ==10731== by 0x804CBEB: main (main.c:108) ==10731== Address 0x41ff7d4 is not stack'd, malloc'd or (recently) free'd ==10731== ==10731== Invalid read of size 2 ==10731== at 0x408EC70: event_add (in /usr/lib/libev.so.3.0.0) ==10731== by 0x804941E: register_fd (event_ops.c:36) ==10731== by 0x4078361: dect_fd_register (io.c:103) ==10731== by 0x4077C14: dect_netlink_init (netlink.c:358) ==10731== by 0x405FE5C: dect_open_handle (libdect.c:66) ==10731== by 0x804CBEB: main (main.c:108) ==10731== Address 0x41ff7d8 is not stack'd, malloc'd or (recently) free'd ==10731== ==10731== Invalid read of size 4 ==10731== at 0x408ECD3: event_add (in /usr/lib/libev.so.3.0.0) ==10731== by 0x804941E: register_fd (event_ops.c:36) ==10731== by 0x4078361: dect_fd_register (io.c:103) ==10731== by 0x4077C14: dect_netlink_init (netlink.c:358) ==10731== by 0x405FE5C: dect_open_handle (libdect.c:66) ==10731== by 0x804CBEB: main (main.c:108) ==10731== Address 0x41ff7c8 is 8 bytes after a block of size 88 alloc'd ==10731== at 0x4023FE0: malloc (vg_replace_malloc.c:236) ==10731== by 0x407897D: dect_malloc (utils.c:21) ==10731== by 0x4078486: dect_fd_alloc (io.c:56) ==10731== by 0x4077BBF: dect_netlink_init (netlink.c:352) ==10731== by 0x405FE5C: dect_open_handle (libdect.c:66) ==10731== by 0x804CBEB: main (main.c:108) ==10731== ==10731== Invalid read of size 4 ==10731== at 0x408ECF0: event_add (in /usr/lib/libev.so.3.0.0) ==10731== by 0x804941E: register_fd (event_ops.c:36) ==10731== by 0x4078361: dect_fd_register (io.c:103) ==10731== by 0x4077C14: dect_netlink_init (netlink.c:358) ==10731== by 0x405FE5C: dect_open_handle (libdect.c:66) ==10731== by 0x804CBEB: main (main.c:108) ==10731== Address 0x41ff7d4 is not stack'd, malloc'd or (recently) free'd ==10731== ==10731== Invalid read of size 4 ==10731== at 0x408ED2F: event_add (in /usr/lib/libev.so.3.0.0) ==10731== by 0x804941E: register_fd (event_ops.c:36) ==10731== by 0x4078361: dect_fd_register (io.c:103) ==10731== by 0x4077C14: dect_netlink_init (netlink.c:358) ==10731== by 0x405FE5C: dect_open_handle (libdect.c:66) ==10731== by 0x804CBEB: main (main.c:108) ==10731== Address 0x41ff7d4 is not stack'd, malloc'd or (recently) free'd ==10731== ==10731== Invalid write of size 4 ==10731== at 0x408ED35: event_add (in /usr/lib/libev.so.3.0.0) ==10731== by 0x804941E: register_fd (event_ops.c:36) ==10731== by 0x4078361: dect_fd_register (io.c:103) ==10731== by 0x4077C14: dect_netlink_init (netlink.c:358) ==10731== by 0x405FE5C: dect_open_handle (libdect.c:66) ==10731== by 0x804CBEB: main (main.c:108) ==10731== Address 0x41ff7d4 is not stack'd, malloc'd or (recently) free'd ==10731== ==10731== Invalid write of size 4 ==10731== at 0x408ECB5: event_add (in /usr/lib/libev.so.3.0.0) ==10731== by 0x804941E: register_fd (event_ops.c:36) ==10731== by 0x4078361: dect_fd_register (io.c:103) ==10731== by 0x4077C14: dect_netlink_init (netlink.c:358) ==10731== by 0x405FE5C: dect_open_handle (libdect.c:66) ==10731== by 0x804CBEB: main (main.c:108) ==10731== Address 0x41ff7d4 is not stack'd, malloc'd or (recently) free'd ==10731== --10731-- VALGRIND INTERNAL ERROR: Valgrind received a signal 11 (SIGSEGV) - exiting --10731-- si_code=1; Faulting address: 0x74616874; sp: 0x62bdea58 valgrind: the 'impossible' happened: Killed by fatal signal ==10731== at 0x3809F551: myvprintf_str (m_debuglog.c:530) ==10731== by 0x3809FD32: vgPlain_debugLog_vprintf (m_debuglog.c:877) ==10731== by 0x3802A555: vprintf_WRK (m_libcprint.c:111) ==10731== by 0x3802A617: vgPlain_printf (m_libcprint.c:143) ==10731== by 0x380286C6: vgPlain_assert_fail (m_libcassert.c:261) ==10731== by 0x656C501F: ??? sched status: running_tid=1 Thread 1: status = VgTs_Runnable ==10731== at 0x402331F: calloc (vg_replace_malloc.c:467) ==10731== by 0x4055394: nl_object_alloc (object.c:49) ==10731== by 0x404284F: nl_dect_cluster_alloc (cluster_obj.c:64) ==10731== by 0x4077C34: dect_netlink_init (netlink.c:148) ==10731== by 0x405FE5C: dect_open_handle (libdect.c:66) ==10731== by 0x804CBEB: main (main.c:108) Thanks for help me

2 3

Re: Problems with dectmon
by Patrick McHardy 03 Nov '10

03 Nov '10

Am 31.10.2010 21:03, schrieb Oscar Soriano Riera: > Hi Patrick > I compile and install the dectmon perfect, but when i will to execute the dectmon always get a segment default, here are the output kerneloops: For the last time, please use the linux-dect list for reporting problems. Also don't send your mail as reply to an arbitrary mail but start a new thread for a new subject. > *root@DECT:/usr/src/dectmon/src# ./dectmon * > **** glibc detected *** ./dectmon: free(): invalid next size (normal): 0x095bf5c8 **** > *======= Backtrace: =========* > */lib/i686/cmov/libc.so.6(+0x6b281)[0xb771b281]* > */lib/i686/cmov/libc.so.6(+0x6cad8)[0xb771cad8]* > */lib/i686/cmov/libc.so.6(cfree+0x6d)[0xb771fbbd]* > */usr/local/lib/libnl.so.3(nlmsg_free+0x83)[0xb78381d3]* > */usr/local/lib/libnl-dect.so.3(nl_dect_cluster_query+0x50)[0xb78450b0]* > */usr/lib/libdect.so.0(+0x1cc9d)[0xb781ec9d]* > */usr/lib/libdect.so.0(dect_open_handle+0xbd)[0xb7806e5d]* > *./dectmon[0x804cbec]* > */lib/i686/cmov/libc.so.6(__libc_start_main+0xe6)[0xb76c6c76]* > *./dectmon[0x8049021]* This unfortunately doesn't show the cause of the crash, the nlmsg_free() is definitely correct. It is also unreproducable here. Please try running dectmon under valgrind to see whether it can locate the real cause (valgrind src/dectmon).

1 0

Asterisk with cluster in PP mode
by NoOne 03 Nov '10

03 Nov '10

Hi ... I successfully ran asterisk with a cluster in FP mode with one handset. Now I tried to use asterisk acting as a PP so that it can accept calls from PSTN. I catched EMC and FPN of my base station via dect-llme-scan. Where do I pass the PIN code for access_rights_requests? When I want to start asterisk I get following error messages: netlink: cu: mode PP ARI: class A: EMC: 0d13 FPN: 126f4 netlink: FPC: full_slot,page_repetition,basic_a_field_setup,in_min_delay netlink: HLC: adpcm_g721_voice,gap_pap_basic_speech,standard_authentication,location_registration LCE: set default pmid e16c8 LCE: registered protocol 0 (Link Control) LCE: registered protocol 3 (Call Control) LCE: registered protocol 4 (Call Independant Supplementary Services) LCE: registered protocol 6 (ConnectionLess Message Service) LCE: registered protocol 5 (Mobility Management) netlink: MAC_ME_RFP_PRELOAD-req netlink: HLC: adpcm_g721_voice,gap_pap_basic_speech,standard_authentication,standard_ciphering,location_registration,ciss_service,clms_service,list_access_features [Nov 1 11:44:09] ERROR[3477]: chan_dect.c:2338 dect_load_module: Unable to set FP capabilities == Unregistered channel type 'DECT' Kind regards TheNoOne

2 1

Bug #6
by Tomcsányi Domonkos 31 Oct '10

31 Oct '10

Hello Everyone, I am struggling with this problem for almost two weeks now, please I need help, could someone figure out what is wrong here? http://dect.osmocom.org/trac/dect/ticket/6 Thanks, Domonkos Tomcsanyi

2 1

dectmon released
by Patrick McHardy 28 Oct '10

28 Oct '10

I've uploaded a first release of dectmon, a DECT protocol decoder. It can decode MAC, DLC and NWK-layer messages and show their content in a human readable form. See http://dect.osmocom.org/trac/dect/wiki/Siemens#Traces for examples. Details, including links to the git repository, can be found at http://dect.osmocom.org/trac/dect/blog/kaber-2010/10/27/dectmon_released

1 0

Re: Architecture and software development
by Oscar Soriano Riera 23 Oct '10

23 Oct '10

Hi Patrick The scenario that I find most attractive is 2, can associate with a PC with a card pcmcia to any type of FP either an asterisk or any other manufacturer's base seems exciting. I'll be anxious to try any new developments that take place in the software, if you think that the slides can be useful for the web I can send examples to illustrate the sources, since it is a topic largely unknown in Spain and could help. Anything that can help you be an honor for me. Thank you very much for your work Heavy greetings On Sat, 23 Oct 2010 18:29:29 +0200, Patrick McHardy wrote: > Am 21.10.2010 12:37, schrieb Oscar Soriano Riera: >> Hi Patrick >> >> I have a question about the architecture and software development >> today. >> I've prepared an image(Dect-labv1.0.jpg) on the 3 scenarios in which >> I >> work, basically would be the following: >> >> 1) DECT Terminals Connected to Asterisk >> This lab works perfectly, with the latest versions that have posted >> until today. >> >> 2) Connect a PC card pcmcia Dosh & Amand like a Portable Part (PP) >> You can use a pc with a pcmcia and associate as a PP to asterisk >> server-Dect for make calls with other users?, I have questions / >> problems as a register from the laptop to asterix >> >> 3) Linking two Asterisk servers using the DECT protocol to share >> calls >> between PBXs >> >> It is possible this configuration? > > Both 2) and 3) certainly can be done, but are not implemented - its > basically the same thing, in scenario 3) one of the asterisk servers > would pose as PP. It shouldn't be that much work to add support for > this to the asterisk dect channel plugin, I'd estimate a few hours.

1 0

Re: Problems during compiling dect_raw_event with lasted libdect
by Patrick McHardy 21 Oct '10

21 Oct '10

Am 17.10.2010 02:30, schrieb Oscar Soriano Riera: > Hi > I would like to install the lasted libdect modification , but on the make > step i see a posible problem with a pointer > > root@DECT:/usr/src/libdect# make > SUBDIR include/ > SUBDIR src/ > CC src/raw.c > src/raw.c: In function ‘dect_raw_event’: > src/raw.c:140: error: ‘slot’ undeclared (first use in this function) > src/raw.c:140: error: (Each undeclared identifier is reported only once > src/raw.c:140: error: for each function it appears in.) > src/raw.c:142: warning: passing argument 3 of ‘dh->ops->raw_ops->raw_rcv’ > makes integer from pointer without a cast > src/raw.c:142: note: expected ‘uint8_t’ but argument is of type ‘struct > dect_msg_buf *’ > src/raw.c:142: error: too few arguments to function > ‘dh->ops->raw_ops->raw_rcv’ > make[1]: *** [src/raw.o] Error 1 > make: *** [src] Error 2 Fixed now in git.

2 1

Asterisk DECT channel driver
by Patrick McHardy 15 Oct '10

15 Oct '10

I've written an asterisk DECT channel driver as part of an entire open source DECT stack available at http://dect.osmocom.org, which is attached to this email. The patch is not meant for merging at this time, there's still quite a bit of work to by done, but its in a good enough state that some review, especially of the interactions with asterisk, would be very welcome. The channel driver implements a DECT FP (Fixed Part, aka basestation), currently supporting G.726 audio and a few supplementary features like text messages and user authentication. Telephones can register with the FP using a procedure called "access rights requests", during which an authentication key and an extension is allocated for the telephone. When the telephone is active and in range to the FP, it performs a procedure called "location registration" (probably known from GSM) to announce it is ready to receive calls. The extension is then registered in the dialplan in a special context for the Dial() application in order to support completely dynamic setups where the amount of telephones is not known in advance. It is of course also possible to manually define dialplan rules for the telephones. The telephone specific subscription data (extension, keys, capabilities, ...) are stored in the ast_db and read again on startup. This part is not particulary pretty due to the inflexibility of ast_db(), specifically it needs various keys associated with each telephone, which are stored separately and associated again through the database path (/dect/<IPEI>/...). The ast_realtime architecture unfortunately also doesn't seem to be suitable for this since it appears to be lacking a way to iterate over data or query for multiple entries. Call connection can work in two ways: - when the phone supplies an existing extension during call setup, the call is immediately connected. - otherwise the call is placed in "OVERLAP SENDING" state and for each dialed digit, an extension lookup is performed and the call is connected as soon as an existing extension is dialed. I think that should be about everything where the driver's behaviour diverges from other drivers, the remaining parts should be pretty much self-explanatory. Comments and review welcome.

1 0

Siemens proprietary protocol
by Patrick McHardy 15 Oct '10

15 Oct '10

I'm currently trying to reverse engineer the proprietary Siemens protocol carried in <<ESCAPE-TO-PROPRIETARY>> information elements in order to better support the many features that Siemens implements in a proprietary fashion instead of following the standardized methods (see http://dect.osmocom.org/trac/dect/wiki/Siemens for more information). Since I only own two different kinds of telephones, it would be useful to get some more data. What I'm currently looking for is the debug output from the asterisk channel driver (with "dect set debug on") for the initial pairing, location registration and a call. If people could send me that it would be much appreciated. Please also include the telephone type and CC the linux-dect list. I'll also release a program to capture and decode NWK layer dumps between telephones and non-local FPs similar to the traces at http://dect.osmocom.org/trac/dect/wiki/Siemens#Traces in one or two weeks, I'll post an update then. Thanks!

3 5

Re: Posible Bug Asterisk : known formats found in format list (wav49|gsm|wav) on Asterisk git
by Patrick McHardy 15 Oct '10

15 Oct '10

Am 15.10.2010 01:48, schrieb Oscar Soriano Riera: > Hi PAtrick > I can see some errors in debug mode on asterisk problems with the audio: > > [Oct 15 01:17:05] WARNING[19906]: file.c:1396 ast_format_str_reduce: > ignoring unknown format 'wav49' > [Oct 15 01:17:05] WARNING[19906]: file.c:1396 ast_format_str_reduce: > ignoring unknown format 'gsm' > [Oct 15 01:17:05] WARNING[19906]: file.c:1396 ast_format_str_reduce: > ignoring unknown format 'wav' > [Oct 15 01:17:05] WARNING[19906]: file.c:1426 ast_format_str_reduce: no > known formats found in format list (wav49|gsm|wav) > [Oct 15 01:17:05] ERROR[19906]: app_voicemail.c:11702 load_config: Error > processing format string, defaulting to format 'wav' > > > I find in issues of Asterisk and i thing that this version is affected > > https://issues.asterisk.org/view.php?id=17709 > > I download the patch and solved the problem: > > wget > 'https://issues.asterisk.org/file_download.php?file_id=26764&type=bug' -O - > | patch -p0 Yeah, its not related to the DECT channel driver, but my asterisk version is slightly outdated. Unfortunately I can't resync easily without loosing the history since my master tree got corrupted a while ago due to filesystem errors. I'll probably try again to merge my tree with a fresh SVN import, if that doesn't work I guess I'll have to throw the history away. BTW, please use the linux-dect list (CCed) for anything related to my stack.

1 0

Re: Connecting Dect phones with softphones on asterisk new stack
by Patrick McHardy 14 Oct '10

14 Oct '10

Am 13.10.2010 20:11, schrieb Oscar Soriano Riera: > Hi everyone > > 1)Its posible connect the dect phones to softphone and vicevers , on > asterisk server and do calls between them? Yes. > 2)Its posible that two dect PP that are correct register on asterisk can > run on the same channel ? On the same carrier yes, on the exact same channel (timeslot + carrier) no, unless you have multiple transceivers. > I have 2 siemens a260 their connect perfect to Asterisk PF with dect > channel, but cant call between this two units, but in the log i can see > that the connection is ok: > *CLI> dect show portables > Name Extension > DECT-PT-600 600 > DECT-PT-601 601 > > When do a call from dect 600 to dect 601, doesnt work: > > LCE: link -1 (RELEASED): alloc > LCE: link 24 (ESTABLISHED): start SDU timer > LCE: link 24 (ESTABLISHED): new link: PMID: bb600 LCN: 0 LLN: 1 SAPI: 0 > > LCE: RX: 03 05 05 07 80 a8 00 c0 d3 ae 2a 06 07 a0 a5 01 > |..........*.....| > LCE: RX: 18 27 d6 18 e0 80 7b 06 81 00 02 18 01 44 > |.'....{......D| > LCE: link 24 (ESTABLISHED): stop SDU timer > LCE: link 24 (ESTABLISHED): new transaction: protocol: Call Control F: 0 > TV: 0 > CC: unknown transaction: msg type: 5 > CC-SETUP > parse {CC-SETUP} message > IE: <<PORTABLE-IDENTITY>> id: 5 len: 9 dst: 0xc655568 > type: IPUI (0) > PUT: N (IPEI) > EMC: 0c0d > PSN: 3ae2a > IE: <<FIXED-IDENTITY>> id: 6 len: 9 dst: 0xc69a448 > type: PARK (20) > class: A > EMC: 1182 > FPN: 0fac3 > IE: <<BASIC-SERVICE>> id: e0 len: 2 dst: 0xc5bd578 > call class: normal call (8) > service: basic speech default attributes (0) > IE: <<ESCAPE-TO-PROPRIETARY>> id: 7b len: 8 dst: 0xc65f940 > EMC: 2 > Content: 18 01 44 > LCE: link 24 (ESTABLISHED): set IPUI N EMC: 0c0d PSN: 3ae2a > LCE: link 24 (ESTABLISHED): confirm transaction: Call Control TV: 0 Role: > 1 > CC: call 0xc65e758 (CALL INITIATED): new call > CC: call 0xc65e758 (CALL INITIATED): MNCC_SETUP-ind > > CC: call 0xc65e758 (CALL INITIATED): MNCC_SETUP_ACK-req > build {CC-SETUP-ACK} message > IE: <<PORTABLE-IDENTITY>> id: 5 0xc655568 > type: IPUI (0) > PUT: N (IPEI) > EMC: 0c0d > PSN: 3ae2a > IE: <<FIXED-IDENTITY>> id: 6 0xc69a448 > type: PARK (20) > class: A > EMC: 1182 > FPN: 0fac3 > IE: <<SIGNAL>> id: e4 0xb2c48e2c > signal: ring tone on (0) > IE: <<DELIMITER-REQUEST>> id: a2 0xb2c48e38 > LCE: TX: 83 0d 05 07 80 a8 00 c0 d3 ae 2a 06 07 a0 a5 01 > |..........*.....| > LCE: TX: 18 27 d6 18 e4 00 a2 |.'.....| > [Oct 13 20:09:17] NOTICE[2365]: chan_dect.c:1000 dect_mncc_setup_ind: > Incoming call from DECT-PT-600 > > LCE: RX: 03 7b 2c 03 36 30 31 |.{,.601| > CC: call 0xc65e758 (OVERLAP SENDING): receive msg type 7b > CC: call 0xc65e758 (OVERLAP SENDING): CC-INFO > parse {CC-INFO} message > IE: <<MULTI-KEYPAD>> id: 2c len: 5 dst: 0xc606da8 > info: '601' > CC: call 0xc65e758 (OVERLAP SENDING): MNCC_INFO-ind It seems your dialplan is not set up correctly to direct outgoing calls to the PTs. When registering the PTs, an Dial() extension is automatically created in the context specified as "regcontext". Incoming calls are placed in the context specified as "context". Try adding "include => <regcontext>" to <context", that should make it work. > > LCE: RX: 03 7b 7b 05 81 00 02 30 00 |.{{....0.| > CC: call 0xc65e758 (OVERLAP SENDING): receive msg type 7b > CC: call 0xc65e758 (OVERLAP SENDING): CC-INFO > parse {CC-INFO} message > IE: <<ESCAPE-TO-PROPRIETARY>> id: 7b len: 7 dst: 0xc6680c0 > EMC: 2 > Content: 30 00 > CC: call 0xc65e758 (OVERLAP SENDING): MNCC_INFO-ind > CC: call 0xc65e758 (OVERLAP SENDING): <CC.01>: overlap sending timer > build {CC-RELEASE} message > IE: <<RELEASE-REASON>> id: e2 0xb2c491e8 > release reason: timer expiry (d) > LCE: TX: 83 4d e2 0d |.M..| > CC: call 0xc65e758 (RELEASE PENDING): MNCC_REJECT-ind: cause: > DECT_CAUSE_LOCAL_TIMER_EXPIRY > > LCE: RX: 03 5a e2 00 |.Z..| > CC: call 0xc65e758 (RELEASE PENDING): receive msg type 5a > CC: call 0xc65e758 (RELEASE PENDING): CC-RELEASE-COM > parse {CC-RELEASE-COM} message > IE: <<RELEASE-REASON>> id: e2 len: 2 dst: 0x9420ea0 > release reason: normal (0) > CC: call 0xc65e758 (RELEASE PENDING): MNCC_RELEASE-cfm > LCE: link 24 (ESTABLISHED): close transaction: Call Control TV: 0 Role: 1 > LCE: link 24 (ESTABLISHED): normal release > > LCE: recvmsg: Transport endpoint is not connected > LCE: link 24 (RELEASE_PENDING): normal release complete > LCE: link 24 (RELEASED): destroy > > > > I probe the demo test on extension.conf runs perfect with clients iax.conf > with softphones, but when i do a call to 600 extension this fails: > >>From the Softphone: > > LCE: link 24 (RELEASED): destroy > -- Accepting AUTHENTICATED call from 10.0.0.1: > > requested format = unknown, > > requested prefs = (), > > actual format = ulaw, > > host prefs = (), > > priority = mine > -- Executing [700@from-dect:1] Playback("IAX2/tst-1089", > "demo-echotest") in new stack > -- <IAX2/tst-1089> Playing 'demo-echotest.gsm' (language 'en') > == Spawn extension (from-dect, 700, 1) exited non-zero on > 'IAX2/tst-1089' > -- Hungup 'IAX2/tst-1089' > >>From the Softphone to dect phone siemmens A260: > > -- Accepting AUTHENTICATED call from 10.0.0.1: > > requested format = unknown, > > requested prefs = (), > > actual format = ulaw, > > host prefs = (), > > priority = mine > -- Executing [600@from-dect:1] Gosub("IAX2/tst-7748", > "stdexten(600,DECT/DECT-PT-600)") in new stack > -- Executing [600@from-dect:50000] NoOp("IAX2/tst-7748", "Start > stdexten") in new stack > -- Executing [600@from-dect:50001] Set("IAX2/tst-7748", > "LOCAL(ext)=600") in new stack > -- Executing [600@from-dect:50002] Set("IAX2/tst-7748", > "LOCAL(dev)=600") in new stack > -- Executing [600@from-dect:50003] Set("IAX2/tst-7748", > "LOCAL(cntx)=DECT/DECT-PT-600") in new stack > -- Executing [600@from-dect:50004] Set("IAX2/tst-7748", > "LOCAL(mbx)="600""@DECT/DECT-PT-600"") in new stack > -- Executing [600@from-dect:50005] Dial("IAX2/tst-7748", "600,20") in > new stack > [Oct 13 19:51:51] WARNING[2447]: app_dial.c:1940 dial_exec_full: Dial > argument takes format (technology/[device:]number1) > == Spawn extension (from-dect, 600, 50005) exited non-zero on > 'IAX2/tst-7748' > -- Hungup 'IAX2/tst-7748' > >

2 4

Re: Release of the DECT stack
by Patrick McHardy 30 Sep '10

30 Sep '10

On 30.09.2010 11:53, Rik Snel wrote: > Hi all, > > On Thu, Sep 23, 2010 at 01:08:43PM +0200, Patrick McHardy wrote: >> I've released my DECT stack, its available at http://dect.osmocom.org. >> There's also a small README file explaining its use, more documentation >> will probably follow over the next one or two weeks. > > That's great work! Thanks for the timing comments in the firmware; they > make the workings clearer for me. > > I have a Type III card with an LMX3161, for which support doesn't seem > to be complete (I get an OOPS at > > sc1442x.c: dev->radio_ops->rx_init(dev, off); > > because rx_init is NULL). > > Are there design issues that need to be addressed before LMX3136 support > can be easily implemented? (eg: labels in the firmware explicitly refer > to U2785) I've started working on the radio support for LMX3161 last weekend, the frequency calculations and radio programming is basically complete, however there are some differences in the firmware besides the radio initialization which I still need to analyze. I'm hoping we can use the same firmware for both radios. Will let you know once I have something testable. BTW, there is a new list for topics related to the stack: linux-dect(a)lists.osmocom.org

2 2

Re: Help Compiling libpcap support DECT
by Patrick McHardy 30 Sep '10

30 Sep '10

On 29.09.2010 20:24, Oscar Soriano Riera wrote: > > Hi > I try to install libpcap git, But i cant install: > > I Do #./CONFIGURE > perfect > > But when i do make the error is the next one: > > MAKE: *** NO HAY > NINGUNA REGLA PARA CONSTRUIR EL OBJETIVO `@DECT_SRC@', NECESARIO PARA > `LIBPCAP.A'. ALTO. > > In the makefile: > PSRC = pcap-linux.c pcap-usb-linux.c > @DECT_SRC@ > > I do a modification of Makefile and change @DECT_SRC@ to > libdect.c , but the same failed error. > > What is this value ? You might need to run autoreconf before configure. If that doesn't help, please post the configure output (in english).

1 0

Re: Curious startup of Asterisk + Dect stack 2.6.36-rc5+
by Patrick McHardy 28 Sep '10

28 Sep '10

Am 28.09.2010 01:04, schrieb Oscar Soriano Riera: > I see a curious startup with the new stack of Dect protocol. I have one > laptop (Debian+Dect DOSCH-AMAND pcmcia radio U2785B) and a computer > with DOSCH-AMAND PCI with the same kernel and compilation > > I do all instructions of http://dect.osmocom.org/README. When finish all > configurations and start the daemon Asterix in debug mode i can see the > next event on the log: > > 1) Start the daemon: > > # /etc/init.d/asterisk debug > > > == Registered channel type 'DECT' (Digital Enhanced Cordless > Telecommunications (DECT)) > == Parsing '/etc/asterisk/dect.conf': == Found > -- Registered extension context 'dect_register' (0xc548c10) in table > 0xc5b21c0; registrar: DECT > -- Added extension '601' priority 1 to dect_register (0xc548c10) > -- Added extension '602' priority 1 to dect_register (0xc548c10) > -- Added extension '603' priority 1 to dect_register (0xc548c10) > *dect_netlink_init: Object not found* This indicates the cluster doesn't exist. > *[Sep 28 00:31:22] ERROR[20318]: chan_dect.c:1905 dect_load_module: > Unable to initialize DECT handle* > > 2)Here's what I think that first create the cluster, and proceed to > activate FP mode to realize the call server: > > #dect-cluster-add --name cluster0 --emc 0x1182 --fpn 0x0fac2 --mode fp > #dect-cell-add --name cell0 --cluster cluster0 > #dect-transceiver-bind --transceiver trx0 --cell cell0 > > 3) Launch another time Asterix in Debug, and failed too: > > # /etc/init.d/asterisk debug > > > == Registered channel type 'DECT' (Digital Enhanced Cordless > Telecommunications (DECT)) > == Parsing '/etc/asterisk/dect.conf': == Found > -- Registered extension context 'dect_register' (0xbfc4d50) in table > 0xbebd608; registrar: DECT > -- Added extension '601' priority 1 to dect_register (0xbfc4d50) > -- Added extension '602' priority 1 to dect_register (0xbfc4d50) > -- Added extension '603' priority 1 to dect_register (0xbfc4d50) > *LCE: dect_lce_init: Permission denied* Asterisk is dropping permissions at startup, so you're unable to bind to the cluster. Try starting it as root using "asterisk -pfc". I'll look into fixing this, AFAIK asterisk retains the CAP_NET_ADMIN capability, so I'll probably adjust the permission checks to accept that. > *[Sep 28 00:33:56] ERROR[20438]: chan_dect.c:1905 dect_load_module: > Unable to initialize DECT handle* > > 4) The posible Workaround (I think that all my config is correct) to get > up the daemon Asterix is do this order: > > *delete the cluster:* > > #dect-cluster-delete --name cluster0 > #dect-cell-delete --cell cell0 > > *Detected broadcast message for all:* > > > Message from syslogd@WIFI at Sep 28 00:36:12 ... > kernel:[42723.933296] Oops: 0000 [#1] SMP > > Message from syslogd@WIFI at Sep 28 00:36:12 ... > kernel:[42723.933318] last sysfs file: /sys/module/nfnetlink/initstate > > Message from syslogd@WIFI at Sep 28 00:36:12 ... > kernel:[42723.934154] Process lt-dect-cell-de (pid: 20504, ti=d7a0a000 > task=f6b64c70 task.ti=d7a0a000) > > Message from syslogd@WIFI at Sep 28 00:36:12 ... > kernel:[42723.934184] Stack: > > Message from syslogd@WIFI at Sep 28 00:36:12 ... > kernel:[42723.934361] Call Trace: > > Message from syslogd@WIFI at Sep 28 00:36:12 ... > kernel:[42723.934927] Code: 39 83 08 02 00 00 74 07 89 d8 e8 04 da ff > ff 8d 65 f4 5b 5e 5f 5d c3 55 89 e5 57 56 53 89 c3 8b 40 28 85 c0 74 08 > 8b 08 8d 53 20 <ff> 51 04 0f b7 83 b4 03 00 00 31 f6 85 c0 74 48 83 ca > ff 0f bc > > Message from syslogd@WIFI at Sep 28 00:36:12 ... > kernel:[42723.935158] EIP: [<f8452d64>] dect_cell_shutdown+0x14/0x142 > [dect] SS:ESP 0068:d7a0bc90 > > Message from syslogd@WIFI at Sep 28 00:36:12 ... > kernel:[42723.935203] CR2: 0000000000000004 Please send the full oops message. > 5)Then start daemon on debug > *#/etc/init.d/asterisk debug* > > func_blacklist.so => (Look up Caller*ID name/number from blacklist > database) > == Registered channel type 'DECT' (Digital Enhanced Cordless > Telecommunications (DECT)) > == Parsing '/etc/asterisk/dect.conf': == Found > -- Registered extension context 'dect_register' (0xd3bcd50) in table > 0xd2b5608; registrar: DECT > -- Added extension '601' priority 1 to dect_register (0xd3bcd50) > -- Added extension '602' priority 1 to dect_register (0xd3bcd50) > -- Added extension '603' priority 1 to dect_register (0xd3bcd50) > > > And then the Daemon start "apparently" correct > > Some questions: > > 1) its posible that need create the cluster,cell and Rtx before launch > Asterix ? Yes, that's how its supposed to work. > 2)Its posible that need create all the componets of the cluster with and > only with user as asterisk? > > 3) When i run "*nl-link-list" *i can see all interfaces , but i cant > see "a dect interface" , its is normal ? > > # ./nl-link-list > lo loopback <loopback,up,running,lowerup> > eth0 ether 00:06:1b:de:ee:4c <broadcast,multicast> > eth1 ether 00:0c:f1:28:60:f4 <broadcast,multicast,up,running,lowerup> > pan0 ether 6a:08:e2:74:24:db <broadcast,multicast> There is dect-cluster-list, dect-cell-list and dect-transceiver-list for listing the respective DECT components.

2 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

linux-dect