Error Explanation

Dawson5924 · September 20, 2018, 6:38am

Hi guys!
I am new at using asterisk so i do not completely understand it yet. I will be very grateful if you
help me understand what is going on in below images

david551 · September 20, 2018, 9:11am

You are trying to pass an invalid user name to the Dial application, possibly one including authentication data. As a result, it things 43582 is the host name of the peer.

Dawson5924 · September 20, 2018, 5:54pm

Thanks david! Just figured it out…Now there is another problem that i m facing

I have done some research over it and have my debug data if you want that to give a solution.

Dawson5924 · September 20, 2018, 5:56pm

I don’t know how to read this so cannot yet come up with the solution

Dawson5924 · September 20, 2018, 5:59pm

Most of the blogs say that either its NAT or Firewall but i cannot figure it out. Your help will be really appreciated.
Thanks!

david551 · September 20, 2018, 10:06pm

I can’t quote the error line because you used an image, rather than text, but there are two formats for SIP dialstrings with dialled digits included:


SIP/<dialeddigits>@<device-or-host>

and

SIP/<device-or-host>/<dialeddigits>```

You have an unholy mix of both and the dialled digits are different between the front and back.

david551 · September 20, 2018, 10:10pm

Did you read the URI in the message about retransmissions. Basically a request or response is either being blocked or sent to the wrong place.

Dawson5924 · September 20, 2018, 10:31pm

I m trying to figure the transmission issue. just forwarded some ports and dzm enabled the server IP,
but it was all useless as that was not the problem i guess its just sent to wrong adrress .Now i m reading log files of firewall to get the blocked file, but encountered some files that were sent to unknown IP. What should I do to lessen this ache?

Dawson5924 · September 20, 2018, 10:48pm

I m actually using VMware 14 pro to run this asterisk as guest so does not allows me to copy the text…yes i read that URI and many other blogs as well. I also changed quality =500 in sip.conf file to confirm If the carrier does support qualify, then the packets are not making the entire trip so you can begin tracing packets and it did supported that quality, in sip show peers it showed OK.

I think the error is related to SIP 2.0 402 Not found while transmitting NAT

Dawson5924 · September 20, 2018, 10:52pm

I m really thankful for your time and help.

Dawson5924 · September 20, 2018, 10:56pm

Is there any other path that I can take for sure success?

Dawson5924 · September 20, 2018, 11:14pm

And one more thing my server is constantly receiving an unknown RTP code 126 from the host IP. Is it some code to worry about…As per google i turned off X-Lite keepalive box but it is still there.

Dawson5924 · September 20, 2018, 11:34pm

How do you think we can manage variable port number and dynamic public IP?

david551 · September 20, 2018, 11:42pm

Linux terminal driers allow you to copy text from screens, so do the copy completely within Linux. Even better, use the log files which will have better timestamps.

404 simply means the number being called is unknown to your Asterisk system, within context associated with the calling device. “s” is used as a placeholder when there is no user field in the request URI, but is also the default in the URIs used for registration. It has nothing to do with retransmissions.

Dawson5924 · September 21, 2018, 1:17am

PUBLIC LOG CALL 1 TIME=32 SEC
What should I do next?

2018-09-21 06:02:16 ALLOW TCP 192.168.x.x 192.x.x.x 52195 80 0 - 0 0 0 - - - SEND
2018-09-21 06:02:18 ALLOW TCP 192.168.x.x 192.x.x.x 52196 80 0 - 0 0 0 - - - SEND
2018-09-21 06:02:18 ALLOW UDP 192.168.x.x 192.x.x.x 49336 53 0 - - - - - - - SEND
2018-09-21 06:02:18 ALLOW TCP 192.168.x.x 23.208.172.97 52197 80 0 - 0 0 0 - - - SEND
2018-09-21 06:02:20 ALLOW TCP 192.168.x.x 192.x.x.x 52198 80 0 - 0 0 0 - - - SEND
2018-09-21 06:02:22 ALLOW TCP 192.168.x.x 192.x.x.x 52199 80 0 - 0 0 0 - - - SEND
2018-09-21 06:02:22 ALLOW UDP 192.168.x.x 255.255.255.255 17500 17500 0 - - - - - - - SEND
2018-09-21 06:02:24 ALLOW UDP 192.168.x.x 192.168.1.255 137 137 0 - - - - - - - SEND
2018-09-21 06:02:24 ALLOW UDP fe80::ac8f:354b:2b7d:1e32 ff02::1:3 50062 5355 0 - - - - - - - SEND
2018-09-21 06:02:24 ALLOW TCP 192.168.x.x 192.x.x.x 52200 80 0 - 0 0 0 - - - SEND
2018-09-21 06:02:24 ALLOW UDP 192.168.x.x 224.0.0.252 50062 5355 0 - - - - - - - SEND
2018-09-21 06:02:26 ALLOW TCP 192.168.x.x 192.x.x.x 52201 80 0 - 0 0 0 - - - SEND
2018-09-21 06:02:28 ALLOW TCP 192.168.x.x 192.x.x.x 52202 80 0 - 0 0 0 - - - SEND
2018-09-21 06:02:30 ALLOW TCP 192.168.x.x 192.x.x.x 52203 80 0 - 0 0 0 - - - SEND
2018-09-21 06:02:32 ALLOW TCP 192.168.x.x 192.x.x.x 52204 80 0 - 0 0 0 - - - SEND
2018-09-21 06:02:32 ALLOW UDP fe80::20a0:2fa0:4947:a26c ff02::1:2 546 547 0 - - - - - - - SEND
2018-09-21 06:02:34 ALLOW TCP 192.168.x.x 192.x.x.x 52205 80 0 - 0 0 0 - - - SEND
2018-09-21 06:02:34 ALLOW 2 0.0.0.0 224.0.0.1 - - 0 - - - - - - - RECEIVE
2018-09-21 06:02:34 ALLOW 2 192.168.x.x 224.0.0.251 - - 0 - - - - - - - SEND
2018-09-21 06:02:36 ALLOW UDP 192.168.x.x 192.168.1.255 137 137 0 - - - - - - - SEND
2018-09-21 06:02:36 ALLOW UDP fe80::ac8f:354b:2b7d:1e32 ff02::1:3 49449 5355 0 - - - - - - - SEND
2018-09-21 06:02:36 ALLOW UDP 192.168.x.x 224.0.0.252 49449 5355 0 - - - - - - - SEND
2018-09-21 06:02:36 ALLOW UDP 0.0.0.0 255.255.255.255 68 67 0 - - - - - - - SEND
2018-09-21 06:02:36 ALLOW UDP 0.0.0.0 255.255.255.255 68 67 0 - - - - - - - RECEIVE
2018-09-21 06:02:36 ALLOW ICMP fe80::ac8f:354b:2b7d:1e32 ff02::2 - - 0 - - - - 132 0 - SEND
2018-09-21 06:02:36 DROP ICMP fe80::74d6:5ff:fee6:9975 ff02::1 - - 80 - - - - 130 0 - RECEIVE
2018-09-21 06:02:36 ALLOW UDP 192.x.x.x 192.168.x.x 67 68 0 - - - - - - - RECEIVE
2018-09-21 06:02:36 ALLOW ICMP fe80::ac8f:354b:2b7d:1e32 ff02::1:3 - - 0 - - - - 131 0 - SEND
2018-09-21 06:02:36 DROP 2 192.168.x.x 224.0.0.252 - - 32 - - - - - - - RECEIVE
2018-09-21 06:02:36 ALLOW UDP fe80::ac8f:354b:2b7d:1e32 ff02::1:2 546 547 0 - - - - - - - SEND
2018-09-21 06:02:36 ALLOW UDP fe80::ac8f:354b:2b7d:1e32 ff02::1:3 56442 5355 0 - - - - - - - SEND
2018-09-21 06:02:36 ALLOW UDP 192.168.x.x 224.0.0.252 56442 5355 0 - - - - - - - SEND
2018-09-21 06:02:36 ALLOW UDP 192.168.x.x 239.255.255.250 58615 1900 0 - - - - - - - SEND
2018-09-21 06:02:36 ALLOW UDP 127.0.0.1 239.255.255.250 58616 1900 0 - - - - - - - SEND
2018-09-21 06:02:36 DROP 2 192.168.x.x 224.0.0.251 - - 32 - - - - - - - RECEIVE
2018-09-21 06:02:36 DROP 2 192.168.x.x 239.255.255.250 - - 32 - - - - - - - RECEIVE
2018-09-21 06:02:36 DROP 2 192.168.x.x 224.0.0.252 - - 32 - - - - - - - RECEIVE
2018-09-21 06:02:36 ALLOW ICMP :: ff02::1:ff7d:1e32 - - 0 - - - - 135 0 - SEND
2018-09-21 06:02:36 ALLOW ICMP fe80::ac8f:354b:2b7d:1e32 ff02::2 - - 0 - - - - 133 0 - SEND
2018-09-21 06:02:37 DROP 2 192.168.x.x 224.0.0.251 - - 32 - - - - - - - RECEIVE
2018-09-21 06:02:37 DROP 2 192.168.x.x 239.255.255.250 - - 32 - - - - - - - RECEIVE
2018-09-21 06:02:37 DROP 2 192.168.x.x 224.0.0.252 - - 32 - - - - - - - RECEIVE
2018-09-21 06:02:37 ALLOW UDP fe80::ac8f:354b:2b7d:1e32 ff02::1:3 57438 5355 0 - - - - - - - SEND
2018-09-21 06:02:37 ALLOW UDP 192.168.x.x 224.0.0.252 57438 5355 0 - - - - - - - SEND
2018-09-21 06:02:37 DROP ICMP fe80::74d6:5ff:fee6:9975 ff02::1 - - 80 - - - - 130 0 - RECEIVE
2018-09-21 06:02:37 DROP 2 192.168.x.x 224.0.0.252 - - 32 - - - - - - - RECEIVE
2018-09-21 06:02:37 ALLOW ICMP fe80::ac8f:354b:2b7d:1e32 ff02::1 - - 0 - - - - 136 0 - SEND
2018-09-21 06:02:38 ALLOW UDP fe80::ac8f:354b:2b7d:1e32 ff02::1:3 53496 5355 0 - - - - - - - SEND
2018-09-21 06:02:38 ALLOW UDP 192.168.x.x 224.0.0.252 53496 5355 0 - - - - - - - SEND
2018-09-21 06:02:38 ALLOW UDP fe80::ac8f:354b:2b7d:1e32 ff02::1:3 64275 5355 0 - - - - - - - SEND
2018-09-21 06:02:38 ALLOW UDP 192.168.x.x 224.0.0.252 64275 5355 0 - - - - - - - SEND
2018-09-21 06:02:39 ALLOW TCP 192.168.x.x 192.x.x.x 52206 80 0 - 0 0 0 - - - SEND
2018-09-21 06:02:39 ALLOW TCP 192.168.x.x 192.x.x.x 52207 80 0 - 0 0 0 - - - SEND
2018-09-21 06:02:39 DROP ICMP fe80::74d6:5ff:fee6:9975 ff02::1 - - 80 - - - - 130 0 - RECEIVE
2018-09-21 06:02:40 ALLOW TCP 192.168.x.x 162.125.82.3 52208 443 0 - 0 0 0 - - - SEND
2018-09-21 06:02:41 ALLOW UDP 192.168.x.x 239.255.255.250 64276 1900 0 - - - - - - - SEND
2018-09-21 06:02:41 ALLOW UDP fe80::ac8f:354b:2b7d:1e32 ff02::1:3 53979 5355 0 - - - - - - - SEND
2018-09-21 06:02:41 ALLOW UDP 192.168.x.x 224.0.0.252 53979 5355 0 - - - - - - - SEND
2018-09-21 06:02:41 ALLOW UDP fe80::ac8f:354b:2b7d:1e32 ff02::1:3 59708 5355 0 - - - - - - - SEND
2018-09-21 06:02:41 ALLOW UDP 192.168.x.x 224.0.0.252 59708 5355 0 - - - - - - - SEND
2018-09-21 06:02:41 ALLOW UDP fe80::ac8f:354b:2b7d:1e32 ff02::1:3 53700 5355 0 - - - - - - - SEND
2018-09-21 06:02:41 ALLOW UDP 192.168.x.x 224.0.0.252 53700 5355 0 - - - - - - - SEND
2018-09-21 06:02:42 ALLOW UDP fe80::ac8f:354b:2b7d:1e32 ff02::1:3 63481 5355 0 - - - - - - - SEND
2018-09-21 06:02:42 ALLOW UDP fe80::ac8f:354b:2b7d:1e32 ff02::1:3 59837 5355 0 - - - - - - - SEND
2018-09-21 06:02:42 ALLOW UDP fe80::ac8f:354b:2b7d:1e32 ff02::1:3 53603 5355 0 - - - - - - - SEND
2018-09-21 06:02:42 ALLOW UDP 192.168.x.x 224.0.0.252 63481 5355 0 - - - - - - - SEND
2018-09-21 06:02:42 ALLOW UDP 192.168.x.x 224.0.0.252 59837 5355 0 - - - - - - - SEND
2018-09-21 06:02:42 ALLOW UDP 192.168.x.x 224.0.0.252 53603 5355 0 - - - - - - - SEND
2018-09-21 06:02:42 ALLOW UDP 192.168.x.x 216.58.205.36 53702 443 0 - - - - - - - SEND
2018-09-21 06:02:42 ALLOW TCP 192.168.x.x 192.x.x.x 52209 80 0 - 0 0 0 - - - SEND
2018-09-21 06:02:44 ALLOW TCP 192.168.x.x 192.x.x.x 52210 80 0 - 0 0 0 - - - SEND
2018-09-21 06:02:44 ALLOW ICMP fe80::20a0:2fa0:4947:a26c ff02::16 - - 0 - - - - 143 0 - SEND
2018-09-21 06:02:44 ALLOW UDP 192.168.x.x 224.0.0.251 5353 5353 0 - - - - - - - SEND
2018-09-21 06:02:44 ALLOW UDP 192.168.x.x 224.0.0.251 5353 5353 0 - - - - - - - SEND
2018-09-21 06:02:44 ALLOW UDP fe80::ac8f:354b:2b7d:1e32 ff02::fb 5353 5353 0 - - - - - - - SEND
2018-09-21 06:02:44 ALLOW UDP fe80::20a0:2fa0:4947:a26c ff02::fb 5353 5353 0 - - - - - - - SEND
2018-09-21 06:02:44 ALLOW UDP fe80::ac8f:354b:2b7d:1e32 ff02::fb 5353 5353 0 - - - - - - - SEND
2018-09-21 06:02:46 ALLOW TCP 192.168.x.x 192.x.x.x 52211 80 0 - 0 0 0 - - - SEND
2018-09-21 06:02:48 ALLOW TCP 192.168.x.x 192.x.x.x 52212 80 0 - 0 0 0 - - - SEND

david551 · September 21, 2018, 9:13am

I see nothing obviously Asterisk related here. There are no standard SIP port numbers, assuming I’ve correctly reverse engineered the unknown log format.

Protocol 2 is IGMP, used for multicast routing control.

I can’t work out which, if any, field gives the ICMP sub-type.

Normally people would provide the results of decoding by tcpdump or wireshark.

Dawson5924 · September 21, 2018, 10:29am

Thanks for your help @david551. Wireshark is showing the following details:

Dawson5924 · September 21, 2018, 12:22pm

This file is wire shark dump for 43sec in which i placed a call which hanged up automatically.

https://mail.google.com/mail/u/1?ui=2&ik=7ee810d339&attid=0.1&permmsgid=msg-a:r8007940008088390213&view=att&disp=safe&realattid=f_jmbx1pku0

Dawson5924 · September 21, 2018, 7:53pm

Can anyone please tell me the problem in the data posted above, which i missed and now it is stopping my call transmission?

Dawson5924 · September 21, 2018, 8:07pm

@david551 Can you do this? Please i got no way out