[reSIProcate] Transport selection and register/lookup behavior

Gabriel Hege gabriel-mailinglists at gmx.de
Fri Jul 18 13:30:50 CDT 2008


Hi!

I have two questions.
The first one is concerning the stack:
Is it possible to have Resiprocate switch the transport used for sending 
an outgoing message, when the first transport does not succeed within a 
certain timeframe? For example when I first send a message to a UAS and 
don't specify a transport in the URL, it is being sent via UDP. When the 
other side only listens on TCP, I have to wait until the transaction 
expires, when I do not want to create a concurrent transaction.
The way SipX handles that is to first send it via UDP and when the 
message is being retransmitted it also tries it via TCP. Is it possible 
to have a similar behavior in Resiprocate?


The second question is about Repro:
When a client registers with the proxy and specifies a port in the 
To-URI, you always have to specify the port, when calling that client 
via Repro. This is even the case when the specified port is the default 
port (e.g. 5060).
Wouldn't it it make sense for Repro to have the URIs match on lookup 
even though only one of them explicitly specifies the (default) port?


best regards,
  gabriel hege



More information about the resiprocate-devel mailing list