Hello, I must send more data than just a hangup code: a duration, a text value.. X-Asterisk-HangupCauseCode is only sent when a called is hung up after being answered. Plus, it isn’t really a custom header. It must be an int value. Same for Q.850 reason header. I will maintain my current solution then (the in-dialog request via mi_http)
Thank you De : Users <users-boun...@lists.opensips.org> De la part de Brett Nemeroff Envoyé : mardi 27 décembre 2022 16:18 À : OpenSIPS users mailling list <users@lists.opensips.org> Objet : Re: [OpenSIPS-Users] Media server communication with OpenSIPS If your UAC doesn't have the capabilities of sending it in the BYE or an in-dialog request, then you'll have to do something out of band like HTTPS, Redis, etc, which are not bad options. Have you looked into "X-Asterisk-HangupCauseCode" to see if that can help you out? On Tue, Dec 27, 2022 at 8:55 AM Wadii ELMAJDI | Evenmedia <wa...@evenmedia.fr<mailto:wa...@evenmedia.fr>> wrote: > > Hello, > > > I am using Asterisk as a media server behind OpenSIPS. > I need to send some additional data to opensips during the call or at the > latest during the hangup. For instance a custom hang up reason. > Asterisk does not allow neither to send a sequential request withing an > ongoing dialog, nor add headers to a BYE method. > The current solution I’m using is pushing a dialog var (dlg_push_var) using > Call-ID via (mi_http), but that means I rely on a curl http request during my > call… > Is there any better option for a direct communication between the two boxes > during a call ? without any intermediate server (Redis DB …) > > Thank you > > _______________________________________________ > Users mailing list > Users@lists.opensips.org<mailto: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
