dbxe
/
fusionpbx
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
14,548 Commits 3 Branches 10 Tags 224 MiB
Commit Graph

87 Commits

Author SHA1 Message Date
agree 46d0423f6f Update 320_vmain.xml (#4645) 2019-09-24 10:21:26 -06:00
Nate 63a6db6f98 Dialplan XML: Integrate editor. 2019-09-09 10:20:54 -06:00
konradSC c13e8119ce Unset Call_timeout (#4520) 
I believe that call_timeout from the original destination should be unset, so that call_timeouts of the various follow-me destinations can work properly.
 2019-09-09 08:27:19 -06:00
FusionPBX 3d983c1b55
Update dialplan.php 2019-09-02 23:29:14 -06:00
FusionPBX cf3344707d
Update dialplan.php 2019-09-02 22:54:26 -06:00
Nate fabda61963 Misc Classes: Database class integration. 2019-09-02 15:57:18 -06:00
FusionPBX 3d4862b158
Update 500_follow-me-destinations.xml 2019-08-31 12:23:40 -06:00
FusionPBX c1a00f1c91
Update 500_follow-me-destinations.xml 2019-08-31 12:22:21 -06:00
FusionPBX 9531106f20
Update 500_follow-me-destinations.xml 2019-08-31 12:13:47 -06:00
FusionPBX cebfa4bf6e
Create 500_follow-me-destinations.xml 2019-08-31 12:07:28 -06:00
konradSC de141a836d 'record_append=false' for *732 (#4444) 
Without this setting the recordings will append. It may depend on FS versions, but better to be explicit.
 2019-08-16 14:43:00 -06:00
FusionPBX cc7438c53f
Update 010_user_exists.xml 2019-08-05 14:15:24 -06:00
FusionPBX a53e3eeba4
Update 010_caller_details.xml 2019-07-10 16:53:07 -06:00
ednt 3c77185b81 A typo at the last commit (#4313) 2019-06-27 07:06:40 -06:00
ednt 5289b34ade Add the description element for import (#4288) 
To make it possible to use descriptions for own dialplan xmls
 2019-06-18 08:05:50 -06:00
FusionPBX 66ccc863ed
Update 010_user_exists.xml 2019-04-12 10:03:12 -06:00
FusionPBX 4d413a749e
Update 050_user_record.xml 2019-04-12 10:02:22 -06:00
FusionPBX 20f86896c4
Update 200_agent_status.xml 2019-04-11 18:07:54 -06:00
FusionPBX 722c0482ff
Update dialplan.php 2019-04-10 12:37:38 -06:00
FusionPBX b15e692e6f
Update dialplan.php 2019-04-10 12:21:53 -06:00
FusionPBX 50db42eaab
Update 030_is_loopback.xml 2019-03-27 10:57:53 -06:00
FusionPBX a22a7e1bac
Update 400_recordings.xml 2019-03-19 17:29:57 -06:00
FusionPBX 9cebeb75b7
Update 400_recordings.xml 2019-03-14 23:42:09 -06:00
FusionPBX ca0ba0ec39
Delete 520_follow_me_bridge.xml 2019-03-03 15:23:14 -07:00
FusionPBX 5c65247dbb
Update 520_follow_me_bridge.xml 2019-02-20 09:06:34 -07:00
FusionPBX f879183ee9
Update 010_user_exists.xml 2019-02-20 08:58:54 -07:00
FusionPBX 8c36da3e87
Update 520_follow_me_bridge.xml 2019-02-19 11:55:31 -07:00
konradSC d8e1f249b6 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 edb3300dff
Rename 030_is_local.xml to 035_is_local.xml 2019-02-18 18:29:41 -07:00
FusionPBX 112266735c
Update 010_user_exists.xml 2019-02-08 16:06:44 -07:00
FusionPBX 36c8a0116c
Update 050_user_record.xml 2019-02-08 16:01:02 -07:00
Valiantiam 396c936a7f Update 370_tone_stream.xml (#3964) 2019-01-17 13:10:40 -05:00
FusionPBX c81e5c1114
Update 310_extension-to-voicemail.xml 2019-01-14 17:30:42 -05:00
FusionPBX 1eb9c1f0ee
Update 900_voicemail.xml 2019-01-14 17:29:12 -05:00
FusionPBX 848d33bc05
Update 890_local_extension.xml 2019-01-14 17:28:40 -05:00
FusionPBX 77dd11565c
Update 010_user_exists.xml 2019-01-14 17:27:54 -05:00
konradSC 65ebdf38ac 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 7264e21aa7
Update 330_vmain_user.xml 2018-12-14 14:42:34 -07:00
FusionPBX 0bbc81cee5
Rename 507-call_forward_not_registered.xml to 507_call_forward_not_registered.xml 2018-12-08 10:53:58 -07:00
FusionPBX 960d5fe83a
Update 507-call_forward_not_registered.xml 2018-12-08 10:39:05 -07:00
FusionPBX d7d7d385b4
Update 520_follow_me_bridge.xml 2018-12-08 10:35:17 -07:00
FusionPBX 93f8a253d0
Create 507-call_forward_not_registered.xml 2018-12-08 10:34:44 -07:00
FusionPBX c2e581d18e
Update dialplan.php 2018-12-06 09:32:39 -07:00
konradSC 0e7e802c1f 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
konradSC df086084ef 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 67dfa2d046
Update 230_group-intercept.xml 2018-11-29 10:18:19 -07:00
FusionPBX 297532104b
Update 320_vmain.xml 2018-11-14 10:14:42 -06:00
emaktech d79126bd28 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 04158b8a90 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 4bde5ef869
Update 470_valet_park.xml 2018-11-02 17:21:21 -06:00