Team,
When the remote entity sends re-transmitted 200 OK messages, there is no transaction object available that matches the retransmission message. The transaction gets removed from the table after initial 200 OK is received successfully
We are using Jain Stack for proxy use cases.
We played around setting below flag
-
- gov.nist.javax.sip.LINGER_TIMER=int
- A property that will specify for how many seconds the Dialog and Transaction structures will stay in memory before the stack releases them
However this does not help to retain the transaction , but delays cleaning up some of the internal objects.
Is there a mechanism available or any suggestions how the transaction can be cached or retrieved for handling subsequent retransmissions. This helps the implementation of listener interface to apply any solution specific handling to these messages.
Team,
When the remote entity sends re-transmitted 200 OK messages, there is no transaction object available that matches the retransmission message. The transaction gets removed from the table after initial 200 OK is received successfully
We are using Jain Stack for proxy use cases.
We played around setting below flag
However this does not help to retain the transaction , but delays cleaning up some of the internal objects.
Is there a mechanism available or any suggestions how the transaction can be cached or retrieved for handling subsequent retransmissions. This helps the implementation of listener interface to apply any solution specific handling to these messages.