What does disabling an Extension actually achieve..?

[tony]

So - I disabled some Extensions, then I used them to log in some Agents - I can log in, log out, make ready, etc. with no errors... so, my question is; what does disabling an Extension achieve?  Perhaps I need to reboot the TServer for the changes to take effect - but I sincerley hope not! 

Tony

[ecki]

Hi Tony, (Cool image)

Well, when I tested it, and that was a quite time ago, I haven't seen any difference. But probably you could nowadays achieve that apps like URS or SS will not register disabled DNs in TServer. 

E.

[tony]

Thanks ecki,

- I can monitor the Agent and Place in CCP, so I guess SS still works... haven't tried a CCP View on the actual Extension yet, so that might be worth a go...

Thanks!

TT

[SisB]

There is a section in CME help briefly explaining the State Enabled check.
Not sure if that answers your question.

Thanks

[ecki]

That sounds like you will endup with error in your strategy when you try to rout call to disabled DN.

hmmm.... quite pointless

[tony]

ok - in summary, then - a disbaled DN>Extension;

Will continue to be registered with the TServer...
Will not be registered with the URS...
Will continue to be displayed in CCP+/CCA, however it will not be registered with the SS...

It's a bit sporadic, to say the least...

Thanks guys!

TT

[Tambo]

Hi Tony,

I've found when we have had disabled extensions it puts the Place into "not monitored" and this has resulted in the Place and Extension still being targeted by the URS. But because the extension is disabled the calls clear to other VQs. The view in CCpulse shows it as not monitored and you could sit all day in that state and not get a call.