So, we discovered an interesting thing about 3CX for Windows over the MPLS yesterday that really makes me guy 'huh?'. I currently have a test user who last week I setup to use 3CX for Windows from her house, we ran a hand full of test calls to both users inside the office as well as making external calls, both of which require the use of the Patton 4114 to bridge between our existing PBX and 3CX, and all was fine. Then Monday she goes to one of our remote offices connected via an MPLS and we get an established call, no audio, then disconnect. As a test we moved the Out of Office address into the In Office address, save, call, audio works fine. Then we put what was originally in the In Office into both In and Out, save, audio works fine. All the while 3CXPhone to 3CXPhone are fine with all three configurations. DNS from the computer resolves both correctly. The FQDN in Out of Office is the same used both internally and externally. Why on earth can I put the FQDN or IP into both fields and it works flawlessly but when I leave it the way the provisioning profile has it it fails? It seems to me that the easiest thing is to be able to modify the provisioning profile to include the FQDN for both In and Out. Anyway for me to do that?