Charlie Hedlin wrote:
Yesterday I had Ekiga lock up. Upon connecting with gdb I found that
two threads were hung trying to acquire locks.
Thread 5 was processing the OnConnected even tfrom SipConnection, up
to OpalManager and down to OpalConnection::Released. It was blocked on
Hello,
I am testing the functionality of Fraunhofer Fokus OpenIMS core network
with different SIP phones and found out strange behavior of Ekiga, which
could be considered as a possible bug.
Ekiga registers and then tries to establish a call.
REGISTER request is the following:
Damien Sandras wrote:
Le mercredi 09 mai 2007 à 09:03 +0200, Jan Schampera a écrit :
Hey Charlie!
If this problem and fix can be confirmed it should probably be moved to
Opal. I was trying to avoid having another custom package when I added
these calls to
Le mercredi 09 mai 2007 à 09:48 -0500, Charlie Hedlin a écrit :
Damien Sandras wrote:
Le mercredi 09 mai 2007 à 09:03 +0200, Jan Schampera a écrit :
Hey Charlie!
If this problem and fix can be confirmed it should probably be moved to
Opal. I was trying to avoid
Therefore, Ekiga should always keep track of all the URIs in Contact
header ever sent to another parties (as these parties could try to
connect Ekiga using this URIs) as well as all the URIs from REGISTER
requests. I.e. it is not fully correct to consider Contact header as
a
temporary
Le mercredi 09 mai 2007 à 17:52 +0200, Mikhanov Sergey a écrit :
Therefore, Ekiga should always keep track of all the URIs in Contact
header ever sent to another parties (as these parties could try to
connect Ekiga using this URIs) as well as all the URIs from REGISTER
requests. I.e.
Le mercredi 09 mai 2007 à 11:14 -0500, Charlie Hedlin a écrit :
2.0.9 and HEAD should have the same level of stability (we backport
changes from HEAD to Phobos).
If you encounter stability problems, please report them back here so
that we can fix them. But do you encounter stability
At this point I should probably move to the Opal list, but unless that
is requested I will stay on this thread.
I tried to compile Opal Phobos and failed on src/opal/connection.cxx.
Looking at the CVS log it shows the updates committed to revision
2.55.2.4 while Phobos is assigned to
Hi,
Le mercredi 09 mai 2007 à 18:21 +0200, Damien Sandras a écrit :
I will write when I have done testing. Once I have a reliable
version
we will be placing about 10k calls per day on ekiga through our
asterisk server. We are currently using Sip Foundry's sipXtapi and
have contributed
Oops.
Version is curent SVN.
Le jeudi 10 mai 2007 à 00:05 +0200, yannick a écrit :
Hi,
Calling this number:
sip:[EMAIL PROTECTED] (gizmo echo test via SIPbroker)
I sometime experience crashes (I'm not sur the trace below can help...)
Another interesting thing with this number is: when I
10 matches
Mail list logo
