Recent content by gergje

it is already solved apparently the user had a button (headset i believe) turned on this was causing the error.. go figure :)

yeah this isnt possible i believe just trying to build in a step with a separate agent/skill that we can use to change routing between two numbers

restrict call-fwd for the cos is set on no by the way

hi i can't seem to put a call-fwd on a vdn i have already tried adding console permissions to the station on which im using *21, followed by the vdn number, followed by the number to which has to be forwarded suggestions?

yeah you can go to configure server then just fill in the plain ip-address for the ntp server extra options aren't necessary make sure it isn't a w32time server this doesn't work it has to be ntpd still in my case it doesnt work :) that sucks

i have a s8500 which every two weeks jumps four minutes forward with time i already changed it a couple times before office hours, but still it keeps on going forward i found out about the servers having a local clock drift, much as a windows pc running ahead of time then i suggested an ntp...

i already found out do not use drop use release ;)

i have a wired headset which i plug into the phone i plug these into 4610 and 4620 phones i want to keep the headset button on indefinitely but i constantly hear a dialtone only when transfering a call then the dialtone disappears in the headset even when i get a call and it ends, and i...

non-eas

thanks for your reply i solved it i think by adding a cover path with attendant on position 1 there is no use of vectors (don't ask)

Hi I have a huntgroup with 9 people in it People call to the hunt group but if all agents are having a call, how can i make sure there is a redirection to another extension? Cover path or other possibilities?

hi i do a trace on an agent who is trying to log in into a callmaster denial event 1376: no huntgrp for split strange thing however is that the hunt group does exist any ideas?

thanks ill set it up!

yeah ill have to look into that also im gonna check out the configuration set and setting it to pbx instead of network see if that changes anything

this error occurs during logging in not specifically with reports