Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

OPI and overflow

Status
Not open for further replies.

PCLOP

Technical User
Nov 11, 2004
62
NO
Case:
2 customers are charring one MD110. They have different OACC and CORG each OPI can only answer there own CORG.
There is only one external route.
If you call one of the customers and that OPI is busy, the call is "overflowed" to the other OPI. How can I prevent this solution?

Calls to customer A should not bee answered on OPI customer B and vice versa.

OPI have cust=, but I can’t set CUST on the route because they are charring the same route.

BC11 sp9
 
Hi

Could you post the OPI configuration?
Have you set OPCGS for each OPI to answer only to the corresponding CORG ?
 
<OPCTP:CORG=ALL;
OPERATOR CALL TYPE DATA
COMMON OACC NUMBER = 9
CORG CALT ROU OACC CUST NDIR RERNUM CEN CCOP
1 1 - 8990 1 Y 4170 N N
1 2 - 8990 1 Y 4170 N N
1 3 - 8990 1 Y 4170 N N
2 7 1 7700 15 N - N N
3 1 - 8988 15 Y 8990 N N
3 2 - 8988 15 Y 8990 N N
3 3 - 8988 15 Y 8990 N N
4 7 1 4000 1 Y 4170 N N
9 7 1 5800 3 N - N N
10 1 - 8992 3 N - N N
10 2 - 8992 3 N - N N
10 3 - 8992 3 N - N N
11 1 - 8993 4 N - N N
11 2 - 8993 4 N - N N
11 3 - 8993 4 N - N N
12 7 1 2330 4 N - N N
13 1 - 8989 5 N - N N
13 2 - 8989 5 N - N N
13 3 - 8989 5 N - N N
16 7 1 4580 10 Y 8987 N N
16 1 - 4580 10 Y 8987 N N
16 2 - 4580 10 Y 8987 N N
16 3 - 4580 10 Y 8987 N N
17 7 1 4100 1 N - N N
17 1 - 4100 - N - N N
17 2 - 4100 - N - N N
17 3 - 4100 - N - N N

END

<OPDDP:DIR=ALL;
OPERATOR DIRECTORY DATA
DIR EQU OCUST TYPE PCM REV
3310 001-0-42-01 1 1 - -
3311 001-0-42-03 1 1 - -
3312 002-2-72-00 1 6 - -
3314 002-2-60-01 15 6 - -
3330 002-2-30-00 6 5 1 R6A
4589 002-1-40-13 10 6 - -

END

<OPCGP:DIR=ALL;
OPERATOR CALL ORIGIN GROUP DATA
DIR
333334
333335
111138
012409
CORG ------
1 111000
2 000100
3 111000
4 111000
9 111000
10 111000
11 111000
12 111000
13 111000
16 000001
17 111000
 
Hi

Pls when doing copy and past, insert before the past [ tt ] and after the past [ / tt ], it will make the print out better, like this
[tt]
<OPCTP:CORG=ALL;
OPERATOR CALL TYPE DATA
COMMON OACC NUMBER = 9
CORG CALT ROU OACC CUST NDIR RERNUM CEN CCOP
1 1 - 8990 1 Y 4170 N N
1 2 - 8990 1 Y 4170 N N
1 3 - 8990 1 Y 4170 N N
2 7 1 7700 15 N - N N
3 1 - 8988 15 Y 8990 N N
3 2 - 8988 15 Y 8990 N N
3 3 - 8988 15 Y 8990 N N
4 7 1 4000 1 Y 4170 N N
9 7 1 5800 3 N - N N
10 1 - 8992 3 N - N N
10 2 - 8992 3 N - N N
10 3 - 8992 3 N - N N
11 1 - 8993 4 N - N N
11 2 - 8993 4 N - N N
11 3 - 8993 4 N - N N
12 7 1 2330 4 N - N N
13 1 - 8989 5 N - N N
13 2 - 8989 5 N - N N
13 3 - 8989 5 N - N N
16 7 1 4580 10 Y 8987 N N
16 1 - 4580 10 Y 8987 N N
16 2 - 4580 10 Y 8987 N N
16 3 - 4580 10 Y 8987 N N
17 7 1 4100 1 N - N N
17 1 - 4100 - N - N N
17 2 - 4100 - N - N N
17 3 - 4100 - N - N N

END

<OPDDP:DIR=ALL;
OPERATOR DIRECTORY DATA
DIR EQU OCUST TYPE PCM REV
3310 001-0-42-01 1 1 - -
3311 001-0-42-03 1 1 - -
3312 002-2-72-00 1 6 - -
3314 002-2-60-01 15 6 - -
3330 002-2-30-00 6 5 1 R6A
4589 002-1-40-13 10 6 - -

END

<OPCGP:DIR=ALL;
OPERATOR CALL ORIGIN GROUP DATA
DIR
333334
333335
111138
012409
CORG ------
1 111000
2 000100
3 111000
4 111000
9 111000
10 111000
11 111000
12 111000
13 111000
16 000001
17 111000
[/tt]
Now I feel confused with your configuration,
you speek about 2 customer and there is 7 cust.....
and more complicated, some OPI does answer to some specific CORG on some CUST, and some other to some CORG/CUST/OACC....

The best way is to simplify the configuration and to assign to each OACC a unique cust.
Normally, it is what I usually do and it is working fine...
 
OK I have "clean" a little i MD110.....

This is how it looks

Any solution?
Are there any AS-parameters I can check?

[ tt ]
<OPCTP:CORG=ALL;
OPERATOR CALL TYPE DATA
COMMON OACC NUMBER = 9
CORG CALT ROU OACC CUST NDIR RERNUM CEN CCOP
1 1 - 8990 1 Y 4170 N N
1 2 - 8990 1 Y 4170 N N
1 3 - 8990 1 Y 4170 N N
2 7 1 7700 2 N - N N
3 1 - 8988 2 Y 8990 N N
3 2 - 8988 2 Y 8990 N N
3 3 - 8988 2 Y 8990 N N
4 7 1 4000 1 Y 4170 N N

END

<OPDDP:DIR=ALL;
OPERATOR DIRECTORY DATA
DIR EQU OCUST TYPE PCM REV
3310 001-0-42-01 1 1 - -
3311 001-0-42-03 1 1 - -
3312 002-2-72-00 2 6 - -

END

<OPCGP:DIR=ALL;
OPERATOR CALL ORIGIN GROUP DATA
DIR
333
333
111
012
CORG ---
1 110
2 001
3 001
4 110


[ / tt ]
 
Hi
remove the space inside the [ ] and it will be better. I just have inserted the space, because you won't see the caracter otherwise. Have a look at

This configuration is working for me in BC11 SP14. So I guess that you have to move to BC11 SP14 or SP15, as it could be some error corrected
 
If you can seperate the calls into different routes, then you will be able to stop calls spilling over using the TCMAP in the ROCAP and the OPCAP.

If this is not feasible then i think you will struggle, it seems to be a "feature" of the MD110 when it comes to the operators, there are also a few quirks with Night Service, i.e. when one customer logs off all of their operators, the switch is still NOT in Night Service.

[tt]OPADC :CORG=...[,NDIR=] [ ,RERNUM= ][,TIME= ,OFLNUM=]; [/tt]

This may address your issue? Calls will tend to end up at the wrong operator position if they do NOt have an alternative.

hope this helps
Al.



[red]Striker : My orders came through. My squadron ships out tomorrow, we're bombing the storage depots at Daiquiri at 18:00 hours. We're coming in from the North, below their radar.[/red]
[blue]Elaine : When will you be back?[/blue]
[red]Striker : I can't tell you that? It's classified.[/red]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top