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

DTMF events are not being reported #55

Closed
designedbywill opened this issue May 20, 2022 · 1 comment · Fixed by #145
Closed

DTMF events are not being reported #55

designedbywill opened this issue May 20, 2022 · 1 comment · Fixed by #145
Labels
bug Something isn't working

Comments

@designedbywill
Copy link

Testing out some new code to replace and old TAPI based system since it is no longer supported by Microsoft.
My inital code very similar to your example but the getDTMF() is not returning anything.
Wireshark is showing the RTP events during the call:
RTP EVENT 60 Payload type=RTP Event, DTMF Nine 9

    while call.state == CallState.ANSWERED:
        pressed=call.getDTMF()
        if pressed == '9':
            call.hangup()
        time.sleep(1)

This is running through a Grandstream UCM6202 and tested with both a MicroSIP on the PC running the code and cell phone being called out over a POTS line. All the other functions are running properly.

my program output:

Dialing...
TODO: Add 500 Error on Receiving SIP Response <-- still on your TODO list? ;)
Ringing/Answered
Friday May 20, 2 10 PM, ,Press 9 to hang up. <-- pyttsx and librosa to make voice prompt in correct format
Sending message
Waiting for input or hangup. <-- listening for DTMF 9
.
.
CallState.ENDED <-- finally manually hangup call
Goodbye

@Duvio
Copy link

Duvio commented Jul 28, 2022

I have the same problem, somehow this function does not work. I was already about to code my own bare-minimum library because of other problems...

@tayler6000 tayler6000 added the bug Something isn't working label Sep 26, 2022
@tayler6000 tayler6000 added this to pyVoIP May 9, 2023
@tayler6000 tayler6000 moved this from Todo - Release to Backlog in pyVoIP May 9, 2023
@github-project-automation github-project-automation bot moved this to Todo - Release in pyVoIP May 9, 2023
@tayler6000 tayler6000 moved this from Backlog to In Progress in pyVoIP Jun 2, 2023
tayler6000 added a commit that referenced this issue Jun 2, 2023
[FIX] Changed socket out to be a reference to socket in for RTPClient.
      Some systems were just replying to the port they were receiving RTP on
      instead of sending RTP to the port specified in the SDP of the INVITE or
      OK message. This was causing loss of audio and DTMF on those systems.
@tayler6000 tayler6000 linked a pull request Jun 2, 2023 that will close this issue
@tayler6000 tayler6000 moved this from In Progress to Done in pyVoIP Jun 5, 2023
tayler6000 added a commit that referenced this issue Jun 7, 2023
tayler6000 added a commit that referenced this issue Jun 7, 2023
Fixed #55
Fixed #96
Fixed #146

Co-authored-by: SEIDO-JP <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants