Klaus,
This is perfect as far as what I'm looking for,
although this is going to be for a production environment, so I'm a
little hesitant right now as to throwing it into production via this
method. Would you happen to have any better suggestions other than a
avp_db_query to pull the socket from openser.location for the current
$rU, or is that as good as its going to get?
Thanks!
(sent reply to all)
Brandon Armstead schrieb:It is just that you have to call the fetch.. function (1st link) first, othervise the PVs will not be available.
Klaus,
That second link looks like exactly what I'm looking for, thanks!
klaus
Users@lists.kamailio.org <mailto:Users@lists.kamailio.org>
On Wed, Apr 22, 2009 at 5:31 AM, Klaus Darilion <klaus.mailinglists@pernau.at <mailto:klaus.mailinglists@pernau.at>> wrote:
Maybe this can help you:
http://www.kamailio.org/docs/modules/devel/registrar.html#id2530856
http://www.kamailio.org/docs/modules/devel/registrar.html#id2531067
Brandon Armstead wrote:
Hello guys,
Is there a method upon using lookup("location") to also pull
out the "socket" information for the original location the UAC
registered to, for scenarios of this example:
P1 & P2 share same usrloc database.
UA1 registers to P1
UA2 registers to P2
UA1 calls UA2
UA1 invites -> P1 -> INVITES -> UA2 (bypassing P2 -- where the
actual nat binding is).
Now upon P1 looking up usrloc for UA2, I would like to recognize
that P1 is not the Proxy to deliver the call, and forward the
request to P2 to send to UA2.
So currently I have:
UA1 INVITE -> P1 INVITE -> UA2
I wish to have:
UA1 INVITE -> P1 INVITE -> P2 INVITE -> UA2
Is there an easy method to do this? I have been looking at the
new nat traversal module it looks like it is doable with this
(any further input as far as that?). Also is it possible with
the classic Nat Helper module? Any input is appreciated, thanks!
------------------------------------------------------------------------
_______________________________________________
Kamailio (OpenSER) - Users mailing list