This is going to be a bit of an odd situation, but perhaps might become more and more common (as mobile phone SIP clients utilize PUSH proxies instead of the battery draining direct registering with SIP servers).
I have a SIP client which can be on the same RFC-1918 LAN as my Asterisk server. Even though it's on the same LAN as the Asterisk server, it's registration comes from an IP address external to the LAN. This is because the client is registering to the local Asterisk server through a SIP proxy server that is external to the LAN. Is there any way for Asterisk to determine that this is what is happening and to direct/setup the media session to the client on it's LAN address? Put another way, even though the registration comes from an external (NATted) IP address, I want the media connection to stay within the LAN. One solution of course is to add the external IP address of the SIP proxy -- the address that the client's registration is coming from -- to localnet but that breaks the use-case of the SIP client (which is mobile) leaving the LAN and having an external IP address. Ultimately I am hoping there is something in the registration that will indicate to Asterisk that even though the registration is coming from an external IP address, the client has an internal IP address that is on the same network as it is and sets the IP address in the SDP payload to a local IP address. I do realize this is fairly non-standard configuration so it might not be possible. Any suggestions would be welcome. Cheers, b.
signature.asc
Description: This is a digitally signed message part
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- Check out the new Asterisk community forum at: https://community.asterisk.org/ New to Asterisk? Start here: https://wiki.asterisk.org/wiki/display/AST/Getting+Started asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
