Hi Luka, For me is the same... just to compliant comment inside source code:
/* on asterisk user's side, we're using port 1-2. * Here in non normal human's world, we begin * counting at 0. */ So you confirm that "TAPI/%s","1" map both port0 and port1 to TAPI/1 and you can't use asterisk extensions rule to choose which port to use to route the call.... Do you think we need to patch the source to use chan = ast_channel_alloc(1, state, NULL, NULL, "", ext, ctx, 0, c, "TAPI/%d", (c + 1)); or chan = ast_channel_alloc(1, state, NULL, NULL, "", ext, ctx, 0, c, "TAPI/%d", c); Eddi... On Tue, Nov 11, 2014 at 10:59 PM, Luka Perkov <l...@openwrt.org> wrote: > Hi Eddi, > > On Tue, Nov 11, 2014 at 07:11:13PM +0100, Eddi De Pieri wrote: > > it seems it work better in this way... > > > > > > > I don't know so well asterisk programming... please let me know if it > seems > > correct to you! > > I'm not sure. Why don't you use '"TAPI/%d", c' so the naming starts with 0? > > Luka >
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel