Thanks, we are able to reproduce this issue for a custom dial plan with ‘4' + 4 digits, standard local dialing permission and a GW assigned as you describe below. It is tracked at
At first glance it looks like the bean does not get the permission manager instantiated properly, and a private transient m_permissionManager declared variable in DialPlan.java looks suspect, as the transient keyword can affect spring bean creation.
Not sure why the error only triggers with this particular dial plan definition, but could perhaps be injection timing related. Anyhow, should be a simple fix and we will include it in update 8 shortly.
We have already fixed the missing SBC authentication records for next update 8, and are looking for a simple solution to the custom logo issue with this update as well.