Just an update on this, we eventually got it resolved / a work-around by having the license/support moved to different deployment ID’s. Mike at Sangoma really got things moving for us and got it taken care of.
@mfredrickson In our case, it was broken out of the box (appliance) with the factory deployment ID, no migrations or any of the sort had been performed. Definitely feels more like a back-end issue/administrative side versus a tech issue since the deployment ID change fixed it.