Skip to content
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

Merged
merged 1 commit into from
Jun 16, 2021

Conversation

BlindChickens
Copy link
Contributor

Sending a DTMF tone after a 183 Session Progress for example would raise an INVALID_STATE_ERROR. This PR fixes that.

@jmillan jmillan merged commit a4748e4 into versatica:master Jun 16, 2021
@jmillan
Copy link
Member

jmillan commented Jun 16, 2021

Hi,

Reverted due to this #689

@BlindChickens
Copy link
Contributor Author

Hi, I cannot exactly deduce what extra conditions I need to test on. If you can clarify I can test.
What I can say is that before the change it does not work for me right after a 183 Session Progress, and after the change it works anytime from 183 Session Progress to 200 OK.

@jmillan
Copy link
Member

jmillan commented Jun 16, 2021

I guess you are sending DTMFs of type JsSIP_C.DTMF_TRANSPORT.RFC2833, right?

@ibc
Copy link
Member

ibc commented Jun 16, 2021

Can I know more? It should indeed be possible to send DTMF (in band or via INFO) once we have received a 18X.

@jmillan
Copy link
Member

jmillan commented Jun 16, 2021

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.

@ibc
Copy link
Member

ibc commented Jun 16, 2021

Why not?

@ibc
Copy link
Member

ibc commented Jun 16, 2021

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.

@jmillan
Copy link
Member

jmillan commented Jun 16, 2021

Due to the problem posted here #689. Yes, this is a bug in the library.

@ibc
Copy link
Member

ibc commented Jun 16, 2021

BTW I promise it's possible to send DTMF in PSTN calls even before the call is answered. I used that in the past.

@ibc
Copy link
Member

ibc commented Jun 16, 2021

Si I think such a bug must be fixed, yes, but no real reason to revert this PR.

@BlindChickens
Copy link
Contributor Author

I guess you are sending DTMFs of type JsSIP_C.DTMF_TRANSPORT.RFC2833, right?

Yes indeed I am.

@BlindChickens
Copy link
Contributor Author

If I send the DTMF of type INFO, there is no error on my side, but also no corresponding sound on the other end indicating that it worked. I don't know what the differences are here, but I am going to assume our service provider does not allow for the INFO type DTMF's. I can see the websocket messages going out when I send them, but no sound on the other end.

@jmillan
Copy link
Member

jmillan commented Jun 16, 2021

Si I think such a bug must be fixed, yes, but no real reason to revert this PR.

That's a point.

We are now preventing RFC2833 DTMFs from being sent. Ok, let's merge it.

@jmillan
Copy link
Member

jmillan commented Jun 16, 2021

Changes added to the new release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants