4 Jan
2023
4 Jan
'23
2:28 p.m.
Hello all,
I'm trying to figure out one problem on my Kamailio server.
When kamailio receive a reinvite from the infra, I get the error message "477 -
Unforunately error on sending to next hop" and the call drop.
I don't understand why this message appears as the first invite is well answered and
the call is going well.
Any ideas how to resolve this issue ?
Thanks in advance for your help.
Regards,
Nathan
4 Jan
4 Jan
2:45 p.m.
On 4 Jan 2023, at 14:28, nathan.castillo(a)snapcom.fr
wrote:
Hello all,
I'm trying to figure out one problem on my Kamailio server.
When kamailio receive a reinvite from the infra, I get the error message "477 -
Unforunately error on sending to next hop" and the call drop.
I don't understand why this message appears as the first invite is well answered and
the call is going well.
The first invite and a reinvite is routed different ways.
The re-invite is in dialog and thus follows the record route and the contact address.
Any ideas how to resolve this issue ?
Read the headers and figure it out :-)
Cheers,
/O
5:15 p.m.
Hello,
as mentioned, analyse the sip traces, the re-INVITE in particular regarding Route header
etc..
Cheers,
Henning
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://gilawa.com
-----Original Message-----
From: nathan.castillo(a)snapcom.fr <nathan.castillo(a)snapcom.fr>
Sent: Wednesday, January 4, 2023 2:28 PM
To: sr-users(a)lists.kamailio.org
Subject: [SR-Users] Call drop when reinvite is proceed
Hello all,
I'm trying to figure out one problem on my Kamailio server.
When kamailio receive a reinvite from the infra, I get the error message "477 -
Unforunately error on sending to next hop" and the call drop.
I don't understand why this message appears as the first invite is well answered and
the call is going well.
Any ideas how to resolve this issue ?
Thanks in advance for your help.
Regards,
Nathan
__________________________________________________________
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:
5 Jan
5 Jan
10:16 a.m.
Hello all,
Thank you for your all your answers
I checked the headers and I 've seen several things:
1/ In the Invite I see :
sip:test@KAMAILIO_SERVER_IP
In the reinvite i see:
sip:remote_endpoint
via Kamailio IP address
2/ In the call flow everything is going well until the ack.
At the beginning of the reinvite, the route is well known
The caller send the ack to Kamailio but Kamailio is unable to forward it to the remote
endpoint.
Checking the headers, I see that in the ACK, the route is not present anymore.
Is it possible to force the route in Kamailio directly ?
I have the call flow but I cannot send image here.
Regards,
Nathan
12:45 p.m.
Hello,
On 05.01.23 10:16, Nathan C wrote:
Hello all,
Thank you for your all your answers
I checked the headers and I 've seen several things:
1/ In the Invite I see :
sip:test@KAMAILIO_SERVER_IP
In the reinvite i see:
sip:remote_endpoint
via Kamailio IP address
2/ In the call flow everything is going well until the ack.
At the beginning of the reinvite, the route is well known
The caller send the ack to Kamailio but Kamailio is unable to forward it to the remote
endpoint.
Checking the headers, I see that in the ACK, the route is not present anymore.
Is it possible to force the route in Kamailio directly ?
I have the call flow but I cannot send image here.
although it should not be done according to the specs, maybe the end
point implementation refreshes the record-route set with the re-INVITE.
Try by adding record_route() when processing the re-INVITE (inside the
route[WITHINDLG] if you use the structure of the default kamailio.cfg).
See if it helps.
Cheers,
Daniel
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com
4:49 p.m.
Hello Daniel,
Thank you for the information.
It works well. If it can help someone, I added in route[WITHINDLG]:
if (is_method("INVITE")) {
record_route();
}
Thank you all for your help.
Regards,
Nathan
5:18 p.m.
Nathan,
It is only valid to add a Record-Route header to an initial INVITE (NOT within a dialog),
because it tells both parties to the dialog where to send in-dialog requests (e.g.
re-invites, BYE, e2e ACK) -- the kind handled in route[WITHINDLG}.
So, this is quite radiantly wrong, though it should not have nullary effect as the RR will
be ignored by the counterparty.
-- Alex
--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com
Tel: +1-706-510-6800
486
days inactive
487
days old
6 comments
6 participants
participants (6)
-
Alex Balashov -
Daniel-Constantin Mierla -
Henning Westerholt -
Nathan C -
nathan.castillo＠snapcom.fr
-
Olle E. Johansson