Symposium ip phone- opt81

[techgrl2]

Hello

I have been advise to out and rebuild an ip
phone for a acd user on the pbx side
I have been told its been de-aquired
on the symposium side and outed.
but when I print this phone out on the
switch , it looks like its just de-aquired
and not outed. When I stat this phone
it reads ---idle resgistered..should I be
concerned. Or is there just a time
frame that it take for the PBX to see that
it is outed from the symposium side

thanks

 

[sandyml]

Outing a phone from the Symposium side does not out it from the PBX. Your next step is to out it from the PBX and then rebuild it in the PBX. Then, put it back in to Symposium and reacquire it.

 

[techgrl2]

I understand that the symposium side does
not out it on the pbx side, im a season MAC tech...
but new to the acd phones with no
symposium back ground..I've compared and stared
and see the difference's on a phone aquired and non-aquired.
but i do see it still AACS: yes
so it appears to be aquired still, will i will
check soon to see if there were any changes over night.

no changes..the AACS: YES and the phone still appears only
de-aquired...
Thanks

 

[sandyml]

Sorry I misunderstood, I thought you said that when you checked the phone on the switch, "it looks like its just de-aquired and not outed." Anyway, you should have seen a change right away. Here is a command to completely deacquire from the PBX:

LD 48

DACR AGT l s c u

That should clear everything for you.

 

[BDSAINT]

Most likely you are running succession 3.0? They made a change in 3.0 that makes it so that if anything is aquiring a phone set, (whether it be symposium or any other 3rd party application such as monitoring, etc..) the switch will give you an error and tell you that you cannot out the phone if its still acquired. It did not do this prior to 3.0.

Do you have any other applications that may be aquiring the phone such as call monitoring etc...? You can do the DACR as mentioned above by Sandyml, but really you should be looking as to why the phoneset isnt being de-acquired correctly, or why something else has it aquired.

Hope that helps,


Dusty

 

[sandyml]

Yes, indeed, bdsaint. My suggestion was only a workaround, and did not address the root cause. Thanks.