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!

Route calls that begin with "22" to a specific RLI?

Status
Not open for further replies.

lwurl2

Technical User
Nov 1, 2012
77
US
How can I route calls that being with "22" to a specific RLI? I put in a new dsc through ld87, but I could not figure out how to wild card the next 5 digits that woudl come after 22.
 
There is no wild card, just route 22 and any digits after that will go.
 
How so? When I put a DSC of "22", it works fine until the 5th digit, then I receive reorder tones, and "Release and Try again" on my set.
 
The reason for this is that we are tying in a Cisco system, and I want to use this 22 access code to send calls out RLI 40, which is my working SIP trunk to the Cisco environment.
 
CDP has always been this way. For example if you have Extensions 2200 thru 2299 then your cdp entry would be 22. Maybe your FLEN is set to 4 or something like that or possibly the reorder is another problem all together.
 
Where can I check the FLEN at? I noticed that some documents I pulled up said FLEN can be set in ld87, but my system does not prompt me for FLEN.
 
You said these are SIP trunks, are you using NRS or Session Manager for routing? Just because you put in a CDP entry for an IP trunk either H323 or SIP you still have to do the routing in NRS.
 
I have been doing single extension forwarding for right now - specific CDP entries - ie: 54908 to RLI 40.
RLI and ROUT as follows:


[pre]RLI 40
ENTR 0
LTER NO
ROUT 80
TOD 0 ON 1 ON 2 ON 3 ON
4 ON 5 ON 6 ON 7 ON
VNS NO
SCNV NO
CNV NO
EXP NO
FRL 0
DMI 0
CTBL 0
ISDM 0
FCI 0
DORG NO
SBOC NRR
PROU 1
IDBB DBD
IOHQ NO
OHQ NO
CBQ NO

ISET 0
NALT 5
MFRL 0
OVLL 0
[/pre]

[pre]TYPE RDB
CUST 00
ROUT 80
DES SIP_TRK
TKTP TIE
M911P NO
ESN NO
CNVT NO
SAT NO
RCLS INT
VTRK YES
ZONE 00001
PCID SIP
CRID NO
NODE 101
DTRK NO
ISDN YES
MODE ISLD
DCH 10
IFC SL1
PNI 00001
NCNA YES
NCRD YES
TRO YES
FALT NO
CTYP UKWN
INAC NO
ISAR NO
DAPC NO
MBXR NO
MBXOT NPA
MBXT 0
PTYP ATT
CNDP UKWN
AUTO NO
DNIS NO
DCDR NO
ICOG IAO
SRCH LIN
TRMB YES
STEP
ACOD 8686
TCPP NO
PII NO
AUXP NO
TARG 01
CLEN 1
BILN NO
OABS
INST
IDC NO
DCNO 0 *
NDNO 0
DEXT NO
ANTK
SIGO STD
STYP SDAT
ICIS YES
TIMR ICF 512
OGF 512
EOD 13952
DSI 34944
NRD 10112


PAGE 002

DDL 70
ODT 4096
RGV 640
GRD 896
SFB 3
NBS 2048
NBL 4096

IENB 5
TFD 0
VSS 0
VGD 6
SST 5 0
NEDC ORG
FEDC ORG
CPDC NO
DLTN NO
HOLD 02 02 40
SEIZ 02 02
SVFL 02 02
DRNG NO
CDR NO
VRAT NO
MUS NO
RACD NO
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
ALRM NO
ART 0
SGRP 0
ARDN NO
CTBL 0
AACR NO

[/pre]
 
I think you have an NRS issue, those entries need to be in NRS also.
 
[pre]FEAT esn_data

ESN009
FEAT ESN

MXLC 0
MXSD 10
MXIX 2
MXDM 120
MXRL 120
MXCM 0
MXFC 5
MXSC 500
NCDP 5
AC1 9
AC2
DLTN NO
ERWT YES
ERDT 5
TODS 0 00 00 23 59
RTCL DIS
[/pre]
 
The reorder after the last digit makes me think the PBX is routing the call but the NRS database is not there to take it to the correct end point. Have you checked that?
 
Try changing NDCP to the actual # of digits you are dialing.
If it's set to 5 then 5 is all you can dial.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top