Re: [Freeswitch-dev] APP interface flags

2010-06-28 Thread Juan Antonio Ibañez Santorum
Thank you Rupa and Mathieu! 2010/6/28 Rupa Schomaker > 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 allow

Re: [Freeswitch-dev] APP interface flags

2010-06-27 Thread Rupa Schomaker
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

Re: [Freeswitch-dev] APP interface flags

2010-06-27 Thread Juan Antonio Ibañez Santorum
Where would be interesant to user SAF_SUPPORT_NOMEDIA and SAF_ROUTING_EXEC? Regards 2010/6/28 Mathieu Rene > > 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

Re: [Freeswitch-dev] APP interface flags

2010-06-27 Thread Mathieu Rene
> 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 (

[Freeswitch-dev] APP interface flags

2010-06-26 Thread Juan Antonio Ibañez Santorum
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/mai