OXE with a BPRA in Master / Network <==> OXO Compact

[stefanc_DUP]

Hi !

Anyone that has setup a OXE with a BPRA to act as a Network Master to "drive" OXO (MiX board). I have tested to setup the OXE BPRA in S0 mode, added a couple of users and setup the same users inside the OXO and i works. But now i want to setup the OXE as a public switch. Set a trunk, and from the outside "thru" the OXE and make a call setup onto the OXO.

We want this function to play around and educate on the OXO.

Any suggestions ...

[jasic]

You must create a new trunk Group, in this trunk group you set the b-channel choice to yes, then you go to the digital access from your BPRA
there you set the network mode to yes and set access type S0 to yes,
if you managed this you create a prefix for this trunk

[stefanc_DUP]

Thanks four your answer, so far I´ve understand the fact, but do I have to create all the numbers as invidual S0 users to "route" trough the Enterprise.( If I want to route outside DDI thru this trunk group.)

//stefanc

[jasic]

You can manage all number as Network Number, or or manage one Prefix for the Trunk , in this case you have ddi , you can translate all number to oxo in the ddi translator of the oxe, for example

Trunkprefix is 90

In the DDI translator of the public trunk you translate
first external number 100
first internal number 90100
Range Size 50

Now the ddi 100 - 149 from the oxe are routed to oxo trunk

[vad]

When you connect f.e. two 4400 with T0 - you need on one end decleare network mode=yes and ACCESS TYPE S0=YES!!!

[stefanc_DUP]

Hi !

Thanks for all your answers, I shall test it asap, But we have some trouble with a site that runs OxE 7.0 4.40119 that steels all my time.
The system looses GAP DECT Sets on remote shelfs. Even 4074GB is lost. Any clue.

Again ....

Thank you all for your help.

[vad]

Remote shelf - what type of link? And what you see with infocs command?

[stefanc_DUP]

Hi !


* Remote ACT shelf via RT2, This shelf is on a DECT4HB board with DTM and all that.

* The GD has a IBS.

* The node has a IBS , it seems that 4074 is still up and running.




+----------------------------------------------------------------------+
| N_CR | N_CPL | TYPE | N_ACCES | PRIO | SYNC_CLOCK | TG/LK |
+----------------------------------------------------------------------+
| 0 | 14 | PRA2 | 0 | 0 | SYNCHRO | TG:1 |
+----------------------------------------------------------------------+

+---------------------------------------------------------------------+
| Synchronization on global domain |
+---------------------------------------------------------------------+


+========================== Synchro DECT ==================================+

+--------------------------------------------------------------------------+
| N_CR | N_CPL | TYPE | DECT_CLOCK | Depending Crystals |
+--------------------------------------------------------------------------+
| 1 | 9 | DECT4HB | DTM SYNCHRO | |
| 2 | 4 | DECT4HB | DTM SYNCHRO | |
+--------------------------------------------------------------------------+


+========= campus synchronization via INTOFS ====================+

this node 1 is SLAVE of campus synchronization (master node = ?)
synchro = PHASE_NO_OPERATION (phase shift values = 0,0)
info1=0 info2=0 info3=0 info4=0

[vad]

What type of CPU in you system? And what DECT type IBS in main area and RBS on remote (RT2)? Or you use DECT4HB for synchronization only?

[vad]

F.e. if you have IBS DECT and CPU6, CPU7.
DECT/RBS system - manage ACT handover=yes and decleare ACT No=0 (where CPU located).
For remote RT2 ACT manage for RT2 synchronization priority 200 and remove DECT4HB board (if you use this board before only for synchronization).