3 Feb
2010
3 Feb
'10
4:10 p.m.
On 02/03/2010 04:04 PM, Iñaki Baz Castillo wrote:
El Miércoles, 3 de Febrero de 2010, Alex Balashov
escribió:
Iñaki, you are correct. Sorry, I was confused looking at my config; it
turns out I was thinking of the NAT bflag that comes from the registrar.
What about using add_rr_param() to indicate NAT somehow so that this
flag can be fished later out of the Record-Route header / Route set on
sequential requests and replies?
--
Alex Balashov - Principal
Evariste Systems LLC
Tel : +1 678-954-0670
Direct : +1 678-954-0671
Web : http://www.evaristesys.com/
Oh, wait. I think I understand what you're
asking. Set a flag when the
initial INVITE is being processed and NAT is detected; this will show
up in the
When handling the initial INVITE from the customer set a flag. This
will show back up on re-INVITE. Works for me.
Hi, I don't understand what you mean above as a bflag only exists per
transaction so it will not be available within the re-INVITE transaction.