FusionPBX
07fb1c2dc6
Remove follow_me_caller_id_uuid field.
2021-03-06 09:12:39 -07:00
Nate
a6b06ee8a9
Call Forward/Follow Me/DND: Update classes.
2019-11-30 21:42:15 -07:00
Nate
5656110199
Calls: Update classes.
2019-11-30 17:50:51 -07:00
Nate
bec5c647c9
List View: Updates to action classes.
2019-11-30 15:18:48 -07:00
Nate
bf5cb9c1a7
Minor class mods, Conference Centers list view updates.
2019-11-02 13:40:17 -06:00
Nate
b27410c600
Follow Me, Call Forward, DND: List view updates.
2019-10-29 20:18:51 -06:00
FusionPBX
a69c0b75d3
Update follow_me.php
2019-09-05 13:59:24 -06:00
FusionPBX
b662d05f78
Update follow_me.php
2019-08-31 11:52:43 -06:00
Nate
e4abb2eebe
Misc Classes: Database class integration.
2019-08-29 18:20:33 -06:00
Igor Olhovskiy
8361016fa5
FollowMe external number timeout fix ( #4438 )
2019-08-19 09:12:17 -06:00
FusionPBX
8b7647971d
Update follow_me.php
2019-08-16 15:05:50 -06:00
FusionPBX
ba16d22ed7
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
99c46af6bc
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
aaf7dacbb3
Only set "is_follow_me_loopback" if using loopback ( #4057 )
2019-04-24 13:36:14 -06:00
FusionPBX
7291298996
Update follow_me.php
2019-04-24 13:24:40 -06:00
konradSC
45456917e2
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
d527e45959
Update follow_me.php
2019-03-21 21:06:07 -06:00
FusionPBX
49797b36d8
Update follow_me.php
2019-03-21 20:05:48 -06:00
FusionPBX
4472f99bab
Update follow_me.php
2019-03-21 16:56:00 -06:00
FusionPBX
28c8c69843
Update follow_me.php
2019-03-04 13:03:31 -07:00
FusionPBX
9b0f97469d
Update follow_me.php
2019-02-21 17:45:43 -07:00
FusionPBX
d1d6d263f3
Update follow_me.php
2019-02-19 11:26:44 -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
b190190070
Update follow_me.php
2019-02-04 13:47:05 -07:00
FusionPBX
d6f2dc13f2
Update follow_me.php
2019-01-19 11:59:47 -07:00
FusionPBX
6cb5264b1c
Update follow_me.php
2019-01-19 11:39:04 -07:00
FusionPBX
4a9f0f5e38
Update follow_me.php
2019-01-19 11:36:40 -07:00
FusionPBX
c8b5819f1d
Update follow_me.php
2019-01-19 11:27:05 -07:00
konradSC
9e6da1078c
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
d22f5ab5e0
Update follow_me.php
2018-11-01 17:40:16 -06:00
FusionPBX
036dd12654
Update follow_me.php
2018-10-30 18:01:50 -06:00
FusionPBX
19f933bc40
Update follow_me.php
2018-10-05 19:23:27 -06:00
FusionPBX
903b566da9
Update follow_me.php
2018-10-05 13:39:47 -06:00
FusionPBX
bfbcda6736
Update follow_me.php
2018-08-14 12:02:43 -06:00
FusionPBX
3975ba0599
Update follow_me.php
2018-02-27 21:34:54 -07:00
FusionPBX
a1363b6e86
Update follow_me.php
2017-06-05 09:35:14 -06:00
Luis Daniel Lucio Quiroz
3e50f562a0
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
4d331049f9
Update follow_me.php
2017-03-02 15:45:50 -07:00
FusionPBX
6f031d582d
Update follow_me.php
2017-02-22 12:51:14 -07:00
FusionPBX
a269f765dd
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
63ebb355fa
Add. Support number_alias field as presence id in follow me/call forward ( #2075 )
2016-11-17 11:40:22 -07:00
FusionPBX
c50c228190
Update follow_me.php
2016-11-01 13:45:51 -06:00
reliberate
78d38090bc
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
markjcrane
3ea3fa4436
Use effective_caller_id_name and effective_caller_id_number with follow me.
2016-05-13 08:21:58 -06:00
markjcrane
72c366518f
Fix some warnings more warnings.
2016-05-11 13:23:53 -06:00
Harry G. Coin
bda6861f88
\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
skyeblueiscool
1524775135
Update follow_me.php
2016-02-05 16:47:36 -08:00
Alexey Melnichuk
bce90dfc55
Change. Use `destination_caller_id_number` as call follow_me caller id.
2015-10-23 14:55:48 +03:00
Alexey Melnichuk
ff7c7adb41
Change. Use toll_allow of extension who set follow me.
2015-08-14 13:35:50 +04:00
Alexey Melnichuk
4ba483f294
Fix. Empty comma in dialstring
2015-08-05 13:41:27 +04:00