<div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>El Wednesday 19 December 2007 13:20:07 I?aki Baz Castillo escribi?:
<br>> El Wednesday 19 December 2007 13:15:35 David Villasmil Govea escribi?:<br>> > What's the difference between<br>> ><br>> > setbflag and setflag<br>> > ??<br>><br>> <a href="http://www.openser.org/dokuwiki/doku.php/utils:flags" target="_blank">
http://www.openser.org/dokuwiki/doku.php/utils:flags</a><br><br>Note that if you use setbflag into a "route" you set the bflag for ALL the<br>branches (there could be more than one branch because pararell forking and
<br>so).<br><br>If you want to set bflag just for a branch you should use "setbflag"<br>into "branch_route".<br><br>And NEVER do "isbflagset" into a "route" since the result can be unexpectable
<br>(if a branch has that bflag active and other one not active, "isbflagset"<br>in "route" could return 1 or 0 depending on which branch examinates before).<br><br></blockquote></div><br>I ask, because i had this cfg file that was working perfectly with nat/rtpproxy. I replace it with a new cfg that was using bflag instead of flag. client-rtpproxy-client rtps stopped working. When i replace those bflags with regular flags it started working again!...
<br><br>Also, as i read there, "per branch" means each location... talking about location, is there a reason a client would have 98 almost exactly alike locations? but for the id, they're the same... weird. And i started seeing lots of "max branch exceeded" on the syslog. We do not limit branches because a client could have his softphone and ata logged in...
<br><br><br>thanks a lot<br>