On Mon, January 9, 2006 14:55, Francesco Peeters (Asterisk) said:
> On Mon, January 9, 2006 14:03, Daniele Orlandi said:
>> On Monday 9 January 2006 11:08, you wrote:
>>>
>>> I partially understand, but for me this will work, so I'll keep the
>>> patch
>>> for myself and apply whenever updating to a newer patch level! ;-)
>>
>> I may be adding a workaround based on a filter which specifies which
>> extensions do support overlap dialing so, it won't last for too much.
>> But
>> I
>> have to work on the EC, first :)
>
> Maybe you could make it an entry in the visdn.conf, based on the same
> format as the dial rules... I'll think on it and see whether I can figure
> out something helpful... ;-)
>
Been thinking... What if you would define a context for overlap dialling,
that way it could be included in the normal dialplan context with an
include, making only a single configuration step necessary...
In visdn.conf you could then have an 'overlap-context => visdn-overlap'
type of line...
I'll investigate and drop you a few line once I've got something more
concrete...
--
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
