pv_xavp_print() has enlightened me to the fact that ds_select_dst() does not
reset the dispatcher destination set XAVP. It only adds the selected
destinations to the top of the XAVP stack. There are some ds_select_dst() calls
for group 1 and group 2 earlier on in request_route, and those
Any recommendations for a tool that can generate SBOM for a Kamailio
instance based on configured modules?
Thanks,
Ivan
__
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to
Hi Henning,
I used xavp_params_implode() and xlog() to log the contents of the XAVP
You can see the contents of the XAVP in the previously provided log lines
(showing the contents before and after the ds_next_dst() call):
FAILURE ROUTE: Already have replies on this transaction. Selecting next
Hello,
have not checked the code, but the ds_next_dst() should just get the next
destination from the configured XAVP.
Have you tried to print it e.g. with pv_xavp_print() to see if there is maybe
too much or wrong content inside?
Cheers,
Henning
--
Henning Westerholt -
Hi Patrick,
That's exactly the workaround that I have in my back pocket - I tested it and
it works well. I am still interested in getting some clarification, though.
Thanks
From: Patrick Karton
Sent: Wednesday, September 27, 2023 12:37
To:
Hi,
before using t_relay you can probably check if next hop uri is still in the
target group with
ds_is_from_list([groupid [, mode [, uri] ] ])
for example ds_is_from_list("3","3","$du"); all parameters can be variables too.
you can check on documentation the mode parameter to see how
Hi,
Probably because you are returning negative value in this failure_route
De : satyaprakash ch via sr-users
Envoyé : mercredi 27 septembre 2023 06:45
À : Kamailio (SER) - Users Mailing List
Cc : satyaprakash ch
Objet : [SR-Users] ERROR: run_top_route
Hi,
We
Hi Daniel,
I've actually been spending a lot of time with the dispatcher readme to try to
figure this out. If there are restrictions in usage as you indicate, then it is
not documented.
>From the dispatcher readme:
ds_next_dst
Takes the next destination address from the corresponding XAVPs
Hello,
Thanks for the reply. I'm using the bundled/skeleton configurations just to
test with a few modifications (adding the actual voicemail server) however even
with the skeleton configurations, when the call goes unanswered, and the call
forks to voicemail, the INVITE packet is sent first,
Hello,
On 27.09.23 07:45, satyaprakash ch via sr-users wrote:
> Hi,
>
> We are having an error in the Kamailio logs which we need to resolve
> this issue,
>
> ERROR is ::* /usr/local/sbin/kamailio[10149]: ERROR: tm
> [t_reply.c:1081]: run_failure_handlers(): error running run_top_route
> for
Hello,
Kamailio SIP Server v5.7.2 stable release is out.
This is a maintenance release of the latest stable branch, 5.7, that
includes fixes since the release of v5.7.1. There is no change to
database schema or configuration language structure that you have to do
on previous installations of
Hello,
the v5.7.2 is going to be released today, therefore any commits to
branch 5.7 have to be announced to sr-dev and wait for ack before
pushing to github repository in order to avoid conflicts during release.
Once the announcement is out, commits can go to branch 5.7 as usual.
Cheers,
Daniel
Hello,
default kamailio.cfg has a skeleton for doing serial forking to a
voicemail server. Follow the token WITH_VOICEMAIL to discover the
related snippets -- this can be a starting point to implement it in your
config.
Cheers,
Daniel
On 27.09.23 04:12, Alex Balashov via sr-users wrote:
> Hi
Hello,
normally ds_select_dst() should be used inside request_route and
ds_next_dst() in the failure_route. As you do the former also in the
failure_route, you keep selecting the destination from the group and add
them to the list of possible next hops.
Look at the readme of dispatcher module,
14 matches
Mail list logo
