<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>Asterisk Ideas and Wishlist Repository</title>
	<link>http://www.asteriskideas.org</link>
	<description>What's missing in your Asterisk? Add it to this repository!</description>
	<pubDate>Tue, 29 Apr 2008 11:47:50 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
	<language>en</language>
			<item>
		<title>Support for SIPConnect</title>
		<link>http://www.asteriskideas.org/channels/sip/2008-04/support-sipconnect/</link>
		<comments>http://www.asteriskideas.org/channels/sip/2008-04/support-sipconnect/#comments</comments>
		<pubDate>Tue, 29 Apr 2008 11:47:50 +0000</pubDate>
		<dc:creator>fmenard123</dc:creator>
		
		<category><![CDATA[chan_sip]]></category>

		<category><![CDATA[sip forum]]></category>

		<category><![CDATA[tcp]]></category>

		<category><![CDATA[tls]]></category>

		<guid isPermaLink="false">http://www.asteriskideas.org/channels/sip/2008-04/support-sipconnect/</guid>
		<description><![CDATA[The SIP Forum has just released SIPconnect Technical Recommendation Version 1.0 on January 23, 2008.Press release: http://www.sipforum.org/content/view/297/171/Spec: http://www.sipforum.org/component/option,com_docman/task,doc_download/gid,134/Itemid,75/ The impact on Asterisk of the requirements of this specification have yet to be fully gaged. I propose that we start this topic to start going down the list of requirements for implementation of SIPconnect in *. francois@menards.ca
]]></description>
		<wfw:commentRss>http://www.asteriskideas.org/channels/sip/2008-04/support-sipconnect/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Enhance SIPPEER() to expose channel variables</title>
		<link>http://www.asteriskideas.org/channels/sip/2008-03/enhance-sippeer-expose-channel-variables/</link>
		<comments>http://www.asteriskideas.org/channels/sip/2008-03/enhance-sippeer-expose-channel-variables/#comments</comments>
		<pubDate>Mon, 17 Mar 2008 07:21:21 +0000</pubDate>
		<dc:creator>oej</dc:creator>
		
		<category><![CDATA[Dialplan functions]]></category>

		<category><![CDATA[chan_sip]]></category>

		<guid isPermaLink="false">http://www.asteriskideas.org/channels/sip/2008-03/enhance-sippeer-expose-channel-variables/</guid>
		<description><![CDATA[The SIPPER function needs to be enhanced to expose channel variables set by the peer with &#8220;setvar&#8221; in sip.conf. SIPPEER(adam,chanvar[CELLPHONE]) 
]]></description>
		<wfw:commentRss>http://www.asteriskideas.org/channels/sip/2008-03/enhance-sippeer-expose-channel-variables/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Show channels controlled by AGI or FastAGI</title>
		<link>http://www.asteriskideas.org/dev/agi/2008-02/show-channels-agi-fastagi/</link>
		<comments>http://www.asteriskideas.org/dev/agi/2008-02/show-channels-agi-fastagi/#comments</comments>
		<pubDate>Sun, 10 Feb 2008 10:23:17 +0000</pubDate>
		<dc:creator>oej</dc:creator>
		
		<category><![CDATA[AGI - Asterisk Gateway Interface]]></category>

		<category><![CDATA[cli]]></category>

		<category><![CDATA[fastagi]]></category>

		<guid isPermaLink="false">http://www.asteriskideas.org/dev/agi/2008-02/show-channels-agi-fastagi/</guid>
		<description><![CDATA[When running &#8220;show channels&#8221;, there&#8217;s no difference between channels controlled by a running AGI or FastAGI script and normal channels that execute the dialplan.I would like to see visually in the CLI that a channel is controlled by AGI.  
]]></description>
		<wfw:commentRss>http://www.asteriskideas.org/dev/agi/2008-02/show-channels-agi-fastagi/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Support for COPS (Common Open Policy Server)</title>
		<link>http://www.asteriskideas.org/general-networking/2008-02/cops-common-open-policy-server/</link>
		<comments>http://www.asteriskideas.org/general-networking/2008-02/cops-common-open-policy-server/#comments</comments>
		<pubDate>Tue, 05 Feb 2008 18:32:43 +0000</pubDate>
		<dc:creator>yem</dc:creator>
		
		<category><![CDATA[General networking]]></category>

		<category><![CDATA[cisco]]></category>

		<category><![CDATA[cops]]></category>

		<category><![CDATA[network]]></category>

		<category><![CDATA[qos]]></category>

		<guid isPermaLink="false">http://www.asteriskideas.org/general-networking/2008-02/cops-common-open-policy-server/</guid>
		<description><![CDATA[Support for COPS would be extremely handy, since it could send COPS messages to a Policy server to enable QoS or traffic flows on routers as soon as a call is started &#8230;. And most Cisco devices support that.RFCs are 2748 and 3084
]]></description>
		<wfw:commentRss>http://www.asteriskideas.org/general-networking/2008-02/cops-common-open-policy-server/feed/</wfw:commentRss>
		</item>
		<item>
		<title>AMI over Jabber</title>
		<link>http://www.asteriskideas.org/dev/ami/2008-02/ami-xmpp/</link>
		<comments>http://www.asteriskideas.org/dev/ami/2008-02/ami-xmpp/#comments</comments>
		<pubDate>Sun, 03 Feb 2008 09:21:50 +0000</pubDate>
		<dc:creator>oej</dc:creator>
		
		<category><![CDATA[AMI - The manager interface]]></category>

		<category><![CDATA[Development]]></category>

		<category><![CDATA[res_jabber (xmpp)]]></category>

		<category><![CDATA[jabber]]></category>

		<category><![CDATA[manager]]></category>

		<guid isPermaLink="false">http://www.asteriskideas.org/dev/ami/2008-02/ami-xmpp/</guid>
		<description><![CDATA[Interfacing the AMI manager port to the xmpp/jabber resource module would lead to many things.

Manager multicast - sending AMI events to a jabber conference room for multicasting to multiple clients
Manager unicast - sending AMI events to &#8220;buddies&#8221; as messages
Manager &#8220;chat sessions&#8221; for action/response handling

 Jabber is a scalable messaging infrastructure that&#8217;s already in place. Do you [...]]]></description>
		<wfw:commentRss>http://www.asteriskideas.org/dev/ami/2008-02/ami-xmpp/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Memcached dialplan function</title>
		<link>http://www.asteriskideas.org/functions/2008-01/memcached-dialplan-function/</link>
		<comments>http://www.asteriskideas.org/functions/2008-01/memcached-dialplan-function/#comments</comments>
		<pubDate>Wed, 30 Jan 2008 07:59:46 +0000</pubDate>
		<dc:creator>brettnem</dc:creator>
		
		<category><![CDATA[Functions]]></category>

		<category><![CDATA[clustering]]></category>

		<category><![CDATA[dialplan]]></category>

		<category><![CDATA[memcached]]></category>

		<guid isPermaLink="false">http://www.asteriskideas.org/functions/2008-01/memcached-dialplan-function/</guid>
		<description><![CDATA[Creation of an func_memcached dialplan Function. This has it&#8217;s advantages over the built in DB structure in that it&#8217;s all in memory and it can be hit by other servers as well to retrieve the same information (&#8221;network ready&#8221;).Memcached Libraries are at: http://www.danga.com/memcached/(pardon my syntax.. from memory here..)For example:
exten =&#62; s,1,Set(VMBOX=${MEMCACHEGET('vmbox-5125551212') })
exten =&#62; s,n,VoiceMail(${VMBOX})
Or perhaps [...]]]></description>
		<wfw:commentRss>http://www.asteriskideas.org/functions/2008-01/memcached-dialplan-function/feed/</wfw:commentRss>
		</item>
		<item>
		<title>XML configuration driver</title>
		<link>http://www.asteriskideas.org/res/realtime-res/2008-01/realtime-xml/</link>
		<comments>http://www.asteriskideas.org/res/realtime-res/2008-01/realtime-xml/#comments</comments>
		<pubDate>Thu, 24 Jan 2008 07:09:09 +0000</pubDate>
		<dc:creator>oej</dc:creator>
		
		<category><![CDATA[Realtime Drivers]]></category>

		<category><![CDATA[config]]></category>

		<category><![CDATA[realtime]]></category>

		<category><![CDATA[xml]]></category>

		<guid isPermaLink="false">http://www.asteriskideas.org/res/realtime-res/2008-01/realtime-xml/</guid>
		<description><![CDATA[I would like to see an XML based configuration format for the static configuration files. This can be done through the ARA realtime subsystem - without support for the dynamic objects, only static configurations. This would just be a wrapper around the current configuration files, but could optionally  add some error-checking with XML schemas. 
Example:
 &#60;device type=&#8221;peer&#8221; [...]]]></description>
		<wfw:commentRss>http://www.asteriskideas.org/res/realtime-res/2008-01/realtime-xml/feed/</wfw:commentRss>
		</item>
		<item>
		<title>H.323 support missing T.38 passthrough</title>
		<link>http://www.asteriskideas.org/channels/h323/2008-01/h323-support/</link>
		<comments>http://www.asteriskideas.org/channels/h323/2008-01/h323-support/#comments</comments>
		<pubDate>Wed, 23 Jan 2008 19:04:41 +0000</pubDate>
		<dc:creator>vhatz</dc:creator>
		
		<category><![CDATA[H.323 channels]]></category>

		<category><![CDATA[T.38]]></category>

		<guid isPermaLink="false">http://www.asteriskideas.org/channels/h323/2008-01/h323-support/</guid>
		<description><![CDATA[H323 is not supported enough on Asterisk. OH323 is no more, OOH323 does not seem to progress any more and chan_h323 is not actively developed any longer.H323 is still the prevalent protocol for VoIP calls between carriers (not between user and carrier).Also, T38 pass through is missing from H323.
]]></description>
		<wfw:commentRss>http://www.asteriskideas.org/channels/h323/2008-01/h323-support/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Radius authentication</title>
		<link>http://www.asteriskideas.org/3rdparty/2008-01/radius-authentication/</link>
		<comments>http://www.asteriskideas.org/3rdparty/2008-01/radius-authentication/#comments</comments>
		<pubDate>Wed, 23 Jan 2008 07:57:59 +0000</pubDate>
		<dc:creator>anontrol</dc:creator>
		
		<category><![CDATA[3rd party integration]]></category>

		<category><![CDATA[authentication]]></category>

		<category><![CDATA[radius]]></category>

		<guid isPermaLink="false">http://www.asteriskideas.org/3rdparty/2008-01/radius-authentication/</guid>
		<description><![CDATA[I would love to have an asterisk plug-in that would easily add authentication entries to RADIUS so that hotspot users could pay for their access by dialing a 1-900 number
]]></description>
		<wfw:commentRss>http://www.asteriskideas.org/3rdparty/2008-01/radius-authentication/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Avoid reading &#8220;meetme.conf&#8221; in each MeetMe execution</title>
		<link>http://www.asteriskideas.org/apps/meetme/2008-01/avoid-reading-meetmeconf-meetme-execution/</link>
		<comments>http://www.asteriskideas.org/apps/meetme/2008-01/avoid-reading-meetmeconf-meetme-execution/#comments</comments>
		<pubDate>Wed, 23 Jan 2008 07:54:49 +0000</pubDate>
		<dc:creator>ibc</dc:creator>
		
		<category><![CDATA[MeetMe]]></category>

		<category><![CDATA[realtime]]></category>

		<guid isPermaLink="false">http://www.asteriskideas.org/apps/meetme/2008-01/avoid-reading-meetmeconf-meetme-execution/</guid>
		<description><![CDATA[Now, app_meetme read &#8220;meetme.conf&#8221; file for each MeetMe() execution, this is an issue when using Static Realtime for meetme as I reported here:http://bugs.digium.com/view.php?id=11786Note that this report has been quickly closed as &#8220;no change required&#8221; because:&#8221;You&#8217;re right, the reason that this happens is because meetme.conf gets re-read at every execution of the application. However, I do [...]]]></description>
		<wfw:commentRss>http://www.asteriskideas.org/apps/meetme/2008-01/avoid-reading-meetmeconf-meetme-execution/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
