outgoing call stop working ?

V

vuthy09

Member
Jun 12, 2023
124
12
18
41
outgoing call stop working, log file

2025-02-22 23:49:35.495953 95.80% [DEBUG] switch_core_state_machine.c:40 sofia/external/02825550755 Standard INIT
2025-02-22 23:49:35.495953 95.80% [DEBUG] switch_core_state_machine.c:48 (sofia/external/02825550755) State Change CS_INIT -> CS_ROUTING
2025-02-22 23:49:35.495953 95.80% [DEBUG] switch_core_state_machine.c:624 (sofia/external/02825550755) State INIT going to sleep
2025-02-22 23:49:35.515972 95.80% [DEBUG] switch_core_state_machine.c:581 (sofia/external/02825550755) Running State Change CS_ROUTING (Cur 2 Tot 154)
2025-02-22 23:49:35.515972 95.80% [DEBUG] switch_core_state_machine.c:640 (sofia/external/02825550755) State ROUTING
2025-02-22 23:49:35.515972 95.80% [DEBUG] mod_sofia.c:158 sofia/external/02825550755 SOFIA ROUTING
2025-02-22 23:49:35.515972 95.80% [DEBUG] switch_ivr_originate.c:67 (sofia/external/02825550755) State Change CS_ROUTING -> CS_CONSUME_MEDIA
2025-02-22 23:49:35.515972 95.80% [DEBUG] switch_core_state_machine.c:640 (sofia/external/02825550755) State ROUTING going to sleep
2025-02-22 23:49:35.515972 95.80% [DEBUG] switch_core_state_machine.c:581 (sofia/external/02825550755) Running State Change CS_CONSUME_MEDIA (Cur 2 Tot 154)
2025-02-22 23:49:35.515972 95.80% [DEBUG] sofia.c:7493 Channel sofia/external/02825550755 entering state [calling][0]
2025-02-22 23:49:35.515972 95.80% [DEBUG] switch_core_state_machine.c:659 (sofia/external/02825550755) State CONSUME_MEDIA
2025-02-22 23:49:35.515972 95.80% [DEBUG] switch_core_state_machine.c:659 (sofia/external/02825550755) State CONSUME_MEDIA going to sleep
2025-02-22 23:49:35.536013 95.80% [DEBUG] sofia.c:7493 Channel sofia/external/02825550755 entering state [calling][0]
2025-02-22 23:50:07.535946 98.40% [DEBUG] sofia.c:7493 Channel sofia/external/02825550755 entering state [terminated][408]
2025-02-22 23:50:07.535946 98.40% [NOTICE] sofia.c:8736 Hangup sofia/external/02825550755 [CS_CONSUME_MEDIA] [RECOVERY_ON_TIMER_EXPIRE]
2025-02-22 23:50:07.535946 98.40% [DEBUG] switch_core_state_machine.c:581 (sofia/external/02825550755) Running State Change CS_HANGUP (Cur 2 Tot 154)
2025-02-22 23:50:07.535946 98.40% [DEBUG] switch_core_state_machine.c:844 (sofia/external/02825550755) Callstate Change DOWN -> HANGUP
2025-02-22 23:50:07.535946 98.40% [DEBUG] switch_core_state_machine.c:846 (sofia/external/02825550755) State HANGUP
2025-02-22 23:50:07.535946 98.40% [DEBUG] mod_sofia.c:469 Channel sofia/external/02825550755 hanging up, cause: RECOVERY_ON_TIMER_EXPIRE
2025-02-22 23:50:07.535946 98.40% [DEBUG] switch_core_state_machine.c:59 sofia/external/02825550755 Standard HANGUP, cause: RECOVERY_ON_TIMER_EXPIRE
2025-02-22 23:50:07.535946 98.40% [DEBUG] switch_core_state_machine.c:846 (sofia/external/02825550755) State HANGUP going to sleep
2025-02-22 23:50:07.535946 98.40% [DEBUG] switch_core_state_machine.c:616 (sofia/external/02825550755) State Change CS_HANGUP -> CS_REPORTING
2025-02-22 23:50:07.535946 98.40% [DEBUG] switch_core_state_machine.c:581 (sofia/external/02825550755) Running State Change CS_REPORTING (Cur 2 Tot 154)
2025-02-22 23:50:07.535946 98.40% [DEBUG] switch_core_state_machine.c:932 (sofia/external/02825550755) State REPORTING
2025-02-22 23:50:07.535946 98.40% [DEBUG] switch_core_state_machine.c:168 sofia/external/02825550755 Standard REPORTING, cause: RECOVERY_ON_TIMER_EXPIRE
2025-02-22 23:50:07.535946 98.40% [DEBUG] switch_core_state_machine.c:932 (sofia/external/02825550755) State REPORTING going to sleep
2025-02-22 23:50:07.535946 98.40% [DEBUG] switch_core_state_machine.c:607 (sofia/external/02825550755) State Change CS_REPORTING -> CS_DESTROY
2025-02-22 23:50:07.535946 98.40% [DEBUG] switch_core_session.c:1748 Session 154 (sofia/external/02825550755) Locked, Waiting on external entities
2025-02-22 23:50:07.555952 98.40% [DEBUG] switch_ivr_originate.c:4056 Originate Resulted in Error Cause: 102 [RECOVERY_ON_TIMER_EXPIRE]
2025-02-22 23:50:07.555952 98.40% [NOTICE] switch_core_session.c:1766 Session 154 (sofia/external/02825550755) Ended
2025-02-22 23:50:07.555952 98.40% [NOTICE] switch_core_session.c:1770 Close Channel sofia/external/02825550755 [CS_DESTROY]
2025-02-22 23:50:07.555952 98.40% [DEBUG] switch_core_state_machine.c:735 (sofia/external/02825550755) Running State Change CS_DESTROY (Cur 1 Tot 154)
2025-02-22 23:50:07.555952 98.40% [DEBUG] switch_core_state_machine.c:745 (sofia/external/02825550755) State DESTROY
2025-02-22 23:50:07.555952 98.40% [DEBUG] mod_sofia.c:380 sofia/external/02825550755 SOFIA DESTROY
2025-02-22 23:50:07.555952 98.40% [DEBUG] switch_core_state_machine.c:175 sofia/external/02825550755 Standard DESTROY
2025-02-22 23:50:07.555952 98.40% [DEBUG] switch_core_state_machine.c:745 (sofia/external/02825550755) State DESTROY going to sleep
2025-02-22 23:50:07.555952 98.40% [DEBUG] switch_channel.c:2197 (sofia/internal/100@192.168.178.104) Callstate Change RING_WAIT -> ACTIVE

025-02-22 23:50:07.555952 98.40% [DEBUG] switch_core_state_machine.c:647 (sofia/internal/100@192.168.178.104) State EXECUTE going to sleep
2025-02-22 23:50:07.555952 98.40% [DEBUG] switch_core_state_machine.c:581 (sofia/internal/100@192.168.178.104) Running State Change CS_HANGUP (Cur 1 Tot 154)
2025-02-22 23:50:07.555952 98.40% [DEBUG] switch_core_state_machine.c:844 (sofia/internal/100@192.168.178.104) Callstate Change ACTIVE -> HANGUP
2025-02-22 23:50:07.555952 98.40% [DEBUG] switch_core_state_machine.c:846 (sofia/internal/100@192.168.178.104) State HANGUP
2025-02-22 23:50:07.555952 98.40% [DEBUG] mod_sofia.c:463 sofia/internal/100@192.168.178.104 Overriding SIP cause 504 with 408 from the other leg
2025-02-22 23:50:07.555952 98.40% [DEBUG] mod_sofia.c:469 Channel sofia/internal/100@192.168.178.104 hanging up, cause: RECOVERY_ON_TIMER_EXPIRE
2025-02-22 23:50:07.555952 98.40% [DEBUG] mod_sofia.c:523 Sending BYE to sofia/internal/100@192.168.178.104
2025-02-22 23:50:07.555952 98.40% [DEBUG] switch_core_state_machine.c:59 sofia/internal/100@192.168.178.104 Standard HANGUP, cause: RECOVERY_ON_TIMER_EXPIRE
2025-02-22 23:50:07.555952 98.40% [DEBUG] switch_core_state_machine.c:846 (sofia/internal/100@192.168.178.104) State HANGUP going to sleep
2025-02-22 23:50:07.555952 98.40% [DEBUG] switch_core_state_machine.c:616 (sofia/internal/100@192.168.178.104) State Change CS_HANGUP -> CS_REPORTING
2025-02-22 23:50:07.555952 98.40% [DEBUG] switch_core_state_machine.c:581 (sofia/internal/100@192.168.178.104) Running State Change CS_REPORTING (Cur 1 Tot 154)
2025-02-22 23:50:07.555952 98.40% [DEBUG] switch_core_state_machine.c:932 (sofia/internal/100@192.168.178.104) State REPORTING
2025-02-22 23:50:07.555952 98.40% [DEBUG] switch_core_state_machine.c:168 sofia/internal/100@192.168.178.104 Standard REPORTING, cause: RECOVERY_ON_TIMER_EXPIRE
2025-02-22 23:50:07.555952 98.40% [DEBUG] switch_core_state_machine.c:932 (sofia/internal/100@192.168.178.104) State REPORTING going to sleep
2025-02-22 23:50:07.555952 98.40% [DEBUG] switch_core_state_machine.c:607 (sofia/internal/100@192.168.178.104) State Change CS_REPORTING -> CS_DESTROY
2025-02-22 23:50:07.555952 98.40% [DEBUG] switch_core_session.c:1748 Session 153 (sofia/internal/100@192.168.178.104) Locked, Waiting on external entities
2025-02-22 23:50:07.555952 98.40% [NOTICE] switch_core_session.c:1766 Session 153 (sofia/internal/100@192.168.178.104) Ended
2025-02-22 23:50:07.555952 98.40% [NOTICE] switch_core_session.c:1770 Close Channel sofia/internal/100@192.168.178.104 [CS_DESTROY]
2025-02-22 23:50:07.555952 98.40% [DEBUG] switch_core_state_machine.c:735 (sofia/internal/100@192.168.178.104) Running State Change CS_DESTROY (Cur 0 Tot 154)
2025-02-22 23:50:07.555952 98.40% [DEBUG] switch_core_state_machine.c:745 (sofia/internal/100@192.168.178.104) State DESTROY
2025-02-22 23:50:07.555952 98.40% [DEBUG] mod_sofia.c:380 sofia/internal/100@192.168.178.104 SOFIA DESTROY
2025-02-22 23:50:07.555952 98.40% [DEBUG] switch_core_state_machine.c:175 sofia/internal/100@192.168.178.104 Standard DESTROY
2025-02-22 23:50:07.555952 98.40% [DEBUG] switch_core_state_machine.c:745 (sofia/internal/100@192.168.178.104) State DESTROY going to sleep
 
P

pbxgeek

Active Member
Jan 19, 2021
234
89
28
38
A SIP trace would be better to investigate your issue. We will be able to see the SIP response you got from the other side.
 
V

vuthy09

Member
Jun 12, 2023
124
12
18
41
No. Time Source Destination Protocol Length Info
77 16:01:14 192.168.178.128 74.125.250.129 CLASSIC-STUN 62 Message: Binding Request
78 16:01:14 192.168.178.128 74.125.250.129 CLASSIC-STUN 62 Message: Binding Request
79 16:01:14 74.125.250.129 192.168.178.128 CLASSIC-STUN 74 Message: Binding Response
80 16:01:14 74.125.250.129 192.168.178.128 CLASSIC-STUN 74 Message: Binding Response
81 16:01:14 192.168.178.128 192.168.178.104 SIP/SDP 1279 Request: INVITE sip:02825550755@192.168.178.104 |
82 16:01:15 192.168.178.104 192.168.178.128 SIP 887 Status: 407 Proxy Authentication Required |
83 16:01:15 192.168.178.128 192.168.178.104 SIP 417 Request: ACK sip:02825550755@192.168.178.104 |
84 16:01:15 192.168.178.128 192.168.178.104 IPv4 1514 Fragmented IP protocol (proto=UDP 17, off=0, ID=5152) [Reassembled in #85]
85 16:01:15 192.168.178.128 192.168.178.104 SIP/SDP 79 Request: INVITE sip:02825550755@192.168.178.104 |
86 16:01:15 192.168.178.104 192.168.178.128 SIP 388 Status: 100 Trying |
87 16:01:16 192.168.178.128 192.168.178.1 TCP 66 56196 → 53 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 WS=256 SACK_PERM
88 16:01:16 192.168.178.128 192.168.178.1 TCP 66 56197 → 53 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 WS=256 SACK_PERM
89 16:01:16 192.168.178.128 192.168.178.1 TCP 66 56198 → 53 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 WS=256 SACK_PERM
90 16:01:16 192.168.178.1 192.168.178.128 TCP 66 53 → 56196 [SYN, ACK] Seq=0 Ack=1 Win=14600 Len=0 MSS=1460 SACK_PERM WS=32
91 16:01:16 192.168.178.128 192.168.178.1 TCP 54 56196 → 53 [ACK] Seq=1 Ack=1 Win=131328 Len=0
92 16:01:16 192.168.178.1 192.168.178.128 TCP 66 53 → 56197 [SYN, ACK] Seq=0 Ack=1 Win=14600 Len=0 MSS=1460 SACK_PERM WS=32
93 16:01:16 192.168.178.128 192.168.178.1 TCP 56 56196 → 53 [PSH, ACK] Seq=1 Ack=1 Win=131328 Len=2 [TCP PDU reassembled in 95]
94 16:01:16 192.168.178.128 192.168.178.1 TCP 54 56197 → 53 [ACK] Seq=1 Ack=1 Win=131328 Len=0
95 16:01:16 192.168.178.128 192.168.178.1 DNS 105 Standard query 0x43f5 AAAA browser.events.data.microsoft.com
96 16:01:16 192.168.178.128 192.168.178.1 TCP 56 56197 → 53 [PSH, ACK] Seq=1 Ack=1 Win=131328 Len=2 [TCP PDU reassembled in 97]
97 16:01:16 192.168.178.128 192.168.178.1 DNS 105 Standard query 0x5318 A browser.events.data.microsoft.com
98 16:01:16 192.168.178.1 192.168.178.128 TCP 66 53 → 56198 [SYN, ACK] Seq=0 Ack=1 Win=14600 Len=0 MSS=1460 SACK_PERM WS=32
99 16:01:16 192.168.178.128 192.168.178.1 TCP 54 56198 → 53 [ACK] Seq=1 Ack=1 Win=131328 Len=0
100 16:01:16 192.168.178.128 192.168.178.1 TCP 56 56198 → 53 [PSH, ACK] Seq=1 Ack=1 Win=131328 Len=2 [TCP PDU reassembled in 101]
101 16:01:16 192.168.178.128 192.168.178.1 DNS 105 Standard query 0x557c HTTPS browser.events.data.microsoft.com
102 16:01:16 192.168.178.1 192.168.178.128 TCP 56 53 → 56196 [ACK] Seq=1 Ack=3 Win=14624 Len=0
103 16:01:16 192.168.178.1 192.168.178.128 TCP 56 53 → 56196 [ACK] Seq=1 Ack=54 Win=14624 Len=0
104 16:01:16 192.168.178.1 192.168.178.128 TCP 56 53 → 56197 [ACK] Seq=1 Ack=3 Win=14624 Len=0
105 16:01:16 192.168.178.1 192.168.178.128 TCP 56 53 → 56197 [ACK] Seq=1 Ack=54 Win=14624 Len=0
106 16:01:16 192.168.178.1 192.168.178.128 TCP 56 53 → 56198 [ACK] Seq=1 Ack=3 Win=14624 Len=0
107 16:01:16 192.168.178.1 192.168.178.128 TCP 56 53 → 56198 [ACK] Seq=1 Ack=54 Win=14624 Len=0
108 16:01:16 192.168.178.1 192.168.178.128 DNS 276 Standard query response 0x43f5 AAAA browser.events.data.microsoft.com CNAME browser.events.data.trafficmanager.net CNAME onedscolprdcus10.centralus.cloudapp.azure.com SOA ns1-201.azure-dns.com
109 16:01:16 192.168.178.1 192.168.178.128 DNS 231 Standard query response 0x5318 A browser.events.data.microsoft.com CNAME browser.events.data.trafficmanager.net CNAME onedscolprdcus10.centralus.cloudapp.azure.com A 52.182.143.210
110 16:01:16 192.168.178.1 192.168.178.128 DNS 276 Standard query response 0x557c HTTPS browser.events.data.microsoft.com CNAME browser.events.data.trafficmanager.net CNAME onedscolprdcus10.centralus.cloudapp.azure.com SOA ns1-201.azure-dns.com
111 16:01:16 192.168.178.128 192.168.178.1 TCP 54 56196 → 53 [FIN, ACK] Seq=54 Ack=223 Win=131072 Len=0
112 16:01:16 192.168.178.128 192.168.178.1 TCP 54 56198 → 53 [FIN, ACK] Seq=54 Ack=223 Win=131072 Len=0
113 16:01:16 192.168.178.128 192.168.178.1 TCP 54 56197 → 53 [FIN, ACK] Seq=54 Ack=178 Win=131072 Len=0
114 16:01:16 192.168.178.128 52.182.143.210 TCP 66 56199 → 443 [SYN] Seq=0 Win=64240 Len=0 MSS=1460 WS=256 SACK_PERM
115 16:01:16 192.168.178.1 192.168.178.128 TCP 56 53 → 56196 [FIN, ACK] Seq=223 Ack=55 Win=14624 Len=0
116 16:01:16 192.168.178.128 192.168.178.1 TCP 54 56196 → 53 [ACK] Seq=55 Ack=224 Win=131072 Len=0
117 16:01:16 192.168.178.1 192.168.178.128 TCP 56 53 → 56198 [ACK] Seq=223 Ack=55 Win=14624 Len=0
118 16:01:16 192.168.178.1 192.168.178.128 TCP 56 53 → 56197 [ACK] Seq=178 Ack=55 Win=14624 Len=0
119 16:01:16 192.168.178.1 192.168.178.128 TCP 56 53 → 56197 [FIN, ACK] Seq=178 Ack=55 Win=14624 Len=0
120 16:01:16 192.168.178.1 192.168.178.128 TCP 56 53 → 56198 [FIN, ACK] Seq=223 Ack=55 Win=14624 Len=0
121 16:01:16 192.168.178.128 192.168.178.1 TCP 54 56197 → 53 [ACK] Seq=55 Ack=179 Win=131072 Len=0
122 16:01:16 192.168.178.128 192.168.178.1 TCP 54 56198 → 53 [ACK] Seq=55 Ack=224 Win=131072 Len=0
123 16:01:16 52.182.143.210 192.168.178.128 TCP 66 443 → 56199 [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1440 WS=256 SACK_PERM
124 16:01:16 192.168.178.128 52.182.143.210 TCP 54 56199 → 443 [ACK] Seq=1 Ack=1 Win=132352 Len=0
125 16:01:16 192.168.178.128 52.182.143.210 TCP 1494 56199 → 443 [ACK] Seq=1 Ack=1 Win=132352 Len=1440 [TCP PDU reassembled in 126]
126 16:01:16 192.168.178.128 52.182.143.210 TLSv1.3 452 Client Hello (SNI=browser.events.data.microsoft.com)
127 16:01:16 52.182.143.210 192.168.178.128 TCP 56 443 → 56199 [ACK] Seq=1 Ack=1839 Win=4194816 Len=0
128 16:01:16 52.182.143.210 192.168.178.128 TLSv1.3 153 Hello Retry Request, Change Cipher Spec
129 16:01:16 192.168.178.128 52.182.143.210 TLSv1.3 738 Change Cipher Spec, Client Hello (SNI=browser.events.data.microsoft.com)
130 16:01:16 AVMAudiovisu_5d:a6:50 Broadcast HomePlug AV 60 Qualcomm Atheros, GET_SW.REQ (Get Device/SW Version Request)
131 16:01:16 AVMAudiovisu_5d:a6:50 Broadcast 0x8912 60 Ethernet II
132 16:01:17 52.182.143.210 192.168.178.128 TLSv1.3 1506 Server Hello
133 16:01:17 52.182.143.210 192.168.178.128 TCP 1506 443 → 56199 [ACK] Seq=1552 Ack=2523 Win=4194048 Len=1452 [TCP PDU reassembled in 136]
134 16:01:17 52.182.143.210 192.168.178.128 TCP 1506 443 → 56199 [ACK] Seq=3004 Ack=2523 Win=4194048 Len=1452 [TCP PDU reassembled in 136]
135 16:01:17 52.182.143.210 192.168.178.128 TCP 1506 443 → 56199 [ACK] Seq=4456 Ack=2523 Win=4194048 Len=1452 [TCP PDU reassembled in 136]
136 16:01:17 52.182.143.210 192.168.178.128 TLSv1.3 652 Application Data
137 16:01:17 192.168.178.128 52.182.143.210 TCP 54 56199 → 443 [ACK] Seq=2523 Ack=6506 Win=132352 Len=0
138 16:01:17 192.168.178.128 52.182.143.210 TLSv1.3 128 Application Data
139 16:01:17 192.168.178.128 52.182.143.210 TLSv1.3 146 Application Data
140 16:01:17 192.168.178.128 52.182.143.210 TLSv1.3 1289 Application Data
141 16:01:17 192.168.178.128 52.182.143.210 TCP 1494 56199 → 443 [ACK] Seq=3924 Ack=6506 Win=132352 Len=1440 [TCP PDU reassembled in 144]
142 16:01:17 192.168.178.128 52.182.143.210 TCP 1494 56199 → 443 [ACK] Seq=5364 Ack=6506 Win=132352 Len=1440 [TCP PDU reassembled in 144]
143 16:01:17 192.168.178.128 52.182.143.210 TCP 1494 56199 → 443 [ACK] Seq=6804 Ack=6506 Win=132352 Len=1440 [TCP PDU reassembled in 144]
144 16:01:17 192.168.178.128 52.182.143.210 TLSv1.3 503 Application Data
145 16:01:17 52.182.143.210 192.168.178.128 TCP 56 443 → 56199 [ACK] Seq=6506 Ack=8693 Win=4194816 Len=0
146 16:01:17 52.182.143.210 192.168.178.128 TLSv1.3 157 Application Data
147 16:01:17 52.182.143.210 192.168.178.128 TLSv1.3 116 Application Data
148 16:01:17 192.168.178.128 52.182.143.210 TCP 54 56199 → 443 [ACK] Seq=8693 Ack=6671 Win=132096 Len=0
149 16:01:17 192.168.178.128 52.182.143.210 TLSv1.3 85 Application Data
150 16:01:17 52.182.143.210 192.168.178.128 TLSv1.3 418 Application Data, Application Data
151 16:01:17 192.168.178.128 52.182.143.210 TCP 54 56199 → 443 [ACK] Seq=8724 Ack=7035 Win=131840 Len=0
152 16:01:18 2404:4408:8a6b:d400:d9e8:7e50:c5ba:b4fd 2404:4408:5:51cc::83cb:398 TCP 75 56108 → 443 [ACK] Seq=1 Ack=1 Win=514 Len=1
153 16:01:18 2404:4408:5:51cc::83cb:398 2404:4408:8a6b:d400:d9e8:7e50:c5ba:b4fd TCP 86 443 → 56108 [ACK] Seq=1 Ack=2 Win=501 Len=0 SLE=1 SRE=2
154 16:01:18 192.168.178.128 192.168.178.104 UDP 44 60808 → 5060 Len=2
155 16:01:18 192.168.178.128 104.18.27.90 TCP 55 56166 → 443 [ACK] Seq=1 Ack=1 Win=512 Len=1
156 16:01:18 104.18.27.90 192.168.178.128 TCP 66 443 → 56166 [ACK] Seq=1 Ack=2 Win=10 Len=0 SLE=1 SRE=2
157 16:01:18 AVMAudiovisu_5d:a6:50 Broadcast HomePlug AV 60 Qualcomm Atheros, GET_SW.REQ (Get Device/SW Version Request)
158 16:01:18 AVMAudiovisu_5d:a6:50 Broadcast 0x8912 60 Ethernet II
159 16:01:20 RaspberryPiT_7c:87:bc ChongqingFug_7b:33:bb ARP 42 Who has 192.168.178.128? Tell 192.168.178.104
160 16:01:20 ChongqingFug_7b:33:bb RaspberryPiT_7c:87:bc ARP 42 192.168.178.128 is at c0:b5:d7:7b:33:bb
161 16:01:20 AVMAudiovisu_5d:a6:50 Broadcast HomePlug AV 60 Qualcomm Atheros, GET_SW.REQ (Get Device/SW Version Request)
162 16:01:20 AVMAudiovisu_5d:a6:50 Broadcast 0x8912 60 Ethernet II
163 16:01:22 AVMAudiovisu_5d:a6:50 Broadcast HomePlug AV 60 Qualcomm Atheros, GET_SW.REQ (Get Device/SW Version Request)
164 16:01:22 AVMAudiovisu_5d:a6:50 Broadcast 0x8912 60 Ethernet II
165 16:01:24 192.168.178.128 192.168.178.104 UDP 46 57414 → 5060 Len=4
166 16:01:24 AVMAudiovisu_5d:a6:50 Broadcast HomePlug AV 60 Qualcomm Atheros, GET_SW.REQ (Get Device/SW Version Request)
167 16:01:24 AVMAudiovisu_5d:a6:50 Broadcast 0x8912 60 Ethernet II
168 16:01:25 192.168.178.1 224.0.0.1 IGMPv3 50 Membership Query, general
169 16:01:25 192.168.178.128 192.168.178.104 SIP 591 Request: REGISTER sip:192.168.178.104 (1 binding) |
170 16:01:25 192.168.178.104 192.168.178.128 SIP 674 Status: 401 Unauthorized |
171 16:01:25 192.168.178.128 192.168.178.104 SIP 853 Request: REGISTER sip:192.168.178.104 (1 binding) |
172 16:01:25 192.168.178.104 192.168.178.128 SIP 635 Status: 200 OK (REGISTER) (1 binding) |
173 16:01:26 192.168.178.128 35.174.127.31 TLSv1.2 294 Application Data
174 16:01:26 35.174.127.31 192.168.178.128 TLSv1.2 315 Application Data
175 16:01:26 192.168.178.128 35.174.127.31 TCP 54 56017 → 443 [ACK] Seq=480 Ack=526 Win=516 Len=0
 
P

pbxgeek

Active Member
Jan 19, 2021
234
89
28
38
Are both of these external outbound calls?

First screenshot: The beginning of communication looks good. You are sending an INVITE and the other side replies with 401 to authenticate. Are you using REGISTER instead of IP Authentication? It's OK if you do. Just want to make sure. After your second INVITE , which should have the authenticating info, the other side isn't answering. My best guess is that it never reaches them.

Second screenshot: The call didn't go through the external trunk, as it seems. It's showing a local IP.

Possible network or NAT issues on your end?
 
  • Like
Reactions: vuthy09
V

vuthy09

Member
Jun 12, 2023
124
12
18
41
pbxgeek said:
Are both of these external outbound calls?

First screenshot: The beginning of communication looks good. You are sending an INVITE and the other side replies with 401 to authenticate. Are you using REGISTER instead of IP Authentication? It's OK if you do. Just want to make sure. After your second INVITE , which should have the authenticating info, the other side isn't answering. My best guess is that it never reaches them.

Second screenshot: The call didn't go through the external trunk, as it seems. It's showing a local IP.

Possible network or NAT issues on your end?
Click to expand...
yes, I call to 02825550755
 
P

pbxgeek

Active Member
Jan 19, 2021
234
89
28
38
Oh, I got it. Same call with but two different legs. Makes more sense now. Well, after the call leaves your box the other side isn't responding. Hence why you keep resending the INVITEs. It could be an issue with resolving their IP address. Have you asked them to find these calls and see if they see anything past the initial INVITE? It can also be that they are sending a reply, but it's not making it back to you (NAT issue on your end)
 
  • Like
Reactions: vuthy09
V

vuthy09

Member
Jun 12, 2023
124
12
18
41
pbxgeek said:
Oh, I got it. Same call with but two different legs. Makes more sense now. Well, after the call leaves your box the other side isn't responding. Hence why you keep resending the INVITEs. It could be an issue with resolving their IP address. Have you asked them to find these calls and see if they see anything past the initial INVITE? It can also be that they are sending a reply, but it's not making it back to you (NAT issue on your end)
Click to expand...
You're right. How to configure NAT for local network ?
 
You must log in or register to reply here.
Top Bottom