I agree here, the 183 must be relayed back to the original caller (which
generate the received INVITE) and let it do the PRACK - this
confirmation must be end-2-end in the dialog.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
https://www.siphub.com
On 12.02.2024 11:36, Ihor Olkhovskyi wrote:
You should relay 183 to original source (ione that is sending INVITE)
and got PRACK from there.
That would be the most correct way of handling this
Le lun. 12 févr. 2024 à 02:29, Social Boh <soc...@bohboh.info> a écrit :
Maybe someone can help me.
This is the scenario.
OpenSIPs receive a INVITE and send it to a server that reply with
a 302
message (always)
Then OpenSIPs, in the failure route, take the user part present in
the
302 contact header, change the destination IP and send with t_relay
The destination reply with a 183 with Require: 100rel header so
OpenSIPs
have to reply with a PRACK. This is my problem.
I don't know which is the best way to handle this (the PRACK)
Thank you
Regards
---
I'm SoCIaL, MayBe
El 9/02/2024 a las 6:46 a. m., Social Boh escribió:
> Hello list,
>
> can OpenSIPs generate a PRACK message to reply a 180/183 message?
>
> Thank you
>
> Regards
>
> ---
> I'm SoCIaL, MayBe
>
>
> _______________________________________________
> Users mailing list
> Users@lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
--
Best regards,
Ihor (Igor)
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
