Hi
I have come across this challenge:
Initial invite (no to_tag) has is authenticated and has credentials. So a lookup for the username is made to determine if the customer needs backhauling, thus rtpengine needs to be engaged.
On a subsequent invite (re-invite to change codec or to refresh session timer) there is a to_tag so it is being routed without sending a challenge and has no auth username.
I don't use dialog on the registrar. This is another transaction. So I don't know, if I need to engage rtpengine on that DSP or not.
What is the best way to find out, if rtpengine is already handling that callid?
if(rtpengine_query_v("j", "$var(dummy)")) { rtpengine_manage(); }
basically works, but generates a couple of ugly error messages in the log as rtpengine_query_v does not find the call.
Is there a nicer way?
you can add a Record Route parameter to the initial INVITE [1] and for that parameter after loose_route() for in-dialog INVITE [2]
[1] https://www.kamailio.org/docs/modules/5.5.x/modules/rr.html#rr.f.add_rr_para... [2] https://www.kamailio.org/docs/modules/5.5.x/modules/rr.html#rr.f.check_route...
On Fri, Feb 16, 2024 at 4:25 PM Benoît Panizzon via sr-users < sr-users@lists.kamailio.org> wrote:
Hi
I have come across this challenge:
Initial invite (no to_tag) has is authenticated and has credentials. So a lookup for the username is made to determine if the customer needs backhauling, thus rtpengine needs to be engaged.
On a subsequent invite (re-invite to change codec or to refresh session timer) there is a to_tag so it is being routed without sending a challenge and has no auth username.
I don't use dialog on the registrar. This is another transaction. So I don't know, if I need to engage rtpengine on that DSP or not.
What is the best way to find out, if rtpengine is already handling that callid?
if(rtpengine_query_v("j", "$var(dummy)")) { rtpengine_manage(); }
basically works, but generates a couple of ugly error messages in the log as rtpengine_query_v does not find the call.
Is there a nicer way?
-- Mit freundlichen Grüssen
-Benoît Panizzon- @ HomeOffice und normal erreichbar
I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________
Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________ __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
Hi Bastian
you can add a Record Route parameter to the initial INVITE [1] and for that parameter after loose_route() for in-dialog INVITE [2]
Thank you, that looks promising.
But now I face another issue with parallel branching.
On the branch route I do add_rr_param(";rtp=yes") if I need to backhaul RTP towards that $nh. I also set $avp(rtp) = 1 to engage rtpengine on transaction replies in my MANAGE_REPLY route.
check_rr_param works fine on subsequent transactions. But not on the initial one with branches.
But assume I got two parallel branches. One needs rtp backhauling, the other one does not.
How can I, within my MANAGE_REPLY route, figure out, if I am processing a reply which needs backhauling or not?
Mit freundlichen Grüssen
-Benoît Panizzon-
Check route[NATMANAGE] in default configuration [1]. Replies are handled via branch flags.
[1] https://github.com/kamailio/kamailio/blob/dad7f3ff3af02d086c1cb3f915f1502bca...
On Mon, Feb 19, 2024 at 10:48 AM Benoit Panizzon benoit.panizzon@imp.ch wrote:
Hi Bastian
you can add a Record Route parameter to the initial INVITE [1] and for that parameter after loose_route() for in-dialog INVITE [2]
Thank you, that looks promising.
But now I face another issue with parallel branching.
On the branch route I do add_rr_param(";rtp=yes") if I need to backhaul RTP towards that $nh. I also set $avp(rtp) = 1 to engage rtpengine on transaction replies in my MANAGE_REPLY route.
check_rr_param works fine on subsequent transactions. But not on the initial one with branches.
But assume I got two parallel branches. One needs rtp backhauling, the other one does not.
How can I, within my MANAGE_REPLY route, figure out, if I am processing a reply which needs backhauling or not?
Mit freundlichen Grüssen
-Benoît Panizzon-
I m p r o W a r e A G - Leiter Commerce Kunden ______________________________________________________
Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 Pratteln Fax +41 61 826 93 01 Schweiz Web http://www.imp.ch ______________________________________________________
-
Bastian Triller -
Benoît Panizzon