[asterisk-r2] Problem R2

[Juan Carlos Gonzalez Cardona]

Hi, is solved, the problem was of my Provider, because in this city before
not existe technology E1 is the first company installing this, and have some
problems, ok, thanks everyone.

2009/7/6 Moises Silva <moises.silva at gmail.com>

> On Mon, Jul 6, 2009 at 12:26 PM, Juan Carlos Gonzalez Cardona <
> juancarlosg6 at gmail.com> wrote:
>
>> I see tha the status of my sangoma change to Red, can be problem of my
>> provider?
>>
>
> From what I see you may be doing more than one thing wrong, having CCS in
> the dahdi configuration is suspicious since chan_dahdi should have not been
> loaded with mfcr2 signaling, the driver checks if the hardware configuration
> matches the desired telephony signaling in chan_dahdi.conf, in this case
> when using signaling=mfcr2 in chan_dahdi, IIRC, the chan_dahdi.so driver
> checks if the hardware signaling is CAS and therefore should have failed to
> start, which makes me think you're doing something else wrong.
>
> In anycase, your first goal should be have green light in the hardware
> before even trying to start Asterisk. May be the telco is giving you a PRI
> link and you think it's an R2 link.
>
> --
> Moises Silva
> Software Developer
> Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R
> 9T3 Canada
> t. 1 905 474 1990 x 128 | e. moy at sangoma.com
>
> _______________________________________________
> --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
>



-- 
Juan Carlos Gonzalez C.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-r2/attachments/20090706/532d3b25/attachment.htm