>2008/4/1, Timo Bruhn <[EMAIL PROTECTED]>: >> In my scenario a client (with sofialib) registers with to my application >> (nua-api, sofia 1.12.8) over tls.> >> Because of the already know problem the client does not write the used tcp >> port to >> the contact header, but the port specified with NUTAG_SIPS_URL in >> nua_create(). >> >> If I want to call this client through the open tcp/tls-connection know, I >> dont't send the request to the port used >> I received in contact-header, but to the port really used by the client (I >> save the port when i receive the register >> from the client and put it into the to-header in my outgoing invite). >> >> This works and the tcp/tls-connection opened by client for the register >> request is re-used for the invite. >> But when I the send an ACK or BYE to the client, the stack always uses the >> port the client >> specified in contact-header in register.
>So you have two UA's using Sofia-SIP, one (A) registers from NATted >network and another one (B) calls outside through the registrar/proxy. >When B sends an INVITE to A, the proxy uses correctly the connection >incoming from UA A for outbound INVITE. However, the ACK and BYE >requests sent by UA B within dialog are routed directly to the Contact >address given by A? >> Is there any known solution to this problem? Can I specifiy the destination >> port when calling >> nua_bye() or nua_ack()? >Basically, this is outbound problem: the proxy should add a >Record-Route header to the INVITE it sends to A. (A copies >Record-Route to the response, and B uses the Record-Route URI when >sending the ACK and BYE.) The proxy should also map the incoming >ACK/BYE to the A's connection somehow (it can use methods described in >draft-ietf-sip-outbound, for instance). Thanks for our quick answer. Unfortunately I haven't described my scenario clear enough. In fact I am using nua-api to implement a proxy/registrar, just like freeswitch guys do. So I am the proxy and call an UA previously registered to me over tcp/tls. This UA is not behind NAT, it is in the same subnet as the proxy is. Very simple configuration. The UA (sofia 1.12.6) registers with the proxy(me, sofia 1.12.8) with contact address like this: "sips:[EMAIL PROTECTED]:5060". But in fact it uses a different tcp port for the register. I think Stefan Leuenberger reported this to the list some months ago. Now I save the tcp port used for the register request by the UA to overcome the problem. Lets say its port 1234. When the proxy wants to call the UA over tls it re-uses the connection (just because the UA does not have certificates). Therefore i use a to-header like this: "sips:[EMAIL PROTECTED]:1234;transport=tls". This works. The INVITE is sent through the previously opened connection. After the UA responded with 200 OK, I send the ACK. Unfortunately this ACK is sent to 192.168.0.2:5060 through a new tcp connection. Same Problem with BYE. _________________________________________________________________________ Mit der Gruppen-SMS von WEB.DE FreeMail können Sie eine SMS an alle Freunde gleichzeitig schicken: http://freemail.web.de/features/?mc=021179 ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
