Diana's post made me think - something I should do more often
We have all been using the "fake" SIP provider, which did not work with or without stun. Diana used a "real" SIP provider, which does work with stun.
We have had this problem before with voice gateways using a "fake" SIP provider. Even if you configure stun it does not get used unless you add the paramater to the vg access number, or in our case to the speed dial. With stun configured on my "fake" SIP provider (sp2 in my case) this does not work:
sp2(talkshoe@66.212.134.192)
This does work every time:
sp2(talkshoe@66.212.134.192;op=s)
@ mikefoley
Using your "fake" SIP provider on ITSP Profile D > General:
STUNEnable: check
STUNServer: stun.ideasip.com (or stun server of your choice)
Set speed dial to sp4(talkshoe@66.212.134.192;op=s)
Talk about re-inventing the wheel every day! Now where did I leave my glasses ...