R: SIP Call remains active even if sending of the ACK message fails

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




Am 20.09.2010 17:37, schrieb Montevecchi Massimiliano:
> First of all, thank for your quick reply.
>
> Respect the correct behavior you described, the problem is on the answering client (pjsua#2). In fact I see (I looked at wireshark capture) it does not send the BYE even if it declares the call disconnected.
>

 From RFC point of view it is clearly a bug. From robustness point of 
view it might be wise to not terminate a call if there are other 
pointers which indicate successful call setup (e.g. RTP streams).

Anyway, pjsua reports a "disconnected" without sending BYE. That seems 
to be a bug.

regards
Klaus

> This it the pjsua log:
>
>
> From:<sip:1102 at ims2.elsagdatamat.com>
> To:<sip:1004 at ims2.elsagdatamat.com>
> Press a to answer or h to reject call
> a
> Answer with code (100-699) (empty to cancel):
> 17:26:42.747    pjsua_acc.c  sip:1004 at ims2.elsagdatamat.com: registration success, status=200 (OK - SAR succesful and registrar saved), will re-register in 60 seconds 200
>   17:26:43.858    pjsua_app.c  Media for call 1 is active
>   17:26:43.878    pjsua_app.c  Call 1 state changed to CONNECTING
>   17:27:15.884    pjsua_app.c  Call 1 is DISCONNECTED [reason=408 (Request Timeout)]
>
> Max
>
> -----Messaggio originale-----
> Da: Klaus Darilion [mailto:klaus.mailinglists at pernau.at]
> Inviato: luned? 20 settembre 2010 16.49
> A: pjsip list
> Cc: Montevecchi Massimiliano
> Oggetto: Re: [pjsip] SIP Call remains active even if sending of the ACK message fails
>
> Client 1 never konws if the ACK was received by Client 2. Thus client 1
> can not terminate the session due to ACK failures - as it does not know
> about these failures.
>
> Client 2 knows about failed ACKs - thus it is the responsibility of
> client 2 to terminate the call (with BYE):
>
>
> RFC 3261, 13.3.1.4:
>
>      If the server retransmits the 2xx response for 64*T1 seconds without
>      receiving an ACK, the dialog is confirmed, but the session SHOULD be
>      terminated.  This is accomplished with a BYE, as described in Section
>      15.
>
>
> regards
> Klaus
>
> Am 20.09.2010 16:29, schrieb Montevecchi Massimiliano:
>> Hi
>>
>> I am using pjsua rel. 1.8.
>>
>> I have 2 pjsua connected the an IMS platform based on OPENIMSCORE project.
>>
>> One (pjsua#1) has access to the pcscf from internet using its IP address
>> and the other one is connected on the same Lan of the pcscf.
>>
>> I am experimenting the following problem:
>>
>> 1. Pjsua#1 calls PJSUA#2
>>
>> 2. PJsua#2 receives the INVITE and accepts the call sending 200OK
>>
>> 3. Pjsua#1 receives the 200 OK and tries to send ACK.
>>
>> 4. Pjsua#1 does not send ACK because DNS resolution fails.
>>
>> 5. Pjsua#1 does not take care of the failure and changes anyway the
>> state of the call to CONNECTED
>>
>> 6. Pjsua#2 sends again 200 OK until max retransmission then declares
>> disconnect the call.
>>
>> The question is:
>>
>> When the last try to transmit the ACK fails, the INVITE dialog should
>> not complete correctly and the call activation should fail, doesn't it?
>>
>> Best Regards
>>
>> */Massimiliano Montevecchi/*
>>
>>
>>
>> _______________________________________________
>> Visit our blog: http://blog.pjsip.org
>>
>> pjsip mailing list
>> pjsip at lists.pjsip.org
>> http://lists.pjsip.org/mailman/listinfo/pjsip_lists.pjsip.org



[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux