Was Simul-Ring Removed from Add-On Line?

[VOIPoTim]

It's always been like that for most accounts, but we noticed today that Sim Ring had been pushed to some of the accounts, but it was never supposed to be available on any of the addon lines so we had to correct it for the ones it was.

I believe what happened is someone had said it was "missing" from their vPanel once for a cloned line and it got mass pushed out by a developer with the intention of "fixing" it even though it wasn't supposed to be there for a reason.

The addon lines are converted virtual numbers and it's meant to allow a user to have a VN directed to its own "line" instead of ringing only the main line.

Sim ring at minimum quadruples incoming call costs because at minimum we pay for the incoming part of the call AND the outgoing part of the call for the entire duration of all incoming calls (1x for incoming and outgoing costs 3x as much as incoming regardless = quadruple). So there's no way we'd be able to allow sim ring on both lines since that's potentially 8x the cost as normal for incoming calls if they use it actively on both lines. The other thing we have to be careful with is some users appeared to be using the cloned line as a way to get unlimited forwarding on a virtual number. This is actually what prompted me to investigate how some abusing users were racking up so much usage so quickly and I discovered that it omehow got added to the new cloned line vPanel template at some point.

We've tried to include as many of the standard features with the cloned line as possible since I know once people get used to them, they're hard to go without, but the ones that allow extra external usage (like sim ring) just are not feasible for a cloned line due to cost and the abuse issues with it. I know most users won't abuse it, but for every 10 of those, there is 1 that will majorly abuse it that makes up for it.

If there are users who had previously used it assuming it was part of it and legitimately had low usage with it, I am open to reviewing the usage on a case-by-case basis to look at re-enabling for some users. No promises though, but we're trying to be reasonble sine this was a mistake made by us that caused it to unintentionally get pushed out to some users.