Le mercredi 24 décembre 2008 à 01:25 +0100, Palo S. a écrit :
I can confirm that this problem is fixed. The call is not
canceled anymore (although I only tested via VNC ie nobody
on the other side so I cannot say whether there are some
other issues such as voice not coming through).
Good
: Ekiga mailing list
Poslaná: 21.12.2008 10:31
Predmet: Re: [Ekiga-list] \\\remote user cleared the call\\\ problem
Le samedi 20 dĂŠcembre 2008 Ă 20:33 +0100, Palo S. a ĂŠcrit :
A fix has been put into the stable branch and into TRUNK. Is that
something you can test ?
Tried
Le samedi 20 décembre 2008 à 20:33 +0100, Palo S. a écrit :
A fix has been put into the stable branch and into TRUNK. Is that
something you can test ?
Tried to test snapshot from 18th and 19th but none of them
compiled. The (first) error message was:
A fix has been put into the stable branch and into TRUNK. Is that
something you can test ?
Tried to test snapshot from 18th and 19th but none of them
compiled. The (first) error message was:
../../../../lib/engine/components/opal/sip-endpoint.cpp: In member function
`virtual void
Le jeudi 11 décembre 2008 à 22:55 +0100, Palo S. a écrit :
Not sure how to fix Kamailio
It may be possible for Kamailio developers to
identify place (in the code) where Kamailio
sends this CANCEL by itself and fix...
but I wonder if the CANCEL is not taken
into account when it
Le jeudi 11 décembre 2008 à 00:46 +0100, Palo S. a écrit :
So finally I ran Wireshark. It confirmed that there
is no CANCEL from the caller, yet Kamailio sends
CANCEL to the called side. It also shows that
Kamailio sends and resends INVITE to several ports
and keeps sending them until 200
I wonder if we should just not ignore the cancel...
--
It seems that proper fix should be done on Kamailio.
Ignoring CANCEL for INVITE could be a workaround in
the meantime, however it would probably cause
problems in situations when invite should be cancelled
(ie when the other side
Le jeudi 11 décembre 2008 à 22:15 +0100, Palo S. a écrit :
I wonder if we should just not ignore the cancel...
--
It seems that proper fix should be done on Kamailio.
Ignoring CANCEL for INVITE could be a workaround in
the meantime, however it would probably cause
problems in
Not sure how to fix Kamailio
It may be possible for Kamailio developers to
identify place (in the code) where Kamailio
sends this CANCEL by itself and fix...
but I wonder if the CANCEL is not taken
into account when it should not be.
I think that Ekiga does it correctly, at least
I
Le mardi 02 décembre 2008 à 11:19 +0100, Palo S. a écrit :
A cancel can be sent if you are using forking, ie 2 Ekiga registered
with the same account name, from 2 different IP addresses and ports. As
soon as one answers, a CANCEL is sent to the other one.
Couldn\'t it be the case ?
A cancel can be sent if you are using forking, ie 2 Ekiga registered
with the same account name, from 2 different IP addresses and ports. As
soon as one answers, a CANCEL is sent to the other one.
Couldn\'t it be the case ?
It could be that due to a problem with NAT a private
IP
Le lundi 01 décembre 2008 à 02:21 +0100, Palo S. a écrit :
The problem disappeared after I disabled forwarding
of 5060 to the called machine. So yet another NAT
issue. However the port forwarding was set a long
time ago and the problem only appeared recently,
confirming that the new Ekiga
Le dimanche 30 novembre 2008 à 03:01 +0100, Palo S. a écrit :
I have a problem being unable to make a call
from user A to user B: it rings but the call is
immediatelly dropped after B accepts it with
\remote user cleared the call\ on both sides.
No problem making a call from B to A
It looks like a bug on Kamailio (the SIP Router). Because called
receives a CANCEL message, but caller does NOT send a CANCEL message.
Indeed - I did not notice this.
It is true that the problem emerged around the time
when Kamailio started to be used.
I\'m not sure how to fix that :-/
The
The problem disappeared after I disabled forwarding
of 5060 to the called machine. So yet another NAT
issue. However the port forwarding was set a long
time ago and the problem only appeared recently,
confirming that the new Ekiga server was the trigger
of the problem. It would be nice if
15 matches
Mail list logo
