Camp-on

[frank]

Hi

Can someone explain how does this Camp-On feature works?
I was able to disable it for the past 10 years, without looking at how it works.
10 years later, someone ask me to activate it, and I have no clue how to do that.
I followed the documentation without success. I can still call my busy extension, and my set will display "CALL BACK" or "VOICEMAIL" but no CAMP-ON.
Any hint appreciated

[vad]

Calling user - Phone feature COS - suffix Camp-on - allowed?
Called user - Dynamic state user - camp-on allowed or not
Called user - Phone feature COS - what about Rights - Protected (against barge-in etc.).

And called set type - NOE or IP Touch?

[frank]

Dynamic state Camp-On = True
Prefix for Busy Camp On = *#02
Suffix for Busy Camp On = 6

COS
Camp-on control = true
Waiting call consultation/access = true
camp-on waiting = true
camp on control = true

In the same COS where my callers and callees are
Prot against all barge in = false
prot. against set barge-in = false
port against barge in etc... = false


Test sets are ACD Authorized stations
2000 with VM, 8058s
2002 without VM, 8058s

2002 calls 2000 (internal or external)
if 1000 calls 2000 it displays "Call back" or "VM"
if 1000 (IPD) calls 2002 it displays "Call back"

[vad]

If you dial (on called set) - the camping control prefix or press the dynamic feature key Camp - something changed?

[alex]

This feature works by default.
So I would create a VM (or just a lab system) with empty DB and export Feature facilities from it then compare to the working DB to find what's different.

[frank]

If you dial (on called set) - the camping control prefix or press the dynamic feature key Camp - something changed?

No. I added a programmed key with the camp-on prefix and I see camp-on authorized.
still not working.