[OpenSIPS-Users] fix_nated_contact()
Bogdan-Andrei Iancu
bogdan at voice-system.ro
Thu Jun 25 20:46:07 CEST 2009
Hi Anil,
The fix_nated_contact() function do replace the contact with the IP and
Port where the message came from. Indeed, with TCP, things are a bit
more complicated as the communication may be asymmetric (the port
advertised by sender in contact is a receive port and may have nothing
to do with the port where the message is sent from).
Btw, is there any nat involved?
Regards,
Bogdan
Anil M Pannikode (hotmail) wrote:
> Our situation is like this
>
> SIP Client <- TCP -> OpenSIPS <- UDP -> SIP / Media server
>
> SIP client is behind firewall.
>
> Initial invite (Voice) comes from SIP client. Media servers 200 OKS and
> initiates a T.38 INVITE (for switching to Fax) and in our media server , it
> starts a new transaction and OpenSIPS is not able to relay the re-invite
> back to SIP client as the Contact info contains an internal IP address.
>
> If I use fix_nated_contact(), it overwrites and IP address and Port number
> (to say something like IPAddres:17687) and I actually want the port number
> to remain as 5060 which is what was in the initial Contact.
>
> Anil
>
>
> -----Original Message-----
> From: Bogdan-Andrei Iancu [mailto:bogdan at voice-system.ro]
> Sent: Tuesday, June 23, 2009 12:14 PM
> To: Anil M Pannikode (hotmail)
> Cc: users at lists.opensips.org
> Subject: Re: [OpenSIPS-Users] fix_nated_contact()
>
> Hi Anil,
>
> Only if you use a manual subst() operation over the contact
> header....but why would you like to skip the port ?
>
> Regards,
> Bogdan
>
> Anil M Pannikode (hotmail) wrote:
>
>> Rewrites Contact HF to contain request's source address:port.
>>
>> IS there a way to just overwrite the source address and not port ?
>>
>>
>>
>> Anil
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>>
>
>
>
>
More information about the Users
mailing list