Well .. it took me a while to figure this out, and I was looking for either
a confirmation that is was a proper way to quietly deal with redirection, or
suggestions for other approaches. It sounds like what I have is fine, so
I'll stick with it.
Thanks,
Ron
-Original Message-
From: sr-us
I have an instance of Kamailio configured as an outbound proxy and I want to
be able to hide the fact the a 3XX redirection result may have been
encountered while attempting to route the call. I am using the fragment
below and it does appear to work, but I am wondering if there is a better
way.
Thanks Daniel.
I am now using record_route_advertised_address() to set the alternate
address rather than record_route_preset() followed by record_route(). Also,
I am able to add the tag using add_rr_param(). The documentation for the
record_route_preset function isn't clear that it actually a
One additional bit of information. Here is a message flow diagram of the call
scenario. The circled message is where the Record-Route header is added.
http://www.siplabs.net/tracebin/record-route/message-flow-diagram.png
Thanks,
Ron
From: sr-users [mailto:sr-users-boun...@lists.sip-
I have been away from Kamailio for a while and starting working on a project
where it would be a good fit.
I am having a problem when I try to add a Record-Route header with a tag. I
see a message in the log indicating that a Double attempt to record-route
was made, and the tag that I specifie
I did end-up using the http_query() function (and {s.escape.param} for
parameter url-encoding) to send an HTTP request to a Java web server which
has access to the business logic. The server returns the routing data in
JSON format so I used the json_get_field() function to pull-out the field
data.
Two main issues are that there is a size limitation with the payload which
can be carried with the RPC mechanism (limited to the size of a PV), and
that route block processing does not continue after calling the jsonrpc
functions.
-Original Message-
From: sr-users-boun...@lists.sip-router
I am the OP. I actually have a solution running now, using JSON-RPC as the
connector between Kamailio and the Java EE business logic. I am looking for
an alternate solution to resolve the limitations with the RPC mechanism.
Performance is not an issue at all. In-fact performance is barely a
cons
I am looking for a way to integrate Java business logic with Kamailio to
influence routing decisions, add/remove/modify headers, record
accounting-related information, etc. A while back there was a project named
WeSIP, but it doesn't appear to active anymore.
Is anyone doing something like thi
