[Serusers] REGISTER problem with the last stable SER version.

[Andrei Pelinescu-Onciul]

On Jul 08, 2005 at 15:18, Ricardo Martinez <rmartinez at redvoiss.net> wrote:
> Hello list.
> 	I detected a strange behavior with my SER. I downloaded the last
> stable version from the CVS.  And it seems to work ok.  But for a particular
> endpoint the register proccess seems to be corrupted.  This is what i have.
> (please check the PORT for the register)
> 
> U 200.113.154.25:12196 -> 10.0.0.35:5060
> REGISTER sip:sipproxy.mydomain.com SIP/2.0.
> 
> 
> U 10.0.0.35:5060 -> 200.113.154.25:12196
> SIP/2.0 401 Unauthorized.
> Via: SIP/2.0/UDP 200.113.154.25:12196;branch=z9hG4bK-e4d3ecd4;rport=12196.
> 
> 
> U 200.113.154.25:12196 -> 10.0.0.35:5060
> REGISTER sip:sipproxy.mydomain.com SIP/2.0.
> 
> U 10.0.0.35:5060 -> 200.113.154.25:12196
> SIP/2.0 200 OK.
> 
> 
> domain: 'location'
> aor   : '5555847110'
> ~~~Contact(0x42326db8)~~~
> domain    : 'location'
> aor       : '5555847110'
> Contact   : 'sip:5555847110 at 200.113.154.25:121962196'

You are probably using fix_nated_contact twice, or fix_nated_contact and
some substitution on Contact.


Andrei