From rhys@nexusone.com.au Thu Mar 3 14:47:49 2022 From: Rhys Hanrahan To: sr-users@lists.kamailio.org Subject: Re: [SR-Users] rtpengine - SRTP <> RTP missing a=crypto Date: Thu, 03 Mar 2022 13:47:41 +0000 Message-ID: <412777D9-C9B0-4881-B3DC-8BC027A318D1@nexusone.com.au> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0140868813==" --===============0140868813== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Richard, Yes, from what I=E2=80=99ve seen in the logs there are multiple branches happ= ening. One between Teams and Kamailio and one between Kamailio and Asterisk. In terms of the rtpengine processing, I=E2=80=99ve tried lots of different va= riations, but right now I=E2=80=99ve got: * Rtpengine_manage() by itself for new branches and replies (MANAGE_BRANC= H, MANAGE_REPLY) * Rtpengine_manage(=E2=80=9CRTP/AVP=E2=80=9D) or rtpengine_manage(=E2=80= =9CRTP/SAVP=E2=80=9D) essentially in request_route for the initial invites to= /from Teams * I do also have the stock NATMANAGE using rtpengine but there=E2=80=99s = no NAT involved here so I don=E2=80=99t think it applies. So as far as I can tell, I shouldn=E2=80=99t be calling rtpengine_manage mult= iple times. Is this bad to do? I did have previous configs where I was doing = this. E.g. during RELAY I would call it with general options and then just mo= dify AVP or SAVP in another section. Interestingly, I noticed that a new branch is created just as I answer the ca= ll, and this is when it fails, so perhaps the issue is with how I=E2=80=99m h= andling new branches then? Below is a bit of a log to try and summarise what= =E2=80=99s happening. Unfortunately it=E2=80=99s not logging the MS Teams sid= e of the call except for the initial invite. I will work on getting you a sip dump as it=E2=80=99s probably the easiest wa= y to properly see what=E2=80=99s going on. Thanks! root(a)sbc5-syd-01:/etc/kamailio# tail -f /var/log/syslog | grep RTPEngine Mar 4 00:39:38 sbc5-syd-01 kamailio[9240]: 44(9311) ERROR: {1 1 INVITE 5b76d= fb297c455358bb0ec0dac3c1af7}