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

Marco Capetta mcapetta at sipwise.com
Tue Apr 14 08:22:13 EDT 2020


What you find written in the logs with "IP=XX.XX.38.229:42314" is the 
source IP (so the port from which your provider is sending the message) 
not the destination IP.
You have to ask them to use always the same source ip:port to send 
messages to you.

Cheers
Marco


On 4/14/20 2:08 PM, Robert Cuaresma wrote:
>
> Hi Marco, thanks for the reply.
>
> Yes I have seen that you say but I don’t understand. This is strange. 
> My SIP Provider always send me the SIP traffic with destination port 
> 5060 UDP, that Sipwise is listening for. The RURI show that the call 
> was sended to the port 5060, but the IP tag show that the destination 
> port is 42314. This looks as instead of setting the destination port, 
> sipwise are setting the source port of the sip packet. I don't know if 
> I'm explaining myself correctly.
>
> It works.
>
> New request on proxy - M=INVITE R=sip:3493712XXXX at XX.XX.144.197:5060 
> F=sip:3465522XXXX at XX.XX.38.229 T=sip:3491530XXXX at XX.XX.144.197 
> IP=XX.XX.38.229:5060 (127.0.0.1:5060) 
> ID=520502484_50133906 at XX.XX.38.229 UA='<null>'
>
> Call from PSTN - R=sip:3493712XXXX at XX.XX.144.197:5060 
> ID=520502484_50133906 at XX.XX.38.229 UA='<null>'
>
> Inbound peering group '2' matched, looking up peer host - 
> R=sip:3493712XXXX at XX.XX.144.197:5060 
> ID=520502484_50133906 at XX.XX.38.229 UA='<null>'
>
> Fail
>
> New request on proxy - M=INVITE R=sip:3493764XXXX at XX.XX.144.197:5060 
> F=sip:3469786XXXX at XX.XX.38.229 T=sip:349376XXXX at XX.XX.144.197 
> IP=XX.XX.38.229:42314 (127.0.0.1:5060) 
> ID=520504084_38977676 at XX.XX.38.229 UA='<null>'
>
> Call from PSTN - R=sip:3493764XXXX at XX.XX.144.197:5060 
> ID=520504084_38977676 at XX.XX.38.229 UA='<null>'
>
> No matching inbound peer rule in any peering group, rejecting call - 
> R=sip:3493764XXXX at XX.XX.144.197:5060 
> ID=520504084_38977676 at XX.XX.38.229 UA='<null>'
>
> Saludos,
>
> Robert Cuaresma
>
> *De:* Marco Capetta <mcapetta at sipwise.com>
> *Enviado el:* martes, 14 de abril de 2020 12:36
> *Para:* spce-user at lists.sipwise.com
> *Asunto:* Re: [Spce-user] Issue after upgrade from 4.5.13 to 5.5.11
>
> Hi Robert,
>
> as I suppose in one of my previous email, the problem is that your 
> peer doesn't send the INVITE always from the same port
> From the log you sent me, I can see that in working cases it is 5060, 
> instead, other times it is different: 42314, 42443, ...
>
> In order to let the incoming call working, the source port has always 
> to match the port you configured in the peer.
>
> Regards
> Marco
>
>
> On 4/7/20 5:07 PM, Robert Cuaresma wrote:
>
>     Hi Marco!
>
>     Did you receive the log files?
>
>     Thanks!!
>
>     Saludos,
>
>     Robert Cuaresma
>
>     *De:* Robert Cuaresma <rcuaresma at cloudcom.cat>
>     <mailto:rcuaresma at cloudcom.cat>
>     *Enviado el:* viernes, 03 de abril de 2020 16:51
>     *Para:* Marco Capetta <mcapetta at sipwise.com>
>     <mailto:mcapetta at sipwise.com>; spce-user at lists.sipwise.com
>     <mailto:spce-user at lists.sipwise.com>
>     *Asunto:* Re: [Spce-user] Issue after upgrade from 4.5.13 to 5.5.11
>
>     Hi Marco!,
>
>     I have sent the records to your email.
>
>     Saludos,
>
>     Robert Cuaresma
>
>     *De:* Marco Capetta <mcapetta at sipwise.com
>     <mailto:mcapetta at sipwise.com>>
>     *Enviado el:* viernes, 03 de abril de 2020 16:46
>     *Para:* spce-user at lists.sipwise.com
>     <mailto:spce-user at lists.sipwise.com>
>     *Asunto:* Re: [Spce-user] Issue after upgrade from 4.5.13 to 5.5.11
>
>     Hi Robert,
>
>     I was waiting for the logs, but I didn't receive them.
>     If I'm not in wrong they were neither attached to your last email.
>
>     Thanks
>     Marco
>
>     On 4/3/20 4:42 PM, Robert Cuaresma wrote:
>
>         Hi Marco!
>
>         Did you receive the log files?
>
>         Thanks!!
>
>         Saludos,
>
>         Robert Cuaresma
>
>         *De:* Marco Capetta <mcapetta at sipwise.com
>         <mailto:mcapetta at sipwise.com>>
>         *Enviado el:* martes, 31 de marzo de 2020 9:52
>         *Para:* Robert Cuaresma <rcuaresma at cloudcom.cat
>         <mailto:rcuaresma at cloudcom.cat>>; spce-user at lists.sipwise.com
>         <mailto:spce-user at lists.sipwise.com>
>         *Asunto:* Re: [Spce-user] Issue after upgrade from 4.5.13 to
>         5.5.11
>
>         Hi Robert
>
>         Yes for a complete analysis I would need, for a working and
>         not working call, the lb and proxy log level 2 and a sip trace.
>
>         Thanks
>         Marco
>
>         On 3/30/20 4:09 PM, Robert Cuaresma wrote:
>
>             Hi Marco, don’t worry.
>
>             Yes. The calls are coming from the same provider, same IP
>             and same port. Both subscribers exist and it can receive
>             calls in other moments until it start to fail.
>
>             R=sip:349X76X097X at 123.123.123.123:5060àOK
>
>             FROM IP ADDRESS: 217.1X0.3X.2X9
>
>             R=sip:349X56X60X0 at 123.123.123.123:5060àFail
>
>             FROM IP ADDRESS: 217.1X0.3X.2X9
>
>             If you like, I can send you a complete log in private for
>             your analisis.
>
>             Saludos,
>
>             Robert Cuaresma
>
>             *De:* Marco Capetta <mcapetta at sipwise.com>
>             <mailto:mcapetta at sipwise.com>
>             *Enviado el:* lunes, 30 de marzo de 2020 15:55
>             *Para:* spce-user at lists.sipwise.com
>             <mailto:spce-user at lists.sipwise.com>
>             *Asunto:* Re: [Spce-user] Issue after upgrade from 4.5.13
>             to 5.5.11
>
>             Hi Robert,
>
>             sorry for the delay...
>
>             From the log line you attached it is difficult to
>             understand the real issue: source IP and ports are missing.
>             As you said both the messages are coming from the same
>             provider, but can you please also check that both are
>             coming from the same IP and port? IP and port have to be
>             the same you configured in the peer details.
>
>             Cheers
>             Marco
>
>
>             On 3/30/20 3:40 PM, Robert Cuaresma wrote:
>
>                 Hi Mario!
>
>                 Any suggestion about this?
>
>                 Thanks a lot!
>
>                 Saludos,
>
>                 Robert Cuaresma
>
>                 *De:* Robert Cuaresma <rcuaresma at cloudcom.cat>
>                 <mailto:rcuaresma at cloudcom.cat>
>                 *Enviado el:* lunes, 23 de marzo de 2020 17:18
>                 *Para:* spce-user at lists.sipwise.com
>                 <mailto:spce-user at lists.sipwise.com>
>                 *Asunto:* Re: [Spce-user] Issue after upgrade from
>                 4.5.13 to 5.5.11
>
>                 Hi Marco! Sorry by the delay on response…
>
>                 I have attached two examples (with masked IPs and numbers)
>
>                 OK Inbound Call:
>
>                 Mar  8 10:49:05 sbc01 proxy[8656]: NOTICE: <script>:
>                 Call from PSTN -
>                 R=sip:349X76X097X at 123.123.123.123:5060ID=520416609_119976867 at 217.1X0.3X.2X9
>                 <mailto:ID=520416609_119976867 at 217.1X0.3X.2X9>UA='<null>'
>
>                 Mar  8 10:49:05 sbc01 proxy[8656]: NOTICE: <script>:
>                 No matching inbound peer rule in any peering group,
>                 rejecting call - R=sip:
>                 349X76X097X at 123.123.123.123:5060
>                 <mailto:349X76X097X at 123.123.123.123:5060>ID=520416609_119976867 at c
>                 <mailto:ID=520416609_119976867 at 217.1X0.3X.2X9>UA='<null>'
>
>                 Failed Inbound Call:
>
>                 Mar  8 22:55:20 sbc01 proxy[8655]: NOTICE: <script>:
>                 Call from PSTN -
>                 R=sip:349X56X60X0 at 123.123.123.123:5060ID=671503121_83856560 at 217.1X0.3X.2X9
>                 <mailto:ID=671503121_83856560 at 217.1X0.3X.2X9>UA='<null>'
>
>                 Mar  8 22:55:20 sbc01 proxy[8655]: NOTICE: <script>:
>                 Inbound peering group '2' matched, looking up peer
>                 host - R=sip: 349X56X60X0 at 123.123.123.123:5060
>                 <mailto:349X56X60X0 at 123.123.123.123:5060>ID=671503121_83856560 at 217.1X0.3X.2X9
>                 <mailto:ID=671503121_83856560 at 217.1X0.3X.2X9>UA='<null>'
>
>                 Inbound Route:
>
>                 Both calls come from the same SIP Provider (COLT).
>
>                 Banned IP are empty.
>
>                 Thanks a lot!!
>
>                 Saludos,
>
>                 Robert Cuaresma
>
>                 *De:* Marco Capetta <mcapetta at sipwise.com
>                 <mailto:mcapetta at sipwise.com>>
>                 *Enviado el:* jueves, 12 de marzo de 2020 9:03
>                 *Para:* spce-user at lists.sipwise.com
>                 <mailto:spce-user at lists.sipwise.com>
>                 *Asunto:* Re: [Spce-user] Issue after upgrade from
>                 4.5.13 to 5.5.11
>
>                 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>
>                     <mailto:rcuaresma at cloudcom.cat>
>                     *Enviado:* martes, 10 de marzo de 2020 9:28
>                     *Para:* spce-user at lists.sipwise.com
>                     <mailto:spce-user at lists.sipwise.com><spce-user at lists.sipwise.com>
>                     <mailto: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>
>                     <mailto:alutay at sipwise.com>
>                     *Sent:* Tuesday, March 10, 2020 8:57:01 AM
>                     *To:* spce-user at lists.sipwise.com
>                     <mailto:spce-user at lists.sipwise.com><spce-user at lists.sipwise.com>
>                     <mailto: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
>                     <mailto: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
>
>             -- 
>
>             *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
>
>         -- 
>
>         *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
>
>     -- 
>
>     *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
>
> -- 
>
> *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
>
>

-- 
*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/20200414/4610813f/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 15759 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20200414/4610813f/attachment-0001.png>


More information about the Spce-user mailing list