From: "briangpowell ." <briangpowellms@gmail.com>
To: Christian Thaeter <ct.orgmode@pipapo.org>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: sip: links
Date: Tue, 23 Jun 2015 00:24:18 -0400 [thread overview]
Message-ID: <CAFm0skH4tS7t_C55=p0i9M0-9_35ESsYkM==u-8HrQmAtC0z5Q@mail.gmail.com> (raw)
In-Reply-To: <20150622170202.286a8986@jupiter.pipapo.org>
[-- Attachment #1: Type: text/plain, Size: 1625 bytes --]
Cool, what do you do with "xmpp:"?
On Mon, Jun 22, 2015 at 11:02 AM, Christian Thaeter <ct.orgmode@pipapo.org>
wrote:
>
>
> On 2015-06-22 11:27, Michael Strey wrote:
>
> > On So, 2015-06-21, Christian Thaeter wrote:
> >
> > [...]
> >
> > > looks good, I'll use that instead of my hack.
> >
> > Look out for bugs. It's one of my very first emacs-lisp hacks.
> >
> > > I've a minor ideas to add:
> > >
> > > Instead just append the telephone number to the end of the
> > > dial command one could use (org-replace-escapes STRING TABLE), that
> > > allows little more flexible commandline generation.
> >
> > Thanks for the hint. Could you please give me an example where this
> > increased flexibility would be required?
>
> I am using linphone too, where that just works to append the
> sanitized telephone number at the end. But I can imagine that other
> dial programs may have different calling conventions. Also I may feel a
> bit safer by quoting the telephone number, For example:
>
> linephone -c 'sip:%n'
>
> Maybe in the long run (I have no urge here, works for me now).
> You/we/someone could make this whole thing more generic, handling
> different kinds of communication protocols (I made another one for
> xmpp: meanwhile).
>
> tel: urls are somewhat simple https://www.ietf.org/rfc/rfc3966.txt
> (still surprisingly more syntax than just a number) but when you look
> at sip: http://tools.ietf.org/html/rfc3261#section-19.1 things get way
> more complicated.
>
> Christian
>
>
>
> >
> > Best regards
> > --
> > Michael Strey
> > http://www.strey.biz * https://twitter.com/michaelstrey
> >
> >
>
>
>
[-- Attachment #2: Type: text/html, Size: 2663 bytes --]
next prev parent reply other threads:[~2015-06-23 4:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-20 15:23 sip: links Christian Thaeter
2015-06-21 0:39 ` Christian Thaeter
2015-06-21 10:37 ` Michael Strey
2015-06-21 16:15 ` Christian Thaeter
2015-06-22 9:27 ` Michael Strey
2015-06-22 15:02 ` Christian Thaeter
2015-06-23 4:24 ` briangpowell . [this message]
2015-06-23 8:33 ` Christian Thaeter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFm0skH4tS7t_C55=p0i9M0-9_35ESsYkM==u-8HrQmAtC0z5Q@mail.gmail.com' \
--to=briangpowellms@gmail.com \
--cc=ct.orgmode@pipapo.org \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).