priority to recalls towards an operator ? 2

[mdfan]

Hi

How to give priority to recalls towards an operator. I have seen that internal and trunk calls are always entering first .
Is this possible ?

Duvel

 

[Kressmark]

Hi duvel,

ASPACARNUM=172,PARVAL=2;

is explained with
"queue time has higher priority (longest time in queue)"

I think this setting would make the recalls have higher
priority than internal / trunk calls, but I have not had
the time to test it yet.

Try it and let us know...

BTW: Do you know that you can select which queue to pick
calls from with an OWS? just press the del key on the
numeric keyboard when you have calls in several queue's
and the queue selector (square) will jump from one que to
the next.

Best Regards
Mattias Kressmark

 

[mdfan]

I have tried this and I think you mean ASPAC PARNUM 173 instead of 172.
And it did not change the behaviour mainly because recalls
is not treated as internal calls.

Anyone else ?

 

[eriuser]

Try setting up seperate CORG's, one for internal/recalls, the second for external calls. You can then set your operators with diferent CHO values for the CORG,s.

 

[mdfan]

Sorry for late answer Kressmark . I tested the DEL key function to select from trunk queue and operator queue.
It did not work.
I run SP7.
Any special configuration to do ?

 

[mdfan]

It seems to work if I while having recalls/operator/trunk callls in queue first ask for external line and remove this. (0 + removal of this line).
Then the DEL key selects the queue.
But why ?
Is this normal ?
I would expect to reach the queue selector right away.

 

[meltitdown]

Which "Del"key are you using? It is the one on the numeric key pad. (also has a decimal point on it.) ie the one at the bottom most right hand corner of the key board. The other Del key is used for parking operator calls. Do you have a key overlay? Usually comes in the manual. Or perhaps an OWS key board?

 

[mdfan]

I use the correct DEL key .
And the question is not that it doesn't work but that I have to make external line and remove this to get it working.

 

[meltitdown]

do you have the num lock on?

 

[mdfan]

Sure .
If it was not on it shouldn't have worked at all ...

 

[meltitdown]

This situation may not be possible for you to resolve. What your describing is a call from the common queue being presented at a console and then you want to swap between queues once it is presented. As soon as you sieze a trunk the MD pulls that call back and that allows you to switch between the queues. So yes from your past posts this normal.

 

[mdfan]

So this is with other words the offical procedure to do it ?

The DEL thing only is not the 100 % correct procedure ?

 

[meltitdown]

The del key is the only way I have ever seen to switch between the ind / recall and common queues. To force the MD to take the presented call back you can also go off duty. The manual doesn't give any other explaination either.

 

[eriuser]

Ther is an optional Traffic Keyboard that connects to a Comm port of the PC. This has 3 seperate answer buttons for Internal/External/Recall.

 

[summerdike]

Boys & Girlz,
The first lesson to take is the lesson of reading.
Read carefully what eriuser tells you
"Try setting up seperate CORG's, one for internal/recalls, the second for external calls. You can then set your operators with diferent CHO values for the CORG,s."

Eriuser posted this on sept. 8th. Weeks later people talk about inapropriate solutions. Why? Eriuser just told you how it make it work.

 

[meltitdown]

Different CORG's and priorities is a work around, why have a key to choose which queue to take calls from if you can't really choose?

 

[Helpfulness]

Recalls has nothing to do with CORG's.
The only way to give priority to recall towards an operator is to insert a patch solution in DOR.
Use FR 95621.DOR in BC11 and FR 103011.DOR in BC12.
Priority for recalls to OWS:s has to be changed. In ordinary
old symbolic OPI the individual queue (recalls) has always higher priority than calls to the common queue. This will cause that, for exchanges with high incoming traffic, recalls seldom will be reanswered in OWS:s.
This was the purpose of FR 89827 in BC10.
Customer's in Sweden can not be without this function.

 

[summerdike]

Recalls has nothing to do with CORG's."

Lol!

Call type (I believe nr. 3 but I don't have the whole Alex library in my head) in command OPCTS is recalls. Together with command OPCGS you can direct recalls to the operator(s) that you want to receive recalls.




______________________________
"Reload and Restart Requested
System Initiated"

 

[Helpfulness]

Oh!
An operator answers a call on the left side and dials an extension on the right side. After this the operator extends the call. When the extension doesn't answer, the call is recalled to the operator when the time in PARNUM 10 expires (normally 30 seconds).
This is a basic function in MD and has nothing to do with CORG's.
Can you give me an explanation if I have wrong, please?

CALT
0 Emergency calls
1 Rerouted calls
2 Diverted/deflected calls
3 Internal calls (calls to OC-number, e.g. 9)
4 Manuel tie line
5 Normal external line
6 Automatic tie line
7 Direct indialling

 

[mdfan]

Just to finalize this discussion in regards to the question of origin . The correct answer I was looking for was NOT resolved by using CORG but by using the DEL key.