Re: [reSIProcate-users] B2BUA and TLS transport
Support for this type of functionality was recently added to repro
(outbound support). If you are using DUM ServerRegistration then the
ContactInstanceRecord contains a mReceivedFrom member. Looks like you
would also need to enable InteropHelper::getRRTokenHackEnabled() in
order to get the mReceivedFrom set. mReceivedFrom can then be used to
route (Invite) requests to this registered user by calling
sipMsg->setDestination(contactInstanceRecord->mReceivedFrom).
Note: You will probably want to ready the comments in
ServerRegistration::dispatch first, it contains warnings about doing
what you want to do.
Byron - feel free to correct any errors in my analysis. : )
Scott
On Tue, Sep 9, 2008 at 2:20 PM, Dario Bozzali
<Dario.Bozzali@xxxxxxxxxxxxxxxxx> wrote:
> Hello,
> I'm trying to write a B2BUA (it should work also as a registrar) using
> DUM. Using UDP transport now I'm able to register UAs to B2BUA and to
> send/receive calls between UAs through B2BUA. I'm facing some problems
> using TLS transport (I suppose that it will be the same using TCP
> transport, but I haven't tried yet) since it's not clear to me how to
> reuse the connection opened by UA on REGISTER to send INVITE/ACK/BYE
> etc. messages from B2BUA to UA. My B2BUA now is able to receive REGISTER
> messages using TLS transport, but if B2BUA uses the Contact address
> received on REGISTER message to send INVITE then a new connection is
> opened.
> Should I use rport parameter value received with REGISTER to override UA
> Contact information? Should I set INVITE target address using
> SipMessage::setDestination() or Tuple::mFlowKey? Do you know if any
> sample code is available?
> Any help would be appreciated. Thank you in advance.
> Dario.
> _______________________________________________
> resiprocate-users mailing list
> resiprocate-users@xxxxxxxxxxxxxxx
> List Archive: http://list.resiprocate.org/archive/resiprocate-users/
>