use SAF_SUPPORT_NOMEDIA if your app doesn't care about the state of the media.  Think things like set, lcr, hash, etc.  They don't touch the media so we don't need to ensure there is media when running the app.

SAF_ROUTING_EXEC allows one to specify that it is safe / possible to execute the app at route.  This allows one to run stuff prior to the actual execution of the dialplan.  You can read more about this on the wiki at:

http://wiki.freeswitch.org/wiki/Dialplan_XML#Inline_Actions

2010/6/28 Juan Antonio Ibañez Santorum <juanito1982@gmail.com>
Where would be interesant to user SAF_SUPPORT_NOMEDIA and SAF_ROUTING_EXEC?

Regards

2010/6/28 Mathieu Rene <mrene_lists@avgs.ca>
> SAF_NONE

Nothing
> SAF_SUPPORT_NOMEDIA
Means the channel wont be automatically pre_answered (in sip: it won't send a 183) before the application is started
> SAF_ROUTING_EXEC
Means the application can run within the routing state
> SAF_MEDIA_TAP
Means its setting up a media tap (media bug)

Mathieu Rene
Avant-Garde Solutions Inc
Office: + 1 (514) 664-1044 x100
Cell: +1 (514) 664-1044 x200
mrene@avgs.ca




On 2010-06-26, at 11:56 AM, Juan Antonio Ibañez Santorum wrote:

> Helllo!
>
>   When adding one APP interface, what is the meaning of following app flags?
>
> SAF_NONE
> SAF_SUPPORT_NOMEDIA
> SAF_ROUTING_EXEC
> SAF_MEDIA_TAP
>
> Regards


_______________________________________________
FreeSWITCH-dev mailing list
FreeSWITCH-dev@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-dev
http://www.freeswitch.org




--
-Rupa