I know PLDS pretty good on the enterprise side. You can be in a bad place where you can add a hostID under one customer/FL#/group/etc and assign licenses to it while also buying new entitlements and activating them under another customer number. You can also add hostIDs for that other customer number and they can be the same as your original system.
What you can end up with is :
PLDS having under FL 0051234567 a hostID of 00-11-22-33-44-55 that has IPO licenses for 31 endpoints, 16 PRI channels, etc
PLDS having under FL 0059876543 a hostID of 00-11-22-33-44-55 that has IPO licenses for 10 extra IP endpoints
You can generate a license for the hostID with either everything under one FL or everything under the other FL but you can never combine them because the entitlements aren't owned by the same customer FL.
If you look in PLDS under Activation Records for the original license, you'll see who the owner is and you should make sure that is the same 'owner' as the new entitlements.
If they're a new customer for you, try using the CAT tool. support.avaya.com-->diagnostics and tools-->registration and licensing-->customer authorization tool
It lets you punch in a FL#, and a customer contact to authorize you, and that will bring that customer's FL under your management in Avaya's portals.
I guess in plain English I'd say that older license models like ADI have the license sticky to the system serial number. In PLDS, it's sticky to the combo of partner+customer.
Even with Aura stuff, I couldn't just deal with a customer with another partner and sell them 10 licenses and go in PLDS and "add" that to what they already had. I need to use the CAT tool to make that customer tied to my partnerID. Then I can activate 10 licenses and use their hostID and give them a license with everything they had before + the new 10 users.
Maybe that helps you out
