Public IP in Contact header
Can anybody please point me to settings or a freeswitch state that makes sofia put public IP into the Contact header? Currently I have SIP clients behind NAT registering to freeswitch. Freeswitch registers these clients with their respective private IPs. Bellow is the profile status. ================================================================================================= Name internal Domain Name N/A Auto-NAT false DBName sofia_reg_internal Pres Hosts 178.238.X.Y,178.238.X.Y Dialplan XML Context default Challenge Realm auto_from RTP-IP 178.238.X.Y Ext-RTP-IP 178.238.X.Y SIP-IP 178.238.X.Y Ext-SIP-IP 178.238.X.Y URL sip:mod_sofia@178.238.X.Y:5060 BIND-URL sip:mod_sofia@178.238.X.Y:5060;maddr=178.238.X.Y HOLD-MUSIC local_stream://moh OUTBOUND-PROXY N/A CODECS IN PCMA,PCMU,GSM,G7221@32000h,G7221@16000h,G722 CODECS OUT PCMA,PCMU,GSM,G7221@32000h,G7221@16000h,G722 TEL-EVENT 101 DTMF-MODE rfc2833 CNG 13 SESSION-TO 0 MAX-DIALOG 0 NOMEDIA false LATE-NEG false PROXY-MEDIA false AGGRESSIVENAT false STUN-ENABLED true STUN-AUTO-DISABLE false CALLS-IN 0 FAILED-CALLS-IN 0 CALLS-OUT 0 FAILED-CALLS-OUT 0 Registrations: ================================================================================================= Call-ID: 3454998XYZ@192_168_59_102 User: 1@ribtjuhd Contact: "383372XYZ" <sip:1@192.168.59.111:5060> Agent: A580 IP/022270000000 Status: Registered(UDP)(unknown) EXP(2011-11-02 13:30:43) EXPSECS(100) Host: eva IP: 81.90.X.Y Port: 22055 Auth-User: 1 Auth-Realm: ribtjuhd MWI-Account: 1@ribtjuhd Thanks! Hynek
RTP-IP 178.238.X.Y Ext-RTP-IP 178.238.X.Y SIP-IP 178.238.X.Y Ext-SIP-IP 178.238.X.Y Let's take a look at what 'ext' might be! Keep in mind you'll need to change it on your external profile as well. On Wed, Nov 2, 2011 at 5:39 AM, Hynek Cihlar <hynek.cihlar@gmail.com> wrote:
Can anybody please point me to settings or a freeswitch state that makes sofia put public IP into the Contact header? Currently I have SIP clients behind NAT registering to freeswitch. Freeswitch registers these clients with their respective private IPs. Bellow is the profile status.
================================================================================================= Name internal Domain Name N/A Auto-NAT false DBName sofia_reg_internal Pres Hosts 178.238.X.Y,178.238.X.Y Dialplan XML Context default Challenge Realm auto_from RTP-IP 178.238.X.Y Ext-RTP-IP 178.238.X.Y SIP-IP 178.238.X.Y Ext-SIP-IP 178.238.X.Y URL sip:mod_sofia@178.238.X.Y:5060 BIND-URL sip:mod_sofia@178.238.X.Y:5060;maddr=178.238.X.Y HOLD-MUSIC local_stream://moh OUTBOUND-PROXY N/A CODECS IN PCMA,PCMU,GSM,G7221@32000h,G7221@16000h,G722 CODECS OUT PCMA,PCMU,GSM,G7221@32000h,G7221@16000h,G722 TEL-EVENT 101 DTMF-MODE rfc2833 CNG 13 SESSION-TO 0 MAX-DIALOG 0 NOMEDIA false LATE-NEG false PROXY-MEDIA false AGGRESSIVENAT false STUN-ENABLED true STUN-AUTO-DISABLE false CALLS-IN 0 FAILED-CALLS-IN 0 CALLS-OUT 0 FAILED-CALLS-OUT 0
Registrations:
================================================================================================= Call-ID: 3454998XYZ@192_168_59_102 User: 1@ribtjuhd Contact: "383372XYZ" <sip:1@192.168.59.111:5060> Agent: A580 IP/022270000000 Status: Registered(UDP)(unknown) EXP(2011-11-02 13:30:43) EXPSECS(100) Host: eva IP: 81.90.X.Y Port: 22055 Auth-User: 1 Auth-Realm: ribtjuhd MWI-Account: 1@ribtjuhd
Thanks!
Hynek
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
You also have to put in local-network-acl so it knows when to lie and when not to lie in the contact. /b On Nov 2, 2011, at 11:54 AM, Brad Mina wrote:
RTP-IP 178.238.X.Y Ext-RTP-IP 178.238.X.Y SIP-IP 178.238.X.Y Ext-SIP-IP 178.238.X.Y
Let's take a look at what 'ext' might be! Keep in mind you'll need to change it on your external profile as well.
Brad, Brian, thanks for your replies Actually, the switch is not used in the standard setup, where the external profile is used as a gateway and the internal (default) profile for directly connected sip clients. In my case, the switch has two profiles. The so called external is connected to another switch, just passing calls. The connection is routed. The second profile (internal) which is giving me troubles, is used for registering SIP clients. The SIP clients are usually behind their own NAT routers. SIP-IP and EXT-SIP-IP are both the same public IP, since the router is publicly visible on the internal profile. On the external profile, they are assigned to a private internal IP. The switch is sitting on two subnets. Now, the local-network-acl is set to localnet.auto on both profiles. I was assuming ACLs are used solely for security! Hynek On Wed, Nov 2, 2011 at 6:16 PM, Brian West <brian@freeswitch.org> wrote:
You also have to put in local-network-acl so it knows when to lie and when not to lie in the contact.
/b
On Nov 2, 2011, at 11:54 AM, Brad Mina wrote:
RTP-IP 178.238.X.Y Ext-RTP-IP 178.238.X.Y SIP-IP 178.238.X.Y Ext-SIP-IP 178.238.X.Y
Let's take a look at what 'ext' might be! Keep in mind you'll need to change it on your external profile as well.
FreeSWITCH-users mailing list FreeSWITCH-users@lists.freeswitch.org http://lists.freeswitch.org/mailman/listinfo/freeswitch-users UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users http://www.freeswitch.org
participants (3)
-
Brad Mina
-
Brian West
-
Hynek Cihlar