Hello, Sorry, I forgot to mention that, between the call of the two webrtc clients, there is a B2BUA that only supports SIP UDP and RTP, so I need to use rtpengine to translate from DTLS/SRTP to RTP. I will try to make a call between the two webrtc clients and only use kamailio without rtpengine to limit the issue.
Os melhores cumprimentos / Best regards, *José Lopes* Research and Development Technician Phone: +351 256 370 980 Email: [email protected] On Tue, May 5, 2020 at 5:15 PM Juha Heinanen <[email protected]> wrote: > This 488 think reminds me that SIP over webrtc is broken. > > Webrtc UAS (at least JsSIP) cannot issue 488 before the UAS has started > to ring. It is very frustrating for the callee to get such a spam ring. > > RFC3261 section "8.2 UAS Behavior" tells: > > Note that request processing is atomic. If a request is accepted, > all state changes associated with it MUST be performed. If it is > rejected, all state changes MUST NOT be performed. > > So it is against the standard to issue 180 and after that reject the > request with 488. > > -- Juha > > _______________________________________________ > Kamailio (SER) - Users Mailing List > [email protected] > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >
_______________________________________________ Kamailio (SER) - Users Mailing List [email protected] https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
