RE: [reSIProcate] DUM: setting custom Contact in SIP messages

["Derek MacDonald" <derek@xxxxxxxx>]

I was also looking at this, but don't we also want the vias to be populated
with the external ip/port combination?  Rport will provide this for proxies
that support rport, but not all proxies do, and some don't do received
properly. 

This wouldn't be hard, I just wonder what affect it would have on how
TransportSelector determines which transport to use.

If we think this is the way to go, we could easily add a setDefaultContact
to dum, and if this is set have the via be populated using the host and port
from this NameAddr.


--Derek

> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:resiprocate-
> devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Jason Fischl
> Sent: Wednesday, September 01, 2004 9:09 AM
> To: Dmitry Semyonov; resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: RE: [reSIProcate] DUM: setting custom Contact in SIP messages
> 
> This is a good point. I will try and fix this in dum. It seems like the
> profile should have a field to specify a preferred contact to fill in on
> any
> request/response that is forming or in a dialog.
> 
> Jason
> 
> 
> > -----Original Message-----
> > From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
> > [mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx]On Behalf Of
> > Dmitry Semyonov
> > Sent: Tuesday, August 31, 2004 3:42 AM
> > To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: [reSIProcate] DUM: setting custom Contact in SIP messages
> >
> >
> > Hello.
> >
> > Recently I've played with a device behind NAT and wanted DUM to
> > properly set the Contact field of SIP header to the IP of NAT box.
> >
> > I noticed that DUM correctly sets the field itself if INVITE is coming
> > from wire, (i.e. it contains NAT IP address in proper places). But if
> > I want to initiate invite session via DUM, I have to set the field
> > manually, i.e. something like the following:
> >
> >    SipMessage is_msg = dum->makeInviteSession(dstAor, aor, ua.sdp);
> >    NameAddr my_contact(MY_AOR);
> >    is_msg.header(h_Contacts).clear();
> >    is_msg.header(h_Contacts).push_back(my_contact);
> >    dum->send(is_msg);
> >
> > because I have not found another way to tell DUM what Contact to use.
> >
> > The above example works, but then I have to do the similar trick for
> > all the messages I want to send within this dialog. And the worst
> > thing - DUM automatically sends ACK in response to 200 OK, so the
> > Contact field in this ACK remains incorrect.
> >
> > Could someone confirm that DUM does not provide simple way to use
> > own Contact, or point me to the right direction?
> > Thanks.
> >
> >
> > ...Bye..Dmitry.
> > _______________________________________________
> > resiprocate-devel mailing list
> > resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> > https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
> >
> 
> 
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel