New subject: Curious startup of Asterisk + Dect stack 2.6.36-rc5+

28 Sep 2010

      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:

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

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*

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:

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?

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.

Re: Curious startup of Asterisk + Dect stack 2.6.36-rc5+