Protocol mismatch error

[Tasha]

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 at 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 at 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