LSP 1

[btrain8]

Would anyone be able to send me any info or explain this simply to me regarding how LSP's work.

I have a main site 8700cm3.1 and we're putting in a s8300/g700 in a remote office as an lsp. While I understand the actual extensions get administered on the s8700 switch but what about dialplan/udp/aar type things. If I have 4 digit dialing setup between my offices which are all standalone how and where does the LSP get it's dialplan programming? I would imagine it gets configured locally as a standalone switch but while in lsp mode where is it getting it's dialplan instructions?

Also, if this new site will be using the main sites MM system what needs to be done on the MM side?? The offices will be linked by an MPLS network so medium isn't a concern.

Also, does it matter that the remote office will be running cm5 and the main site 3.1?

 

[steeltown89]

Everything will be administered on the 8700 period. The translations will get copied nightly (if setup correctly) to the LSP from the 8700. Dial plan gets changed on the 8700 so if you have conflicting DID ranges you are in trouble. All get administered on 8700 (UDP, AAR, ARS, etc.).

MM just needs to know of the new extensions.

4 digit dialing will be internal on the same PBX (the 8700), don't think of it separately because it is not, it's just another extension.

I believe as long as the LSP is at the same version or higher than the 8700 site it is fine but it can not be a lower revision than the main 8700.

One example of setting up the remote site would be from the main 8700: change ars ana 911 location 2

In this example location 2 is setup on your 8700 as your LSP location (change locations). This is how you would setup local 911 trunks from the G700 at the LSP site and force it out POTS lines at the remote location. So you can have local trunking on the media-gateway at the LSP location. This is also how you could have local T1's for local DID's at the LSP site.

On the Network Region form if you are using VoIP phones there is a location field. If it is TDM there will be a location field on the Network Region form of the media-gateway. List media-gateway, get the Network Region and that Network region will have a location associated with it.

Hope that helps

 

[btrain8]

thanks for the explanation. An example of what I mean is on my s8700 switch in my udp 23xx is an entry for aar and in aar it goes to a RP that uses an IP trunk to our atlanta office then as a backup the call then goes over our TG that is for the PSTN with inserted digits for the area code and exchange of that atlanta office.

I'm assuming that since this new switch is treated as if it's part of the main switch then nothing really needs to change on the s8700 dialplan but what if the LSP site loses the WAN link and needs local programming?

We definitely do not want the same exact translations on my main site in NY to be on that switch for various reasons. is there something in the 8700 that segregates different switches to keep them virtually seperate.

 

[definityandcmuk]

the LSP filesyncs every night and will have exact copies of the main server translations, I don't believe there's anyway round that at all or understand how it would be a problem.

If it loses the WAN link it will automatically become active using the translations it has received from the main site.

As chandler says the ARS is administered by location; so if you have 10 locations you have 10 ARS tables. In CM5 AAR locations are available too

 

[steeltown89]

Yeah I don't think you understand the s8700 controls everything. The LSP site does not have an active PBX running until the WAN link goes down. If you have UDP setup for 23xx for your Atlanta office then you are going to have a problem if the LSP location has extensions that start with 23xx. Is the Atlanta location where the LSP is located now and if yes was this a stand alone PBX before connected via IP trunks? If the answer was yes you don't have IP trunking anymore because there is no PBX at Atlanta so those UDP entries to route across an IP trunk are not needed.

 

[btrain8]

I do get the 8700 controls everything. The new DID's that this new LSP site have been given only clashes with non DID #'s on my main site so they are no big deal to change.

The atlanta remote site is a standalone 8300 with an IP trunk back to the main site and there DID range is 23xx. There are no clashes with that but my question is the new LSP will follow the same rules to dial 23xx as the main site already has?? or does a new set of udp/aar rules need to be setup on the main site strictly for the new LSP??

Also, if all the programming is done on the main site then where do you start?

 

[definityandcmuk]

is the LSP going into the Atlanta site? if so there'll be no IP trunk or aar routing to get there, all extensions will appear on the main site

 

[btrain8]

no, the lsp is going to california so it will need to dial 4 digits to every office as we currently do everywhere.

I understand the translations are done on the main switch but is it blended in with the existing translations on the main switch or in the main switch do you have a seperate set of programming for each lsp that is specifically for that? If so where do you start with the programming?

 

[Mitch672]

its all one big switch btrain8, all blends together, which is why the diaplan must be compatible between sites, DIDs, etc. Of course you can have separate ARS tables (via ars location x), and separate trunks for each site, etc, but they all have to be compatible with what you already have.
you can't have duplicated DIDs/extension #'s, for example.

mitch


AVAYA Certified Specialist

 

[steeltown89]

Your California site will follow the rules at the main site unless you specify things for California. So in the network region form if you had say location 2. You could change the routing for 911 by typing this: change ars ana 911 location 2. If you do nothing it will follow the rules of the main site. So to answer your question, yes the UDP, AAR and ARS entries and routes you already have setup for Atlanta will work with the phones in California with no additinal programming. You will want to setup a new ars for the local California phone numbers

http://www.nanpa.com

, Tools, and then a search. So if you know San Diego is 619, lookup tools, area code search and type 619. You will notice 7 digit and 11 digit local is allowed, and it looks like 714 is tied to it also. You may need someone locally to help you with all the calling rules in that area. The point is you will need to type in: ch ars ana 3 location 2

And when the screen comes up add the following to allow 7 digit local dialing in California (this is assuming you have some local trunking at the G700).

Dialed
String Min Max Route Pattern Call type
2 7 7 1 locl
3 7 7 1 locl
4 7 7 1 locl
etc.

