similar to: Retransmission

Hi Guys Given these occassional errors on my Asterisk CLI: [Jul 2 10:23:36] WARNING[2060]: chan_sip.c:3641 retrans_pkt: Retransmission timeout reached on transmission 17bb3a993ad10f8818970ae952b81e73 at 192.168.11.31:5060 for seqno 102 (Critical Request) -- See https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions Packet timed out after 32000ms with no response [Jul 2 10:23:49]

Hello everyone, I've suffering cut offs after 6 or 7 seconds a call is answered, incoming calls are working fine, but outgoing ones show the gollowing messages when are being dropped: [2013-05-15 12:55:14] WARNING[3569]: chan_sip.c:3641 retrans_pkt: Retransmission timeout reached on transmission ZjJkZjlkZWMyZTE4ZmY2NWZlZTExNDM1MDRhMTY4MTc. for seqno 2 (Critical Response) -- See

This seems basic but something is missing..... I dial from my cell phone to my DID and enter the context in extensions.conf I am hoping to cascade through the plan and successfully automatically dial the 1444 number listed. But it fails. And, I dpon't know why? Should I removed the Hangup application? Syntax issue somewhere? I have a good SIP registration with the vendor, voipvoip.

On 12/30/2017 08:18 PM, Dovid Bender wrote: > Script kiddies trying to find vulnerable systems that they can make > calls on. Lock down the box with iptables and use fail2ban to block > them. The via is probably bogus unless a box at the DoD was comprimised. > > > > On Sat, Dec 30, 2017 at 6:49 PM, sean darcy <seandarcy2 at gmail.com > <mailto:seandarcy2 at

I've been getting a lot of timeouts on non-critical invite transactions. I turned on sip debug. They were the result of SIP invites like this: Retransmitting #10 (NAT) to 185.107.94.10:13057: SIP/2.0 401 Unauthorized Via: SIP/2.0/UDP 215.45.145.211:5060;branch=z9hG4bK-524287-1---zg4cfkl50hpwpv4p;received=185.107.94.10;rport=13057 From:

Hello, I recently upgraded from Asterisk 1.8 to Asterisk 13. Now users are starting to complaint about packets loss, conversations are choppy! I don't even know where to start looking! Choppy conversations happened within users. I am using sip.conf [1091] type=friend context=sip-phone call-limit=2 trustrpid=no callerid="dev1" <1091> disallow=all allow=ulaw

Hello, I am trying to make my first call on Asterisk to succeed. I have Asterisk 1.8.10.1 running on Ubuntu machine.The configuration is quite simple just for my first test, Trying to have a call between two X-lite sipphone. The subscribers succeeded to register and the call is established, but still no voice can be heard, and lead the call to be disconnected after! By checking the logs, I can see

On Wed, Jan 25, 2017 at 16:00 Olivier <oza.4h07 at gmail.com> wrote: > What did you exactly upgade ? Asterisk only ? Asterisk and OS ? > How did you installed Asterisk 1.8 and 13 ? From source or from package ? > > I would be curious to see what would happen after downgrading back to 1.8. > > 2017-01-24 21:03 GMT+01:00 Motty Cruz <motty.cruz at gmail.com>: > >

Hello friends: I am facing cutoffs randomly when negotiating calls. The PBX dials the destination, the provider (softswitch) receives the request *[1]* and sudenly the PBX hangs up the call* [2]* while the provider is still dialing it, as a consequence the remote peer receives a ghost call. Along the atempt I could see six times a messages regarding NAT isuues *[3]* I hope anyone can give me an

Hello folks, since I started with asterisk 1.8.2 I got this messages in my console when finish a call. -- Executing [1610 at from-e1:1] Dial("SIP/xxx-00000027", "SIP/1610,60") in new stack == Using SIP RTP CoS mark 5 -- Called 1610 -- SIP/1610-00000028 is ringing -- SIP/1610-00000028 answered SIP/xxx-00000027 -- Locally bridging SIP/xxx-00000027 and

