Skip to main content


Created by Ryan Harris, last modified on 2018.02.07


string It is intended for use with devices registering behind a NAT where the Request-URI should contain the contact that was bound to the AOR during the registration request while the request itself should be sent to the public IP and port number of the NAT "pinhole". It does not add a Route header field to the request like the ;fs_path= or the sip_route_uri options do.


<action application="bridge" data="{sip_network_destination=sip:5551234567@}sofia/external/5551234567@"/>