PS. In pondering these matters, it is useful to compartmentalise the idea of
"address to which request is sent" (logically) from "the network and
transport-layer destination (e.g. IP/port) used to reach the endpoint". In the
case of NAT, they are not one and the same.
The RURI stays equal to t
Thank you Alex.
On 18 August 2015 at 14:06, Alex Balashov wrote:
> It should not change during the call. The rules prohibit that. The only
> way to change the remote target address within a dialog is, ironically, via
> a reinvite and/or response, but that would need to come from the UA itself.
It should not change during the call. The rules prohibit that. The only way to
change the remote target address within a dialog is, ironically, via a reinvite
and/or response, but that would need to come from the UA itself.
Your best bet to ensure that the NAT pinhole to the endpoint does not g
Apologies, you're right that the lookup() would not apply in this case.
So what, if anything, should Kamailio do in the case where a SUA's address
changes during a call?
On 18 August 2015 at 13:42, Alex Balashov wrote:
> Hello,
>
> On 08/17/2015 11:22 PM, David Cunningham wrote:
>
> We have a
Hello,
On 08/17/2015 11:22 PM, David Cunningham wrote:
We have a scenario like this:
SUA -> Kamailio with registrar module -> Asterisk
A call from the SUA is set up with SIP timers, and after 15 minutes
Asterisk sends a re-INVITE to Kamailio to forward on to the SUA. That
re-INVITE has a RURI
Hello,
We have a scenario like this:
SUA -> Kamailio with registrar module -> Asterisk
A call from the SUA is set up with SIP timers, and after 15 minutes
Asterisk sends a re-INVITE to Kamailio to forward on to the SUA. That
re-INVITE has a RURI with the address and port of the SUA at the time t
