Hi,
2011/4/11 Manuel Argüelles :
>> On client side, stack calls the ordinary response callback on client
>> transaction. If the request method is INVITE and the response status
>> is >= 300 (and the response is not internally generated), you know
>> that stack will automatically send an ACK.
>>
>>
Hello,
On Mon, Apr 11, 2011 at 06:29:49PM +0300, Pekka Pessi wrote:
> Hi,
>
> 2011/4/11 Manuel Argüelles :
> >> The ACK to error responses such as 486 is part of the transaction so
> >> NTA takes care of it. What kind of notification would you like to get?
>
> > Anything that notifies the progra
Hi,
2011/4/11 Manuel Argüelles :
>> The ACK to error responses such as 486 is part of the transaction so
>> NTA takes care of it. What kind of notification would you like to get?
> Anything that notifies the program about this event will do.
On client side, stack calls the ordinary response call
On Mon, Apr 11, 2011 at 04:28:25PM +0300, Pekka Pessi wrote:
>
> The ACK to error responses such as 486 is part of the transaction so
> NTA takes care of it. What kind of notification would you like to get?
>
Hello Pekka,
Anything that notifies the program about this event will do.
Thanks
-
Hi,
2011/4/10 Manuel Argüelles :
> I'm using an nta agent in a multi-thread application (proxy), I noticed that
> during an invite transaction if the peer returns a 486 Busy Here code, sofia
> sip seems to internally handle it and replies with an ACK, since the callback
> function doesn't gets cal
