What exactly is needed in a scope string? 2

[hunterrob]

I am having a discussion with a co-worker on what exactly is needed in the scope strings. Below are the strings I want to use:
Data MCIPADD=10.84.80.20,MCPORT=1719,L2QVLAN=14
Voice MCIPADD=10.84.80.20,MCPORT=1719,HTTPSRVR=10.240.5.149,HTTPPORT=80
They are very basic, everything else we can control in the 46XX file. We are using PE for all of our systems. The question being asked is at LSP and ESS sites is it needed to put in the strings the processor or C-LAN IP addresses? I say no, my co-worker says yes. Yes because IF the WAN goes down there is nothing for a phone to look to if it is booting up while the WAN goes down to register to. Any help is appreciated.

 

[Mitch672]

the LSP or alternate gatekeepers are assigned "node-names", on the "change ip-network-region x" form (each region has its own), on page 2, you assign the "survivable processors", when a phone registers to this IP-Network-region, this list is downloaded to the phone, dynamicly.

Never, put ESS or LSP IP's in a DHCP option 176 or 242, as the phones will "hunt" between these IP's, and if the LSP/ESS is not "awake" the phones will NOT be able to register.

THe proper way is to administer the alternate gatekeeper list on each IP-Network-Region



Mitch

AVAYA Certified Expert

 

[mattKnight]

>THe proper way is to administer the alternate gatekeeper list on each IP-Network-Region

Interesting - just looked at a wireshark trace of my phone registering...
and it shows 3 entries in the alternate gatekeeper list, plus obviously the primary gatekeeper. (AltGK list = primary, LSP, primary)

As I have only the 1 LSP, I'd expect there to be only the 1 AltGK. Is this right?

My DHCP strings are set to be
MCIPADD=<IP of Main>, <IP of LSP>,MCPORT=.......


Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[wildcard100001]

This is how I set mine:
Phone boots up into the data vlan, scope assigns vlan to phone. Phone is not in the correct vlan so it reboots into the phone vlan as the scope options indicate.
Data VLAN x DHCP Scope:
Option 242 = L2Q=1,L2QVLAN=xx(voice vlan)
Option 176 = L2Q=1,L2QVLAN=xx (voice vlan)

After the reboot the phone grabs the scope options defined in the voice scope.
Voice VLAN xx DHCP Scope:
Option 242 = MCIPADD=x.x.x.x,MCPORT=1719,HTTPSRVR=X.X.X.X,L2Q=1,L2QVLAN=xx,VLANTEST=30

Option 176 = MCIPADD=x.x.x.x,MCPORT=1719,TFTPSRVR=x.x.x.x,L2Q=1,L2QVLAN=xx,VLANTEST=30

Option 176 = old phones
Option 242 = new phones

 

[Mitch672]

mattKnight, don't put the LSP in the DHCP "MCIPADD=" line, it is not needed, and will cause you problems. Assign a "node-name" to this IP, and put it in the "IP-Network-Region", on page 2, "Backup Servers (In Priority Order)", this list is dynamiclly downloaded to the IP phones, as they register.

If you put it in the DHCP Option, you will end up with phones that can't register, if the main IP is slow to respond, as the phone will try the LSP's IP, and since the LSP is not active, the phone will not register. Only have "active" H323 gatekeepers in the DCHP "MCIPADD=" string.



Mitch

AVAYA Certified Expert

 

[mattKnight]

>Assign a "node-name" to this IP, and put it in the "IP->Network-Region", on page 2, "Backup Servers (In Priority >Order)", this list is dynamiclly downloaded to the IP >phones, as they register.

My concern with this is that if the main server has failed and a phone restarts - it will now nothing about the LSP..

This is howour BP has set it up - dual IP addresses in the HCP string and backup servers in each region


Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[Mitch672]

your Business Partner is wrong, plain and simple.

I am also a Business Partner, and I can't tell you how many issues this causes, because the phones all of the sudden stop working, because they cannot register to the inactive LSP/ESS server.

If the main server fails, the phones have a dynamicly downloaded list to try to register to. Only if you POWER OFF the phones, would there be an issue with them not having the dynamiclly downloaded list, and if that happens, you have more serious issues than just incorrect gatekeepers.

Once again, if the main IP is slow to respond, the IP phones will try the other IP's in the DHCP option string, they will try the LSP/ESS IP's, and because they are "offline" (inactive), this often causes the phones to simple lock up.

take this from experience. ignore this advise if you want, but I have been working with IP phones and AVAYA equipment since 1996





Mitch

AVAYA Certified Expert

 

[mattKnight]

>your Business Partner is wrong, plain and simple.

This I don't have trouble believing...

>Only if you POWER OFF the phones, would there be an issue with them not having the dynamiclly downloaded list,

This is my concern - and where I will have difficulty covincing the business that the change is required and for the better.

> and if that happens, you have more serious issues than just incorrect gatekeepers.

I hadn't thought of it like that!

> take this from experience. ignore this advise if you want, but I have been working with IP phones and AVAYA equipment since 1996

I hope (and it certainly wasn't my intent to do so) that I haven't questioned your experience and knowledge. I am trying to understand the ramifications of this - and why it was set up like this. I too have been working with Avaya for a long time(but only with CM for about 6 months)

Is my alternative gatekeeper list (in wireshark) correct - as my network regions only show the 1 LSP (correctly) but the AGL shows 3 entries (Main server, LSP Main Server)

Like I say, I am trying gain a better insight into what I have and why it is like that....



Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[wildcard100001]

Not that it adds much to the conversation... but I add a single CLAN ip-address to the MCIPADD value. All other CLAN IP addresses (gatekeepers - at most 5 I believe)in the region get downloaded on phone registration.

I set the DHCP IP phone range in the IP-network-map screen to the proper network region if it's different than the CLAN/network region I'm registering to via scope.

For the situation there is also the Survivable GK Node Name: field on the 1st page of the station form. You'd enter the node name of the onsite LSP/ESS.

I'd agree - never put a LSP/ESS address in the scope.