Emia
Emia
Anyway this is something that will be addressed more. I suggest going with some temporarly fix. It can be option on transport layer. Give me some time to add it....
@p-akshay this is now forced to be IPV4. I would consider your issue is fixed, but we still need better way to solve.
it is called lazy parsing. Altering parser default headers parsing, should bring you to this level, but I could agree there could be some global level of control, to still...
Fixed on main for now on Message level. `CompactHeaders` field is added. I for now see no reason to extend this on Client level but maybe later. Please check solution...
Not sure, I would need some sip traces to check. It is like your transaction was terminated
Hi @p-akshay I think lately dialog handling API is lot improved. Can you still replicate this behavior. I suggest if you are building B2BUA system that you switch to diago...
If you are exiting Invite Server Transaction, then you are terminating Transaction. Normally you should do all responses in this goroutine. So after sending final response (>199) you are free...
@andzsinszan ok I see your point. Maybe it makes sense to return error, similar as context.Context returns on cancelation
Hi @andzsinszan now when responding on server transaction you should recieve error. This last one I do not get. Adding more runtime checks could be sign of bad written library...
It is not implemented, but you can close all transactions from TransactionLayer, and just have some server handler tracking. You may want todo extra for Call Sessions