-
Notifications
You must be signed in to change notification settings - Fork 750
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
Fix invalid state error on DTMF send #717
Conversation
Hi, Reverted due to this #689 |
Hi, I cannot exactly deduce what extra conditions I need to test on. If you can clarify I can test. |
I guess you are sending DTMFs of type JsSIP_C.DTMF_TRANSPORT.RFC2833, right? |
Can I know more? It should indeed be possible to send DTMF (in band or via INFO) once we have received a 18X. |
That's why I ask. I want to confirm this, because INFO DTMFs for sure don't work. |
Why not? |
It should be possible to send in-dialog messages as far as the dialog is created, and that happens once we get a 18X with Contact header. |
Due to the problem posted here #689. Yes, this is a bug in the library. |
BTW I promise it's possible to send DTMF in PSTN calls even before the call is answered. I used that in the past. |
Si I think such a bug must be fixed, yes, but no real reason to revert this PR. |
Yes indeed I am. |
If I send the DTMF of type |
That's a point. We are now preventing RFC2833 DTMFs from being sent. Ok, let's merge it. |
Changes added to the new release. |
Sending a DTMF tone after a
183 Session Progress
for example would raise anINVALID_STATE_ERROR
. This PR fixes that.