<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix"><br>
</div>
<blockquote
cite="mid:CAPeT9jgHDGDQJ-AOMSabFgmhYnbEv682LL41N6FjKcKb0hXthA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>
<br>
</div>
<div>Anyway, refering to <a moz-do-not-send="true"
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>
</div>
</blockquote>
"Termination Unit" probably means you get the T reference point and
behind the unit you do have the S reference point with a 4 wire
signal, which would be a standard setup.<br>
<blockquote
cite="mid:CAPeT9jgHDGDQJ-AOMSabFgmhYnbEv682LL41N6FjKcKb0hXthA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt
0.8ex;border-left:1px solid
rgb(204,204,204);padding-left:1ex">
<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>
</div>
</div>
</blockquote>
Maybe it is easier if you could mention your country and your
telco. I would guess you are either in France or Belgium, but I
could be wrong. Then we could simply lookup what is relevant for
you.<br>
<blockquote
cite="mid:CAPeT9jgHDGDQJ-AOMSabFgmhYnbEv682LL41N6FjKcKb0hXthA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<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>
</div>
</div>
</div>
</blockquote>
I said T.30 and not T.38 and the complete explanation would be
rather technical. In essence a T.30 fax with ecm enabled does not
react nicely to certain signaling errors and pertubations and this
is easy to detect. Most of the time I can guess what the problem is
when I see the type of error. Don't ask me how I learned this. Once
you know what to look for, Asterisk 1.whatever is very reliable as
far as facsimiles go.<br>
<br>
jg<br>
</body>
</html>