On Fri, January 6, 2006 0:09, Daniele orlandi said:
> On Thursday 05 January 2006 23:21, you wrote:
>>
>> The 'open failed' errors occur on the connect commands...
>
> You are missing the /dev/visdn/cxc-control or /dev/visdn/netdev-control,
> this
> is how the dev directory should appear:
>
> # ll /dev/visdn/
> totale 0
> crw-------  1 root root 253, 1  5 gen 18:46 cxc-control
> crw-------  1 root root 251, 0  5 gen 18:46 netdev-control
> crw-------  1 root root 249, 0  5 gen 18:46 ppp
> crw-------  1 root root 250, 0  5 gen 18:46 streamport
> lrwxrwxrwx  1 root root     13  5 gen 18:46 timer -> timers/system
> drwxr-xr-x  2 root root     60  5 gen 18:46 timers
>
> 30-visdn.rules-oldudev is missing this line:
>
> KERNEL="cxc-control", NAME="visdn/cxc-control"
>

I'll add that and try again

> Why are you still using that old udev?
>

Because the udev in CentOS doesn't support new config format, and I am
trying to stay as close to standard as possible, as I'l have to do 3
identical servers once all works...

If this doesn't work, I'll try updating udev from src...

>> Jan  5 23:10:28 VERBOSE[8792] logger.c:   == Parsing
>> '/etc/asterisk/visdn.conf':
>>  Jan  5 23:10:28 VERBOSE[8792] logger.c:   == Parsing
>> '/etc/asterisk/visdn.conf' : Found
>> Jan  5 23:10:28 WARNING[8792] chan_visdn.c: Unknown configuration
>> variable
>> type_of_number
>> Jan  5 23:10:28 WARNING[8792] chan_visdn.c: Unknown configuration
>> variable
>> local_type_of_number
>
> Please re-update your tree, there have been a lot of configuration naming
> changes today, take visdn.conf.sample and customize it from scratch.
>
> Bye,
>
>
Will do! Thanks!

Have a good night!

-- 
F Peeters
  PIII 450 - 1 GB - * 1.2 - BRIstuff 0.3.0 Pre 1 - Florz patch
  2 Sweex HFC-PCI modes=2 sync_slave=2 timer_card=0
    Cologne HFC-S pins #52, #54, #55 connected in parallel for synching.
  AMD Duron 1GHz - 1GB - * 1.2.1
  2 Sweex HFC-PCI cards
_______________________________________________
Visdn-hackers mailing list
[email protected]
https://mailman.uli.it/mailman/listinfo/visdn-hackers

Reply via email to