Commit Graph

117 Commits

Author SHA1 Message Date
FusionPBX a53e3eeba4
Update 010_caller_details.xml 2019-07-10 16:53:07 -06:00
FusionPBX 78acbee816
Update dialplans.php 2019-06-27 08:35:31 -06:00
FusionPBX cb7cf1bec2
Update dialplans.php 2019-06-27 08:08:41 -06:00
FusionPBX 85c8602c6f
Update app_config.php 2019-06-27 07:55:39 -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
chansizzle b368d6fc74 Update dialplans.php (#4277) 2019-06-11 12:32:25 -06:00
Len 2757dfc69a
Update dialplans.php 2019-05-22 11:06:26 -04:00
Len ef26a2e6f1
Update dialplans.php 2019-05-22 10:35:59 -04:00
Robert Stevens e59250cfd4 fix sip_h_Diversion typo 2019-05-17 00:24:57 -07:00
konradSC 9fd784046f 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 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 4924676825
Update app_defaults.php 2019-03-14 23:53:15 -06:00
FusionPBX 9cebeb75b7
Update 400_recordings.xml 2019-03-14 23:42:09 -06:00
FusionPBX 2585949b3d
Update app_defaults.php 2019-03-07 16:37:47 -07:00
FusionPBX ca0ba0ec39
Delete 520_follow_me_bridge.xml 2019-03-03 15:23:14 -07:00
emaktech f30457b12b 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 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
FusionPBX 7d62552c98
Update dialplan_add.php 2019-02-05 18:36:45 -07:00
FusionPBX 1b4e080b53
Update dialplan_detail_edit.php 2019-02-05 18:34:55 -07:00
FusionPBX a24d4b969d
Update dialplan_detail_delete.php 2019-02-05 18:33:18 -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
FusionPBX 51737ef033
Update dialplan_edit.php 2018-12-05 17:20:09 -07:00
FusionPBX 2f8eb25ce3
Update app_languages.php 2018-12-05 17:19:28 -07:00
FusionPBX 801e9cca19
Update app_config.php 2018-12-05 17:18:27 -07:00
FusionPBX ffc07fcd82
Update dialplans.php 2018-12-04 23:17:27 -07:00