-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is this library alive? #17
Comments
I’m in between jobs at the moment and might take a look - I’m a bit rusty though. |
It's alive in the sense that the non-profit I work for is actively using it in some of our applications, but everything we do with the library is currently perfectly working, so I don't feel the need to put any time into it. I'm ready to test any PR if you feel something needs to be fixed though. And of course I would be totally fine with @danbarua doing whatever he wants with his own code! ;-) |
Do you think you will get a chance to look at #10 ? |
I’m going to have to go back through the history of the code because I may
have tried this before and hit an obstacle.
Can you provide some example message traffic and a use case that would
trigger it?
I suppose something in a SIP message transmitted verbatim might do it?
thanks
…On Tue, 9 May 2023 at 10:43, Andrew Golledge ***@***.***> wrote:
Do you think you will get a chance to look at #10
<#10> ?
—
Reply to this email directly, view it on GitHub
<#17 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADSRSFKO6B5K4W2TO2KE4DXFIGTTANCNFSM6AAAAAAXN5RPUE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
ITNOA
Hi
Is this library alive?
The text was updated successfully, but these errors were encountered: