Commit Graph

110 Commits

Author SHA1 Message Date
Len a423f85116 Update dialplans.php 2019-05-22 11:06:26 -04:00
Len 95eaf6b2d6 Update dialplans.php 2019-05-22 10:35:59 -04:00
Robert Stevens be8c73036c fix sip_h_Diversion typo 2019-05-17 00:24:57 -07:00
konradSC 6d935e3c00 Bug Fix: Paging Controls in the wrong place (#4056)
* 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
2019-04-27 09:50:18 -06:00
FusionPBX 381c06db2d Update 010_user_exists.xml 2019-04-12 10:03:12 -06:00
FusionPBX 8fcd1bcbf4 Update 050_user_record.xml 2019-04-12 10:02:22 -06:00
FusionPBX 2d5743a9e0 Update 200_agent_status.xml 2019-04-11 18:07:54 -06:00
FusionPBX ee274b03db Update dialplan.php 2019-04-10 12:37:38 -06:00
FusionPBX 9e3bfdd7bc Update dialplan.php 2019-04-10 12:21:53 -06:00
FusionPBX e175a931a3 Update 030_is_loopback.xml 2019-03-27 10:57:53 -06:00
FusionPBX f6188357b1 Update 400_recordings.xml 2019-03-19 17:29:57 -06:00
FusionPBX 06b040c42f Update app_defaults.php 2019-03-14 23:53:15 -06:00
FusionPBX 9076f44d3a Update 400_recordings.xml 2019-03-14 23:42:09 -06:00
FusionPBX 7ba3fd49c5 Update app_defaults.php 2019-03-07 16:37:47 -07:00
FusionPBX bd18ccb7e6 Delete 520_follow_me_bridge.xml 2019-03-03 15:23:14 -07:00
emaktech a5ff016ef5 Retrieve gateway names with variables and failover (#4004)
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
2019-03-03 11:10:15 -07:00
FusionPBX 293386d72c Update 520_follow_me_bridge.xml 2019-02-20 09:06:34 -07:00
FusionPBX 823ce58d4c Update 010_user_exists.xml 2019-02-20 08:58:54 -07:00
FusionPBX b99054552f Update 520_follow_me_bridge.xml 2019-02-19 11:55:31 -07:00
konradSC 9727035305 Marker for identifying call as follow-me loopback (#3977)
* 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.
2019-02-18 18:41:24 -07:00
FusionPBX af7a313cad Rename 030_is_local.xml to 035_is_local.xml 2019-02-18 18:29:41 -07:00
FusionPBX 9d2b5d40c1 Update 010_user_exists.xml 2019-02-08 16:06:44 -07:00
FusionPBX 90e93e8977 Update 050_user_record.xml 2019-02-08 16:01:02 -07:00
FusionPBX fec97a0a20 Update dialplan_add.php 2019-02-05 18:36:45 -07:00
FusionPBX 9e9d9a6252 Update dialplan_detail_edit.php 2019-02-05 18:34:55 -07:00
FusionPBX 72274b9a50 Update dialplan_detail_delete.php 2019-02-05 18:33:18 -07:00
Valiantiam ca9a179549 Update 370_tone_stream.xml (#3964) 2019-01-17 13:10:40 -05:00
FusionPBX 254c1649eb Update 310_extension-to-voicemail.xml 2019-01-14 17:30:42 -05:00
FusionPBX ac746ac9c9 Update 900_voicemail.xml 2019-01-14 17:29:12 -05:00
FusionPBX cc17e23c91 Update 890_local_extension.xml 2019-01-14 17:28:40 -05:00
FusionPBX adaf7b0db4 Update 010_user_exists.xml 2019-01-14 17:27:54 -05:00
konradSC 365aebc308 Update BLF for agents when making changes in the GUI. Also use BLF as a speed dial for login/logout. (#3949)
* Create call_center_notify.php

Function for sending BLF notify to ELS.

* Update call_center_agent_status.php

* Update 200_agent_status.xml

* Update 200_agent_status.xml
2018-12-25 22:25:24 -07:00
FusionPBX cfa1b5a040 Update 330_vmain_user.xml 2018-12-14 14:42:34 -07:00
FusionPBX 8ff1b40633 Rename 507-call_forward_not_registered.xml to 507_call_forward_not_registered.xml 2018-12-08 10:53:58 -07:00
FusionPBX e9a487da68 Update 507-call_forward_not_registered.xml 2018-12-08 10:39:05 -07:00
FusionPBX db91ddadab Update 520_follow_me_bridge.xml 2018-12-08 10:35:17 -07:00
FusionPBX 94ad0df3ca Create 507-call_forward_not_registered.xml 2018-12-08 10:34:44 -07:00
FusionPBX 2cdc5f1b95 Update dialplan.php 2018-12-06 09:32:39 -07:00
konradSC d075905309 Update dialplan.php (#3934)
Adds the ability to set "dialplan_destination" db field from Upgrade App Defaults and xml dialplan templates.
2018-12-06 09:24:33 -07:00
FusionPBX 8dbcf22541 Update dialplan_edit.php 2018-12-05 17:20:09 -07:00
FusionPBX df36be9570 Update app_languages.php 2018-12-05 17:19:28 -07:00
FusionPBX df090e31dc Update app_config.php 2018-12-05 17:18:27 -07:00
FusionPBX b4db529ebd Update dialplans.php 2018-12-04 23:17:27 -07:00
konradSC f2ca04d256 Update 520_follow_me_bridge.xml (#3893)
Search through all SIP Profiles when looking up the Contact.
2018-12-03 10:44:33 -07:00
FusionPBX c424afc733 Update 230_group-intercept.xml 2018-11-29 10:18:19 -07:00
FusionPBX 3cc0ba3caf Update 320_vmain.xml 2018-11-14 10:14:42 -06:00
emaktech 18b6d4e920 Add record_append=false (#3854)
When re-recording the extension voice mail name the new recorded name is appended to the old recorded name file.  The new recorded name should replace the old recorded name.
2018-11-13 23:38:12 -06:00
emaktech 65ea399502 Add record_append=false (#3855)
When re-recording the extension voice mail name the new recorded name is appended to the old recorded name file.  The new recorded name should replace the old recorded name.
2018-11-13 23:37:53 -06:00
FusionPBX 95d3c4a00e Update 470_valet_park.xml 2018-11-02 17:21:21 -06:00
FusionPBX 6bc098778d Update 520_follow_me_bridge.xml 2018-11-01 12:29:10 -06:00