Page 1 of 1

request timed out

PostPosted: Thu Jan 24, 2013 12:05 am
by raju
HI Friends,


i am facing a problem with outbound and inbound calling. when ever we make outbound call at the time we are getting this warnings.

WARNING[3869]: chan_sip.c:3779 retrans_pkt: Maximum retries exceeded on transmission 6b9fe1d7200a6a98776ef46e6c2039a0@x.x.x.x for seqno 102 (Critical Request) -- See doc/sip-retransmit.txt.
[Jan 24 10:30:54]
WARNING[3869]: chan_sip.c:3806 retrans_pkt: Hanging up call 6b9fe1d7200a6a98776ef46e6c2039a0@x.x.x.x - no reply to our critical packet (see doc/sip-retransmit.txt).
== Everyone is busy/congested at this time (1:0/0/1)

please help me where is the problem.

Thanks
Raju

Re: request timed out

PostPosted: Thu Jan 24, 2013 4:55 am
by DomeDan
I googled "Maximum retries exceeded on transmission" and found this: http://wiki.kolmisoft.com/index.php/Max ... ansmission
Asterisk under NAT

In CLI also visible: No reply to our critical packet
WARNING[25126]: chan_sip.c:2057 retrans_pkt: Maximum retries exceeded on transmission 2c051da44ee93e675cbef8932367e41a@209.216.2.xxx for seqno 102 (Critical Response) -- See doc/sip-retransmit.txt.
[2011-08-10 09:45:16] WARNING[25126]: chan_sip.c:2079 retrans_pkt: Hanging up call 2c051da44ee93e675cbef8932367e41a@209.216.2.xxx - no reply to our critical packet (see doc/sip-retransmit.txt).
It is possible that Asterisk is under NAT and not properly configured.
Solution: Asterisk under NAT
If it does not help - change your router.


maybe you've done some changes to the router recently?
and also, post your system info, install method, iso version, vicidial build etc
you should also explain your network setup in this case

Re: request timed out

PostPosted: Fri Feb 01, 2013 8:13 pm
by williamconley
1) raju, you've been here a while and I'm sure you already know this but were in a hurry (down system!) right? Still these help us to help you as well as helping the "next guy" find this thread which may help him ... so here they are:

when you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.

this IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

2) You have described a classic firewall issue. Your server is sending packets out but not receiving them back. This can happen because a firewall is blocking the return packets.

3) However, it can also happen if the sip.conf file setting for "externip=" is not set but is required. This should be set to the external IP address of your system if you have a private network. An asterisk reload is necessary after this setting is changed (reload in the asterisk cli).