similar to: 1.6.0.10: server locks up on iax max_retries

I have a 100MB internal lan. aastra's are wired. asterisk box is wired next to the switch. But look: sip show peers ........ 142/142 10.10.10.42 D A 5060 OK (137 ms) 144/144 10.10.10.44 D A 5060 OK (136 ms) 145/145 10.10.10.45 D A 5060 OK (168 ms) 150/150 10.10.10.50

From: https://wiki.asterisk.org/wiki/display/AST/Asterisk+16+Configuration_res_pjsip_outbound_registration#Asterisk16Configuration_res_pjsip_outbound_registration-registration_max_retries max_retries This sets the maximum number of registration attempts that are made before stopping any further attempts.* If set to 0 then upon failure no further attempts are made.* Regards, IanG On

Package: xcp-xapi Version: 1.3-15 Severity: wishlist The current initscript has the possibility of slowing down the boot process by 50 seconds. If this is required, it probably should be backgrounded. # Wait for xapi to write its "init complete" cookie: after here it's safe to modify templates. wait_for_xapi() { MAX_RETRIES=50 RETRY=0 while [ ${RETRY} -lt ${MAX_RETRIES}

Le 28/02/2020 à 23:43, hw a écrit : > On Thursday, February 27, 2020 3:03:47 PM CET hw wrote: >> Hi, >> >> sometimes 'pjsip show registrations' shows registrations to the VOIP >> provider as Rejected. I have already added >> >> >> max_retries = 0 >> auth_rejection_permanent = no >> >> >> in pjsip_wizard.conf and still

Hi, sometimes 'pjsip show registrations' shows registrations to the VOIP provider as Rejected. I have already added max_retries = 0 auth_rejection_permanent = no in pjsip_wizard.conf and still asterisk does not recover. I need asterisk to keep trying to register and to renew the registration without requiring manual intervention. How can I make asterisk do that?

I''ve been digging through the various manuals and am a bit irritated with limitation on the rules system Why do I have to specify a source zone to allow a source IP range on all zones? There is no iptables requirement for anything more than a source address, so I don''t understand why all:<ip> does not just add an accept rule into the head of the INPUT chain or even simply

While troubleshooting my MultiISP box, I suspect I might have found either a bug or an incompatibility with CentOS 5.2. In prog.header (function detect_dynamic_gateway), Shorewall tries to look for: /var/lib/dhcp/dhclient-${1}.lease However (at least under CentOS 5 - unknown about other OSes), this should be: /var/lib/dhclient/dhclient-${1}.leases (different path, and "leases"

Guys, i know i saw this somewhere but i cant seem to locate that info now... Scenario: ............... I have a simple two interface firewall. The firewall machine also provides some services to the LAN and to the NET. What i would like to do is allow only a particular range of IPs frm the internet to access those services. What do i need to do with my ''rules'' file. Ideally

Hi list. I have a specific document that does not handle updates sitting in the index. What can I do about that? 2010-01-30T13:58:07 Eval failure: Exception: No termlist for document 287376 at /usr/lib/perl5/Search/Xapian/Enquire.pm line 56. 2010-01-30T13:58:07 job failed. considering retry. is max_retries of 1000 >= failures of 1? 2010-01-30T13:58:07 job failed: Exception: No

On Saturday, April 18, 2020 5:42:11 PM CEST Joshua C. Colp wrote: > On Sat, Apr 18, 2020 at 8:47 AM hw <hw at gc-24.de> wrote: > > Hi, > > > > how do I make a bug report? I filled in the form to make a report and > > https://issues.asterisk.org/jira/issues/?filter=-2 still shows no issues > > reported by me. > > If successful then JIRA will redirect

Hi list, I''m struggling with this problem for a long time, hopefully someone can explain me what I''m doing wrong: I have a shorewall installation with interfaces net eth0 - eth1 hosts loc 10.0.10.0/24 loc 10.0.20.0/24 +some other zones and subnets there are aliases on eth1 for gateways for the two loc subnets eth1:1 10.0.10.1 eth1:2 10.0.20.1 Everything works fine, loc

Hi everyone! First of all, sorry about my bad English and the e-mails extension. I need some help to implement a VPN connection using shorewall and openswan as IPSec Tunnel. My network map: CLIENT VPN APPLIANCE --> +++INTERNET+++ --> FIREWALL --> OPENSWAN SERVER (DMZ) I have two VPN connections with two different subnets to the other end. The two of then are correctly established.

Hi There, Due to shortage computer, I need to install Apache to my Shorewall box (192.168.1.1) But the real web server is on another box (192.168.1.2) I tried to put rule: DNAT net loc:192.168.168.1 tcp 80 But everytime www connection coming in, it will hit my shorewall Any solution? Cheer Access Yahoo!7 Mail on your mobile. Anytime. Anywhere. Show me how:

I think we discussed this in the past and I floated a hack at the time, but I don''t recall any real resolution. I want to see if time has solved my problem or if it still exists. My scenario is that I have two ISPs, one of which uses DHCP. Because I have two ISPs, history has shown that allowing the provisioning script for the interface to plumb a default route is troublesome and

Hello, We have a provider which is using Kamailio as front end. Our asterisk 13/chan_sip server has no problem to register and pass/receive calls form this provider. Now we want to move to asterisk 16/pjsip and face problem. Registration is OK but when we pass a call our INVITE never receive answer from the provider. We opened a ticket to their support but in the mean time we want to know

Package: xcp-xapi Version: 1.3.2-8 Severity: important Tags: patch Found race condition (specific only to slave hosts): xcp-xapi can start earlier than xcp-networkd due lack of dependency in init.d script. Syptoms: After reboot slave's xcp does not work: xe (anything): The host failed to acquire an IP address on its management interface and therefore cannot contact the master. log:

The Shorewall team is pleased to announce the availability of Shorewall 4.2.10. Astute users will notice that the version of Shorewall-perl included in this release is 4.2.10.1. We corrected a problem which was discovered after the release was initially uploaded, and we wanted to avoid the confusion that would inevitabley result if we were to release a different set of code with the same version

Package: xcp-xapi Version: 1.3.2-8 Severity: important During startup /etc/init.d/xendomains script is called. That script is installed with xen-utils-common witch xcp-xapi is depends on. That script calls /usr/sbin/xen as xen list &> /dev/null This 'xen' seems to call xapi: xen list ^Z [1]+ Stopped xen list root at lab-xh3:~# ps f PID TTY STAT TIME

Package: xcp-xapi Version: 1.3.2-9 Severity: normal Function wait_for_xapi in /etc/init.d/xcp-xapi does not work as intented. Symptoms: (on slave) /etc/init.d/xcp-xapi restart [....] Restarting The XenAPI server: xapiThe host toolstack is still initialising. Please wait. Cause: Line 'xe pif-scan host-uuid=${INSTALLATION_UUID}' called before xapi is fully synced with master.

On Thursday, February 27, 2020 3:03:47 PM CET hw wrote: > Hi, > > sometimes 'pjsip show registrations' shows registrations to the VOIP > provider as Rejected. I have already added > > > max_retries = 0 > auth_rejection_permanent = no > > > in pjsip_wizard.conf and still asterisk does not recover. > > I need asterisk to keep trying to register