[luci] problems with LuCi Asterisk Webpages, Asterisk-XIP and running with Asterisk 1.4

[Jo-Philipp Wich]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Paul.

> 7] However, although the /etc/config/asterisk file is updated by changes to
> the webpages, none of the config files of the asterisk application are
> modified.

Verify that you're using asterisk-xip, not the asterisk package from
OpenWrt. Also check /etc/default/asterisk, ENABLE_ASTERISK must be set
to "uci".

> 8] after spending time searching across forums etc I did find some
> information (Michael Geddes Aug 2008 [a]) about trying to set up asteriskuci
> scripts and defaults etc but this did not work.

The asterisk-xip package is based on his work.

> 9] It is at this point I realised (doh!) that I couldn't verify that the
> asterisk-xip scripts were on the target - (../uci/sipiaxconf etc) - I
> suspect my build did not go correctly in the first place! (incomplete
> Makefile??)

The asterisk <-> uci glue resides in /usr/lib/asterisk/uci on the target
device.

> 10] tried bringing the scripts onto the running target , but again no
> success.

Please check whether they're present in the location mentioned above.

> Q1 - is it correct to say that I should be able to verify that the
> asterisk-xip UCI supporting files are on the target by looking in
> ../etc/init.d/ for these files?

See above.

> Q2 - is it correct that the Makefile that is on the svn LuCi trunk, that
> defines the luci-asterisk package, does not include the required package
> definitions for the asterisk-xip (although the luci-asterisk is built with
> asterisk-xip-core as a dependency) - i.e my Makefile is wrong, I need to
> explicitly add asterisk-xip just like every other package? or is this taken
> care of by the Makefile sitting in ../contrib/package/asterisk-xip folder?

The Makefile of contrib/package/asterisk-xip takes care of the
appropriate package definitions.

> Q3 - after building with asterisk-xip, should I be able to see asterisk-xip
> as a package in the build output just like luci-asterisk etc?

Yes.

> Q4 - is it possible to bring the required asterisk-xip UCI code onto a
> running target without having to build again?

Yes.

> Q5 Have I got it all wrong and that I need some other supporting code in
> addition to asterisk-xip?

No.

> Q5 - Does this set-up, with LuCi programming asterisk, actually work at this
> stage or I am trying this before its ready?

You're trying it before it's ready :) Maybe you noticed that
luci-asterisk is marked as broken atm. I'm in the middle of rewriting
the current pages, also it still needs lots of work until it's finished
but I'm on it.

The final goal is to simplify lots of the current pages by consolidating
many of the options into wizzards and automagic generation of config
bits. Also I'll reorder the menu layout to better present features.

The ultimate goal ist to merge asterisk-xip back into into mainline
OpenWrt but it's too early to tell any specifics.


I've a question; do you want to just test the current asterisk ui
progress or do you have any specific goals in mind? Maybe we could join
efforts then.


If you have further questions, don't hesitate to ask.


Greetings,
JoW
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAknNBvMACgkQdputYINPTPNyHACgn/IcwsgoFBC4VVTaqI6uPt+h
3osAn3s5Ko3XgUdfZMqfL9jDpskTtwy0
=9IjA
-----END PGP SIGNATURE-----