Hello,

I am using the nua interface of sofia-sip 1.12.8 in my application. With 
nua_create() I specify 
the URLs to listen on as follows:

nua = nua_create(root,  event_callback,   NULL, 
                              NUTAG_URL("sip:ip:5060;transport=udp,tcp"), 
                              NUTAG_SIPS_URL("sip:ip:5061;transport=tls"),
                              TPTAG_CERTIFICATE(certificate_dir),
                              TAG_END());

Where "ip" is my local interface ip.

This works fine so far. 

My question now is: If there is incoming request like an INVITE and my callback 
function gets
called, how do I know which port this request arrived on? 

The problem is that I need to know on application level if the request used 
udp/tcp or tls. I had
a look into freeswitch code and they seem to use the contact header to find out 
if the request came
over tls. Unfortunately it is possible to send a request to the udp socket of 
my application (over udp)
with a contact header like this: "sips:[EMAIL PROTECTED];transport=tls". In 
this case application believes
that the request used tls, but actually is unencrypted.

Can anybody give me a hint how to get to know the transport used by incoming 
requests on application level?

Using two nua_t objects, one for udp/tcp and one for tls could be a solution, 
but I would prefer using a single nua_t 
object for all transports.

Thanks in advance,
Timo


_______________________________________________________________
Schon gehört? Der neue WEB.DE MultiMessenger kann`s mit allen: 
http://www.produkte.web.de/messenger/?did=3016


-------------------------------------------------------------------------
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

Reply via email to