<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">2013/12/11 jg <span dir="ltr"><<a href="mailto:webaccounts@jgoettgens.de" target="_blank">webaccounts@jgoettgens.de</a>></span><br><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="im"><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
At the moment, I'm having trouble with lines going up and down all day long.<br>
I asked them to be created as P2P.<br>
Mostly but not always calls are passing in and out correctly.<br>
</blockquote></div>
I doubt that the energy-saving is causing the trouble. How do you get the ISDN-signal? Is it an S0-bus?</blockquote><div><br></div><div>I'm not 100% sure I'm correctly understanding these latter two questions.<br>
<br></div><div>Anyway, refering to <a href="http://en.wikipedia.org/wiki/Integrated_Services_Digital_Network">http://en.wikipedia.org/wiki/Integrated_Services_Digital_Network</a> / Basic rate Interface paragraph, my setup includes :<br>
</div><div>- a single network termination unit, installed and managed by telco, is connected to public network through 2 twisted pairs,<br></div><div>- this unit includes two small electronic cards,<br></div><div>- each card has two RJ45 sockets,<br>
</div><div>- each card is connected through a single Cat5 straight, 1m long patch cord to a single BRI port from my Patton box,<br></div><div>- both Patton's BRI ports are managed as a "hunt group" (for outbound calls),<br>
</div><div>- for inbound, I didn't checked but usually, Telco sends one call on one interface, the next one and the next interface.<br><br></div><div>So to summarize, (I think):<br></div><div>- I'm getting ISDN signal from two distinct copper pairs,<br>
</div><div>- it is not an S0-bus.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> If yes, I may be able to be of further help. Even if the connection goes down, it should not matter for P2MP connections.</blockquote>
<div><br></div><div>You mean: layer1 is down but layer3 remains up ?<br></div><div>I'm seeing layer3 going down for 4 or 5 seconds, then up again. This happens for both interfaces.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
But S0-bus problems can be nasty (though seen rarely these days).<div class="im"><br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
So, if I'm not mistaken, either :<br>
- these lines are configured as P2MP (and not as P2P as required),<br>
- I'm facing something else I've never met before.<br>
</blockquote></div>
I would bet on the 2nd choice.</blockquote><div><br><br></div><div>From memory, with a misconfiguration between P2P and P2MP, you get no call at all which is not the case. <br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class="im"><br>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
As these lines are up most of the time, I'm having a hard time to get any useful help by Telco beside "level 1" basic checks.<br>
<br>
For the record, these lines are terminated on my side with a Patton smartnode (most of the time, I use Digium BRI boards).<br>
During off hours, I'll try to check what happens when toggling to P2MP mode.<br>
</blockquote></div>
I doubt that you do get anything useful if you pick the wrong mode.<br>
<br>
Are you sure that your are not dealing with termination issues? <br></blockquote><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> Try sending a T.30 fax with fine resolution and ecm enabled when your connection is up. If it takes too long or fails, this is something to look at.</blockquote>
<div><br></div><div>Can you elaborate a bit ?<br></div><div>I'm using an old Asterisk 1.6.1 version there so I can't rely on T.38/T.30 gateway feature at the moment.<br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div class=""><div class="h5"><br>
<br>
jg<br>
<br>
<br>
-- <br>
______________________________<u></u>______________________________<u></u>_________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
<a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/<u></u>mailman/listinfo/asterisk-<u></u>users</a><br>
</div></div></blockquote></div><br></div></div>