> Very strange... > I ran the Asterisk CLI for other tasks, and suddenly I got this message: > > == Using SIP RTP CoS mark 5 > -- Executing [000972592603325 at default:1] Verbose("SIP/192.168. > 20.120-0000002a", "2,PROXY Call from 0123456 to 000972592603325") innew stack > == PROXY Call from 0123456 to 000972592603325 > -- Executing

For such cases i created a dialplan in the default dialplan which blocks the ip of the hacker with iptables. On Monday, June 8, 2015, Luca Bertoncello <lucabert at lucabert.de> wrote: > Hi list! > > Very strange... > I ran the Asterisk CLI for other tasks, and suddenly I got this message: > > == Using SIP RTP CoS mark 5 > -- Executing [000972592603325 at

I'm guessing this is a small/home system? I suggest you install SecAst from this site: www.telium.ca It's free for small office / home office and will deal with these types of attacks and more. It can also block users based on their Geographic location (based on the phone number it attempted to dial I suspect this is middle east), look for suspicious dialing patterns, etc. If you

Hello, I have a strange situation with my asterisk 1.8.7.0 version. I compiled as usual everything seems to be ok but from time to time when i look on my console i get the following error message: [Oct 11 14:44:52] WARNING[17646]: chan_sip.c:2754 _sip_tcp_helper_thread: Failure to write to tcp/tls socket [Oct 11 14:44:52] WARNING[17646]: chan_sip.c:2754 _sip_tcp_helper_thread: Failure to write

What is the problem with SIP retransmits? ----------------------------------------- Sometimes you get messages in the console like these: - "retrans_pkt: Hanging up call XX77yy - no reply to our critical packet." - "retrans_pkt: Cancelling retransmit of OPTIONs" The SIP protocol is based on requests and replies. Both sides send requests and wait for replies.

Hi list! Very strange... I ran the Asterisk CLI for other tasks, and suddenly I got this message: == Using SIP RTP CoS mark 5 -- Executing [000972592603325 at default:1] Verbose("SIP/192.168.20.120-0000002a", "2,PROXY Call from 0123456 to 000972592603325") in new stack == PROXY Call from 0123456 to 000972592603325 -- Executing [000972592603325 at default:2]

Hello, CentOS 6.x and Asterisk 11.x I have an interesting, to me at least, situation. Using a Polycom 501(also tried with X-Lite). I have set up Asterisk to accept registration from the Polycom and it registers successfully but then withing 30 seconds on the CLI I get the message that the Polycom is unreachable. The phone still shows that it is registered and if I try to place a call from the

Hi all I've been trying to make * work with IAXtel to no avail, all seems ok in the config but am not getting anywhere This is what I'm getting from console (user/pass/dest # changed for obvious reasons): DEBUG[1133735216]: File chan_sip.c, Line 3841 (check_user): Setting NAT on RTP to 0 DEBUG[1133735216]: File chan_sip.c, Line 4891 (handle_request): Check for res for phone1

Is there a way to increase the number of retries or the time to help with this? WARNING[40966]: File chan_sip.c, Line 462 (retrans_pkt): Maximum retries exceeded on call 0ea2761d6a82fa49221f547c739bde18@192.168.0.200 for seqno 103 (Request) WARNING[40966]: File chan_sip.c, Line 462 (retrans_pkt): Maximum retries exceeded on call 0ea2761d6a82fa49221f547c739bde18@192.168.0.200 for seqno 103

Hi, How would I go about troubleshooting this: [Dec 24 07:15:11] WARNING[5228]: chan_sip.c:3397 retrans_pkt: Maximum retries exceeded on transmission a50346a4-bfdc32ed at 192.168.1.95 for seqno 101 (Critical Response) -- See doc/sip-retransmit.txt. [Dec 24 07:15:12] WARNING[5228]: chan_sip.c:3397 retrans_pkt: Maximum retries exceeded on transmission 90bd2c4d-aaaec88 at 192.168.1.95 for seqno 101