We have a OXE with 4039 sets. We just installed last week. At first, I could program a button on the set for Park/Retrieve (*75) and it worked. For some reason now, when I press the button it says Feature Rejected. But if I just type in *75, it works! This is the same from all sets. I can't find how to fix this. I have been looking for days - I though it might be a COS thing. I have looked everywhere. I look in mgr, and I looke in 4760i. Any ideas would be greatly appreciated.
Thanks
Paul
Feature Rejected!#@#!
-
pryan
-
pryan
-
freedom
I don't realy understand why you should program call/park retreive on a key.
As far as I know the 4039 is the same as the 4038, execpt TDM and not IP.
As soon as an extension has the external right 'call-park/retreive' set to on in the phone feature COS of the set, automatically the softkey 'park the call' will be visible if the set is called or makes a call.
Are you sure that there is nothing else but *75 under the key?
Do you still need to fill in an extension number after pushing the button?
Some other suggestions:
* Perhaps you programmed a number after *75?
* Did you assign the correct phone feature COS to the set? (I think so otherwise you would not be able to park a call using the prefix manually).
* What if you break down a set and recreate it?
*Are the sets in a group and is this group restricted?
I hope this will help you.
Good luck!
As far as I know the 4039 is the same as the 4038, execpt TDM and not IP.
As soon as an extension has the external right 'call-park/retreive' set to on in the phone feature COS of the set, automatically the softkey 'park the call' will be visible if the set is called or makes a call.
Are you sure that there is nothing else but *75 under the key?
Do you still need to fill in an extension number after pushing the button?
Some other suggestions:
* Perhaps you programmed a number after *75?
* Did you assign the correct phone feature COS to the set? (I think so otherwise you would not be able to park a call using the prefix manually).
* What if you break down a set and recreate it?
*Are the sets in a group and is this group restricted?
I hope this will help you.
Good luck!
-
pryan
I am trying to put park/retrieve on a button for convenience when retrieving a parked call. When parking a call we would not use the programmed button.
I am certain there is nothing behind the button, only *75.
I have removed a user and created them back, and the same thing.
If the call is parked on my ext for example, when I press *75, the call is automatically retrieved. If I am at another set, and press *75, I am prompted to dial the ext #. This is how it should work, I would think.
I am certain there is nothing behind the button, only *75.
I have removed a user and created them back, and the same thing.
If the call is parked on my ext for example, when I press *75, the call is automatically retrieved. If I am at another set, and press *75, I am prompted to dial the ext #. This is how it should work, I would think.
-
freedom
Now I understand why you would like to create the key.
And you're right. That is how it should work!
I'm only thinking what can be the problem.
Just like Frank everything is working fine in my lab.
I also programmed a key with the prefix. I have tried to get the same error you discribe, but it is working every time. I even get an icon of a musicnote next to the key if someone parks a call on my set, to indicate there is a parked call on my set.
Have you already tried a reboot of the system?
After this I'm running out of options.....
I can imagine that this problem is a real mindcracker!
And you're right. That is how it should work!
I'm only thinking what can be the problem.
Just like Frank everything is working fine in my lab.
I also programmed a key with the prefix. I have tried to get the same error you discribe, but it is working every time. I even get an icon of a musicnote next to the key if someone parks a call on my set, to indicate there is a parked call on my set.
Have you already tried a reboot of the system?
After this I'm running out of options.....
I can imagine that this problem is a real mindcracker!
-
suproutage_DUP
I might be completey on the wrong track here but some time ago on R3 4400 I had a similar problem.
System had 30 channels of T2 and if I remember in system/React.Recieving State messages were all set to NO which is default but setting them to YES fixed the problem.
Can't find any notes from those bygone days but give it a try.
suproutage
System had 30 channels of T2 and if I remember in system/React.Recieving State messages were all set to NO which is default but setting them to YES fixed the problem.
Can't find any notes from those bygone days but give it a try.
suproutage
-
Steveo
