I'm starting to become superstitious and not do softphones on 5060/5061 anymore. I've seen it with my own two eyes on a traceSBC that my Android hijacks port 5061.
So, when I'm all on mobile - I see registration and PPM just fine from my mobile public IP
When I'm on wifi, I see my mobile public IP register SIP and then PPM come from my wifi IP and my registration doesn't work.
So I pulled out my sim card. Then I just never sent any SIP registration.
Though, if you can hotspot a laptop thru the mobile and be OK and also run the laptop on wifi and be OK, you can prove it out.
Re certs:
A lot is changing. If you got a SMGR that was upgraded from 6.3, then the CA is still SHA1 signed even though all the SM certs are SHA256. iOS will start rejecting that soon.
What I've seen people do is get a cert with a bunch of subjectAlternativeNames. like aads.customer.com, sm8-sm100.customer.com, etc. So, if you make 1 key and 1 csr and get 1 cert back you can still load it as a 3rd party cert on more than 1 thing - like a SBC or AADS or a SM or a web gateway for Equinox web collaboration.
So if your SBC outside has that public cert AND you pop it on the AADS inside, then if you got the DNS stuff setup right, the equinox client can log in to AADS and download his dynamic config which can SET TRUSTCERTS SMGRCA.pem and use the 'coalesced truststore'. Apps can have their own trust store on top of the device's - firefox is like this on Windows already. So, doing that, anyone can get on AADS and then told to have their app trust SMGR thereafter without having to go through a whole exercise of distributing certs en masse.