[Freeswitch-users] Best way to replicate include =>?

Michael Jerris mike at jerris.com
Mon Oct 20 14:26:32 PDT 2008

you can just as the last exten in your context do a transfer to the  
other context.


On Oct 20, 2008, at 5:11 PM, Michael Collins wrote:

>> Sure:
>> [include]
>> exten => 727,1,DoStuff
>> exten => 800,1,DoOtherStuff
>> [default]
>> include => include
>>  I know it's a simple case and not really an "example" but I'm really
>> just looking for a way for a context to just "plow through" another
>> context looking for a match before it returns "No Route" and aborts.
>> Not exactly elegant but sometimes it's just got to be done (I guess).
> Curious - why exactly must it some times be done? That is, what
> scenarios? The reason I ask is that the devs are pretty clever and  
> have
> anticipated just about any scenario. My guess is that there's an  
> elegant
> solution without stacking a bunch of includes, but I think we'd need  
> to
> hear about specific scenarios.
> Thoughts?
> -MC
>>  It looks like that's what transfer is supposed to do...  Is there
>> any way for me to just remove a condition on the match in [default]
>> and then just run through another context as defined by my args to
>> transfer before returning no route?  It would be nice to be able to  
>> do
>> multiple "includes" like so:
>>  <extension name="include" continue="true">
>>    <action application="transfer" data="${dialed_ext} XML include"/>
>>  </extension>
>>  <extension name="include2" continue="true">
>>    <action application="transfer" data="${dialed_ext} XML include2"/>
>>  </extension>
>>  I know it's ugly... :(

More information about the FreeSWITCH-users mailing list