Server Edition and IP Endpoint Licenses

[cztech]

I installed an Expansion system IP500v2 today. This new system has a VCM32 and therefore 12 'Virtual IP Endpoint' licenses. The customer bought 5 additional IP Endpoint licenses which were applied (and show 'VALID') to the main, Primary Server. However, at the new location, I can only bring up 12 IP phones; phones 13-17 are showing 'No License Available.' My support channel agrees with me that phones 13-17 should grab the necessary IP Endpoint licenses from the Primary Server. On the Primary Server, supporting the customers main location, only 156 out of an available 181 IP Endpoint licenses are in use, so I know nothing I have the capacity, but this expansion site is not grabbing the needed licenses beyond the 12 virtual.

One other note:
Primary server: 8.1.65
Secondary server: 8.1.63
IP500v2 gateway: 8.1.63
IP500v2 expansion (new): 8.1.67

Any thoughts ?

cztech /

http://www.cztechnologies.net

 

[jamie77]

Are the ip phones registering to the server or the local IP 500??

I haven't touched SE yet but I thought the call server on the phones should be the server and the local ip endpoint licenses were useless. Hence the VCM v2 mods with no free licenses.

Jamie Green

[bold]A[/bold]vaya [bold]R[/bold]egistered [bold]S[/bold]pecialist [bold]E[/bold]ngineer

 

[cztech]

The 12 phones that are working are registering with the new, local IP500v2. From what I understand, with SE and endpoints, you can put them on the Primary server or the Expansion gateway.

cztech /

http://www.cztechnologies.net

 

[cztech]

As an aside, and very strange, my 2 analog station ports on the combo card would NOT work until I got the server edition license for this expansion system on the primary. It was weird not having dial tone on the station ports - usually you can always count on some POTS dial-tone even when all else is failing!

cztech /

http://www.cztechnologies.net

 

[tlpeter]

You are right and it should not matter where the IP endpoint licenses are.
Can you try to delete the virtual license?


BAZINGA!

I'm not insane, my mother had me tested!

 

[cztech]

I am hesitant to delete the virtual licenses, as I suspect they are currently providing 100-percent of my current working phone functionality!

I guess my only plan now is to downgrade this new site to 8.1.65 to match it w/ the Primary server.

cztech /

http://www.cztechnologies.net

 

[tlpeter]

Ahaaa, you did not tell that part
You shoudl always up or downgrade the system from the webcontrol page.
In case you do not know go to "solution management" and click on upgrade expansion systems"
If this is the only unit then it will downgrade it for you.
You have to do really nothing else then one click.
It will first check and then upload all files needed and then do the upgrade.


BAZINGA!

I'm not insane, my mother had me tested!

 

[TelcoAdy]

The way I understand SE licencing is that you needed to licence whichever system your handsets are going to register to.

So if you wanted all 17 handsets to register to the IP500 that would need to have enough licences to cater for those 17 handsets.

If you then use the primary server as a backup server for the phones then they will register with a guest licence.

 

[tlpeter]

TelcoAndy, that is the case as he has enough licenses on the primary server.
Normally this would work if you have a VCM32v2 (it gives no virtual license)
But somehow the system looks only to the 12 virtual licenses generated by the VCM32v1
This situation should work fine but does not.


BAZINGA!

I'm not insane, my mother had me tested!

 

[TelcoAdy]

tlpeter, the way I have had it explained to me is that if you want your handsets to be registered to an expansion system then that system needs to be licensed accordingly.

In this scenario I would have thought the additional 5 licenses should be on the IP500, this would give them the 17 IPEndpoint licenses required.

I would imagine if the OP tried to register the additional 5 handsets to the primary server then they would register ok.

I agree that it would be easier if you could just licence the primary server and just register your handsets wherever you want but as I understand SE it doesn't work like that.

 

[tlpeter]

It is confusing i agree.

Note 7 – License can be also administered and used locally on the Secondary
and Expansion. For customers who already have IP500v2 systems that they
migrate to Server Edition expansion systems some of the existing licenses
can stay on the IP500v2. The licenses on the IP500v2 cannot be added to the
central pool of licenses on the Primary Server.

But if you add licenses to the SD card then these will be transfered to the server if i am right.


BAZINGA!

I'm not insane, my mother had me tested!

 

[TelcoAdy]

It says that "some of the licensing can stay on the IP500" and also "the licenses cannot bearded to the central pool"

The way I read that is that if you have licenses on an IP500 and bring it into a SE solution then the licensing is only available on that unit.

I would have thought the same principle would apply for additional ISDN channels

 

[tlpeter]

You are right i think.
But that would be stupid as the IP endpoint licensing should be on the server.
We have a server and IP500v2 and 12 virtual licenses on the IPO.
I am going to try to add more extension to it and reserve the license and see what happens but i will try that later this weekend.


BAZINGA!

I'm not insane, my mother had me tested!

 

[cztech]

Downgraded the new IP500v2 node to 8.1.65, to match the release of the Primary SE. This did not fix the issue, unfortunately. Local IP phones are maxing out at 12 up at a time. Plenty of endpoint licenses available on the Primary SE, but they are not usable - at this time - by this new remote expansion IP500v2.

What is interesting is that this new system is pulling the necessary Server Edition license from the main site. Each node must have it's own SE license, and this new system is utilizing it. That license is centrally located on the Primary SE. So, it's pulling the SE license, but not the endpoint licenses.

Could it have anything to do with how resiliency is setup? I thought that was just for backup situations, not actual license distribution.

The SE w/ Primary and Secondary were already installed by a different BP, I am new to this customer and trying to figure things out. Not helping that I can only bring up 80% of their IP phones right now!

cztech /

http://www.cztechnologies.net

 

[tlpeter]

What does Avaya say about this?


BAZINGA!

I'm not insane, my mother had me tested!

 

[cztech]

We are having also having IPOSS registration delays, so it hasn't gone to Avaya, yet. My support channel went through all configs and the .cfi files, and have verified proper programming is in place. They are speculating that we have a bug. In the meantime, 5 IP endpoint licenses have been purchased for the new 500v2 SD card, so we should have 17 local endpoint licenses soon. Obviously not a great 'technical' solution!

cztech /

http://www.cztechnologies.net

 

[tlpeter]

Not really

BAZINGA!

I'm not insane, my mother had me tested!

 

[cztech]

So we think this is a VCMv1 vs. VCMv2 issue! The VCMv1 (which we have here) has the 12 virtual endpoints, and precludes you from using 'centralized' endpoint licensing! With the VCMv2 (which as stated above does not have the 12 virtual endpoint licenses), you will be able to use centralized endpoint licensing.

I'll update this post. This site was the first of 15+ expansion systems that are going to be tied into the SE network, so we will probably be using VCMv2's moving forward and will return to this issue very soon.

cztech /

http://www.cztechnologies.net

 

[wrenchmonkey]

A couple of notes you may find interesting. You should always use vcmv2's on Server Edition, I thought most of the configurators were updated to allow only the vcmv2's. Additionally, you will want IP phones registering to the 500v2 chassis if you want them to be able to failover. Server Edition endpoints cannot failover to a 500, but 500 endpoints can failover to the Server. Just a few thoughts.

 

[tlpeter]

The VCM32v1 is supported as it is not mentioned as not supported.
They should fix the bug or documentation (probably the last one)

BAZINGA!

I'm not insane, my mother had me tested!