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 Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SBO (Branch Office) NCOS Barring Problem 2

Status
Not open for further replies.

sl1input

Technical User
Apr 17, 2006
233
GB
I have vaious Rel 4 Survivalble Branch Office (SBO) Sites connected to a Rel 4 CS1000m, all sites have Sig Servers and Virtual Trunking.

The SBO sets register to the Main Office (MO) and use all the MO facilites. To make PSTN calls the SBO phones dial out from their local lines, using a Virtual Trunk to get back for PSTN access.

The problem is that the SBO phone ignores the NCOS programmed on the i2001 or i2004 and with NCOS 1 or 2 can dial mobile/cell phone and full PSTN access.

If i create a local digital set e.g. 3904 to the SBO the set <<DOES>> follow the NCOS tables and at NCOS 1 is internal only.

So i guess the fault is with the Virtual Trunks not programmed correctly???

Here's the Virtual Route:>

TYPE RDB
CUST 00
DMOD
ROUT 115
DES VIRTRK
TKTP TIE
NPID_TBL_NUM 0
ESN NO
RPA NO
CNVT NO
SAT NO
RCLS EXT
VTRK YES
ZONE 255
PCID H323
CRID NO
NODE 1
DTRK NO
ISDN YES
MODE ISLD
DCH 10
IFC SL1
PNI 00001
NCNA YES
NCRD YES
TRO YES
FALT NO
CTYP CDP
INAC YES
ISAR NO
DAPC YES
TBL 0
PTYP ATT
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 1615
TCPP NO
TARG 01
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 0 *
NDNO 0
DEXT NO
SIGO ESN5
MFC NO
ICIS YES
OGIS YES
TIMR ICF 512
OGF 512
EOD 13952
LCT 256
DSI 34944
NRD 10112
DDL 70
ODT 4096
RGV 640
GTO 896
GTI 896
SFB 3
PRPS 800
NBS 2048
NBL 4096
IENB 5
TFD 0
VSS 0
VGD 6
EESD 1024
SST 5 0
DTD NO
SCDT NO
2 DT NO
NEDC ORG
FEDC ORG
CPDC NO
DLTN NO
HOLD 02 02 40
SEIZ 02 02
SVFL 02 02
DRNG YES
NDRI 00
CDR YES
INC YES
LAST YES
TTA YES
ABAN YES
CDRB NO
QREC NO
OAL YES
AIA YES
OAN YES
OPD YES
NDP EXC 0
CDRX NO
NATL YES
SSL
CFWR NO
IDOP NO
VRAT NO
MUS NO
PANS YES
MANO NO
FRL 0 0
FRL 1 0
FRL 2 0
FRL 3 0
FRL 4 0
FRL 5 0
FRL 6 0
FRL 7 0
OHQ NO
OHQT 00
CBQ NO
AUTH NO
TTBL 0
ATAN NO
OHTD NO
PLEV 2
OPR NO
ALRM NO
ART 0
PECL NO
DCTI 0
TIDY 1615 115
ATRR NO
TRRL NO
SGRP 0
AACR NO


Looking at the FRL's, this may be the problem???

But im not well up on FRL feature at all.

Help much App.
 
Is this route at BO or MO?

FRL in the route is a mapping for NCOS: FRL 5 is map to NCOS 0.
This may be the problem. However, the rout is ESN5 meaning you are sending NCOS through the trunk (Travelling NCOS=TCOS)

Give a try changing FRL
I may give you an example that is working
 
using a Virtual Trunk to get back for PSTN access" is the issue.

When the call routes back to the SBO it uses the NCOS of the SBO virtual trunk (ld 14) and not the NCOS of the phone. Restricting remote office IP phones has to be handled in the Home PBX.

Unless there is a way to have traveling NCOS values on calls between PBXs. Does anyone out there know if this can be done?
 
The FRL in the RDB (ld 16) come into play on direct trunk access (code restrictions) so they shouldn't be the issue here.

dlesap: Can you provide setup details on Traveling NCOS. Is it a simple setup?
 
Hello
Here is an example of the Virtual route on Main office side that is working for call revert back to BO for PSTN:

TYPE RDB
CUST 00
DMOD
ROUT 20
DES VIRTUAL_ROUTE
TKTP TIE
NPID_TBL_NUM 0
ESN NO
RPA NO
CNVT NO
SAT NO
IDEF NET
RCLS EXT
VTRK YES
ZONE 011
PCID H323
CRID NO
NODE 1
DTRK NO
ISDN YES
MODE ISLD
DCH 20
IFC SL1
PNI 00001
NCNA YES
NCRD YES
TRO NO
FALT NO
CTYP UKWN
INAC NO
ISAR NO
DAPC YES
TBL 1
PTYP ATT
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB NO
STEP
ACOD 9997
TCPP NO
TARG
CLEN 1
BILN NO
OABS
INST
IDC YES
DCNO 0
NDNO 0 *
DEXT NO
DNAM NO
SIGO STD
STYP SDAT
MFC NO
ICIS YES
OGIS YES
TIMR ICF 512
OGF 512
EOD 32640
DSI 34944
NRD 10112
DDL 511
ODT 16128
RGV 640
GTO 896
GTI 896
SFB 3
NBS 2048
NBL 4096
TFD 0
EESD 1024
SST 5 0
DTD NO
SCDT NO
2 DT NO
NEDC ORG
FEDC ORG
CPDC NO
DLTN NO
HOLD 02 02 40
SEIZ 02 02
SVFL 02 02
DRNG NO
CDR NO
NATL YES
SSL
CFWR NO
IDOP NO
MUS NO
PANS YES
MANO NO
FRL 0 0
FRL 1 1
FRL 2 2
FRL 3 3
FRL 4 4
FRL 5 5
FRL 6 6
FRL 7 7
AUTH NO
TTBL 0
ATAN NO
OHTD NO
OPR NO
ALRM NO
ART 0
PECL NO
DCTI 0
TIDY 9997 20
ATRR NO
TRRL NO
SGRP 0
AACR NO

To identify NCOS travelling through ESN5 trunk you will see 3 front digits added to your number when monitoring the DCH:
dialing 1234 ---> 1051234 in the DCH for NCOS 5 set
 
Thanks guys.

The Virt Rt was from the BO switch, i will get Virt Trunk prints from both MO & BO when possible.

I will also setup up some DCH monotoring to see if NCOS is being sent/received.

Scenario: IP Set at BO regist'd to MO

Q: At the MO i should see the NCOS being sent out?

Q: At the BO i should see the NCOS being received?

Q: dlesap: Your route is SIGO:STD, mine is ESN5, i thought STD would not send the NCOS over the route????
 
Q: At the MO i should see the NCOS being sent out?
Yes cause ESN5 in RDB. Then you may see 10x+dialled digits

Q: At the BO i should see the NCOS being received?
Guess no, cause going through LD 90 of Main office. Not sure.
You may only have digits to be dialled out to PSTN.

Q: dlesap: Your route is SIGO:STD, mine is ESN5, i thought STD would not send the NCOS over the route????
That's right. I think it's not necessary to send it cause your phone is registered on the Main office. MO controls the restriction, not BO
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top