Restrict internal call-forward

[nknook]

Hi,

I have the following problem:
We have a few VIP's, who are not to be called directly (internal nor external). No problem I said, just give them a coverage path, and let the station always be in SAC mode. Calls to the VIP go to his/her secretary, easy, no?

But now I have a case where some (l)user forwards his own station to the VIP station. When you call this (l)users' extension, the call gets forwarded to the VIP and terminates there. This completely bypasses the SAC and/or forwarding of the VIP's station and results in a ringing VIP phone.

I have played around with COR calling restrictions (and also tennant partitioning) and Intercom groups and the like, but have not been able to prevent this from happening (without screwing up something else).

Anyone have any idea's? Am I missing something? Or is there really just nothing we can do about it (except for beating up users who forward their station to the VIP ).

Just disabling call-forward for everyone is not an option by the way.

Cheers,
Nico

 

[RTMCKEE]

While i was looking for an answer or work around on this I did find the "new" command list call-forwarding. That is pretty helpful, I used to work on a v6 and the only way to figure that out was to status each station.

RTMCKEE

 

[GroundRatt]

nknook,
Change the calling permissions to "no" on the user's stations COR to not be able to call the COR you assign the vip. This should solve your problem...

Steve
UTHCT

 

[tkinney]

once you find the culprit in list call-foward change their station cos to restrict call fwd-all calls and see if that eliminates them from fowarding their phone.

 

[mikeydidit]

What about instead of a coverage path on the VIP's phone put a call forward button on it? Then if by mistake someone does forward their phone to him, it will still go to the secretary's phone. If she does take a call that he needs to take he can hit the call forward button to deactivate and he can get his calls. Just my first thought.

Mike Jones
LSUHSC

 

[RTMCKEE]

also check display system-parameters coverage-forwarding
bottom of page it says: Coverage After Forwarding? it that set to yes?

RTMCKEE

 

[Bobg1]

RTMCKEE
"command list call-forwarding" Heck that was available at least as far back as v4.

 

[RTMCKEE]

DOH! i see that on our V5+m we have... You know what they say.. you learn something new everyday!

RTMCKEE

 

[nknook]

Thanks for the tips.

I know about the "list call-forwarding" command, but it's only usefull when it's too late. I (or rather the customer I'm working for) would like to find a way to prevent the forward from happening in the first place.

Also I played around with the COR calling permissions, and it's possible to block one station from calling another station (or any other object having a COR), and thus also preventing the forward, however, people need to be able to call the VIP (and end up with the secretary through coverage or forward of the VIP's phone). The problem with restricting through the COR is that the number is completely unreachable, and also calls can't be transferred to the VIP's station by the secretary (even though the secretary has permissions to call the VIP, and using intercom also doesn't work).

Using forward at the VIP's station instead of coverage also doesn't work, when you forward another station to the VIP, call's to that station will terminate at the VIP, no matter what it's status is (err, with the exception of disconnecting the VIP's phone of course, that would prevent it from ringing very well.. )

I'm currently looking into making the VIP's extension an EAS agent, and see if I can come up with something that way. I'll keep you posted, but suggestions are still welcome of course...