Re: NAT & rfc 3327

Good to hear, thanks.  In addition to REGISTER requests, OpenSER
forwards INVITE/ACK requests as well -- what we've built is a B2BUA.

Jeroen van Bemmel wrote:
> Ryan,
>
> Sounds about right. It appears that in your setup OpenSER is
> proxy/load-balancer only for REGISTER requests?
>
> Regards,
> Jeroen
>
> Ryan Mitchell wrote:
>> Hello,
>>
>> We're using OpenSER for proxy/load-balance in front of our JAIN based
>> b2bua/registrar, and use OpenSER's PATH module to insert Path: headers
>> when needed for NAT'd clients per rfc 3327.
>>
>> The plan is to store PathHeaders with contacts in the registrar, then
>> for new requests that resolve to that contact I'll take the
>> PathHeaders and convert them to RouteHeaders.  At this point the
>> stack should send the request to the first hop in the first
>> RouteHeader (which in our case should be the OpenSER proxy).
>>
>> Does that sound correct?  If there is anyone else that has explicitly
>> implemented rfc 3327 support is this the way to do it?
>>
>> thanks! 
>


-- 
Ryan Mitchell <[email protected]>
Telecom Logic, LLC