Cannot login to Symposium, only default ACD?

[Utreg]

Hi,
I've created a new ACD Queue and programmed a M3904 in that Queue.
The phoneset is aquired but when the user logs in it shows ACD PRIO so it does not login to Symposium but into default ACD.
I've copied the phoneset from a working (other ACD Queue) set and it is aquired so looks like the set is programmed fine.

When I compare the ACD programming I notice a difference.
The working ACD shows:
AACQ YES
ASID 16
SFNB
USFB 1 3 4 5 6
CALB 1 3 4 5 6 8 11

But I don't see these prompt when checking the new ACD queue.
Could this be my problem?

The NTP states: AACQ Application Acquired Queue nxcc-22
(NO) The ACD DN is not acquired by the application
YES The ACD DN is acquired by the application

I don't know how to get the AACQ prompt; when I do a change on the working ACD or on the non-working ACD that prompt does not pop up.
The ACD queue loks "not aquired" but don't know how to fix that.

Thanks 4 tips to sort this out.

 

[Imstillhere]

Did you build the cdn in Configuration under symposium?

 

[Utreg]

Yes; CDN config is up'n'running (and defaults to the new ACD)
Looked like the ACD has to be aquired but have never have to do that?

 

[trvlr1]

Can you log in to this phone using an agent ID from another queue that works? You would log in to their old queue, but that would point you towards a phone programming issue, or a Symposium programming issue.

 

[Utreg]

Thanks for your reply.
No, login is not possible; still ACD PRIO message.

Figured out the old ACD was aquired in: Symposium, Configuration, IVR ACD-DNs.
Added the new ACD there and aquired (this now looks the same as the old one).

Going to test it monday...
Would be wierd if that was the cause, never had to aquire an ACD before...

 

[jamaistrix]

ACD Queue do not need to be acquired unless it's for CallPilot IVR of ACCESS ports.

Are you sure that the phone that you have built is really acquired by Symposium?

Can you post a print of that phone?

 

[Utreg]

I've de-aquired the ACD Queues.

All is up'n'running now.
I deleted all the phonesets (except 1 working one) and did a CPY 1 from the working phone to the new TN and all is fine now.

Still don't know what caused the issue; in the TN printout the sets were aquired and when logging in the phone was "thinking a long time" and than defaulted to ACD login. Looked like the connection from some phones to the CC6 server was not established?

Anyway, thanks all for thinking with me; on to the next project ;-)