Remember you are only putting these in for California because you stated it was for location 2 (cha ars ana 3 location 2). It will not affect your entries that are already there (assuming you don't already have routes for location 2).

 

[definityandcmuk]

The IP trunk would be between your main site and the standalone in atlanta. The link between California and the main site will be "invisible" i.e no aar routing or UDP

Your extensions will administered be the same for the main site and California, but will be in a different network region (defined in the network map)

it may be worth you going on a course or visiting a site to see how it works, it's probably simpler than you imagine once you understand how it is adminstered (i.e network regions, network map etc)

 

[steeltown89]

Well said definityandcmuk

 

[btrain8]

Thanks for explaining it to me several times. I sort of understand the concept. I just think i need to see it on my screens to fully get the picture. I'll end it with that I don't understand why the main site, with being able to seperate by locations and network regions can't just upload that area of programming to the lsp for it's standalone programming. Meaning, why does that single site have to store my entire main site translations when most of it will be irrelevant and messy.

Does Avaya assign this LSP its own Sold To# or does my main sites Sold To get updated to include this LSP? Also, heavens forbid the system has to go into surviveable mode what is the procedure to log into it via ASA?? Same as any other standalone site?

 

[TechJimF]

Question regarding duplicate DIDs. If site A has a DID of 1234 on trunk group 1 and site B has a DID of 1234 on trunk group 2, doesn't this work okay since change inc-call-handling-trmt is on a per trunk group basis?

Oh, by the way, we are on CM5.0.

Thanks,

Jim

 

[steeltown89]

Yes the LSP will have it's own Sold To #. You can actually login to the LSP now even while it isn't in surviveable mode. It will warn you and say you can't save any translations but it will login. If you do a list conf all it will show you the boards but the vintage will say no board, that is because the boards are registered with the main system. Use the IP of the LSP webpage and port 5023 in ASA. If you don't know the IP type: disp lsp, this will give you the 8300 IP address. This is also how you tell if it is connected to the main site or not.

It does make it a bit messier by having all translations but it makes it easier to administer because you only login to the main site and everything you do at the main gets copied.

You will probably want to use different routes for ARS for California if the main site does go down because even if it is a long distance call the LSP PBX won't be able to use a trunk that is located at the main site in surviveable mode. Or at least in the route pattern setup an alternate trunk group that is local to the LSP for long distance. For example:

User dials 91847xxxxxxx (Chicago #)

ARS
Dialed String Min Max Pattern Type
1847 11 11 4 fnpa

Route 4
Grp # FRL NPA Pfx Mrk
1 4 532 1
2 4 532 1
3 4 532 1
4 4 532 1
15 4 619 1

Where trunk 15 is your LSP trunk in California. The LSP will see the first 4 trunks down when in surviveable and use trunk 15 to call Chicago.

 

[definityandcmuk]

The LSP concept seems to work pretty well as it is, I can't see the problem with it having the whole translations, the only translations that will matter will be the local objects, trunks, stations etc.

The fact that your LSP contains all the translations should be irrelevant as it shouldn't be in LSP mode for too long. It would mean too much administration trying to seperate which translations should be sent to the LSP

you assign an IP address to the LSP and log into it as usual via telnet or ASA etc.

 

[steeltown89]

TechJimF:

Yes you could do that with multiple blocks of DID's coming into the same location even but there is only one user that will get extension 1234. The other users with a DID of 1234 will get a converted extension, say 5234 or somet type of converted extension. I run into that a lot when a LEC gives us a DID range of xxx-xx0-xxxx (we use 5 digit extensions on most of our stuff), or xxx-xx9-xxxx. Obviously you can't give the user 9xxxx so you convert it to 6xxxx or something.

 

[TelecomDepartment]

Btrain8,

Here is something that might work for you, - Think of the “LSP” as two different pieces of equipment. The “LSP” is the S8300 – the G700, G250, G350, or G450 that houses the “LSP/S8300” is just another gateway off the main PBX. You probably have G650s – the gateway at your surviable site is just another cabinet off your S8700. Thus the translations for it are the translations in the S8700. Those gateways (G700, G450, .. ) could sit at the remote location as a cabinet (carrier if you want) off the main PBX with no "LSP/S8300" at all.

These translations are “pushed” to each “LSP/S8300” connected to the main PBX. This LSP sits idle just waiting for the S8700 to fail. When that happens the “LSP/S8300” takes over only for those gateways connected to it, “G700” or whatever gateway(s) is being used. .. . and only uses those translations that are for those gateways it will control. It basically becomes a PBX for that location. With that said there is something called “ESS” – so that “LSP” can be used to run more than just the gateways at its own location, thus it needs all the possible translations (which is all the translations). You could put in G650 gateways at your remote location and use either S87XX or an S8500 instead of a “LSP/S8300”. The result would be same except with higher capacity at the remote site.

By now – if you read through all the previous post, you’ll understand why you give each “LSP/S8300” is own location and put trunks in which are connected to the gateways at each location. Because each location will be using the same translations you can’t use the same station extension in two locations (two different phones). Thus you don’t use UDP – because the gateways/stations at the remote site are really hanging off the main site. The “LSP/S8300” sits there and waits to run those phones in its local gateways if the main S87XX ethernet connectin to it fails. (Be sure to use location codes and network regions).

As far as the connection to the "LSP" - be sure to keep the IP address, login/psswd for the S8300. Administer a setup in ASA or go to the shell in S8700 and type telnet xxx.xxx.xxx.xxx (IP of S8300) - login/passwd -- use vt100 terminal type - (at this point you're in the shell on the S8300. Type sat - and login/passwd again - you're in CM on the surviable. Anything you translate will be overwritten when the ethernet connection is again available and the translations are pushed to it at night - logoff to go back to shell - exit to get out (back to S8700 if you used telnet)

 

[TelecomDepartment]

oh, one more little item -

When you login the second time for "sat" session - use terminal type 4410

 

[acuratsx]

I'm sorry dumb question but what does LSP stand for?