Hi Bogdan, Nice to hear from you again, you are always very helpful :) Unfortunately, I doubt that Microsoft would listen to my request, they're bending RFCs the way they like it, for example - using FQDN in 'Contact' field and no 'to' tag in this 487 reply. I assume it's quite safe to ignore this behaviour? Thanks!
Regards, Yury. ср, 22 мая 2019 г. в 18:37, Bogdan-Andrei Iancu <[email protected]>: > Hi Yury, > > No need to call any script function - all you need to do is to point your > carrier to read the RFC3261 -> any final SIP reply MUST have a TO-tag. > > Regards, > > Bogdan-Andrei Iancu > > OpenSIPS Founder and Developer > https://www.opensips-solutions.com > OpenSIPS Summit 2019 > https://www.opensips.org/events/Summit-2019Amsterdam/ > > On 05/22/2019 11:19 AM, Yury Kirsanov wrote: > > Hi, > My upstream carrier is replying back to CANCEL request with a 487 Call > Cancelled message that doesn't have a 'to' tag in its headers. So, I'm > getting these errors in OpenSIPS logs: > > ERROR:dialog:push_reply_in_dialog: [487] reply in dlg state [2]: missing > TAG param in TO hdr > > But dialogs are closing correctly on BYE and I don't see any dialogs > hanging in any state when the call is finished. Is it something I should be > worried about or can I just ignore this error? Is there any way to avoid it > by OpenSIPS script processing logic? Maybe I need to call some function to > fix this dialog? Thanks! > > Regards, > Yury. > > > _______________________________________________ > Users mailing > [email protected]http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > >
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
