To work around ssl certificate issues with wss connections, use
a single entry point for wss to the system and let nginx do the
internal proxying to the correct addresses.
If prepaid flag is changed in billing profile, all subscribers
of all contracts currently having this profile are updated.
If customer changes from prepaid profile to postpaid and vice versa,
all subscribers of this contract are updated.
If subscriber is created either in subscriber or customer view,
the prepaid pref is set if billing profile of its customer is
prepaid.
but update it, if one is supplied
sub edit_master is now explicitly denied to subscribers, as there is already
a lot of conditional logic there, we should consider to handle a logged in
subscriber separately. (This option is not exposed to subscribers anyway.)
See also 4967#c28533
A subadmin can use the field alias_select to select any number of alias
numbers, which he is allowed to manage. If he selects one, it moves
to this subscribers alias_numbers. If he unselects one, it moves to his
own alias numbers.
Don't delete voip_numbers (which was forgotten if the status
got set to terminated anyways), rather than free them by
undef'ing the subscriber_id and reseller_id.
Now also handle alias numbers with the outsourced subroutine
update_subscriber_numbers.
Plus remove some leftovers which are already handled by
this sub.
Actually use update_subscriber_numbers when updating a subscriber
and not only when creating one. Also handle all neccessary side effects.
Now we can switch our primary number to a number which has been
inactive (that is: did not belong to a subscriber) without an update error.
Outsource the handling of the primary number from
the subscriber controller to a util sub called
update_subscriber_numbers.
It also takes care to reuse a number that has
subscriber_id set to NULL which caused the original
problem in the ticket.
and provide a Modal showing the Detail of each.
Except the case when thedestination_set.name is called "quickset_*" and
it only has one entry.
In that case show the particular destinations of this destination set,
in order to not confuse a user who just configured a trivial cf via the simple view.
under Subscriber Preferences -> Call Forwards
Mantis: 3803, 3801