Ekiga callto stories.
=====================

#1 

Eve wants to contact Adam. After God creating Google on the eight day,
she makes a search and find his number as +46 (0)70-5432100. Since she 
is using Firefox with the ekiga-callto extension, this is actually a 
link. Eve presses the link. When doing so, the Ekiga windows becomes 
visible on top  all windows, the url window contains '+46705432100'
and the call is placed without further actions.

#2 

Adam later wants to call back. He forgot to take a note of Eve's number
(after all, he is a man) so he also googles to find her number which is
011-66666. Using the same Firefox extension he clicks on this number.
As a result, the Ekiga window becomes visible on top of all windows
with the number +46116666 in the url window. The call is placed when
Adam pushes the "Call" button.

#3

Since Eve didn't pick up the phone, Adam sent an email instead. When
Eve reads this, she decides to call him. Adam's nr +46 (0)70-5432100
is noted in the  email signature. Eve selects the number with her 
mouse, copies it and pastes it into the ekiga URL window which thus 
reads '+46 (0)70-5432100'. Now, what happens?

#4

Eve, being the structured type, decides to store Adam's nr in her PIM
Evolution database as a contact. Later, when she want's to call him 
she brings up Ekiga's Address Book Window, where his number is noted
as 070-5432100. Now, what happens?

Some discussion:
----------------

Is the behaviour in #1 and #2 reasonable? Is it possible within the
current framework?

Numbers might be ambiguous if they lack country code, and it's not
clear in what context to evaluate them. The typical example is using a
nr from an US website, which often are supposed to be evaluated 
within US. In this case, it makes sense to let the user edit the number
before the call is placed, that's why Adam has an opportunity to
edit the number before the call is placed in #2. This is also the
overall situation in #3.

Numbers beginning with a '+' sign are never ambiguous, the call could
and should be placed directly as in #1 IMHO.

Numbers in a PIM database are nor ambiguous either, they should be 
evaluated in the user's country. After all, if I store a number
without countrycode, it *will* refer to a Swedish number since I'm
in Sweden. It's safe to assume that if I store a number of a non-Swede
it will be complete with countrycode, this is just the way things work.

In #1 and #2, Ekiga will under the hood be invoked by Firefox with
something like "ekiga -c callto://01166666" i. e., with formatting
characters removed but otherwise unchanged.

What should the user feedback be when placing a call to say 
'0920-12345'? The complete url ekiga uses is maybe 
sip:+4692012345@sip.company.net, but is this something the user
is concerned about? From my perspective, I'm just placing a call
to 0920-12345, the complete url is just a technical detail
on same level as ip addresses and hosts involved. So I think the
proper way would to do it is to  just show the number in the window. 
The exception is if the user has more than one sip provider relaying 
calls to PSTN, but in that case I think I would prefer 
'0920-12345 (Provider)' instead... This is my reasoning behind parts
of #1 and #2.


