< Previous by Date | Date Index | Next by Date > |
< Previous in Thread | Thread Index |
I found that remote target could be updated by calling setForceTarget() in DUM when sending BYE.UA B sends INVITE to UA A and starts a dialog. UA B is behind a static NAT. UA A hangs up by sending BYE. It doesn't reach UA B because of bad Contact header (a private IP address behind NAT) in initial INVITE.Hi!I don't want to modify outgoing request or change local connection parameters.
Is it possible to change remote target in app above DUM for all potencial requests (not just BYE) from UA A within dialog?
Another way could be setting the remote target when INVITE request is received from remote UA (B). This has been already done in Dialog.cxx with data from actual Contact header, but again I don't know how to set the remote target outside the DUM.
Thanks!Regards,Gordana2013/12/4 Scott Godin <sgodin@xxxxxxxxxxxxxxx>
Check out the Profile setting: setOverrideHostAndPort.You may also need to adjust the IP address in your SDP as well. This can be done with an outbound decorator. See https://www.resiprocate.org/Modifying/Decorating_messages_sentRegards,ScottOn Wed, Dec 4, 2013 at 5:23 AM, Gordana Nikolic <gordana.nikolic6@xxxxxxxxx> wrote:
_______________________________________________Hi!Regards,
UA B behind NAT initiates call to UA A by sending INVITE with his address behind NAT in Contact header.
Response sent from UA A reaches the UA B, since "received" tag is inserted in Via header.
If UA A sends BYE, it will not reach UA B, because destination IP is taken from Contact header from INVITE (which creates dialog).
Is it possible to change destination IP from application above DUM?
Gordana
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/