Rachelle

Apply a DMI to that route and delete off the digits that you aren't using.

Build DMI
apply to RLI that this route goes through.
place test calls
post back


rlc

__________________
No matter where you go, there is the Ladies Love Marty Fan Club. :bow2: :bow2: :bow2:

gregosc

We thought about going that direction, however, we don't have individual DID's. Everyone goes out as the main number, so deleting off digits would only leave us with the last 4-digits of our main number. Actually, that's not totally accurate. There are a few people who have CLID entries that go out as 000-000-0000 so as to effectively block caller id to the world.

Is there a way within DMI/RLI/RLB/etc. to delete the digits and insert the DN the call is coming from?

Rachelle

The digit manipulation tables will delete and then insert digits as you wish. Based on the FRL of the set, the entries of an RLI can go to the same routes but, apply different DMI parameters. For example:

RLI 10 could have DMI 10 with an FRL of 2. Then on subsequent entries you could have no DMI at all if the FRL is 1, ect.
DMI 10 would delete 7 and insert 1234567.
If a caller with NCOS of 2 or higher dials a number that is using RLI 10, then they would pass 1234567.

This is where your BARS expertise is going to come in handy. You really need to understand your dialing plan and your access classes to configure this to do what you are asking.

rlc

__________________
No matter where you go, there is the Ladies Love Marty Fan Club. :bow2: :bow2: :bow2:

gregosc

I think I'm taking the wrong approach to solve the problem. It seems to me there would be a way to configure the route so that it appears to be an internal connection (i.e. similar to when 2 M1's are connected via a TIE route). I *think* that the Meridian is viewing the 5ESS TIE route as external, and that's why it's using the DN CLID digits instead of just the DN digits.

Does that make any sense?

Rachelle

Post your RDB of this given route. It is possible that a setting of 4 at the NDGT could do the trick but, then the programming at the far end would need to mirror this setting. Also review your RCLS and make sure that it is set to INT.

I hope this 'approach' allows the functionality you are looking for. However, from your discription of the issue, you are looking at a BARS related programming change.


rlc

__________________
No matter where you go, there is the Ladies Love Marty Fan Club. :bow2: :bow2: :bow2:

gregosc

Here is the dch print:

ADAN DCH 88
CTYP MSDL
GRP 0
DNUM 12
PORT 0
DES IVR
USR PRI
DCHL 88
OTBF 32
PARM RS422 DTE
DRAT 64KC
CLOK EXT
IFC ESS5
SIDE USR
CNEG 1
RLS ID **
RCAP ND2
T200 3
T203 10
N200 3
N201 260
K 7

And the route print:

TYPE RDB
CUST 00
ROUT 38
DES IVR
TKTP TIE
NPID_TBL_NUM 0
ESN NO
CNVT NO
SAT NO
RCLS INT
DTRK YES
DGTP PRI
ISDN YES
MODE PRA
IFC ESS5
SBN NO
PNI 00001
SRVC NNSF
NCNA YES
NCRD YES
CHTY BCH
CTYP UKWN
INAC NO
ISAR NO
CPUB OFF
DAPC NO
BCOT 0
DSEL VOD
PTYP PRI
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 8138
TCPP NO
PII NO
TARG
CLEN 13
BILN NO
OABS
INST
IDC NO
DCNO 0 *
NDNO 0
DEXT NO
ANTK
SIGO STD
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
NRD 10112
DDL 70
ODT 4096
RGV 640
GRD 896
SFB 3
NBS 2048
NBL 4096
IENB 5


PAGE 002

TFD 0
DRNG NO
CDR NO
MUS NO
RACD 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
PLEV 2
ALRM NO
ART 0
SGRP 0
AACR NO

and a route member print:

TN 088 01
TYPE TIE
CDEN SD
CUST 0
TRK PRI
PDCA 1
PCML MU
NCOS 6
RTMB 38 1
B-CHANNEL SIGNALING
TGAR 0
AST NO
IAPG 0
CLS UNR DTN CND WTA LPR APN THFD HKD
P10 VNL
TKID
DATE 4 MAY 2006

Rachelle

So, you have your PBX set as the User side and the IVR would be set as the Network side. Post the config expected in the IVR.


rlc

__________________
No matter where you go, there is the Ladies Love Marty Fan Club. :bow2: :bow2: :bow2:

Rachelle

DSEL might be better served with VCE
If you set your DNIS to YES then, you should see the prompt for NDGT.

__________________
No matter where you go, there is the Ladies Love Marty Fan Club. :bow2: :bow2: :bow2:

gregosc

It's not Nortel, but maybe it will make some sense:
(The IVR setup is an Asterisk box with a Digium TE110P T1 card)

span=1,1,0,esf,b8zs
bchan=1-23
dchan=24

switchtype=5ess
facilityenable=yes
signalling=pri_net
channel=>1-23
pridialplan=unknown

usecallerid=yes
hidecallerid=no
usecallingpres=yes

I changed DNIS to yes and used 4 for NDGT, but that didn't change anything.

Also, here's a PRI debug output from the IVR side:

< Protocol Discriminator: Q.931 ( len=34
< Call Ref: len= 1 (reference 23/0x17) (Originator)
< Message type: SETUP (5)
< [04 02 80 90]
< Bearer Capability (len= 4) [ Ext: 1 Q.931 Std: 0 Info transfer capability: Speech (0)
< Ext: 1 Trans mode/rate: 64kbps, circuit-mode (16)
< Ext: 0 User information layer 1: Unknown (24)
< [18 04 e9 80 83 97]
< Channel ID (len= 6) [ Ext: 1 IntID: Explicit, PRI Spare: 0, Exclusive Dchan: 0
< ChanSel: Reserved
< Ext: 1 DS1 Identifier: 0
< Ext: 1 Coding: 0 Number Specified Channel Type: 3
< Ext: 1 Channel: 23 ]
< [6c 0b a2 38 30 36 37 34 37 32 34 37 34]
< Calling Number (len=13) [ Ext: 1 TON: National Number (2) NPI: Unknown (2)
< Presentation: Presentation permitted, user number not screened (0) '8067472474' ]
< [70 05 a2 34 39 39 31]
< Called Number (len= 7) [ Ext: 1 TON: National Number (2) NPI: Unknown (2) '4991' ]
-- Making new call for cr 23
-- Processing Q.931 Call Setup
-- Processing IE 4 (cs0, Bearer Capability)
-- Processing IE 24 (cs0, Channel Identification)
-- Processing IE 108 (cs0, Calling Party Number)
-- Processing IE 112 (cs0, Called Party Number)

Thanks,
Greg