RE: [reSIProcate] Transport Selection

["Matthias Moetje - TERASENS GmbH" <moetje@xxxxxxxxxxxx>]

Hong,

thanks very much for your reply. I had hoped I could
use the automatic transport selection (TCP, UDP or TLS)
from the stack to avoid checking the target URI parameters
myself. Seems there is no way around doing the transport
selection manually, then?

Best regards,

Matthias


> -----Original Message-----
> From: Hong Yu [mailto:hyu@xxxxxxxxxxx] 
> Sent: Tuesday, March 07, 2006 9:54 PM
> To: Matthias Moetje - TERASENS GmbH; 
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [reSIProcate] Transport Selection
> 
> You can control the transport by calling setForceTarget() on 
> the message to be sent or by calling 
> setFixedTransportInterface/setFixedTransportPort on the user 
> profile you use to send the message.
> 
> Hong
> 
> -----Original Message-----
> From: Matthias Moetje - TERASENS GmbH [mailto:moetje@xxxxxxxxxxxx]
> Sent: Tuesday, March 07, 2006 1:44 PM
> To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [reSIProcate] Transport Selection
> 
> Hi,
>  
> I'm still trying to figure out how to know which transport 
> will be used to send a message before the message is actually 
> sent (to do STUN test).
>  
> Any help would be much appreciated.
>  
> 
> Best regards,
> 
> Matthias Moetje
> 
> 
> 
>