Re: [SR-Users] bflag mystery

2013-04-23 Thread Seudin Kasumovic
Please don't! It's usefully to have NAT flag in usrloc if you need in script handle SDP. Also, once used flag (bit) can't be re-used anywhere else. Seudin On Wed, Apr 10, 2013 at 8:43 PM, Juha Heinanen j...@tutpro.com wrote: Juha Heinanen writes: however, when i look what gets stores in

[SR-Users] bflag mystery

2013-04-10 Thread Juha Heinanen
i have in config: setbflag(8); xlog(L_INFO, bflags are $bf/$bF\n); save(location, 0x02); and i correctly get to syslog: Apr 10 19:51:48 wheezy1 /usr/sbin/sip-proxy[6722]: INFO: bflags are

[SR-Users] bflag mystery

2013-04-10 Thread Juha Heinanen
Juha Heinanen writes: however, when i look what gets stores in location table, cflags column of the contact has value 384. it is also shown by ul_dump: Cflag:: 384 384 = 256 + 128. i must be missing something trivial. how is it possible that also flag 7 (which is my nat_bflag) gets set

[SR-Users] bflag mystery

2013-04-10 Thread Juha Heinanen
Juha Heinanen writes: if i understood the above correctly, existence of received param in path header of register request, automatically sets nat bflag that (in my case 7). where is that documented? it is documented here: 3.19. path_use_received (integer) If set to 1, the “received”