similar to: X100P check for Dialtone

Does anyone know if there is a zapata.conf option to tell * to listen for a dialtone before dialing? I've got a couple of analog phones on a pstn line shared with a x100p * fx line. If someone is on the analog phone and another person initiates a call through * to use the same line, * dials over the top of the existing conversation. Is there a way to have * detect dialtone before dialing?

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first

On 2007 Jul 26 (Thu) at 09:32:00 -0400 (-0400), Jared Smith wrote: :On Wed, 2007-07-25 at 15:06 -0700, Peter Hessler wrote: :> ;; dialtone in the background isn't there any more :> ;; dialed '305' :> ;; everything from here is exactly as expected. : :OK, I missed this in the first email you sent... Asterisk is playing :dialtone *on top* of the background message the first

Hi A quicky - has anyone had success with an X100P in the UK ? I'm seeing some oddness - when I plug the wall socket into the card, I lose dialtone. If I unplug it, it comes back. Does this sound familiar to anyone ? Cheers Nigel Nigel Taylor Technology Director ITAzure Limited Dunn House Warren Park Way Enderby Leicestershire LE19 4SA 0116 286 3016

I have some strange behavior happening with call flow when analog line errors are encountered. This may be due to the way that the X100P detects "busy" signals, or it may be something in the software. Could someone with more in-depth knowledge make a comment on the items below? My dialing logic says "dial local area code numbers out of the analog line, and if the analog line

I'm in the process of setting up a 'phone tree', and are running into some problems. My goal is for users to dial a phone number, the asterisk system picks it up, plays the greeting, and users can type whatever they want into the system. What actually happens is users dial the phone number, asterisk picks up and additionally goes off-hook on another line, plays the greeting and

I just set up a Polycom 500 on *. Every few calls I make, the call connects and the receiving party can hear me (thru Broadvoice), but I still get ringing on my end, as if they never picked up. * logs look just fine. Does any one have any suggestions? Thanks. ________________________________ Adam S. Robins Executive Vice President & CIO PHARMACENTRA, LLP 5901B Peachtree Dunwoody

Hi Jared, I've seen the same while testing on digital ocean, I think it's the context switching that happens when sending a packet. I've done some testing with wireguard and that has a lot better performance but it's still changing quite a lot and only does a subset of what tinc does so probably not a stable solution. Martin On Wed, 17 May 2017 at 18:05 Jared Ledvina <jared at

With Puppet 2.7.20, it seems that when I write file { ''/tmp/bla'': owner => [''root'', ''jared''] } then if the owner of /tmp/bla is either root or jared, nothing happens, and if not, the owner is changed to root. More generically speaking, my reading of the code suggests that if the owner of the file is in the given list (the

I purchased the Samba 3.0 book and it has gotten me pretty far but I finally had to go to the mailing list for this problem. Here is the issue, I am running Debian (woody) with samba 3.0.1-2 and cupsys 1.1.14-5 I have also installed cupsys-bsd cupsys-client and smbclient foomatic-bin and as2ps follwing this http://excess.org/docs/linux_windows_printing.html advice. Samba is running in Domain mode