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
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
__
Kamailio
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/
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
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.casti...@snapcom.fr
Sent: Wednesday,
> On 4 Jan 2023, at 14:28, nathan.casti...@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.
>
