hello, i made a experimental patch for libpri to have NT/PTMP mode, <br>answers please on asterisk-dev at: <br><br><a href="http://lists.digium.com/pipermail/asterisk-dev/2009-May/038455.html">http://lists.digium.com/pipermail/asterisk-dev/2009-May/038455.html</a><br>
<br>Kristijan<br><br><div class="gmail_quote">2009/5/14 Kristijan Vrban <span dir="ltr"><<a href="mailto:vrban.lkml@googlemail.com">vrban.lkml@googlemail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
good news, i just made my isdn device ring! ok, after it ring, any<br>
timout then hangup up the chan, but a ringing from chan_dahdi via<br>
bri_net_ptmp -> isdn_device was possible.<br>
<br>
to made this happen i made some very crude hacks inside libpri, but i<br>
hope the next days i can offer a patch that offer some basic nt_ptmp<br>
functionality. Stay tuned :)<br>
<br>
Kristijan<br>
<br>
2009/5/12, Tzafrir Cohen <<a href="mailto:tzafrir.cohen@xorcom.com">tzafrir.cohen@xorcom.com</a>>:<br>
<div><div></div><div class="h5">> On Tue, May 12, 2009 at 08:05:49AM +0200, Olivier wrote:<br>
>> 2009/5/12 Kristijan Vrban <<a href="mailto:vrban.lkml@googlemail.com">vrban.lkml@googlemail.com</a>><br>
>><br>
>> > For those also need NT over PtMP, i started a initial patch for it. Very<br>
>> > limited at the moment, only one incoming call to chan_dahdi from one<br>
>> > device is possible. But i was pleasantly surprised that NT-ptmp is<br>
>> > working<br>
>> > anyway<br>
>> ><br>
>> > Get the patch here: <a href="http://bugs.digium.com/view.php?id=15048" target="_blank">http://bugs.digium.com/view.php?id=15048</a><br>
><br>
> Or rather: works in one direction: calls from a phone to the NT work.<br>
> Calls in the other way don't make it.<br>
><br>
> I believe it's much better than nothing, though, and I'm testing this<br>
> patch in the new debs I have.<br>
><br>
>> That is great news !!!<br>
>><br>
>> How best can we contribute to make this happen ?<br>
><br>
> Test this. Report how it (mis)behaves. And maybe try to trace why calls<br>
> from the NT side don't get through.<br>
><br>
>> Will the output most probably be a new libpri 1.4.X (or 1.6.X) or will it<br>
>> also include a new Asterisk version ?<br>
><br>
> For starters there will likely be some changes required in libpri .<br>
> There is no libpri 1.6.x and not likely to be one in the near future.<br>
> The "trunk" of libpri is branches/1.4 .<br>
><br>
> --<br>
> Tzafrir Cohen<br>
> icq#16849755 <a href="mailto:jabber%3Atzafrir.cohen@xorcom.com">jabber:tzafrir.cohen@xorcom.com</a><br>
> +972-50-7952406 mailto:<a href="mailto:tzafrir.cohen@xorcom.com">tzafrir.cohen@xorcom.com</a><br>
> <a href="http://www.xorcom.com" target="_blank">http://www.xorcom.com</a> <a href="http://iax:guest@local.xorcom.com/tzafrir" target="_blank">iax:guest@local.xorcom.com/tzafrir</a><br>
><br>
> _______________________________________________<br>
> -- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</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/mailman/listinfo/asterisk-users</a><br>
><br>
</div></div></blockquote></div><br>