<br>On Tue, Dec 22, 2009 at 9:08 AM, Khaled W Chehab <span dir="ltr"><<a href="mailto:kchehab@xplorium.com">kchehab@xplorium.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="EN-US" link="blue" vlink="purple">
<div>
<div style="border:none;border-bottom:solid windowtext 1.0pt;padding:0in 0in 1.0pt 0in">
<p class="MsoNormal" style="border:none;padding:0in">I have a 'CONGESTION' Status
with R2 protocol.</p>
<p class="MsoNormal" style="border:none;padding:0in">While testing this scenario
sip GW--<span style="font-family:Wingdings">à</span>Asterisk –Digium
E1 R2 Protocol<span style="font-family:Wingdings">à</span>Cisco E1 R2
protocol<span style="font-family:Wingdings">à</span>sip Gw</p>
<p class="MsoNormal" style="border:none;padding:0in">Find below my error and
configuration ,where are the errors in my configuration ?</p></div></div></div></blockquote></div><div><br></div><div>Typically you will be better off in the asterisk-r2 mailing list. Your message is more easily spotted by R2 people.</div>
<div><br></div><div>First thing is to check you have green status in your E1, do you? and make sure you have the right clock settings, I never configured a cisco but it seems you configured the cisco to be a slave and I don't see any port in DAHDI system.conf with master clock settings. (span=1,0,0...etc)</div>
<div><br></div><div>After that, enable R2 call logging using mfcr2_call_files=yes and pastebin the generated call file (if any), if no file is generated it means the problem is not at R2 but in your local trunk settings (may be dialing in the wrong group or something). </div>
<div><br></div>-- <br>Moises Silva<br>Senior Software Engineer<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>