Trunk and registrations from same IP into FreeSWITCH

Hi,
in our setup we have a requirement for a trunk from another PBX to our FreeSWITCH server to co-exist with registrations from the same other PBX to the same FreeSWITCH server.
So we start with our other PBX registered on several extensions and this works fine. Then, we add the IP address of the other PBX as a trunk and the trunk works. However, the SIP registrations (Which appear to still be OK) no longer pass calls through.
We had a similar situation with asterisk and we were able to get round it by adding:

[global]
endpoint_identifier_order=auth_username,username,ip,anonymous

to the target server’s config.
Is there something similar we can to to FreeSWITCH?

We’ve found a way to do this by pointing the trunk at the external profile’s port 5080, creating a new ACL for the trunk IPs and applying it to the external profiles.
This allowed the registrations to not be in the the ACLs and the trunk to be in one despite originating from the same IP address.