hi Stefan your question is far from stupid
have you tried manipulating the SIP headers to influence the negotiation process between the provider and your PBX ? you can do that by adjusting the Supported/Require headers in SIP messages within OpenSIPS to indicate that only re-INVITE is supported for session timers this might prompt your new operator system to fallback to using re-INVITE instead of UPDATE Additionally check if your PBX can be configured to prefer re-INVITEs ________________________________ De : Users <users-boun...@lists.opensips.org> de la part de Stefan Carlsson <stefan.carls...@tetab.nu> Envoyé : Monday, March 4, 2024 10:52:58 PM À : users@lists.opensips.org <users@lists.opensips.org> Objet : [OpenSIPS-Users] Reset session timers via re-invite // update Hi ! We have a problem regarding session timers. One operator runs it via re-invite and the new one via update. All our PBX’s “inside” and UA’s runs re-invite and we have the Opensips as a proxy that routes all the traffic to the right UA, Trunks. So my question is, is it even possibly to handle both types of session timers methods in Opensips if endpoints only handles re-invite I’ve tested to send the update with all headers intact back to the operator but then I receive 481 unknown dialog. I’ve tried to read the RFC 3311 but I can’t find any examples that is so clear as re-invite … (tags) Do I need to change/add some headervalues such as the did i’ve got in the 200 message after the invite to build up the complete Update response to the operator. Please bear with me regarding with my “stupid” questions … understanding sip is really hard …… // Regards … Stefan
_______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users
