One for the NARS/BARS gurus

[MagnaRGP]

The setup is a CS1kM SG 4.5 Main office with a 5.0 Branch. (yes, this is supported, but only for 5.0 not 5.5).

I currently have everything working, but now want to finesse the outdialing from both sides to take advantage of Toll Bypass. What I currently have in place at the main for the branch user dialing is:

SPN 102 <--- Zone Base Access Code
FLEN 0
CLTP INTL
RLI 102
SDRR NONE
ITEI NONE


RLI 102
ENTR 0
LTER NO
ROUT 30 < --- SIP Trunks
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 2
DMI 102
ISDM 0
FCI 0
FSNI 0
SBOC NRR
IDBB DBD
IOHQ NO
OHQ NO
CBQ NO

ISET 1
NALT 5
MFRL 2
OVLL 0

DMI 102
DEL 0
ISPN YES
CTYP INTL

What I would LIKE to now do is the following:

1. Change the RLI so that entry 0 will first check an FCAS table for numbers local to the main office and place the call out the local PSTN. Does this make sense?:

Proposed:
RLI XXX
ENTR 0
LTER NO
ROUT 98 < -- PSTN
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 2
DMI XXX
ISDM 0
FCI 1 < -- local numbers
FSNI 0
SBOC NRR
IDBB DBD
IOHQ NO
OHQ NO
CBQ NO

ENTR 1
LTER NO
ROUT 30 < --- SIP Trunks
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 2
DMI 102
ISDM 0
FCI 0
FSNI 0
SBOC NRR
IDBB DBD
IOHQ NO
OHQ NO
CBQ NO

DMI XXX
DEL 4 < -- Access Code plus the 1
ISPN NO
INST
CTYP NPA

2. I also would like the above noted RLI to recognize DID's at the main dialed by branch users and place them as a CDP call, but am not sure what to do to implement that.
3. Similar to number 2, I want to do the reverse for main office users who dial the DID's of the branch users. I have yet to build out the RLI for the NPA of the branch office, so I was hoping that entry 0 would recognize the DID's and convert them, entry 1 would be the SIP trunk route for the NPA and entry 2 would use the local PSTN for the call.

I'm a bit confused and am looking for suggestions here.

Thanks oh so much.

 

[allenmac]

Once you send a call to a particular RLI the only manipulation you can perform is through DMI's. The RLI does not have the ability to recognize dialed numbers, it just sends calls out a particular route with digits determined by any digit manipulation entries.

LD 90 is where you should go to have the PBX recognize DID numbers. under the NPA that contains your DID range, configure LDID entries to process DID's using a DMI to strip the NPA-NXX, and insert any steering codes required. Basically LDID looks for matches within a particular NPA or SPN entry, and then processes those numbers using a DMI that you define for each NPA or SPN, instead of sending that call out the RLI configured for the NPA (I hope that rambling makes sense).

I don't have any branch offices in my inventory, so I don't use zone based dialing codes, but you may need to set INAC to YES on both ends of your virtual trunk route.

 

[MagnaRGP]

INAC is yes both sides.

So, for example, under SPN 102, I need to find the LDID prompt and enter in NPANXX, then using DMI delete 7 1npannx and change call type to CDP?

This would resolve parts 2 and 3 hopefully. I'll have a look and compose a proposed RLI/DMI and post for review

 

[allenmac]

For example, if your DID range is 818-555-1000 - 818-555-1099:

In 86 create a DMI that will delete 6 (or 7 if you dialed a 1), insert whatever steering codes you need, and change the call type to CDP.

In LD 90, change the entry for NPA 818 (& 1818 if necessary). At the SDDR prompt, enter LDID, then at the DMI prompt, enter the appropriate DMI number from the above step (depending on how many digits you need to delete). Now at the LDID prompt enter 55510.

Now any time a user diales AccessCode+818-555-10xx the pbx will apply the DMI, and process the call as if they had dialed the re-formatted digits. In your case - 10210xx.

 

[MagnaRGP]

Thanks for the help here. I've just discovered a slight issue. The blasted DID's do not correspond with the 4 digit extension and there is no correlation between digits at all. So, I think I'm going to have to set it up so that all the DID's are converted to the auto attendant.

 

[allenmac]

That sucks.

You may still be able to use the above programming, if you use the same IDC table on the Virtual Route, as your inbound PSTN route.

I assume there is an IDC table to automatically convert the inbound DID call from the PSTN to the proper internal DN.

 

[MagnaRGP]

Yes, but the IDC table is at the branch and not the main office and I'm trying to prevent the main office calls using the local PSTN to reach a Branch DID.

I'm going to just carry on with basic toll bypass for these calls in issues 2 and 3. Those calls will just have to use up a VoIP trunk and 2 branch PSTN's until the users are sufficiently brow-beaten...err...TRAINED to dial the 4 digit extension.

 

[1998xj8]

once a call hits an rli there is still digit analysis with fcas tables as long as the call is dialed as npa..so you could either allow or deny a set of nxx's in multiple or single npas on an entry level basis....we still use these in our switch although this type of programming has become mostly obsolete