[asterisk-r2] Block Near End

Moises Silva moises.silva at gmail.com
Tue Sep 21 14:02:03 CDT 2010


If you have /etc/dahdi/system.conf as:

cas=1-15:1101

That initialize the trunks to BLOCK when the driver starts.

Each time asterisk starts, I always put the lines to IDLE.

There is currently no way to start Asterisk without setting the trunks to
IDLE, but it should not be hard to add an option to asterisk in
chan_dahdi.conf to start them blocked. Something like
mfcr2_init_state=blocked, which obviously would default to "idle".

I don't have time right now though to work on this feature. If you send me a
patch I can include it. Otherwise I will find some time may be in a couple
of weeks to do it.

Moises Silva
Senior Software Engineer
Sangoma Technologies Inc. | NEW 100 Renfrew Drive, Suite 100, Markham ON L3R
9R6 Canada
t. 1 905 474 1990 x128 | e. moy at sangoma.com



On Tue, Sep 21, 2010 at 2:50 PM, Peron, Guilherme DE Santi <
guilherme.peron at siemens-enterprise.com> wrote:

>  Hi,
>
> Does anybody know how I initialize the trunks in block state by our side?
>
> Thanks,
> Guilherme
>
>
>
> --
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
>
> asterisk-r2 mailing list
> To UNSUBSCRIBE or update options visit:
>   http://lists.digium.com/mailman/listinfo/asterisk-r2
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-r2/attachments/20100921/bda21296/attachment-0001.htm 


More information about the asterisk-r2 mailing list