MiCollab Client - how to stop users from sending calls to their own DID

[lundah]

Anyone have a good method of preventing users from sending calls to their own DID in MiCollab? This is the single biggest issue I have with new installs. Invariably, some user will set up their MiCollab status to send their calls to their own DID number, and wonder why they no longer get calls.

[sunspark]

the fastest method: send an email to users explaining to them that they should not use the Did number to send calls to the internal number.

If not :

You have to set up a loopback trunk and use ARS to route the call through it to strip out the unwanted digits :

so even when someone call from internal : 9 4455 7788 1234 = you absorb 9 digits and keep 1234

http://www.mitelforums.com/articles/3300/how-to-create-loopback-trunk.php

[lundah]

the fastest method: send an email to users explaining to them that they should not use the Did number to send calls to the internal number.

If not :

You have to set up a loopback trunk and use ARS to route the call through it to strip out the unwanted digits :

so even when someone call from internal : 9 4455 7788 1234 = you absorb 9 digits and keep 1234

http://www.mitelforums.com/articles/3300/how-to-create-loopback-trunk.php

That still creates a routing loop, and doesn't work in situations where the DID doesn't match the extension number.

[johnp]

I think billing the customer at a high rate for this when they call might stop it.

[lundah]

I think billing the customer at a high rate for this when they call might stop it.

Agreed. But I don't understand why Mitel makes it so easy for users to do it in the first place. Don't offer the DID number as a destination to send calls to in the client in the first place.

[johnp]

Think it is the same reason if you delete a user with a DID, the number is removed from the DID form instead of being made blank