Aaron Clauson

re-tACK 8f4fed7ec70093e2535423d63e9f9dd400c378ac.

Issue seems resovled. Please feel free to re-open if any further questions.

Is this solved?

I don't think this will work. It's been too long but but for invites I have a vague recollection the transaction logic needs to be able to match different CSeq...

I've refamiliarised myself with the SIP transaciton logic and it's not just a matter of adding extra properties to the `GetRequestTransactionId` method as a workaround. SIP transactions have very specific...

Most SIP Providers use the From header to set the callerID. The From header can be tricky to customise as it's also often used for authentication. Try switching to the...

Feel free to re-open if any further info.

Seems more like a SIP Provider issue than a library issue. Only suggestion i have is to add a space between the From name and URI: `const string from =...

I won't troubleshoot it for you but you hvae options. Use Wireshark to capture the SIP request with ozeki and compare it with the one you are sending with this...

I've just completed some improvements on DTLS certificates and DTLS cipher suite selection in #1201. The failure in your logs was typical of the case where the client only supported...