First i would like to thanks everybody for the help .....
So after some source inspections i've seen in the phapi source something
appearing to me as an obvious bug.
Please this time for those who know well phapi and develop it read the
following.
in phapi-old.c function phAcceptCall3 on line 1252 to 1260 (approx)
you'll find 3 line of c code responsible of sending a 200 OK answer for
an incoming SIP call.
<code>
eXosip_lock();
DBG_SIP_NEGO("NO STUN ports (a.local=%s, a.public=%s) (v.local=%s,
v.public=%s)\n",local_voice_port,0,local_video_port,0);
i = eXosip_answer_call(ca->did, 200, local_voice_port,
ph_get_call_contact(ca), optional(local_video_port), 0, 0);
</code>
The problem appearing to me is a bad copy/paste of those lines
resulting in a duplication.
So this code is executed twice, and it seems that without the
duplication, incoming calls work fine.
Is it possible for someone to check that bug and use my fix ?
Thanks for all.
Le Mesle Séven wrote:
i've got a SIP problem with wengo
on sip INVITE received, no 200 ok is answered
and no listening port for RTP gets open
is it possible that when wengo can't connect to proxy sip RTP port (or
distant negociated RTP port) it just squizz the 200 ok reply
and just go in an ugly freeze ?
i'm affraid that's what i see.
Did someone face such a bug ?
best regards.
Séven Le Mesle
_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
_______________________________________________
Wengophone-devel mailing list
[email protected]
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
