26 May
2020
26 May
'20
6:34 p.m.
Hi gents,
Got this weird "problem", where CANCEL request is relayed to both the right
destination as well as the 255.255.255.255 broadcast address!? I have no
such logic in my script, that's for sure.
I doesn't do anything harmful (as far as I can tell), but I'm just curious
why it's doing that. Any ideas?
version: kamailio 5.3.4
*SIP Trace:*
U 2020/05/26 08:40:10.941722 PBXIP:5060 -> KAMAILIO_IP:5060
CANCEL sip:2383@DOWNSTREAM_IP:10533;transport=TLS SIP/2.0
Via: SIP/2.0/UDP PBXIP:5060;branch=z9hG4bK450689d6
Max-Forwards: 69
From: "some callerid" <sip:18001111111@mypbx.mydomain.com>;tag=as4d223616
To: <sip:2383@DOWNSTREAM_IP:10533;transport=TLS>
Call-ID: 1511475b69f6379b08f04d110f534da1(a)mypbx.mydomain.com
CSeq: 102 CANCEL
User-Agent: B2B
Content-Length: 0
U 2020/05/26 08:40:10.941799 KAMAILIO_IP:5060 -> 255.255.255.255:5060
CANCEL sip:2383@DOWNSTREAM_IP:10533;transport=TLS SIP/2.0
Via: SIP/2.0/UDP PBXIP:5060;branch=z9hG4bK450689d6
Max-Forwards: 69
From: "some callerid" <sip:18001111111@mypbx.mydomain.com>;tag=as4d223616
To: <sip:2383@DOWNSTREAM_IP:10533;transport=TLS>
Call-ID: 1511475b69f6379b08f04d110f534da1(a)mypbx.mydomain.com
CSeq: 102 CANCEL
User-Agent: B2B
Content-Length: 0
T 2020/05/26 08:40:10.941899 KAMAILIO_IP:5061 -> DOWNSTREAM_IP:10533
CANCEL sip:2383@DOWNSTREAM_IP:10533;transport=TLS SIP/2.0
Via: SIP/2.0/TLS
proxy.mydomain.com:5061;branch=z9hG4bK3cbb.4c6a526982fa1fb93ca1ba73afd8484f.0
Max-Forwards: 69
From: "some callerid" <sip:18001111111@mypbx.mydomain.com>;tag=as4d223616
To: <sip:2383@DOWNSTREAM_IP:10533;transport=TLS>
Call-ID: 1511475b69f6379b08f04d110f534da1(a)mypbx.mydomain.com
CSeq: 102 CANCEL
Content-Length: 0
U 2020/05/26 08:40:10.941935 KAMAILIO_IP:5060 -> PBXIP:5060
SIP/2.0 200 canceling
Via: SIP/2.0/UDP PBXIP:5060;branch=z9hG4bK450689d6
From: "some callerid" <sip:18001111111@mypbx.mydomain.com>;tag=as4d223616
To: <sip:2383@DOWNSTREAM_IP
:10533;transport=TLS>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-612a1516
Call-ID: 1511475b69f6379b08f04d110f534da1(a)mypbx.mydomain.com
CSeq: 102 CANCEL
Server: Edge
Content-Length: 0
Thanks,
--Sergiu
26 May
26 May
9:10 p.m.
Hello,
that is the received CANCEL, not the one sent out by Kamailio. The Via
branch generated by Kamailio has the format present in the CANCEL sent
to downstream.
Probably there is some setting in the system (ip forwarding) causing it
or something else out of Kamailio control.
Cheers,
Daniel
On 26.05.20 17:34, Sergiu Pojoga wrote:
Hi gents,
Got this weird "problem", where CANCEL request is relayed to both the
right destination as well as the 255.255.255.255 broadcast address!? I
have no such logic in my script, that's for sure.
I doesn't do anything harmful (as far as I can tell), but I'm just
curious why it's doing that. Any ideas?
version: kamailio 5.3.4
*SIP Trace:*
U 2020/05/26 08:40:10.941722 PBXIP:5060 -> KAMAILIO_IP:5060
CANCEL sip:2383@DOWNSTREAM_IP:10533;transport=TLS SIP/2.0
Via: SIP/2.0/UDP PBXIP:5060;branch=z9hG4bK450689d6
Max-Forwards: 69
From: "some callerid" <sip:18001111111@mypbx.mydomain.com
<mailto:sip%3A18001111111@mypbx.mydomain.com>>;tag=as4d223616
To: <sip:2383@DOWNSTREAM_IP:10533;transport=TLS>
Call-ID: 1511475b69f6379b08f04d110f534da1(a)mypbx.mydomain.com
<mailto:1511475b69f6379b08f04d110f534da1@mypbx.mydomain.com>
CSeq: 102 CANCEL
User-Agent: B2B
Content-Length: 0
U 2020/05/26 08:40:10.941799 KAMAILIO_IP:5060 -> 255.255.255.255:5060
<http://255.255.255.255:5060>
CANCEL sip:2383@DOWNSTREAM_IP:10533;transport=TLS SIP/2.0
Via: SIP/2.0/UDP PBXIP:5060;branch=z9hG4bK450689d6
Max-Forwards: 69
From: "some callerid" <sip:18001111111@mypbx.mydomain.com
<mailto:sip%3A18001111111@mypbx.mydomain.com>>;tag=as4d223616
To: <sip:2383@DOWNSTREAM_IP:10533;transport=TLS>
Call-ID: 1511475b69f6379b08f04d110f534da1(a)mypbx.mydomain.com
<mailto:1511475b69f6379b08f04d110f534da1@mypbx.mydomain.com>
CSeq: 102 CANCEL
User-Agent: B2B
Content-Length: 0
T 2020/05/26 08:40:10.941899 KAMAILIO_IP:5061 -> DOWNSTREAM_IP:10533
CANCEL sip:2383@DOWNSTREAM_IP:10533;transport=TLS SIP/2.0
Via: SIP/2.0/TLS
proxy.mydomain.com:5061;branch=z9hG4bK3cbb.4c6a526982fa1fb93ca1ba73afd8484f.0
Max-Forwards: 69
From: "some callerid" <sip:18001111111@mypbx.mydomain.com
<mailto:sip%3A18001111111@mypbx.mydomain.com>>;tag=as4d223616
To: <sip:2383@DOWNSTREAM_IP:10533;transport=TLS>
Call-ID: 1511475b69f6379b08f04d110f534da1(a)mypbx.mydomain.com
<mailto:1511475b69f6379b08f04d110f534da1@mypbx.mydomain.com>
CSeq: 102 CANCEL
Content-Length: 0
U 2020/05/26 08:40:10.941935 KAMAILIO_IP:5060 -> PBXIP:5060
SIP/2.0 200 canceling
Via: SIP/2.0/UDP PBXIP:5060;branch=z9hG4bK450689d6
From: "some callerid" <sip:18001111111@mypbx.mydomain.com
<mailto:sip%3A18001111111@mypbx.mydomain.com>>;tag=as4d223616
To:
<sip:2383@DOWNSTREAM_IP:10533;transport=TLS>;tag=a6a1c5f60faecf035a1ae5b6e96e979a-612a1516
Call-ID: 1511475b69f6379b08f04d110f534da1(a)mypbx.mydomain.com
<mailto:1511475b69f6379b08f04d110f534da1@mypbx.mydomain.com>
CSeq: 102 CANCEL
Server: Edge
Content-Length: 0
Thanks,
--Sergiu
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Funding: https://www.paypal.me/dcmierla
27 May
27 May
4:07 p.m.
Hi Daniel,
Got it. Thanks for taking the time to look into it, I'll dig further, let
you know if I find what's causing it.
Regards,
--Sergiu
On Tue, May 26, 2020 at 2:10 PM Daniel-Constantin Mierla <miconda(a)gmail.com>
wrote:
Hello,
that is the received CANCEL, not the one sent out by Kamailio. The Via
branch generated by Kamailio has the format present in the CANCEL sent to
downstream.
Probably there is some setting in the system (ip forwarding) causing it or
something else out of Kamailio control.
Cheers,
Daniel
On 26.05.20 17:34, Sergiu Pojoga wrote:
Hi gents,
Got this weird "problem", where CANCEL request is relayed to both the
right destination as well as the 255.255.255.255 broadcast address!? I have
no such logic in my script, that's for sure.
I doesn't do anything harmful (as far as I can tell), but I'm just curious
why it's doing that. Any ideas?
version: kamailio 5.3.4
*SIP Trace:*
U 2020/05/26 08:40:10.941722 PBXIP:5060 -> KAMAILIO_IP:5060
CANCEL sip:2383@DOWNSTREAM_IP:10533;transport=TLS SIP/2.0
Via: SIP/2.0/UDP PBXIP:5060;branch=z9hG4bK450689d6
Max-Forwards: 69
From: "some callerid"
<sip:18001111111@mypbx.mydomain.com>;tag=as4d223616
To: <sip:2383@DOWNSTREAM_IP:10533;transport=TLS>
Call-ID: 1511475b69f6379b08f04d110f534da1(a)mypbx.mydomain.com
CSeq: 102 CANCEL
User-Agent: B2B
Content-Length: 0
U 2020/05/26 08:40:10.941799 KAMAILIO_IP:5060 -> 255.255.255.255:5060
CANCEL sip:2383@DOWNSTREAM_IP:10533;transport=TLS SIP/2.0
Via: SIP/2.0/UDP PBXIP:5060;branch=z9hG4bK450689d6
Max-Forwards: 69
From: "some callerid"
<sip:18001111111@mypbx.mydomain.com>;tag=as4d223616
To: <sip:2383@DOWNSTREAM_IP:10533;transport=TLS>
Call-ID: 1511475b69f6379b08f04d110f534da1(a)mypbx.mydomain.com
CSeq: 102 CANCEL
User-Agent: B2B
Content-Length: 0
T 2020/05/26 08:40:10.941899 KAMAILIO_IP:5061 -> DOWNSTREAM_IP:10533
CANCEL sip:2383@DOWNSTREAM_IP:10533;transport=TLS SIP/2.0
Via: SIP/2.0/TLS
proxy.mydomain.com:5061;branch=z9hG4bK3cbb.4c6a526982fa1fb93ca1ba73afd8484f.0
Max-Forwards: 69
From: "some callerid"
<sip:18001111111@mypbx.mydomain.com>;tag=as4d223616
To: <sip:2383@DOWNSTREAM_IP:10533;transport=TLS>
Call-ID: 1511475b69f6379b08f04d110f534da1(a)mypbx.mydomain.com
CSeq: 102 CANCEL
Content-Length: 0
U 2020/05/26 08:40:10.941935 KAMAILIO_IP:5060 -> PBXIP:5060
SIP/2.0 200 canceling
Via: SIP/2.0/UDP PBXIP:5060;branch=z9hG4bK450689d6
From: "some callerid"
<sip:18001111111@mypbx.mydomain.com>;tag=as4d223616
To: <sip:2383@DOWNSTREAM_IP:10533;transport=TLS>
;tag=a6a1c5f60faecf035a1ae5b6e96e979a-612a1516
Call-ID: 1511475b69f6379b08f04d110f534da1(a)mypbx.mydomain.com
CSeq: 102 CANCEL
Server: Edge
Content-Length: 0
Thanks,
--Sergiu
_______________________________________________
Kamailio (SER) - Users Mailing
Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla -- www.asipto.comwww.twitter.com/miconda --
www.linkedin.com/in/miconda
Funding: https://www.paypal.me/dcmierla
1643
days inactive
1644
days old
2 comments
2 participants
participants (2)
-
Daniel-Constantin Mierla -
Sergiu Pojoga