[Spce-user] Issue after upgrade from 4.5.13 to 5.5.11

Marco Capetta mcapetta at sipwise.com
Thu Mar 12 04:02:57 EDT 2020


Hi Robert,

have you checked that the IP of the peer is not in the list of the 
Banned IP?

If not, can you share some additional info about the issue? For example 
it would be useful to have the log 2 of kamailio proxy, a sip trace of 
the failed call and the peer configuration (ip, hostname and port in 
particular).

Cheers
Marco

On 3/11/20 7:24 PM, Robert Cuaresma wrote:
> Hi guys!
>
> Any suggestion about this?
>
> Thanks!!
>
> Saludos,
> Robert Cuaresma
>
> ------------------------------------------------------------------------
> *De:* Robert Cuaresma <rcuaresma at cloudcom.cat>
> *Enviado:* martes, 10 de marzo de 2020 9:28
> *Para:* spce-user at lists.sipwise.com <spce-user at lists.sipwise.com>
> *Asunto:* Re: [Spce-user] Issue after upgrade from 4.5.13 to 5.5.11
> Hi Alex!
>
> Yes, is a strange issue... I have not enabled any DDOS protection. 
> Have Sipwise any protection for it? This upgrade to 5.5.11 is comming 
> from fresh installation of 4.5.6 with no extra configurations. Only 
> Sipwise are installed.
>
> The server have 2 cores and 8 GB of RAM on a vCloud infraestructure.
>
> The same machine with 4.5.13 works fine everytime.
>
>
> Saludos,
> Robert Cuaresma
>
> ------------------------------------------------------------------------
> *From:* Alex Lutay <alutay at sipwise.com>
> *Sent:* Tuesday, March 10, 2020 8:57:01 AM
> *To:* spce-user at lists.sipwise.com <spce-user at lists.sipwise.com>
> *Subject:* Re: [Spce-user] Issue after upgrade from 4.5.13 to 5.5.11
> Hi,
>
> Just a shoot in a dark: maybe you have enabled some DDOS protection with
> too low parameters?
>
> On 3/10/20 8:18 AM, Robert Cuaresma wrote:
> > After upgrade with no errors all works fine (during all weekend),
> > inbound and outbound calls with any peer works fine (with low traffic).
> > On monday at 07:30 h aprox the traffic grow a little (4-5 simultaneous
> > calls, low traffic too). At this moment I can reproduce the first
> > REJECTED with error "No matching inbound peer rule in any peering
> > group". During the weekend i made a lot of calls for test and it works
> > always fine. The same test to the same number, from the same number,
> > after the first REJECT, it not works anymore and all calls from this
> > peer are rejected.
> >
> > All the peering groups have configured this inbound rule (rule by 
> default):
> > - Field: to_ruri
> > - Pattern: .*
> >
> > Any suggestion about this issue?
> >
> > Thanks a lot in advance.
>
> -- 
> Alex Lutay
>
> -- 
> Spce-user mailing list
> Spce-user at lists.sipwise.com
> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
>

-- 
*Marco Capetta *
VoIP Developer

Sipwise GmbH <http://www.sipwise.com> , Campus 21/Europaring F15
AT-2345 Brunn am Gebirge

Phone: +43(0)1 301 2044 <tel:+4313012044>
Email: mcapetta at sipwise.com <mailto:mcapetta at sipwise.com>
Website: www.sipwise.com <http://www.sipwise.com>

Particulars according Austrian Companies Code paragraph 14
"Sipwise GmbH" - Europaring F15 - 2345 Brunn am Gebirge
FN:305595f, Commercial Court Vienna, ATU64002206

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20200312/4f8e37e6/attachment-0002.html>


More information about the Spce-user mailing list