Harry C Report post Posted 04/06/2023 09:16 PM Now I might have DTMF issue. When I made the test call and it looks like IVR never receive DTMF at all. I did check IVR log and couldn't find anything. Share this post Link to post
SupportTeam Report post Posted 04/06/2023 10:35 PM Please post the WireShark trace that shows all the RTP traffic as well. Maybe best to just filter WireShark capture to show all traffic between IP 10.92.38.36 and IP 10.92.39.22 This WireShark filter should work: (ip.src==10.92.38.36 and ip.dst==10.92.39.22) or ( ip.src==10.92.39.22 and ip.dst==10.92.38.36) current WireShark trace only contains: Share this post Link to post
Harry C Report post Posted 04/07/2023 03:36 AM VoiceGuide04062023_2.pcapng Share this post Link to post
SupportTeam Report post Posted 04/07/2023 04:38 AM There are no DTMF tones and no RFC 2833 DTMF messages in the RTP stream sent to VoiceGuide. You will need to ask the PBX administrator why that is the case. Recommend doing a call where the caller speaks "I am now pressing key 1" and then pressed key "1" a few times, then key 2 and maybe a couple more keys, and forward the WireShark trace of that to the PBX administrator to show them that the key-presses were not sent to VoiceGuide. Maybe do that from a couple different phones as well, to show that the phone used is not the issue. The WireShark capture actually shows that some RTP packets that are sent to VoiceGuide are out of sequence - at around the time it appears that a key might have been pressed - so it's possible that you have something (PBX itself?) removing the DTMF sounds from the voice path., but not issuing RFC 2833 in their place... (eg: a bunch of RTP packets missing between packets 6425 to 6441) BTW. This PBX uses a different IP for it's RTP traffic - 10.92.8.11- but that in itself is not an issue. Share this post Link to post
