The beauty of FreeSWITCH is that there is usually more than one way to skin a cat. Remember, FS is more than just a pbx, it's a back-to-back user agent so it can be different things in different directions. Having said that, if your changes are tested to work and make things easier to understand, then go ahead and document them. You can always add them to what's there as an alternative approach and let the reader decide. Thanks. Bote
-----Original Message----- From: Nicholas Schoonover Sent: Monday, 06 April, 2015 23:16 Subject: [Freeswitch-docs] call forwarding
I added some documentation around the logic that forwards calls to the 'is_forward' extension. I am new to Freeswitch and was stuck on how to set up call forwarding for a bit. I thought some more instruction around this area would help people who are new to the concepts in Freeswitch. Is this change logical?
In my personal set up I put this application,
<action application="set" data="call_forwarding_number=${hash(select/${domain_name}- call_forward/${destination_number})}"/>
into the 'check_call_forwarding' extension and got rid of the 'call_forwarding_number' extension. This made sense to me because it sets 'call_forwarding_number' in the extension before 'is_forward' rather than at the end of the dialplan. Am I misunderstanding something? Would this be a more logical way to format the documentation?
I used this as my check call forwarding extension and did away with the 'call_forwarding_number' extension at the bottom.
<extension name="check_call_forwarding" continue="true"> <condition field="destination_number" expression="^(\d+)$"> <action application="set" data="call_forwarding_number=${hash(select/${domain_name}-call_forward/${des tination_number})}"/> <action application="execute_extension" data="is_forward XML features"/> <action application="bridge" data="sofia/internal/$1@${domain_name}"/> </condition> </extension>
Sorry if I am being unclear or am misunderstanding something.
Thanks, Nicholas Schoonover