[OpenSIPS-Users] The update from yesterday makes all calls fail after 20 seconds, how do I go back?

Thu Sep 15 14:33:34 UTC 2022

I added this code to the end of my script
local_route
{
  if (is_method("BYE"))
  {
      xlog("L_ERR", "LOCAL_ROUTE - BYE - $DLG_end_reason - $ru - $ci");
  }
}
and now my system is filed with these errors:
Sep 15 14:25:36 node5 opensips[238750]: Sep 15 14:25:35 [238750]
LOCAL_ROUTE - BYE - RTPProxy Timeout - sip:7867830513 at 208.73.234.96:5060 -
0e87838610bfe6e1670023aa6bbe9590 at 208.73.234.96Sep 15 14:25:35 [238750]
LOCAL_ROUTE - BYE - RTPProxy Timeout - sip:192.69.217.154;did=8fc1.e2444961
- 0e87838610bfe6e1670023aa6bbe9590 at 208.73.234.96
but my calls do not use the rtpproxy, so why is this affecting my traffic
and killing my calls?
I have 10 rttpproxy services:
grep rtpproxy
  rtpproxy1.service                    loaded active     running
RTPProxy1
  rtpproxy10.service                   loaded active     running
RTPProxy10
  rtpproxy2.service                    loaded active     running
RTPProxy2
  rtpproxy3.service                    loaded active     running
RTPProxy3
  rtpproxy4.service                    loaded active     running
RTPProxy4
  rtpproxy5.service                    loaded active     running
RTPProxy5
  rtpproxy6.service                    loaded active     running
RTPProxy6
  rtpproxy7.service                    loaded active     running
RTPProxy7
  rtpproxy8.service                    loaded active     running
RTPProxy8
  rtpproxy9.service                    loaded active     running
RTPProxy9

here is number 1
[Unit]
Description=RTPProxy1
After=network.target
Requires=network.target

[Service]
Type=forking
PIDFile=/var/run/rtpproxy1.pid
#Environment='OPTIONS= -F -L 10240 -m 20000 -M 30000 -T 20 -d
INFO:LOG_LOCAL5'

Restart=on-failure
RestartSec=5

ExecStart=/usr/local/bin/rtpproxy -p /var/run/rtpproxy1.pid -l
Public.Ip.Address \
   -s udp:127.0.0.1:7890 -F -L 10240 -m 10000 -M 15000 -T 20 -d
WARN:LOG_LOCAL5 -n tcp:127.0.0.1:7889
ExecStop=/usr/bin/pkill -F /var/run/rtpproxy1.pid

StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=rtpproxy1
SyslogFacility=local5

TimeoutStartSec=10
TimeoutStopSec=10

[Install]
WantedBy=multi-user.target

Here is number 2

[Unit]
Description=RTPProxy2
After=network.target
Requires=network.target

[Service]
Type=forking
PIDFile=/var/run/rtpproxy2.pid
#Environment='OPTIONS= -F -L 10240 -m 20000 -M 30000 -T 20 -d
INFO:LOG_LOCAL5'

Restart=on-failure
RestartSec=5

ExecStart=/usr/local/bin/rtpproxy -p /var/run/rtpproxy2.pid -l
Public.IP.address \
   -s udp:127.0.0.1:7891 -F -L 10240 -m 15000 -M 20000 -T 20 -d
WARN:LOG_LOCAL5 -n tcp:127.0.0.1:7889
ExecStop=/usr/bin/pkill -F /var/run/rtpproxy2.pid

StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=rtpproxy2
SyslogFacility=local5

TimeoutStartSec=10
TimeoutStopSec=10

[Install]
WantedBy=multi-user.target

what am I doing wrong?

Federico

On Wed, Sep 14, 2022 at 4:55 PM Daniel Zanutti <daniel.zanutti at gmail.com>
wrote:

> Hi
>
> Everytime opensips sends the BYE, it's generated inside local_route:
> https://www.opensips.org/Documentation/Script-Routes-3-1#toc6
>
> So put a xlog there to see why. Something like this:
> local_route
> {
>   if (is_method("BYE"))
>   {
>       xlog("L_ERR", "LOCAL_ROUTE - BYE - $DLG_end_reason - $ru - $ci");
>   }
> }
>
>
> On Wed, Sep 14, 2022 at 5:04 PM Johan De Clercq <johan at democon.be> wrote:
>
>> Xlog(….);
>>
>> Outlook voor iOS <https://aka.ms/o0ukef> downloaden
>> ------------------------------
>> *Van:* Users <users-bounces at lists.opensips.org> namens Saint Michael <
>> venefax at gmail.com>
>> *Verzonden:* Wednesday, September 14, 2022 9:56:41 PM
>> *Aan:* OpenSIPS users mailling list <users at lists.opensips.org>
>> *Onderwerp:* Re: [OpenSIPS-Users] The update from yesterday makes all
>> calls fail after 20 seconds, how do I go back?
>>
>> how do I do this:
>> " put some log on local_route"
>> Sorry I am learning
>>
>>
>> On Wed, Sep 14, 2022 at 3:55 PM Daniel Zanutti <daniel.zanutti at gmail.com>
>> wrote:
>>
>> So your Opensips is hanging up the call.
>>
>> Do you see any log on it? Try put some log on local_route if you don't
>> see anything.
>>
>>
>>
>> On Wed, Sep 14, 2022 at 4:40 PM Saint Michael <venefax at gmail.com> wrote:
>>
>> This is a trace showing a BYE from Opensips, but none of the sides did
>> actually hangup.
>>
>>
>> On Wed, Sep 14, 2022 at 3:33 PM Saint Michael <venefax at gmail.com> wrote:
>>
>> I use opensips 3.1, and I did an update yesterday. in all the boxes that
>> I upgraded all calls fail after 20 seconds.
>>
>> cd /usr/src/opensips-3.1/
>> git pull
>> make clean;make proper;make all
>> make modules
>> make install
>> clearlog.sh
>> systemctl restart opensips
>> opensips -V
>>
>>
>>
>> How do I go back?
>>
>>
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opensips.org
>> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20220915/71f242d0/attachment.html>