[SIPForum-discussion] RTP Volume Values
Zuñiga, Guillermo
Guillermo.Zuniga at cwpanama.com
Tue Jun 6 20:52:04 UTC 2017
Hi fellows,
I would like you can help me with the following issue.
I am sending a DTMF event packet to a carrier and the carrier is just decoding the DTMF for the first RTP and when I send the second RTP values doesn´t.
I am not clear with the Volume values, I was trying looking for information about this values and how is measured.
This value could be affecting that carrier is not recognizing the dtmf?
Where I can find information about this value?
DTFM for call completed:
Real-Time Transport Protocol
[Stream setup by SDP (frame 234844)]
[Setup frame: 234844]
[Setup Method: SDP]
10.. .... = Version: RFC 1889 Version (2)
..0. .... = Padding: False
...0 .... = Extension: False
.... 0000 = Contributing source identifiers count: 0
0... .... = Marker: False
Payload type: telephone-event (96)
Sequence number: 307
[Extended sequence number: 65843]
Timestamp: 45440
Synchronization Source identifier: 0x6c97d60e (1821890062)
RFC 2833 RTP Event
Event ID: DTMF One 1 (1)
0... .... = End of Event: False
.0.. .... = Reserved: False
..00 0110 = Volume: 6
Event Duration: 1200
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
DTMF for call Not completed:
Real-Time Transport Protocol
[Stream setup by SDP (frame 133217)]
[Setup frame: 133217]
[Setup Method: SDP]
10.. .... = Version: RFC 1889 Version (2)
..0. .... = Padding: False
...0 .... = Extension: False
.... 0000 = Contributing source identifiers count: 0
0... .... = Marker: False
Payload type: telephone-event (96)
Sequence number: 811
[Extended sequence number: 66347]
Timestamp: 124240
Synchronization Source identifier: 0xbaca1533 (3133805875)
RFC 2833 RTP Event
Event ID: DTMF One 1 (1)
0... .... = End of Event: False
.0.. .... = Reserved: False
..00 1101 = Volume: 13
Event Duration: 960
+++++++++++++++++++++++
Regards
Guillermo
Thanks a lot for all your help.
Guillermo Zuniga
Especialista de Soporte Técnico
Gerencia de Soporte Técnico
Tel: +507 263-6671
Cel: +507 6670-0481
Fax: +507 265-3295
Email: Guillermo.Zuniga at cwpanama.com
[cid:imagefa7d38.JPG at 9b6060ee.439c3781]<http://www.cwpanama.com>
<http://www.cwpanama.com>
<http://www.cwpanama.com>
<http://play.google.com/store/apps/details?id=com.croem.web.cwp>
<http://www.facebook.com/masmovilpanama>
<http://www.cwpanama.com>
<http://bit.ly/MasMovil>
<http://www.facebook.com/masmovilpanama>
<http://www.facebook.com/masmovilpanama>
[cid:imaged58729.JPG at 3a1cf9fc.46b2fc3c]<http://www.cwpanama.com/>
El contenido de este correo es confidencial y puede ser objeto de acciones legales. Es dirigido solo para el o los destinatarios(s) nombrados anteriormente. Si no es mencionado como destinatario, no debe leer, copiar, revelar, reenviar o utilizar el contenido de este mensaje. Si ha recibido este correo por error, por favor notifique al remitente y proceda a borrar el mensaje y archivos adjuntos sin conservar copias.
The information contained in this e-mail is confidential and may also be subject to legal privilege. It is intended only for the recipient(s) named above. If you are not named as a recipient, you must not read, copy, disclose, forward or otherwise use the information contained in this email. If you have received this e-mail in error, please notify the sender immediately by reply e-mail and delete the message and any attachments without retaining any copies.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.sipforum.org/pipermail/discussion/attachments/20170606/b3ccd012/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imagefa7d38.JPG
Type: image/jpeg
Size: 19006 bytes
Desc: imagefa7d38.JPG
URL: <http://mail.sipforum.org/pipermail/discussion/attachments/20170606/b3ccd012/attachment-0002.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: imaged58729.JPG
Type: image/jpeg
Size: 61675 bytes
Desc: imaged58729.JPG
URL: <http://mail.sipforum.org/pipermail/discussion/attachments/20170606/b3ccd012/attachment-0003.jpe>
More information about the discussion
mailing list