<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Apr 30, 2009, at 1:49 PM, Iņaki Baz Castillo wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>2009/4/30 Adrian Georgescu <<a href="mailto:ag@ag-projects.com">ag@ag-projects.com</a>>:<br><br><blockquote type="cite">You can use the dialog module to do the same and generate your own correct<br></blockquote><blockquote type="cite">BYEs instead of relaying them, couldn't you?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">You have full control over the reply route and can do all you describe in<br></blockquote><blockquote type="cite">the proxy, can't you?<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">What can a B2BUA detect that the proxy cannot? You can inspect all headers<br></blockquote><blockquote type="cite">and perform acc and send BYE from the proxy too.<br></blockquote><br>No, a proxy is fully vulnerable to a spoofed BYE, why? because the<br>proxy MUST route the BYE according to RURI, Route headers..., while a<br>B2BUA doesn't route it, just "eats" it and generate a new one in leg<br></div></blockquote><div><br></div>As far as I know with OpenSIPS you could chose, through configuration, to not relaying the BYEs all together and generate the BYE in turn yourself based on existing dialog info. Would this solve this scenario?</div><div><br></div><div>Adrian</div><div><br></div><div><br><div><br></div><div><br></div></div></body></html>