This is fixed with
https://git.gnome.org/browse/ekiga/commit/?id=dcc28806f0a5.
On 27/03/13 13:51, Thierry Simonnet wrote:
I can reproduce it with the last trunk.
I have an ekiga.net SIP account
I have a contact "Tokyo" with h323 address : h323:61.197.225.89
It is a Polycom service number.
When
Ah yes, I have it too.
Julien, I think this is for you :) There are two problems:
1- when SIP accounts are registered, h323 contacts propose to use SIP
registrar to call with
2- when SIP accounts are registered and a contact is sip:xyz, we need to
make the difference between:
a- xyz is an IP a
I can reproduce it with the last trunk.
I have an ekiga.net SIP account
I have a contact "Tokyo" with h323 address : h323:61.197.225.89
It is a Polycom service number.
When double clicking on Tokyo it composes :
h323:61.197.225...@ekiga.net
and
It works here. Can you tell precisely how to reproduce the bug?
On 26/03/13 09:03, Thierry Simonnet wrote:
On contacts, for SIP :
* it is possible to select the registrar you use (if multi)
* address is automatically completed by @
For H363 : on most cases only the IP address is mandato
On contacts, for SIP :
it is possible to select the registrar you use (if multi)
address is automatically completed by @
For H363 : on most cases only the IP address is mandatory and
you could use H323 without login.
Then a H323 use is
On 13/03/13 15:57, Thierry Simonnet wrote:
Hello,
I noticed that with the trunk version of ekiga there is a little trouble with
h323 contacts.
Using "contacts" tab, h323 address is completed by a @ when
clickinng on the label.
Unfortunately most h323 contacts use h323: format (see Polycom test
Hello,
I noticed that with the trunk version of ekiga there is a little
trouble with h323 contacts.
Using "contacts" tab, h323 address is completed by a
@ when clickinng on the label.
Unfortunately most h323 contacts use h323: format
(see Polycom test address
