This PBX uses a different IP for it's RTP traffic - 10.92.8.11- but that in itself is not an issue. The range of valid DTMF is from 0 to -36 dBm0 (must accept) lower than -55 dBm0 must be rejected (TR-TSY-000181, ITU-T Q.24A). Set the 'Digit Relay' property to 'DTMF Packetized'. The RTP payload format for a DTMF event is designated as a telephone-event, with the media type as an audio/telephone-event in negotiation. From RFC2833 volume: For DTMF digits and other events representable as tones, this field describes the power level of the tone, expressed in dBm0 after dropping the sign. RTP NTE (aka: RFC2833) is the standards-based form of dtmf used to send DTMF. The use of RFC2833 is configured under the IP Bearer Profile, which is then assigned to the IP channel group. RTP NTE (RFC 2833)stands for Real-Time Protocol (RTP) Named Telephone Events (NTE). (eg: a bunch of RTP packets missing between packets 6425 to 6441)īTW. Created by Leo D'Alessandro on 19 Feb, 2018. 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. Maybe do that from a couple different phones as well, to show that the phone used is not the issue. 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. You will need to ask the PBX administrator why that is the case. There are no DTMF tones and no RFC 2833 DTMF messages in the RTP stream sent to VoiceGuide.
0 kommentar(er)
