[Sofia-sip-devel] REGISTER Request Timeout (408) always using (invalid) tcp-connection

[Florian Limberger]

Hi!

I'm using nua under linux with tcp. When I switch off my wlan-router, I
get a 408 (request timeout) in the nua_r_register. I then destroy the
corresponding nua-handle and start a register again. When I switch on
the wlan-router again, after some time, the stack continues responding
with 408. When I look at the Wireshark-sip-trace I can see the nua-stack
always retransmitting the tcp-register-packet never tearing down the
tcp-socket and creating an new tcp-connection.

After 10 to 20 minutes the stack prints out
 -- nta: REGISTER (118919049): No route to host (113) with tcp/x.x.x.x]:

and nua_r_register delivers a 503 (service unavailable). The next
register succeeds again. The packet-trace shows, that the stack has
created a new tcp-connection.

Interestingly, when running under windows, the stack immediately returns
a 503 and not a 408 and resets the tcp connection.

Why such difference in the stack-behavior between linux and windows? On
which parameters does it depend if a 408 or a 503 will be returned to
the application and the tcp-connection be resetted?

I'm using 1.12.10.

Any help appreciated.

best regards
fl



--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
___
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel

[Sofia-sip-devel] tcp transportation using only one connection

[Florian Limberger]

Hi!

When using UDP for transportation the sofia-sip stack uses the same 
socket (same src port) for all outgoing logical connections. This is not 
the case with tcp. If I want to do a REGISTER with my proxy/registrar, 
the sip stack creates a new tcp connection (with some arbitrary src 
port) but does not insert this arbitrary port into the contact header. 
Instead, the contact header's port is set to the one of the tcp-server 
socket listening in general at port 5060. Hence, the registrar opens a 
new tcp-connection to my UA.

So could someone give me please a hint how to force the REGISTER-socket 
to a port of my choice or how to get the real port into the 
contact-header-line? Or is there any other possibility to have only ONE 
tcp connection to my register with the UA always being the client?

thanks for any advice,
cheers,
flo

-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK  win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100url=/
___
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel