[asterisk-bugs] [JIRA] (ASTERISK-28980) PJSIP outbound registration issue
newborn (JIRA)
noreply at issues.asterisk.org
Mon Jul 6 11:35:25 CDT 2020
[ https://issues.asterisk.org/jira/browse/ASTERISK-28980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
newborn updated ASTERISK-28980:
-------------------------------
Description:
Client establishes a SIP TLS connection to server.
Client IP 192.168.82.32
Server IP 10.2.60.23
We have a some kind of buggy channel between servers.
>From some time, the server stops to receive packets from client.
client continues to push data with no response from server (look tcpdump output from 19:08:18.661449).
When it happens i do the following:
Clean out pjsip.conf (loaded empty one)
then invoked 'module reload'
then restored the pjsip.conf
then invoked 'module reload' again.
No changes. The client continues sending data with TCP Push flag header instead of new SYN or Reset/SYN. Router on the server side just rejects this because it does not belong to any session.
How to destroy a SIP TLS/TCP session on the client without restarting the whole asterisk process?
Here is a tcpdump fragment from client side.
19:07:29.584075 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 35044:36094, ack 27749, win 1059, options [nop,nop,TS val 878646 ecr 2427808571], length 1050
19:07:29.596449 IP 10.2.60.23.5061 > 192.168.82.32.39918: Flags [P.], seq 27749:28415, ack 36094, win 960, options [nop,nop,TS val 2427808584 ecr 878646], length 666
19:07:29.636438 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [.], ack 28415, win 1077, options [nop,nop,TS val 878699 ecr 2427808584], length 0
19:07:46.645838 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 36094:36168, ack 28415, win 1077, options [nop,nop,TS val 895708 ecr 2427808584], length 74
19:07:46.696469 IP 10.2.60.23.5061 > 192.168.82.32.39918: Flags [.], ack 36168, win 960, options [nop,nop,TS val 2427825684 ecr 895708], length 0
19:07:50.590621 IP 10.2.60.23.5061 > 192.168.82.32.39918: Flags [P.], seq 28415:28489, ack 36168, win 960, options [nop,nop,TS val 2427829578 ecr 895708], length 74
19:07:50.590642 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [.], ack 28489, win 1077, options [nop,nop,TS val 899653 ecr 2427829578], length 0
19:08:18.597168 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 36168:36882, ack 28489, win 1077, options [nop,nop,TS val 927659 ecr 2427829578], length 714
19:08:18.608568 IP 10.2.60.23.5061 > 192.168.82.32.39918: Flags [.], ack 36882, win 977, options [nop,nop,TS val 2427857595 ecr 927659], length 0
19:08:18.609224 IP 10.2.60.23.5061 > 192.168.82.32.39918: Flags [P.], seq 28489:29203, ack 36882, win 977, options [nop,nop,TS val 2427857596 ecr 927659], length 714
19:08:18.609232 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [.], ack 29203, win 1096, options [nop,nop,TS val 927671 ecr 2427857596], length 0
19:08:18.609625 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 36882:37932, ack 29203, win 1096, options [nop,nop,TS val 927672 ecr 2427857596], length 1050
19:08:18.621904 IP 10.2.60.23.5061 > 192.168.82.32.39918: Flags [P.], seq 29203:29869, ack 37932, win 993, options [nop,nop,TS val 2427857609 ecr 927672], length 666
19:08:18.661449 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [.], ack 29869, win 1114, options [nop,nop,TS val 927724 ecr 2427857609], length 0
19:09:09.633732 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 978696 ecr 2427857609], length 714
19:09:09.853443 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 978916 ecr 2427857609], length 714
19:09:10.073443 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 979136 ecr 2427857609], length 714
19:09:10.517326 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 979579 ecr 2427857609], length 714
19:09:11.397447 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 980460 ecr 2427857609], length 714
19:09:13.161446 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 982224 ecr 2427857609], length 714
19:09:16.689454 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 985752 ecr 2427857609], length 714
19:09:23.737454 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 992800 ecr 2427857609], length 714
19:09:37.849446 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 1006912 ecr 2427857609], length 714
19:10:06.073475 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 1035136 ecr 2427857609], length 714
19:11:02.521459 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 1091584 ecr 2427857609], length 714
19:12:55.417465 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 1204480 ecr 2427857609], length 714
19:14:55.481451 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 1324544 ecr 2427857609], length 714
was:
Client establishes a SIP TLS connection to server.
Client IP 192.168.82.32
Server IP 10.2.60.23
We have a some kind of buggy channel between servers.
>From some time, the server stops to receive packets from client.
client continues to push data with no response from server (look tcpdump output from 19:08:18.661449).
When it happens i do the following:
Clean out pjsip.conf (loaded empty one)
then invoked 'module reload'
then restored the pjsip.conf
then invoked 'module reload' again.
No changes. The client continues sending data with TCP Push flag header instead of new SYN or Reset/SYN. Router on the server side just rejects this because it does not belong to any session.
How to fix it without restarting the whole asterisk?
Here is a tcpdump fragment from client side.
19:07:29.584075 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 35044:36094, ack 27749, win 1059, options [nop,nop,TS val 878646 ecr 2427808571], length 1050
19:07:29.596449 IP 10.2.60.23.5061 > 192.168.82.32.39918: Flags [P.], seq 27749:28415, ack 36094, win 960, options [nop,nop,TS val 2427808584 ecr 878646], length 666
19:07:29.636438 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [.], ack 28415, win 1077, options [nop,nop,TS val 878699 ecr 2427808584], length 0
19:07:46.645838 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 36094:36168, ack 28415, win 1077, options [nop,nop,TS val 895708 ecr 2427808584], length 74
19:07:46.696469 IP 10.2.60.23.5061 > 192.168.82.32.39918: Flags [.], ack 36168, win 960, options [nop,nop,TS val 2427825684 ecr 895708], length 0
19:07:50.590621 IP 10.2.60.23.5061 > 192.168.82.32.39918: Flags [P.], seq 28415:28489, ack 36168, win 960, options [nop,nop,TS val 2427829578 ecr 895708], length 74
19:07:50.590642 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [.], ack 28489, win 1077, options [nop,nop,TS val 899653 ecr 2427829578], length 0
19:08:18.597168 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 36168:36882, ack 28489, win 1077, options [nop,nop,TS val 927659 ecr 2427829578], length 714
19:08:18.608568 IP 10.2.60.23.5061 > 192.168.82.32.39918: Flags [.], ack 36882, win 977, options [nop,nop,TS val 2427857595 ecr 927659], length 0
19:08:18.609224 IP 10.2.60.23.5061 > 192.168.82.32.39918: Flags [P.], seq 28489:29203, ack 36882, win 977, options [nop,nop,TS val 2427857596 ecr 927659], length 714
19:08:18.609232 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [.], ack 29203, win 1096, options [nop,nop,TS val 927671 ecr 2427857596], length 0
19:08:18.609625 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 36882:37932, ack 29203, win 1096, options [nop,nop,TS val 927672 ecr 2427857596], length 1050
19:08:18.621904 IP 10.2.60.23.5061 > 192.168.82.32.39918: Flags [P.], seq 29203:29869, ack 37932, win 993, options [nop,nop,TS val 2427857609 ecr 927672], length 666
19:08:18.661449 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [.], ack 29869, win 1114, options [nop,nop,TS val 927724 ecr 2427857609], length 0
19:09:09.633732 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 978696 ecr 2427857609], length 714
19:09:09.853443 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 978916 ecr 2427857609], length 714
19:09:10.073443 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 979136 ecr 2427857609], length 714
19:09:10.517326 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 979579 ecr 2427857609], length 714
19:09:11.397447 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 980460 ecr 2427857609], length 714
19:09:13.161446 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 982224 ecr 2427857609], length 714
19:09:16.689454 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 985752 ecr 2427857609], length 714
19:09:23.737454 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 992800 ecr 2427857609], length 714
19:09:37.849446 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 1006912 ecr 2427857609], length 714
19:10:06.073475 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 1035136 ecr 2427857609], length 714
19:11:02.521459 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 1091584 ecr 2427857609], length 714
19:12:55.417465 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 1204480 ecr 2427857609], length 714
19:14:55.481451 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 1324544 ecr 2427857609], length 714
> PJSIP outbound registration issue
> ---------------------------------
>
> Key: ASTERISK-28980
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-28980
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: pjproject/pjsip
> Affects Versions: 13.34.0
> Environment: CentOS 7 with latest updates
> Reporter: newborn
>
> Client establishes a SIP TLS connection to server.
> Client IP 192.168.82.32
> Server IP 10.2.60.23
> We have a some kind of buggy channel between servers.
> From some time, the server stops to receive packets from client.
> client continues to push data with no response from server (look tcpdump output from 19:08:18.661449).
> When it happens i do the following:
> Clean out pjsip.conf (loaded empty one)
> then invoked 'module reload'
> then restored the pjsip.conf
> then invoked 'module reload' again.
> No changes. The client continues sending data with TCP Push flag header instead of new SYN or Reset/SYN. Router on the server side just rejects this because it does not belong to any session.
> How to destroy a SIP TLS/TCP session on the client without restarting the whole asterisk process?
> Here is a tcpdump fragment from client side.
> 19:07:29.584075 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 35044:36094, ack 27749, win 1059, options [nop,nop,TS val 878646 ecr 2427808571], length 1050
> 19:07:29.596449 IP 10.2.60.23.5061 > 192.168.82.32.39918: Flags [P.], seq 27749:28415, ack 36094, win 960, options [nop,nop,TS val 2427808584 ecr 878646], length 666
> 19:07:29.636438 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [.], ack 28415, win 1077, options [nop,nop,TS val 878699 ecr 2427808584], length 0
> 19:07:46.645838 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 36094:36168, ack 28415, win 1077, options [nop,nop,TS val 895708 ecr 2427808584], length 74
> 19:07:46.696469 IP 10.2.60.23.5061 > 192.168.82.32.39918: Flags [.], ack 36168, win 960, options [nop,nop,TS val 2427825684 ecr 895708], length 0
> 19:07:50.590621 IP 10.2.60.23.5061 > 192.168.82.32.39918: Flags [P.], seq 28415:28489, ack 36168, win 960, options [nop,nop,TS val 2427829578 ecr 895708], length 74
> 19:07:50.590642 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [.], ack 28489, win 1077, options [nop,nop,TS val 899653 ecr 2427829578], length 0
> 19:08:18.597168 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 36168:36882, ack 28489, win 1077, options [nop,nop,TS val 927659 ecr 2427829578], length 714
> 19:08:18.608568 IP 10.2.60.23.5061 > 192.168.82.32.39918: Flags [.], ack 36882, win 977, options [nop,nop,TS val 2427857595 ecr 927659], length 0
> 19:08:18.609224 IP 10.2.60.23.5061 > 192.168.82.32.39918: Flags [P.], seq 28489:29203, ack 36882, win 977, options [nop,nop,TS val 2427857596 ecr 927659], length 714
> 19:08:18.609232 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [.], ack 29203, win 1096, options [nop,nop,TS val 927671 ecr 2427857596], length 0
> 19:08:18.609625 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 36882:37932, ack 29203, win 1096, options [nop,nop,TS val 927672 ecr 2427857596], length 1050
> 19:08:18.621904 IP 10.2.60.23.5061 > 192.168.82.32.39918: Flags [P.], seq 29203:29869, ack 37932, win 993, options [nop,nop,TS val 2427857609 ecr 927672], length 666
> 19:08:18.661449 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [.], ack 29869, win 1114, options [nop,nop,TS val 927724 ecr 2427857609], length 0
> 19:09:09.633732 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 978696 ecr 2427857609], length 714
> 19:09:09.853443 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 978916 ecr 2427857609], length 714
> 19:09:10.073443 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 979136 ecr 2427857609], length 714
> 19:09:10.517326 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 979579 ecr 2427857609], length 714
> 19:09:11.397447 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 980460 ecr 2427857609], length 714
> 19:09:13.161446 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 982224 ecr 2427857609], length 714
> 19:09:16.689454 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 985752 ecr 2427857609], length 714
> 19:09:23.737454 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 992800 ecr 2427857609], length 714
> 19:09:37.849446 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 1006912 ecr 2427857609], length 714
> 19:10:06.073475 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 1035136 ecr 2427857609], length 714
> 19:11:02.521459 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 1091584 ecr 2427857609], length 714
> 19:12:55.417465 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 1204480 ecr 2427857609], length 714
> 19:14:55.481451 IP 192.168.82.32.39918 > 10.2.60.23.5061: Flags [P.], seq 37932:38646, ack 29869, win 1114, options [nop,nop,TS val 1324544 ecr 2427857609], length 714
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list