[jitsi-dev] Associate callto: and tel: to Jitsi


#1

Dear Jitsi team,

I was wondering if Jitsi could to be assiciated to "callto:" and "tel:" URL's

It's not on my version of Jitsi and I find it should be in the default
installation script

Would it be difficult to do so ?

Best regards,
Patrick


#2

I would support Patrick's wish, but please note that 'tel:' has superseded 'callto:' so I don't see a real need for that.
'callto:' is a discarded misnomer "because URI schemes locate a resource and do not specify an action to be taken". Read more
about that from RFC 2806 at <http://www.rfc-editor.org/rfc/rfc3966.txt>. - Best wishes ph


#3

Hello Philip,

I fully agree with you from a theoritical point of view but in
practise, most of links are still using callto:

For example, sugarCRM is using this scheme...which was mainly my
trigger to have this 'protocol' associated with Jitsi

If I'm not mistaken, Skype is also reacting only on callto protocol.

Imho, Jitsi should associate both scheme until "tel" is not massively adopted

Best regards,
Patrick

···

On Sat, Nov 26, 2011 at 13:18, Philip Donner <pdonner@znak.fi> wrote:

I would support Patrick's wish, but please note that 'tel:' has superseded 'callto:' so I don't see a real need for that.
'callto:' is a discarded misnomer "because URI schemes locate a resource and do not specify an action to be taken". Read more
about that from RFC 2806 at <http://www.rfc-editor.org/rfc/rfc3966.txt>. - Best wishes ph


#4

Sorry. Some of you might have noticed that I mixed up two references which both make the same point:

Read more about that from RFC 2806 at <http://www.rfc-editor.org/rfc/rfc3966.txt>.

Should have written:

Read more about that from RFC 2806 section 2.7.2 at <http://www.rfc-editor.org/rfc/rfc2806.txt> and RFC 3966 section 7.3. at
<http://www.rfc-editor.org/rfc/rfc3966.txt>.


#5

Hey folks,

Could you please open an issue for callto: and tel: support?

Thanks,
Emil

На 26.11.11 18:41, Patrick написа:

···

Hello Philip,

I fully agree with you from a theoritical point of view but in
practise, most of links are still using callto:

For example, sugarCRM is using this scheme...which was mainly my
trigger to have this 'protocol' associated with Jitsi

If I'm not mistaken, Skype is also reacting only on callto protocol.

Imho, Jitsi should associate both scheme until "tel" is not massively adopted

Best regards,
Patrick

On Sat, Nov 26, 2011 at 13:18, Philip Donner <pdonner@znak.fi> wrote:

I would support Patrick's wish, but please note that 'tel:' has superseded 'callto:' so I don't see a real need for that.
'callto:' is a discarded misnomer "because URI schemes locate a resource and do not specify an action to be taken". Read more
about that from RFC 2806 at <http://www.rfc-editor.org/rfc/rfc3966.txt>. - Best wishes ph

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#6

Hi, Emil:

I totally agree on the issue of sip: , tel: and callto; links. There are too few SIP phones, including Jitsi, that support them. I have tried on OS X to associate the tel:, sip:, and callto: links it works to actually launch Jitsi, but there is no handler or scheme to accept the offered URI or phone number within Jitsi so it doesn't look like too much work to get it working.

marc.

···

_______________________
sip:marc@plan9tele.com
tel:+1-949-514-8999

On Sunday, November 27, 2011 at 2:55 PM, Emil Ivov wrote:

Hey folks,

Could you please open an issue for callto: and tel: support?

Thanks,
Emil

На 26.11.11 18:41, Patrick написа:
> Hello Philip,
>
> I fully agree with you from a theoritical point of view but in
> practise, most of links are still using callto:
>
> For example, sugarCRM is using this scheme...which was mainly my
> trigger to have this 'protocol' associated with Jitsi
>
> If I'm not mistaken, Skype is also reacting only on callto protocol.
>
> Imho, Jitsi should associate both scheme until "tel" is not massively adopted
>
> Best regards,
> Patrick
>
>
> On Sat, Nov 26, 2011 at 13:18, Philip Donner <pdonner@znak.fi (mailto:pdonner@znak.fi)> wrote:
> > I would support Patrick's wish, but please note that 'tel:' has superseded 'callto:' so I don't see a real need for that.
> > 'callto:' is a discarded misnomer "because URI schemes locate a resource and do not specify an action to be taken". Read more
> > about that from RFC 2806 at <http://www.rfc-editor.org/rfc/rfc3966.txt>. - Best wishes ph
> >
>
>

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org (mailto:emcho@jitsi.org) PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#7

Hi. Emil wrote:

Could you please open an issue for callto: and tel: support?

Opening an issue for associating the tel: scheme with Jitsi seems to imply that I should join the java developer team of the program. Or can I operate the issue tracker without doing so? That's anyway something I would love to do, but unfortunately java isn't one of my programming languages. So maybe somebody could act on my behalf. - When you do so, please note that such a link is only one aspect of the need. It would be essential to implement ENUM DNS lookup to make the new feature even more meaningful. Then Jitsi would also be able to handle ENUM mapped phone numbers, as well. Thanks ph


#8

На 28.11.11 17:33, Marc Abrams написа:

Hi, Emil:

I totally agree on the issue of sip: , tel: and callto; links. There are
too few SIP phones, including Jitsi, that support them. I have tried on
OS X to associate the tel:, sip:, and callto: links it works to actually
launch Jitsi, but there is no handler or scheme to accept the offered
URI or phone number within Jitsi so it doesn't look like too much work
to get it working.

Jitsi currently only handles "sip:" links. Support for "tel:" and
"callto:" would have to be added separately.

Cheers,
Emil

···

marc.

_______________________
sip:marc@plan9tele.com
tel:+1-949-514-8999

On Sunday, November 27, 2011 at 2:55 PM, Emil Ivov wrote:

Hey folks,

Could you please open an issue for callto: and tel: support?

Thanks,
Emil

На 26.11.11 18:41, Patrick написа:

Hello Philip,

I fully agree with you from a theoritical point of view but in
practise, most of links are still using callto:

For example, sugarCRM is using this scheme...which was mainly my
trigger to have this 'protocol' associated with Jitsi

If I'm not mistaken, Skype is also reacting only on callto protocol.

Imho, Jitsi should associate both scheme until "tel" is not massively
adopted

Best regards,
Patrick

On Sat, Nov 26, 2011 at 13:18, Philip Donner <pdonner@znak.fi >>> <mailto:pdonner@znak.fi>> wrote:

I would support Patrick's wish, but please note that 'tel:' has
superseded 'callto:' so I don't see a real need for that.
'callto:' is a discarded misnomer "because URI schemes locate a
resource and do not specify an action to be taken". Read more
about that from RFC 2806 at
<http://www.rfc-editor.org/rfc/rfc3966.txt>. - Best wishes ph

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org <mailto:emcho@jitsi.org> PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31

--
Emil Ivov, Ph.D. 67000 Strasbourg,
Project Lead France
Jitsi
emcho@jitsi.org PHONE: +33.1.77.62.43.30
http://jitsi.org FAX: +33.1.77.62.47.31


#9

Hey Philip,

Hi. Emil wrote:

Could you please open an issue for callto: and tel: support?

Opening an issue for associating the tel: scheme with Jitsi seems to
imply that I should join the java developer team of the program. Or
can I operate the issue tracker without doing so?

Yes, you just need to create a java.net account. Anyone is able to do this.

That's anyway
something I would love to do, but unfortunately java isn't one of my
programming languages. So maybe somebody could act on my behalf. -
When you do so, please note that such a link is only one aspect of
the need. It would be essential to implement ENUM DNS lookup to make
the new feature even more meaningful. Then Jitsi would also be able
to handle ENUM mapped phone numbers, as well. Thanks ph

This is not currently on our roadmap. ENUM is most often used by service
providers themselves. It appears to me that having it in an user agent
would be somewhat less useful in the current state of things.

Emil

···

On 01.12.11 18:45, Philip Donner wrote: