PROBLEM ON CALLING OPERATOR in private network

[cuneyt2020]

Hi
We have 2 MD systems One of them is BC10 and the other one is BC12 SP6
2 switches are connected with QSIG

7000 is operator number in BC12 system

In BC10 system when we call 7000 ,it gives "vacant number" message
In BC10 system, when we call 7xxx (except 7000), there is no problem
In BC10 system ; "7" is a destination to route 74 which is connected to BC12 system

In NADAP i can see 7 as a destination code

IN BC10 system

[tt]
EXTERNAL DESTINATION ROUTE DATA
DEST DRN ROU CHO CUST ADC TRC SRT NUMACK PRE
7 74 0606100000000250006 0 1 0
92 1 0606100000000250006 0 1 0


[/tt]


I checked NUTRP on BC12, and there is no number on NUTRP as 7000, which is converted to any other number

Any idea why it occurs?

 

[alchohaz]

What are your Operator settings at the BC10 exchange? Has this worked before? Have you tried Networked Switchboard?

 

[cuneyt2020]

Hi
We don't use operator in BC10 system
Operator is in BC12 (7000 number is in BC12)
Also 7000 is operator common DID service

BC10 subscriber can call operator 7001 &7008 , but he can not call 7000, which is OPERATOR COMMON DID number


By the way, we have same topology with two BC12 systems and there is no problem calling 7000 there.

I think there is a problem between bc10 and BC12

 

[cuneyt2020]

Hi,
Now the problem is fixed by local vendor.
It is about the description of OPCTP

[tt]
<OPCtP:corg=all;
OPERATOR CALL TYPE DATA
CORG CALT ROU OACC CUST NDIR RERNUM CEN CCOP TIME OFLNUM SDAY SNIG
1 7 1 7000 - Y 7111 N N - - - -
1 5 50 - - Y 7111 N N - - - -
1 6 74 7000 - Y 7111 N N - - - -
1 6 90 7000 - Y 7111 N N - - - -
1 6 98 7000 - Y 7111 N N - - - -
1 1 - 9 - Y 7111 N N - - - -
1 2 - 9 - Y 7111 N N - - - -
1 3 - 9 - Y 7111 N N - - - -


[/tt]

Route 74 was not added there, so BC12 system was giving "vacant message" to BC10

Rgrds