One might be tempted to scoff at such a small set of paging controls, yet that would be a grave mistake. Though small stature they work just as well as their bigger brother whilst also providing their own unique experience to the user.
* Bug Fix: Paging Controls in the wrong place
Same fix as the one for the call recordings page. You couldn't type in a page number and press enter.
* Update dialplans.php
Previously, if a bridge statement was written with prepended variables to be passed, the gateway name would not be parsed and replaced. Additionally, if multiple bridges were used in failover in a single bridge statement separated by a pipe, only the first would be parsed and replaced.
I noticed this after upgrade to FreeSWITCH 1.8.5 (from 1.6.20) which changed failover behavior with multiple separate bridge statements. When network returns 486 BUSY, it will proceed to second bridge statement, initiating a second call. To allow failover and not have this behavior, you must write a single statement and separate your failover bridges with a pipe, this change allows the UI to show all gateway names on the line once saved.
Examples:
{fax_use_ecm=on}sofia/gateway/99b1234c-667c-4b31-9d2f-31d4f396abfa/$1
=> {fax_use_ecm=on}sofia/gateway/Gateway_Name/$1
sofia/gateway/0e70e123-00fd-4f0c-b525-bc7f6283cfa1/$1|sofia/gateway/99b1234c-667c-4b31-9d2f-31d4f396abfa/1$1
=> sofia/gateway/Gateway_One/$1|sofia/gateway/Gateway_Two/1$1
* Marker for identifying call as follow-me loopback
We need a way of the dialplan identifying calls that are generated by follow-me using loopback. This setting couple with a dialplan statement allows us to identify and set proper caller-id-name/number.
* Create 030_is_loopback.xml
Are you a follow_me call that is using the loopback interface?
Ok then, are you a user on the system?
Yes, ok. Let's set your outbound_caller_id_name and outbound_caller_id_number so that you show up correctly.
Thanks.
