From dbb303451f8dda5586420fcd5887c7438e1d355d Mon Sep 17 00:00:00 2001 From: Simon Morlat Date: Wed, 16 Feb 2011 19:20:11 +0100 Subject: [PATCH] fix stupid "no response" message when call are released after errors --- coreapi/sal_eXosip2.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/coreapi/sal_eXosip2.c b/coreapi/sal_eXosip2.c index 2eb9a0c32..4394e019c 100644 --- a/coreapi/sal_eXosip2.c +++ b/coreapi/sal_eXosip2.c @@ -24,6 +24,8 @@ Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA. #include "private.h" #include "offeranswer.h" +static bool_t call_failure(Sal *sal, eXosip_event_t *ev); + static void text_received(Sal *sal, eXosip_event_t *ev); void _osip_list_set_empty(osip_list_t *l, void (*freefunc)(void*)){ @@ -1085,8 +1087,9 @@ static void call_released(Sal *sal, eXosip_event_t *ev){ ms_warning("No op associated to this call_released()"); return; } - if (op->did==-1) { - sal->callbacks.call_failure(op,SalErrorNoResponse,SalReasonUnknown,NULL, 487); + if (ev->response==NULL){ + /* no response received so far */ + call_failure(sal,ev); } sal->callbacks.call_released(op); }