Inaki,<br><br> Sorry missed the 'reply to all button'. I think what your saying makes sense, so simply enumerate each server:<br><br>i.e. <br><br>P1 - Set Flag 1<br>P2 - Set Flag 2<br>P3 - Set Flag 3<br><br>these flags will then be written to usrloc, and upon lookup read from usrloc.<br>
<br>In which case I can simply check this $bf psuedo variable for the specific server value, or even potentially do a lookup from a data source w/ avp_db_query and forward to associative proxy correctly by setting the destination uri.<br>
<br>Does this sound feasable? Thanks!<br><br><div class="gmail_quote">On Tue, Apr 21, 2009 at 1:59 PM, Iñaki Baz Castillo <span dir="ltr"><<a href="mailto:ibc@aliax.net">ibc@aliax.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">El Martes, 21 de Abril de 2009, Brandon Armstead escribió:<br>
</div>> Inaki,<br>
<br>
Please, mantain the thread in the maillist.<br>
<div class="im"><br>
<br>
> Thanks for the input -- that does look similar to what I'm looking to<br>
> do, however not 100%. From looking at the RFC it looks as if there is<br>
> always a certain path being traversed, however in my case, its more of a<br>
> "this is not the server that holds this user location socket binding, lets<br>
> forward to the server that does".<br>
><br>
> So in essence:<br>
><br>
> UA1 can register to P1, P2, P3, and so on.....<br>
><br>
> However it does not register to P3 via the means of UA1 REGISTER -> P1 -><br>
> P2 -> P3 (REGISTRATION).<br>
><br>
> It simply registers directly to P1, or P2, or P3, etc....<br>
><br>
> In which case upon user lookup: lookup("location"), I want to be able to<br>
> say "Hey I do not hold the socket for this registration, forward to server<br>
> that does to do the actual lookup(location) and t_relay() to the UA.<br>
<br>
</div>Yes, it's a different scenario.<br>
<br>
You could do some trick:<br>
<br>
- When P1 receives a REGISTER it sets a bflag for it (bflag 1).<br>
- When P2 receives a REGISTER it sets a bflag for it (bflag 2).<br>
- When P3receives a REGISTER it sets a bflag for it (bflag 3).<br>
<br>
When P1 receives a request and performs location for that AoR, it will also<br>
extract the bflags, so P1 checks if bflag 1 is on. If not and bflag 2 is on,<br>
then it routes (by setting $du => without changing the resolved RURI) the<br>
request to P2.<br>
<br>
:)<br>
<font color="#888888"><br>
<br>
--<br>
</font><div><div></div><div class="h5">Iñaki Baz Castillo <<a href="mailto:ibc@aliax.net">ibc@aliax.net</a>><br>
</div></div></blockquote></div><br>