<div class="gmail_quote">On Fri, Aug 7, 2009 at 11:28 AM, Norman Schmidt <span dir="ltr"><<a href="mailto:norman@omegatecnologia.com">norman@omegatecnologia.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
During months, the collect call blocking capabilities of OpenR2 were working<br>
like a charm, using it with Asterisk 1.4.21.2, Zaptel 1.4.12.1 and OpenR2<br>
1.1.0.<br>
<br>
Suddenly, some days ago all E1 R2 trunks we have with Oi (ex-Brasil Telecom<br>
here) started to accept collect calls. These calls are passing thru not<br>
signalled as collect calls anymore:<br>
<br></blockquote><div><br></div><div>That indeed suggest your telco is the one to blame, since they changed something.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I tried "mfcr2_double_answer=yes", but then:<br>
<br>
[Aug 7 11:54:52] NOTICE[9472]: chan_zap.c:961 zt_r2_on_call_init: New<br>
MFC/R2 call detected on chan 1.<br>
[Aug 7 11:54:57] WARNING[9472]: chan_zap.c:1199 zt_r2_write_log: Chan 1 -<br>
MF back cycle timed out!<br>
[Aug 7 11:54:57] ERROR[9472]: chan_zap.c:1202 zt_r2_write_log: Chan 1 -<br>
Protocol error. Reason = Multi Frequency Cycle Timeout, R2 State = Seize ACK<br>
Transmitd, MF state = Category Request Transmitted, MF Group = Backward<br>
Group A, CAS = 0x00<br>
DNIS = 0, ANI = , MF = 0x30<br>
[Aug 7 11:54:57] ERROR[9472]: chan_zap.c:1012 zt_r2_on_protocol_error:<br>
MFC/R2 protocol error on chan 1: Multi Frequency Cycle Timeout<br>
[Aug 7 11:55:02] NOTICE[9472]: chan_zap.c:1225 zt_r2_on_line_idle: Far end<br>
unblocked on chan 1<br>
</blockquote><div><br></div><div>However, adding mfcr2_double_answer does not may cause any protocol error due to MF cycle timeout, this is something else going on and we need a call file log in order to tell more about it.</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
Can I start to blame/curse Oi/Brasil Telecom only, or do I have any<br>
alternatives? Do someone else here on (south of) Brazil facing similar<br>
problems with ex-Brasil Telecom E1 trunks (now "Oi")?<br>
<br>
Norman</blockquote><div><br></div><div>The only 2 ways to block collect calls is double answer and proper tagging of collect calls via special tone, if none of those 2 work you cannot block them. Call your telco :-)</div>
<div> </div></div>-- <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>