Re: [osip-dev] TCP repetition

[Aymeric Moizard]

Bonjour Daniel,

First, there are 2 very different behavior for ACK:

* ACK after error response is part of the INVITE/XXX/ACK transaction

* ACK after a 200ok is NOT part of the INVITE/200ok transaction.

The difference are details in specification.

That means in eXosip2/osip2, the 200ok retransmission doesn't happen

after a timer related to the INVITE transaction.

In branch "multireg" of the git, the retransmission happens when this

method is called:

void _eXosip_retransmit_lost200ok(struct eXosip_t *excontext)

And looking at the code, this method is automatically called for every call to:

eXosip_event_t *eXosip_event_wait(struct eXosip_t *excontext, int tv_s, int tv_ms)

I guess you don't have retransmission because you are using the other method

to retreive events:

   eXosip_event_t *eXosip_event_get(struct eXosip_t *excontext)

This last method is certainly not usable to build a compliant sip application, despite

the fact that it exists... I have added a side note to inform about the API being

deprecated/limited.

Regards,

Aymeric

2012/6/18 Daniel Génin <address@hidden>

Hello,

 

With TCP, the response status 200 is repeated (6 times) when the client don't send the ACK (RFC 3261 17.2).

I don't understand why but i notive that timer G, H or I never fire

 

Osip trace between the two SIP response  200 OK is :  

 

| INFO3 | 9702 <..\..\src\jcallback.c: 1775> cb_snd123456xx (id=1)
| INFO1 | 9702 <..\..\src\jcallback.c: 239> cb_nict_kill_transaction (id=1)
| INFO4 | 9702 <..\..\src\osip2\osip_transaction.c: 436> sipevent evt: method called!
| INFO2 | 9702 <..\..\src\eXconf.c: 783> eXosip: Reseting timer to 10s before waking up!
| INFO1 | 11702 <..\..\src\eXtl_tcp.c: 601> Message sent:

 

My application uses : libosip2-3.3.0 libeXosip2-3.3.0

I try libosip2-3.6.0 libeXosip2-3.6.0 with the same result.

 

Can you help me ?

Thanks

 

Regards,

Daniel Genin

 

 

 

 

 "Les informations contenues dans ce courriel sont données à titre purement informatif et ne peuvent être considérées comme contractuelles entre les récipiendaires et la société Prescom (Secmat)."
 "The content of this e-mail is purely for information and may not be considered as contractual between the recipients and Prescom (Secmat)

_______________________________________________
osip-dev mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/osip-dev

--
Antisip - http://www.antisip.com