Re: [OpenWrt-Devel] Generate configs for asterisk from uci
On Fri, 29 Aug 2008 03:33:34 pm RB wrote: > > > I'm only just starting to work with Asterisk, but integrating its > configuration into UCI will be a great start in that direction. Looks > nice! Well let me know how you go. I've got some changes/ bugfixes / tweaks. I have added musiconhold support (TIP: match the format for your music on hold to a single choice for stream encoding). Also hardware/reboot section. Allowing you to use url or program to cause your ATA to reboot and re-register with asterisk. Remember that 'extensions' is a generated dialplan context that contains all the extensions set up in your 'sip' and 'iax' sections. Check out the 'selfmailbox' option on sip/iax. This, combined with the 'mailbox' option, will allow you to dial your extension to get at your voicemail. Also for 'siptarget' (and 'iax' target) config sections, the 'alwaysinternational' setting has an interesting affect on the generated dialplan - check it out. /etc/init.d/asteriskuci script: http://pastebin.ca/1190086 /etc/init.d/asterisk: http://pastebin.ca/1190092 /etc/config/asteriskhttp://pastebin.ca/1190081 It is now working enough for me to use it for my home phone. If you replace your /etc/init.d/asterisk you just need to set ENABLE_ASTERISK=uci in your /etc/defaults/asterisk file to switch to UCI asterisk. ---8
Re: [OpenWrt-Devel] [Patch] Support for newer Sierra UMTS cards
Dirk Nehring wrote: > these cards are already included in 2.6.27, but needed in older kernel > (2.6.25, 2.6.26). Easy patch, please apply. > Applied in [12447], thanks! -- Nico ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] Missing rule in uci firewall
Hi, I think that a rule is missing in the default firewall configuration. The default INPUT chain is the following: Chain INPUT (policy DROP) target prot opt source destination DROP all -- anywhere anywherestate INVALID ACCEPT all -- anywhere anywherestate RELATED,ESTABLISHED ACCEPT all -- anywhere anywhere SYN_FLOOD tcp -- anywhere anywheretcp flags:FIN,SYN,RST,ACK/SYN input_rule all -- anywhere anywhere zone_lan all -- anywhere anywhere I think that the following rule is also needed: iptables -A INPUT -j zone_wan otherwise the hook provided for user defined rules doesn't work. In my configuration I'm using a wifi interface in client mode as wan interface. However for some reason when the firewall is started the wan interface is not reported as up and then the previous rule is not added to the INPUT chain. After the boot the file /tmp/state/network reports the wan interface as up. In fact if I restart the firewall manually everything works fine. Any ideas about why the wan is not reported as up at boot time? After all the firewall script is executed after the network script. ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org http://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
