Calling LD 90 Experts: Problem adding many SPN SDRR ARRN entries 1

[bdog2020]

Hi Everyone,
Due to local toll issues, I need to send 141 exchanges for a certain area code down our long distance pipe. Our service vendor told me that the best way to do that was to OUT the NPA's for the area code, and then enter in as an SPN.

I was able to do that, set the default RLI for the SPN, and then went ahead entering SDRR and ARRN entries, entering the ARLI for each.

Things went great until I got half way down the second page of extensions.

Then I got ESN0068, 'No more restricted numbers allowed for this code.'

I imagine that's a system setting to save memory for entered SPN's.

Where can I open that up a bit? any hazards in so doing? can I do it just for this one SPN.

Also, not too clear on how I change an SPN with ARRN entries after the fact. For example, how do I take an exchange out of the ARRN list or add other ones? Not to bad to just out it and recreate, but wondering how that works.

Thanks, Nortel gods!
bdog2020

 

[johnpoole]

look at load 87, all the prompts containing x will set a max for a related, can't look it up for you because the american version uses a little diff prompts (i think)(sddr), another hint is to make sure you are entering the shortest form of the nxx.. npa 1803 deny 40 blockes 401 402 etc, and just do a change to add additional codes.. most memorey concerns are carried over from the days when ram was 16k.. still most new installs leave the max prompts near default, in my 81 (8000 stations) almost everything is set to max, by doing that my 1st pri for ld is loop 156, the route is 156 the dch is 156 etc

john poole
bellsouth business
columbia,sc

 

[bdog2020]

John--thanks for your post. I was hoping you'd have time to chime in.

Not finding much related in LD 87. In LD 90, when defining an SPN, you can specify SDRR entries(Supplemental Digit Restriction or Recognition). For each of those you can do an ALOW, DENY, but I'm doing ARRN's, Alternate Routing Remote Number, which allows me to specify an ARLI(Alternate Route List Index).

Not seeing anything in LD 87 that tells me how I can set how many ARRN's I can specify for an SPN. Course that's not what Nortel manuals are designed to do, I suppose.

Somewhere in a system data load sowewhere, could I tweak a setting for the amount of ARRN's?

Thanks,
Ben

 

[johnpoole]

arli max 255, or max 999 with pkg 160...not a sys param.. looked it up now that i am at work...sorry for the mid leading post

john poole
bellsouth business
columbia,sc

 

[bdog2020]

John, great, and no worries, re. other post.

ARLI MAX, that's just what I'm looking for! when you say PKG 160, do you mean LD 160?. I'm using Option 11C, Succession 3.0. never used that load if so.

I talked to someone at my service vendor, and he said to check out LD 86, which has MXSD(Maximum Supplemental Digit Restriction). Mine is now set to 256, but he said it could go all the way to 1500.

However, I only entered about 53 ARRN entries, so I think I may be looking for ARLI MAX.

Looking for LD 160 now(these manuals are useless!).

Thanks for your help, you are a very generous expert!

