<br><br><div class="gmail_quote">On Thu, Oct 1, 2009 at 2:19 PM, <span dir="ltr"><<a href="mailto:Russell.Mosemann@cune.org">Russell.Mosemann@cune.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Anthony Minessale <<a href="mailto:anthony.minessale@gmail.com">anthony.minessale@gmail.com</a>> said:<br>
<br>
> You might want to try the ozmod_pri instead of ozmod_isdn until the new<br>
> revision of ozmod_isdn is published into the source tree.<br>
<br>
</div>libpri took care of the problem with the transfer. Now, someone can call<br>
into FS from the Hicomm and then transfer the call to another extension<br>
on the Hicomm.<br>
<br>
A call from FS to the Hicomm still transfers to the switchboard. I'm not<br>
seeing any CID/ANI on the X-Lite. It shows up as "OpenZAP" and "1". Is<br>
there something like ngrep for the D channel of a PRI? It would be nice<br>
to see what data is being sent between FS and the Hicom.<br>
<font color="#888888"><br></font></blockquote><div>I believe the "OpenZAP" and "1" are coming from your conf file:<br>openzap.conf<br>
[span zt PRI_1]<br>
name => OpenZAP<br>
number => 1<br><br></div></div>As far as debugging with ozmod_libpri I believe the syntax is:<br>oz libpri debug 1 all <br><br>It will do a traditional libpri-style debug, just like "pri debug span 1" in Asterisk.<br>
-MC<br>