You have to use topos:receiving instead of topos:incoming.Le 11 juil. 2024 08:48, Denys Pozniak via sr-users a écrit :Hello!I need to disable topos for one specific SIP trunk (in-out), it looks like it’s enough to use event_route with IP address filtering.But for some reason, the incoming INVITE f
Hello,
how do i get misctest module in debian packages ? it seems not included in a
package.
is compilation the only way to get it ?
im using kamailio 5.7.5 on debian (bullseye) 11.8
version: kamailio 5.7.5 (x86_64/linux)
flags: USE_TCP, USE_TLS, USE_SCTP, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_N
Hello,This is the purpose of topos module to hide Via, Contact, Record-Route and Route headers.If you configure and use it properly there should not be any routing issue.Do you call record_route function in your kamailio script ?Le 11 juin 2024 14:10, Arun K R via sr-users a écrit :Hello,I am usin
Headers manipulations are per transaction so yes you Will Always need to filter them in a branch route Le 21 mars 2024 15:54, Benoit Panizzon via sr-users a écrit :Hi List
I am just wondering...
When I am sending the initial INVITE to a customer CPE, this goes
throug the whole location loo
Yes topos restores the Route headers as soon as the request enters kamailio. So they are already available before you call loose_route.Le 27 févr. 2024 11:13, Benoit Panizzon via sr-users a écrit :Hi
By setting: branch_expire to the same value as dialog_expire which is
12 hours, now my headers
Hello im using redis for topos and i noticed that when kamailio sending INVITEs and no response received yet and and if redis crash the retransmissions stop but the fr_timer is never called so no 408 is generated by kamailio.So the transaction lives for a very long long time in memory.Do topos call
Same bug in 5.7. versionsLe 15 mars 2024 15:08, Brooks Bridges via sr-users a écrit :
Thanks Daniel, I’ll give that a try.
Brooks BridgesSr. Developer
Direct: (888) 444‑
Office: (561) 453‑4085
Email: bbrid...@skyetel.com
902 Clint Moore Road
Suite 206
Hello are htable protected for multiple write access?
can i safely update htable from one process and be sure another process will
access it for write operation ? if yes is the lock on all the htable or only on
the bucket where the key belongs ?
Thanks.
Hi,
ok from kamailio source code, i see that the returned value of last function
called in failure route is also taken also as value so that's why you have that
log error.
you have to find why t_relay() return -1
or you can also do this
failure_route["serial"] {
if (!t_next_contacts()) {
exi
Hi,
no we don't need to change any code level.
but in your script just remove the return with negative code.
you probably have in your script
failure_route[MY_FAILURE]{
return -5; // <-- you probably have this. remove this instruction
return route[ANOTHER_ROUTE] // <-- or
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 compari
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
12 matches
Mail list logo