bdog2020 (also, have no idea how Instructor got next to my ID, I'm no Nortel instructor!!!)

 

[johnpoole]

no load one 160, in ld 22 prt pkg, if you have pkg 160 you can add up to 999 entries..if not you can only add 255, might look at fcas to get this done

john poole
bellsouth business
columbia,sc

 

[bdog2020]

John, thanks so much, again. checked that we, do have PKG 160, so I should be able to add more then.

We went with an SPN handling because it was an easier solution, for both myself and our end-users. With FCAS, as I understand it, we could only allow or deny certain exchanges, but couldn't enter a different RLI for extensions.

For example, I could have two NPA's, 1xxx and xxx for a given extension, xxx. Then I could have a different FCAS table setup and applied to two different RLI's. One would allow only the long-distance exchanges for an exchange, 1xxx, and one would only deny long distance exchanges, xxx.

That solution, among other problems, would require that users knew which extensions(144 of 800+) are long distance within the area code.

With an SPN entry, I can send most out one RLI, and then alternately route the 144 LD exchanges out my long-distance RLI. I just enter it twice, 1xxx and xxx, so my end users don't need to think about it, and calls are always sent over the cheaper pipe.

Seemed easier than folling with multiple FCAS tables, and creating multiple RLI's just to apply a different FCAS table.

If I get it working, maybe you'd like to review it for an FAQ submission, more and more local toll seems to be happening to folks these days.

Thanks,
Ben

 

[techman3030]

prt your ESN in ld 86 and post the MX listings. To do restrictions and permisions in an SPN you MXSD must be set up high enough to accomodate the amount you are imputing if I remember correctly. I haven't had to do that in a while, but I'm pretty sure it is MXSD.

 

[bdog2020]

Techman3030, you are right, it is the MXSD. Mine is set to 256 right now, and it can go to 1500 for Release 22 and later.

her's my ESN now. I haven't changed it yet, as I'm still trying to confirm that that's my problem. When I print my SPN's, I manually count 304 SDRR ARRN entries. So, that's confusing me. I'll crank MXSD up and see if I can add more SDRR ARRN entries.

--------------------------------------------------------
REQ PRT
CUST 0
FEAT ESN

MXLC 5
MXSD 256
MXIX 5
MXDM 5
MXRL 20
MXFC 5
MXFS 5
MXSC 200
NCDP 4
AC1 9
AC2

 

[bdog2020]

Guys, MXSD didn't seem to help. I set it to 1500 in LD 86.

Then tried to add an SDRR ARRN entry, and it didn't work. Same error message, ESN0068.

I might have maxed out the ARLI's like John mentioned above.
-----------------------------------------------

REQ CHG
CUST 0
FEAT NET
TRAN AC1
TYPE SPN

SPN 1xxx
FLEN
RLI
SDRR ARRN
ARRN 554

ESN068
ARRN

 

[johnpoole]

the esn states for this code, as in you may be able to add more rest numbers for a diff number.. the above numbers seem to be for all codes, i don't see a place to set the number of rest pre number..

john poole
bellsouth business
columbia,sc

 

[bdog2020]

John, didn't quite follow all your abbreviations there. do you mean that I may be able to add more Recognized numbers to a different SPN? But, I need to add all 141 to THIS SPN in particular.
Ben

 

[bdog2020]

Our telco support vendor called me back, and turns out with SPN's, you can only enter 64 entries per SDRR block, and an SPN can only have one SDRR block.

So, effectively, you can only re-reroute 64 exchanges within an SPA using this method.

This might be an effective solution though if you had less than 64 exchanges to modify.

Anyway, I have 141, so I'm back to working on two FCAS tables, and applying them to two different RLI's, and then having two different NPA, 1xxx for long distance, and xxx for local calls. He said I can have a maximum of 800 NXX's per NPA in my FCAS table, so I'll make it, I have 641.

 

[bdog2020]

I wish there was a better way to do this, because now my users will get confused as to whether they need a 1 or not in front of the area code they are trying to dial.

does anyone know of another solution? basically another way to route 141 area codes out a different RLI, but just having one NPA entry, instead of having 1xxx for LD, and xxx for local?

thanks,
bdog2020

 

[bdog2020]

sorry, in above meant to say, 141 NXX's, not area codes, all within one NPA.

 

[bdog2020]

just to close the thread on a happy note: Turns out I can use an SPN solution, because in the particular NPA I'm talking about, even though there are 141 NXX's, and I couldn't add all 141, I looked at our phone bill, and over the last 5 months, we only have calls to 39 NXX's in that NPA.

So, I'm going to add ARLI's for those 29, and if a few more pop onto my bill, I'll add those, until I fill up 64 and leave it at that.

Much easier than having my grumpy end-users figure out whether or not they need a 1 before making the call.

I do wish they could up that number for SPN's though, or that you could alternatively route calls to different RLI's with NPA entries.

 

[coniglio]

you said you needed to send 141 exchanges for a particular area code to your long distance provider. are there additional exchanges within this area code or is that the total amount of exchanges within that area code?

 

[bdog2020]

Coniglio, 141 is the total NXX's within the NPA that I need to send out the LD, but I can only enter 64 when doing an SPN type solution. However, I've found only 29 NXX's have been used(so far), and I'm just going to enter those.

The area being called isn't business area, and is probably employees calling home, etc. So, I don't expect many changes in the calling patterns.

If I max out the 64, I won't care very much. this is regional toll, so its not that expensive, like $.02 more than our LD provider per minute, just enough to catch the CFO's attention because they shows come up itemized under our local bill.

 

[coniglio]

I wonder why it was suggested to you that you out the NPA and reprogram as an SPN. Can I assume the NPA (area code) is a long distance area code?

 

[bdog2020]

Coniglio, actually its a funny area code(and I'm told this is increasingly more common).

In this particular area code, 641 exchanges are local calls for us, 141 exchanges are "regional toll".

Otherwise, sure I'd send the entire NPA out Long distance pipe and be done with it.

That's the reason for needing to employ either FCAS tables applied to RLI's or an SPN solution.

bdog2020