similar to: Dealing with muti-body INVITE

Hi I am running following asterisk installed with apt on Debian 7.1. dpkg -l |grep asterisk ii asterisk 1:1.8.13.1~dfsg-3+deb7u1 amd64 Open Source Private Branch Exchange (PBX) ii asterisk-config 1:1.8.13.1~dfsg-3+deb7u1 all Configuration files for Asterisk ii asterisk-core-sounds-en-gsm 1.4.22-1 all asterisk PBX

I couldn''t find the answer in previous posts (hope I didn''t miss it). I have a muti-layer deployment process in which a given deployment depends on previous deployments. How can I know when the fist deployment is finished so I can carry on to the next one? How can I know what is the success rate (assuming multiple nodes deployments)? For example if I want to deploy a web

Dear All, I have installed 4 asterisks on the same Centos machine..>Each Asterisk has its own installation folder and use its own libraries...Everything looks great and all asterisks are doing their jobs correctly except one thing...I faced a voice quality issue...On a specific time, and after the number of calls begin increasing, the voice quality will begin degradation... Could it be a

Hi, Sorry i did't confirm the results sooner. Yes, it's working fine without issues for me. If anyone else can confirm so we can be sure it's 100% resolved. -- Respectfully Mahdi A. Mahdi ________________________________ From: Krutika Dhananjay <kdhananj at redhat.com> Sent: Tuesday, June 6, 2017 9:17:40 AM To: Mahdi Adnan Cc: gluster-user; Gandalf Corvotempesta; Lindsay

Any additional tests would be great as a similiar bug was detected and fixed some months ago and after that, this bug arose?. Is still unclear to me why two very similiar bug was discovered in two different times for the same operation How this is possible? If you fixed the first bug, why the second one wasn't triggered on your test environment? Il 6 giu 2017 10:35 AM, "Mahdi

I?m receiving the following error(s) messages when trying reloading dovecot (Debian wheezy). doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 73: Unknown setting: socket doveconf: Error: managesieve-login: dump-capability process returned 89 Configuration file /etc/dovecot/dovecot.conf : # If you only want to use dovecot-auth, you can set this to "none".

hello *'s, Astcc not workin what is correct format for defining 1-database 2-brands 3-trunks 4-routes i define all these things but not workin may be i define in wrong format.I have FXO card installed.can anyone implement it and also my sip phone generates very loud noise wat is that i tried several settings but not hear any voice just noise. sip.conf [general] context=from-sip port=5060

OK. Is this problem unique to templates for a particular guest OS type? Or is this something you see for all guest OS? Also, can you get the output of `getfattr -d -m . -e hex <path>` for the following two "paths" from all of the bricks: path to the file representing the vm created off this template wrt the brick. It will usually be $BRICKPATH/xxxx....xx/images/$UUID where $UUID

Great, thanks! Il 5 giu 2017 6:49 AM, "Krutika Dhananjay" <kdhananj at redhat.com> ha scritto: > The fixes are already available in 3.10.2, 3.8.12 and 3.11.0 > > -Krutika > > On Sun, Jun 4, 2017 at 5:30 PM, Gandalf Corvotempesta < > gandalf.corvotempesta at gmail.com> wrote: > >> Great news. >> Is this planned to be published in next

The fixes are already available in 3.10.2, 3.8.12 and 3.11.0 -Krutika On Sun, Jun 4, 2017 at 5:30 PM, Gandalf Corvotempesta < gandalf.corvotempesta at gmail.com> wrote: > Great news. > Is this planned to be published in next release? > > Il 29 mag 2017 3:27 PM, "Krutika Dhananjay" <kdhananj at redhat.com> ha > scritto: > >> Thanks for that update.

On about 25% of inbound calls to a ring group, picking up any one extension as it rings results in dead air. Some details regarding my VoIP network to make the following logs more readable: 192.168.7.130 resolves to the trixbox host. 192.168.7.135 resolves to endpoint 812. 192.168.7.137 resolves to endpoint 811. 192.168.7.138 resolves to endpoint 810. 192.168.7.139 resolves to endpoint 813.

After a few days, one of my DomU becomes unresponsive. Here''s the output of my DomU''s. root@xenII:/var/log/xen# xl list Name ID Mem VCPUs State Time(s) Domain-0 0 7126 2 r----- 723932.0 redhat-sdsweb 11 4091 2 -b---- 92633.1 w2k8-AD

On Mon, 2014-04-21 at 15:43 +0200, Sjors Gielen wrote: > Package: xen-utils-4.1 > Version: 4.1.4-3+deb7u1 > Severity: important > > When an LVM LV that serves as the root disk for a Xen DomU contains a boot > loader (or possibly other data) in its volume boot record, pygrub fails to boot > it, printing "Error: boot loader didn't return any data" before exiting.

Hi Mahdi, Did you get a chance to verify this fix again? If this fix works for you, is it OK if we move this bug to CLOSED state and revert the rebalance-cli warning patch? -Krutika On Mon, May 29, 2017 at 6:51 PM, Mahdi Adnan <mahdi.adnan at outlook.com> wrote: > Hello, > > > Yes, i forgot to upgrade the client as well. > > I did the upgrade and created a new volume,

> > >On Thu, 2003-11-13 at 16:50, Freddi Hansen wrote: > > >>>> >Freddi Hansen wrote: >>> >>> >>>>> >> with boards from Aculab, we are replacing Aculab boards with Digium >>>>> >> boards BUT we would need more >>>>> >> Digium boards IF we could use both Digium and Aculab cards in

Hello *'s, Every time I started my asterisk error shows: chan_sip.c:Got 200 ok onRegister that isn't a register. Failed to authenticate in Register to <sip:adnan.007@iptel.org>;tag=asfeaa71f Maximum retries exceeded on call xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx@192.168.10.189 for seqno 107 (Request) Registration for adnan.007@195.37.77.99 timed out ,trying again.

Great news. Is this planned to be published in next release? Il 29 mag 2017 3:27 PM, "Krutika Dhananjay" <kdhananj at redhat.com> ha scritto: > Thanks for that update. Very happy to hear it ran fine without any issues. > :) > > Yeah so you can ignore those 'No such file or directory' errors. They > represent a transient state where DHT in the client process

All, I am trying to find a SIP ITSP that honors dial around compensation. We are adding a Flex ANI code to our outgoing SIP invites by appending an isup-oli tag to our From: address, like this: INVITE sip:18889996563@carriers.icall.net SIP/2.0 Via: SIP/2.0/UDP xxx.y.34.201:5060;branch=z9hG4bK7f314484;rport From: "Dougs Payphone"

>Freddi Hansen wrote: >> with boards from Aculab, we are replacing Aculab boards with Digium >> boards BUT we would need more >> Digium boards IF we could use both Digium and Aculab cards in the same >> server. The reason being that >> TE410P doesn't support SS7-ISUP so we continue using only Aculab cards >> in the servers that must support >>

Package: xen-utils-4.1 Version: 4.1.4-3+deb7u1 Severity: important When an LVM LV that serves as the root disk for a Xen DomU contains a boot loader (or possibly other data) in its volume boot record, pygrub fails to boot it, printing "Error: boot loader didn't return any data" before exiting. I think this is because of the function "is_disk_image" on line 45 of