<div dir="ltr">More info on this.<div><br></div><div><div> Yesterday I managed to configure the SPANs separately on the use o "mfcr2_advanced_protocol_file" with a tip given on another forum, so my above information is incorrect.</div><div><br></div><div> The only thing is that you have to state again the "mfcr2_advanced_protocol_file" parameter and specify a different config file as if you do not it will load the first file for all channels.</div><div><br></div><div>...</div><div>mfcr2_advanced_protocol_file=/etc/asterisk/span1_r2proto.conf</div><div>channel => 1-15,17-31</div><div><br></div><div>...</div><div>mfcr2_advanced_protocol_file=/etc/asterisk/span2_r2proto.conf</div><div>channel =>32-46,48-62</div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 1, 2016 at 3:27 PM, Aleks Honma <span dir="ltr"><<a href="mailto:aleks.honma@gmail.com" target="_blank">aleks.honma@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Just to add one info to this case trying to funnel down the problem.<div><br></div><div>Althought reluctant, today I got a telco's technician to come over to update Cisco 2900 IOS. After that they connect their testing equipment direct to the router's E1 interface and they made a test call from it. The result is that their test call was as fast as having our Legacy PBX connected to it. So I guess with that we rule out a possible router firmware version problem for MFCR2.</div><div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Sat, May 28, 2016 at 4:18 PM, Aleks Honma <span dir="ltr"><<a href="mailto:aleks.honma@gmail.com" target="_blank">aleks.honma@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span><div>Sure, how do I run the trace in openr2?</div><div><br></div><div>I am sending attached</div><div>- extract from Asterisk "full" log file</div><div>- call file</div><div>- and Asterisk CLI output</div><div><br></div></span><div>Here is an extract for the "full" log file showing an 8 second delay.</div><div><br></div><div><div>[2016-05-28 15:50:18] DEBUG[6547][C-00000000] chan_dahdi.c: Chan 1 - Sending category National Subscriber</div><div>[2016-05-28 15:50:23] DEBUG[6559] manager.c: Running action 'Login'</div><div>[2016-05-28 15:50:23] DEBUG[6559] manager.c: Running action 'Command'</div><div>[2016-05-28 15:50:23] DEBUG[6559] manager.c: Running action 'Command'</div><div>[2016-05-28 15:50:23] DEBUG[6559] manager.c: Running action 'Command'</div><div>[2016-05-28 15:50:24] DEBUG[5740] chan_sip.c: Auto destroying SIP dialog '_q_cRCFvo58BQH0taqD0xw..'</div><div>[2016-05-28 15:50:24] DEBUG[5740] chan_sip.c: Destroying SIP dialog _q_cRCFvo58BQH0taqD0xw..</div><div>[2016-05-28 15:50:26] DEBUG[6547][C-00000000] chan_dahdi.c: Enabled echo cancellation on channel 1</div><div>[2016-05-28 15:50:26] VERBOSE[6547][C-00000000] chan_dahdi.c: MFC/R2 call has been accepted on forward channel 1</div></div><div><br></div><div>I thought that enabling the mf_g1_tones.no_more_dnis_available=F would affect just group 0, channels 1-15,17-31 (from SPAN1, my E1 - Telco), but it seems to be a global config to all channels affecting also group 1, channels 32-46,48-62 (from SPAN2, legacy pbx). The option worked great when calling my SIP phone, but "killed" my legacy PBX returning "ERROR[914] chan_dahdi.c: MFC/R2 protocol error on chan 56: Multi Frequency Cycle Timeout". So I had to disable it. :-(</div></div><div class="gmail_extra"><br><div class="gmail_quote"><span>On Fri, May 27, 2016 at 1:16 PM, Moises Silva <span dir="ltr"><<a href="mailto:moises.silva@gmail.com" target="_blank">moises.silva@gmail.com</a>></span> wrote:<br></span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span>On Thu, May 26, 2016 at 1:39 PM, Aleks Honma <span dir="ltr"><<a href="mailto:aleks.honma@gmail.com" target="_blank">aleks.honma@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Moises you probably already know that, but man you rock!<div><br><div>Timer is gone and I get connected 3s earlier, so from 8s in my test we have gone done to 5s. </div></div></div></blockquote><div><br></div></span><div>Good :)</div><span><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>Now the issue seems that it is taking way too much time between sending out digits for ANI and DNIS. On my test above I was dialing just 5 digits (10315) that that is why it was taking 8s. For regular phone number where I dial 021ZZ XXXX-XXXX it takes about 15 seconds or more.</div><div><br></div><div>Is there any option to tweak this ?</div></div></div></blockquote><div><br></div></span><div>It may be a similar issue. Can I see the Asterisk debug log for this? or the openr2 protocol trace?</div></div></div></div>
<br></div></div><span>--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" rel="noreferrer" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-r2 mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-r2" rel="noreferrer" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-r2</a><br></span></blockquote></div><br></div>
</blockquote></div><br></div>
</div></div></blockquote></div><br></div>