it seems it work better in this way... chan = ast_channel_alloc(1, state, NULL, NULL, "", ext, ctx, 0, c, "TAPI/%d", (c + 1));
I don't know so well asterisk programming... please let me know if it seems correct to you! Eddi On Tue, Nov 11, 2014 at 6:11 PM, Eddi De Pieri <e...@depieri.net> wrote: > On Tue, Nov 11, 2014 at 4:24 PM, Luka Perkov <l...@openwrt.org> wrote: > >> Hi Eddi, >> >> I don't remember if that worked on owsip. But asterisk should support >> both channels. >> >> What about TAPI/0? I am unsure if we started naming the channels from 0 >> or 1... >> >> /* on asterisk user's side, we're using port 1-2. > * Here in non normal human's world, we begin > * counting at 0. > */ > > my doubt is: > > chan = ast_channel_alloc(1, state, NULL, NULL, "", ext, ctx, 0, c, > "TAPI/%s", "1"); > > If I understand correctly this is like a printf... so it seems it will > always map c to TAPI/1 > > I think it should be: > > chan = ast_channel_alloc(1, state, NULL, NULL, "", ext, ctx, 0, c, > "TAPI/%s", sprintf("%d", (c+1))); > > Let me try... > > Eddi > >
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel