20 Jun
2023
20 Jun
'23
11:54 p.m.
Hello,
Im having a hard time figuring out how to handle a 302 reidrect, the uac_redirect modules
shows a simple configuration. However for me, what it is not doing is changing the 302
back to invite. It is sending the 302 as is on.
if(!t_check_status("3[0-9][0-9]")) {
exit;
}
get_redirects("3:1");
t_relay();
This code just relays the 302 for me. I should add I am using this with the DISPATCHER
module so perhaps that has something to do with my issue.
Setup is this, kamailio is sitting between to sip servers, so the flow goes like this,
sip_server_a -> kamailio -> sip_server_b. sip_server_b only responds with 302
redirects, sip_server_a does not handle 302’s at all. Kamailio will only get invites
from sip_server_a, and the redirects from sip_server_b will only have one contact. How
can I get kamailio to reply to sip_server_a’s invite with the updated INVITE?
My config is a mesh of the dispatcher example and uac_redirect example with this specific
section handling the redirect:
# Sample failure route
failure_route[RTF_DISPATCH] {
xlog("L_NOTICE", "RTF_DISPATCH: ");
if (t_is_canceled()) {
exit;
}
# next DST - only for 500 or local timeout
if (t_check_status("500")
or (t_branch_timeout() and !t_branch_replied()))
{
if(ds_next_dst())
{
t_on_failure("RTF_DISPATCH");
route(RELAY);
exit;
}
}
if (t_check_status("302")) {
xlog("L_NOTICE", "RTF_DISPATCH: 302 ");
if (!get_redirects("1:1")) {
xlog("L_NOTICE", "RTF_DISPATCH: failed to get_redirects
");
t_reply("480", "Temporarily Unavailable");
exit;
}
xlog("L_NOTICE", "RTF_DISPATCH: got redirects ");
t_relay(“sip_server_a”,”5060”);
}
}
Any ideas what I am doing wrong is this supported? Im expecting once I relay this message
that it should be an INVITE not a 302 redirect. I cant find any examples of anyone else
really doing this.
21 Jun
21 Jun
12:11 a.m.
Actually, I sent this way too soon. I think I tried a bunch of different things and got
confused. This is config is working correctly and sending correctly.
From: Trey Ormsbee <Trey.Ormsbee(a)interoptechnologies.com>
Date: Tuesday, June 20, 2023 at 2:54 PM
To: sr-users(a)lists.kamailio.org <sr-users(a)lists.kamailio.org>
Subject: How to handle 302 redirects
Hello,
Im having a hard time figuring out how to handle a 302 reidrect, the uac_redirect modules
shows a simple configuration. However for me, what it is not doing is changing the 302
back to invite. It is sending the 302 as is on.
if(!t_check_status("3[0-9][0-9]")) {
exit;
}
get_redirects("3:1");
t_relay();
This code just relays the 302 for me. I should add I am using this with the DISPATCHER
module so perhaps that has something to do with my issue.
Setup is this, kamailio is sitting between to sip servers, so the flow goes like this,
sip_server_a -> kamailio -> sip_server_b. sip_server_b only responds with 302
redirects, sip_server_a does not handle 302’s at all. Kamailio will only get invites
from sip_server_a, and the redirects from sip_server_b will only have one contact. How
can I get kamailio to reply to sip_server_a’s invite with the updated INVITE?
My config is a mesh of the dispatcher example and uac_redirect example with this specific
section handling the redirect:
# Sample failure route
failure_route[RTF_DISPATCH] {
xlog("L_NOTICE", "RTF_DISPATCH: ");
if (t_is_canceled()) {
exit;
}
# next DST - only for 500 or local timeout
if (t_check_status("500")
or (t_branch_timeout() and !t_branch_replied()))
{
if(ds_next_dst())
{
t_on_failure("RTF_DISPATCH");
route(RELAY);
exit;
}
}
if (t_check_status("302")) {
xlog("L_NOTICE", "RTF_DISPATCH: 302 ");
if (!get_redirects("1:1")) {
xlog("L_NOTICE", "RTF_DISPATCH: failed to get_redirects
");
t_reply("480", "Temporarily Unavailable");
exit;
}
xlog("L_NOTICE", "RTF_DISPATCH: got redirects ");
t_relay(“sip_server_a”,”5060”);
}
}
Any ideas what I am doing wrong is this supported? Im expecting once I relay this message
that it should be an INVITE not a 302 redirect. I cant find any examples of anyone else
really doing this.
11:04 a.m.
Hello!
We use a similar mechanism and everything works fine. A new branch is
formed with RURI from 302 Contact:
failure_route[N_DISPATCH] {
if ( t_check_status("302") ) {
get_redirects("*:1");
route(RELAY);
exit;
}
...
}
ср, 21 июн. 2023 г. в 00:51, Trey Ormsbee <
Trey.Ormsbee(a)interoptechnologies.com>gt;:
Actually, I sent this way too soon. I think I tried
a bunch of different
things and got confused. This is config is working correctly and sending
correctly.
*From: *Trey Ormsbee <Trey.Ormsbee(a)interoptechnologies.com>
*Date: *Tuesday, June 20, 2023 at 2:54 PM
*To: *sr-users(a)lists.kamailio.org <sr-users(a)lists.kamailio.org>
*Subject: *How to handle 302 redirects
Hello,
Im having a hard time figuring out how to handle a 302 reidrect, the
uac_redirect modules shows a simple configuration. However for me, what it
is not doing is changing the 302 back to invite. It is sending the 302 as
is on.
if(!t_check_status("3[0-9][0-9]")) {
exit;
}
get_redirects("3:1");
t_relay();
This code just relays the 302 for me. I should add I am using this with
the DISPATCHER module so perhaps that has something to do with my issue.
Setup is this, kamailio is sitting between to sip servers, so the flow
goes like this, sip_server_a -> kamailio -> sip_server_b. sip_server_b
only responds with 302 redirects, sip_server_a does not handle 302’s at
all. Kamailio will only get invites from sip_server_a, and the redirects
from sip_server_b will only have one contact. How can I get kamailio to
reply to sip_server_a’s invite with the updated INVITE?
My config is a mesh of the dispatcher example and uac_redirect example
with this specific section handling the redirect:
# Sample failure route
failure_route[RTF_DISPATCH] {
xlog("L_NOTICE", "RTF_DISPATCH: ");
if (t_is_canceled()) {
exit;
}
# next DST - only for 500 or local timeout
if (t_check_status("500")
or (t_branch_timeout() and !t_branch_replied()))
{
if(ds_next_dst())
{
t_on_failure("RTF_DISPATCH");
route(RELAY);
exit;
}
}
if (t_check_status("302")) {
xlog("L_NOTICE", "RTF_DISPATCH: 302 ");
if (!get_redirects("1:1")) {
xlog("L_NOTICE", "RTF_DISPATCH: failed to get_redirects
");
t_reply("480", "Temporarily Unavailable");
exit;
}
xlog("L_NOTICE", "RTF_DISPATCH: got redirects ");
t_relay(“sip_server_a”,”5060”);
}
}
Any ideas what I am doing wrong is this supported? Im expecting once I
relay this message that it should be an INVITE not a 302 redirect. I cant
find any examples of anyone else really doing this.
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to sr-users-leave(a)lists.kamailio.org
Important: keep the mailing list in the recipients, do not reply only to
the sender!
Edit mailing list options or unsubscribe:
--
BR,
Denys Pozniak
22 Jun
22 Jun
10:20 a.m.
Hi
This is how I handle them on the registrar:
[...]
# Record original destination before performing call forwarding
$avp(pre_redir_destination) = $rU;
[...]
Somewhere in the config we start reacting to replies from the
customer like when busy...
if (t_check_status("(486)|(600)")) {
$avp(cf_reason) = "user-busy";
route(CFB); # Check if Call Forward on Busy is active and if so, handle
this
route(CFVM); # Check if Call Forward to Voicemail is active and if so,
handle this
$avp(announcecode) = "BUSY"; # No Call Forward setting found to
handle 'busy' so just send to media server and play BUSY tone.
t_send_reply("$avp(rstatus)", "$avp(rtext)");
exit;
}
Or the one you are looking for, when customer replies with 301 or 302:
if (t_check_status("(301)|(302)")) {
$avp(destination) = $(T_rpl($ct){tobody.user});
if ($avp(debug) > 0) {
xlog("L_INFO", "$cfg(route): Got REDIRECTION:
$avp(rstatus) $avp(rtext) towards $T_rpl($ct) => $avp(destination) RU: $rU");
}
$avp(cf_reason) = "deflection";
t_on_branch("BR_REDIR_TO_CORE");
route(ROUTE_TO_CORE);
exit;
}
branch_route[BR_REDIR_TO_CORE]
{
if ($avp(debug) > 0) {
xlog("L_INFO", "$cfg(route): BR_idx: $T_branch_idx
$avp(pre_redir_destination) NEW: $avp(destination) FROM: $avp(from_in) setting
TO\n");
}
if (is_present_hf("X-OrigFrom")) { # Restore From we had before possible
translation to customer
$fU = $(hdr(X-OrigFrom));
}
remove_hf("Diversion");
$avp(pai_in) = $avp(pre_redir_destination);
$var(newdi) = "<sip:" + $avp(pre_redir_destination) + "@" +
$(fu{uri.host}) + ">;reason=" + $avp(cf_reason);
if ($avp(debug) > 0) {
xlog("L_INFO", "$cfg(route): Adding HEADER:
$var(newdi)\n");
}
append_hf("Diversion: $var(newdi)\r\n");
$tU = $avp(destination);
$rU = $avp(destination);
}
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
______________________________________________________
519
days inactive
521
days old
3 comments
3 participants
participants (3)
-
Benoit Panizzon -
Denys Pozniak -
Trey Ormsbee