nsinnovations/fusionpbx
2
0
Fork 0
mirror of https://github.com/fusionpbx/fusionpbx.git synced 2026-01-03 02:23:48 +00:00
Code Issues Packages Projects Releases Wiki Activity
13,407 Commits 4 Branches 11 Tags
ef9997be7beb0e319e38cba0f94de44c7ce99401
Commit Graph

125 Commits

Author SHA1 Message Date
FusionPBX
b7c68806ea Update follow_me.php 
Commenting out origination caller as it breaks caller id for calls that go through a ring group and then to follow me.
 2019-06-03 15:08:37 -06:00
konradSC
9727991213 Set caller-id for Follow-me using Bridge method (#4059) 
This keeps the same caller-id method for loopback, but adds in a method for caller-id using bridge.
 2019-04-27 09:41:00 -06:00
konradSC
9427b3bdf1 Only set "is_follow_me_loopback" if using loopback (#4057) 2019-04-24 13:36:14 -06:00
FusionPBX
d8b2b6f912 Update follow_me.php 2019-04-24 13:24:40 -06:00
konradSC
cf6ec78beb Follow-me Dialstring Bugfix (#4055) 
Set the follow-me dial_string so the sofia_contact will work with multiple SIP profiles.
 2019-04-24 08:57:02 -06:00
FusionPBX
d30fcbb6d1 Update follow_me.php 2019-03-21 21:06:07 -06:00
FusionPBX
9e326e8a39 Update follow_me.php 2019-03-21 20:05:48 -06:00
FusionPBX
9b595ebc90 Update follow_me.php 2019-03-21 16:56:00 -06:00
FusionPBX
ddc46f8901 Update follow_me.php 2019-03-04 13:03:31 -07:00
FusionPBX
9e8ad4153c Update follow_me.php 2019-02-21 17:45:43 -07:00
FusionPBX
01b9cdff3a Update follow_me.php 2019-02-19 11:26:44 -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
abc927dfde Update follow_me.php 2019-02-04 13:47:05 -07:00
FusionPBX
9e1c8a3252 Update follow_me.php 2019-01-19 11:59:47 -07:00
FusionPBX
732546b653 Update follow_me.php 2019-01-19 11:39:04 -07:00
FusionPBX
33689799d7 Update follow_me.php 2019-01-19 11:36:40 -07:00
FusionPBX
2928f13f48 Update follow_me.php 2019-01-19 11:27:05 -07:00
konradSC
23340a361e Update follow_me.php (#3885) 
Escape the single quote so the sql query will work correctly.
 2018-11-30 14:12:12 -07:00
FusionPBX
6dfd86d50d Update follow_me.php 2018-11-01 17:40:16 -06:00
FusionPBX
a39e350de1 Update follow_me.php 2018-10-30 18:01:50 -06:00
FusionPBX
af4b96fbb3 Update follow_me.php 2018-10-05 19:23:27 -06:00
FusionPBX
8f044db0e0 Update follow_me.php 2018-10-05 13:39:47 -06:00
FusionPBX
d29f1b9b84 Update follow_me.php 2018-08-14 12:02:43 -06:00
FusionPBX
bb30c81efc Update follow_me.php 2018-02-27 21:34:54 -07:00
konradSC
b192a96f84 Add Device Feature Sync (#2905) 
* Update lua.conf.xml

Hook the feature_event lua script to Freeswitch "PHONE_FEATURE_SUBSCRIBE" events.

* Create index.lua

* Create feature_event_notify.lua

* Update call_forward.lua

Add trigger for feature sync.

* Update do_not_disturb.lua

Add trigger for feature sync.

* Update call_edit.php

* Create feature_event_notify.php

* Update index.lua

disable logging
 2017-11-09 12:09:56 -07:00
FusionPBX
abd1607f11 Update call_forward.php 2017-10-07 23:34:38 -06:00
FusionPBX
72779123f1 Create call_forward.php 2017-06-09 10:27:32 -06:00
FusionPBX
0595259ad2 Update follow_me.php 2017-06-05 09:35:14 -06:00
FusionPBX
188c34aadb Update call_forward.php 2017-05-26 15:59:14 -06:00
Luis Daniel Lucio Quiroz
2b5926ffd7 Fix the CID (#2588) 
* Fixes CID

Although you already had somehow fixed the caller id here. you need to put origination and effective. For some reason, not all carriers get the CID from the same field in the SIP payload. origination_* and effective_* affects different parts of the SIP invite.

* Fix the CID


Although you already had somehow fixed the caller id here. you need to put origination and effective. For some reason, not all carriers get the CID from the same field in the SIP payload. origination_* and effective_* affects different parts of the SIP invite.

* Update follow_me.php

* Update call_forward.php
 2017-05-26 15:41:50 -06:00
FusionPBX
7e81e46692 Update call_forward.php 2017-03-02 16:37:07 -07:00
FusionPBX
2cfcb73c4f Update follow_me.php 2017-03-02 15:45:50 -07:00
FusionPBX
78876e08d2 Update follow_me.php 2017-02-22 12:51:14 -07:00
FusionPBX
9aa1133ea6 Update 
Fix the dial string used with follow me when the dial_string is set in default settings.
 2017-01-06 15:49:38 -07:00
Alexey Melnichuk
c30eb90839 Add. Support number_alias field as presence id in follow me/call forward (#2075) 2016-11-17 11:40:22 -07:00
FusionPBX
86fc5c9f51 Update follow_me.php 2016-11-01 13:45:51 -06:00
FusionPBX
305651724b Update call_forward.php 2016-11-01 13:37:43 -06:00
reliberate
ed50859364 Call Control: Minor form layout mods, add Default Setting to control Follow Me Destination count and default Timeout value, integrate ORM. 2016-10-05 01:19:05 -06:00
FusionPBX
630f19fde1 Update call_forward.php 
Add 'sip:' as shown in the 1884 pull request.
 2016-09-01 22:31:23 -06:00
de-jens
71bac37219 add Diversion Header to dail string (#1816) 
* added Diversion Header to dail string

* added Diversion Header to dail string
 2016-08-15 09:20:02 -06:00
markjcrane
f024039a02 Use effective_caller_id_name and effective_caller_id_number with follow me. 2016-05-13 08:21:58 -06:00
markjcrane
a4400b2497 Fix some warnings more warnings. 2016-05-11 13:23:53 -06:00
Harry G. Coin
91a92d8e5e \r\n --> \n 
Cause all the .php files containing lines ending with \r\n to instead end with \n.

DYI with:

find fusionpbx -type f -name '*.php' -exec dos2unix '{}' \;
 2016-04-25 20:30:23 -05:00
mafoo
d408cf2fbc WhitespaceClean-app/batch_1 
whitespace pass over files
for reference regex that was used s/[ \t]+(\r?\n)/\1/
 2016-03-11 11:56:29 +00:00
skyeblueiscool
dcc64101be Update follow_me.php 2016-02-05 16:47:36 -08:00
Alexey Melnichuk
a56e1e94a3 Change. Use destination_caller_id_number as call follow_me caller id. 2015-10-23 14:55:48 +03:00
Alexey Melnichuk
42e45e24f4 Change. Use destination_caller_id_number as call forward caller id. 
This is same value which uses by `Outbound CallerID Number` for extension.
 2015-10-23 14:40:29 +03:00
FusionPBX
8c8e3ce3c3 Merge pull request #1150 from moteus/save_disabled_forwadd_number 
Fix. Allow change Call Forward number without enable it.
 2015-09-09 09:32:22 -06:00
Alexey Melnichuk
8391e996f0 Fix. Allow change Call Forward number without enable it. 2015-09-09 16:26:41 +04:00
markjcrane
bde805bd4c Fix DND use error/user_busy instead of loopback/*99[extension] 2015-09-08 14:12:01 -06:00