similar to: Extract user part from SIP URI

Hi there, I am configuring a small voicemail server and I am facing the following problem. Executing this command: exten => 1234,1,VoiceMail(${NUMBER}@test) When a user does not have a customized temporary greeting vm-intro message is played asking for the message to the user but when the user has already a temporary greeting both the temporary greeting and vm-intro are played. Basically

Hi there, I have been taking a look on how to configure voicemail systems with asterisk and I would like to know if there's any way to define mailbox in a dynamic way. I have 100 users and I would like to know if there's any way to avoid the definition of the 100 mailboxes in voicemail.conf and use for example the variables that I am getting from extensions.conf. Thanks in advance,

I can't seem to get the "r" modifier to work on inbound SIP calls. The way I understood this to work is that the channel would be answered, and a ring "tone" would be played to the channel. This is not very friendly in that it doesn't honor connection supervision rules, but... who cares? There are some instances where it may be in my interests to get a

Hi, In data giovedì 25 giugno 2015 18:44:50, Gabriel Hartmann ha scritto: > I have written a patch (please see attached) which fixes both of these bugs: > > https://bugzilla.redhat.com/show_bug.cgi?id=1092583 > https://bugzilla.redhat.com/show_bug.cgi?id=1232477 > > By default, when saving a URI using xmlSaveUri it escapes everything in the > URI. QEMU doesn't want

hello. This code is abort with Mechanize 0.6.4 . ---------------------------- # sample.rb require "rubygems" require "mechanize" agent = WWW::Mechanize.new agent.user_agent_alias=''Windows Mozilla'' # top page of wikipedia for japanese agent.get("http://ja.wikipedia.org/wiki/%E3%83%A1%E3%82%A4%E3%83%B3%E3%83%9A%E3%83%BC%E3%82%B8")

I'm trying to set a dialing rule in my dialplan. As a part of it, from my point of view, this works wrong priorityjumping=no [test_context] exten => 1234,1,Dial(SIP/test,15,G(text_context,1234,2),j) ; With "j" flag exten => 1234,2,Playback(digits/2) exten => 1234,3,Playback(digits/3) exten => 1234,102,Playback(digits/4) In this case, if I dial the extension, and

URI.escape() is supposed to be able to take a second parameter listing unsafe characters in the URI. This may be a regexp or string. If a string, it''s supposed to represent a character set listing all unsafe characters. An example given in the core documentation at: http://www.ruby-doc.org/stdlib/libdoc/uri/rdoc/classes/URI/Escape.html#M008992 ...is: p URI.escape("@?@!",

From: "Richard W.M. Jones" <rjones@redhat.com> NULL means that libvirt gets to guess what connection URI we meant. Currently it guesses qemu:///session for non-root and qemu:///system for root. Except if LIBVIRT_DEFAULT_URI is set in which case this is used even if it's not appropriate. Except if Xen is installed in which case it guesses xen:/// which is not helpful at all.

Hello, I''m getting an URI::InvalidURIError in my controller when I use german characters in the uri. Google accepts them but open-uri not. How to encode them? That''s my controller simplified: def index require ''open-uri'' address = "Bürgerstraße+68+01127+Dresden" api_key = "my api key" json =

The existing --run '$nbd' outputs an older form that differs between libguestfs and qemu, and which is not always a valid URI. For historical compatibility, we probably can't change that; but we can instead add a new '$uri' that outputs a valid URI. Note that the libguestfs '$nbd' TCP form is already a valid URI (at least, as long as the user isn't exploiting

On Tue, Jun 25, 2019 at 09:35:11PM -0500, Eric Blake wrote: > The existing --run '$nbd' outputs an older form that differs between > libguestfs and qemu, and which is not always a valid URI. For > historical compatibility, we probably can't change that; but we can > instead add a new '$uri' that outputs a valid URI. Note that the > libguestfs '$nbd' TCP

I'm running 1.2.9.1, and I can't get caller id dialplan matching to work. When calling from 9220370 to 1234, the following does not match. exten => 9220370/1234,1,NoOp(${CALLERIDNUM}) exten => 9220370/1234,2,Answer exten => 9220370/1234,3,Playback(tt-weasels) However, when calling from 9220370 to 1234, this DOES match. exten => 1234,1,NoOp(${CALLERIDNUM}) exten =>

Hi, Is the dev_state can also be used to track a mobile phone's status via SIP? I tried it on several phones(nokia, samsung) but it returns NOANSWER but i can hear a beep beep beep sound indicating that it is currently busy. regards, RYAN ICASIANO

On Tue, Jun 25, 2019 at 09:09:58PM -0500, Eric Blake wrote: >I'm not sure whether we want to go with just the first patch (reject >nbd:unix:/path but still accept nbd:/path), or squash the two in order >to go with the second (reject both abbreviated forms, and require >scheme://...). Either way, though, nbdkit -U - --run '$nbd' will now >error out rather than

Hi all, I''m playing around with mongrel handlers and I came across a behaviour that seems abnormal to me with regard to the Configurator#uri calls. It appears that order matters. For instance: ... listener do uri "/icons", :handler => DirHandler.new("/var/www/icons") uri "/", :handler =>

Typing nbdsh --con (the minimum to get an unambiguous prefix for --connect, different from --command) is annoying compared to having a short option. Since it takes a URI as an argument, using -u/--uri is a nicer mnemonic. We still accept --connect for back-compat, and document it in the man page, but omit it from --help as the new spelling is nicer all around. --- Here's what things evolved

I am trying to open a URI using doc = Nokogiri::HTML(open(url)). I get the following error: URI::InvalidURIError: bad URI(is not URI?): http://www.mauipropertytax.com/Datalets.asp?mnu=PSearch&submnu=Profile&pin=390350950000&tp=2&cp=1&State=1|1|*&item=1 from /usr/local/ruby/lib/ruby/1.8/uri/common.rb:436:in `split'' from

(apologies if you see this twice, forgot the CC the first time) In data venerdì 26 giugno 2015 18:50:16, Gabriel Hartmann ha scritto: > > > > > By default, when saving a URI using xmlSaveUri it escapes everything in > > the URI. QEMU doesn't want anything escaped, so now I unescape > > everything after the URI is generated. Unfortunately there's no flag to

Previously, the examples fetch-first-sector and get-size in rust/examples only accepted a unix socket as argument. This commit makes it possible to provide a URI as well. --- rust/examples/fetch-first-sector.rs | 15 +++++++++++---- rust/examples/get-size.rs | 20 +++++++++++++++----- 2 files changed, 26 insertions(+), 9 deletions(-) diff --git a/rust/examples/fetch-first-sector.rs

On Thu, Jun 25, 2015 at 06:44:50PM +0000, Gabriel Hartmann wrote: > I have written a patch (please see attached) which fixes both of these bugs: > > https://bugzilla.redhat.com/show_bug.cgi?id=1092583 > https://bugzilla.redhat.com/show_bug.cgi?id=1232477 > > By default, when saving a URI using xmlSaveUri it escapes everything in the > URI. QEMU doesn't want anything