On Mon, Jul 6, 2009 at 12:26 PM, Juan Carlos Gonzalez Cardona <span dir="ltr"><<a href="mailto:juancarlosg6@gmail.com">juancarlosg6@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I see tha the status of my sangoma change to Red, can be problem of my provider?<br></blockquote></div><br>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.<br>
<br>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.<br><br>-- <br>Moises Silva<br>Software Developer<br>
Sangoma Technologies Inc. | 50 McIntosh Drive, Suite 120, Markham ON L3R 9T3 Canada<br>t. 1 905 474 1990 x 128 | e. <a href="mailto:moy@sangoma.com">moy@sangoma.com</a><br>