Summary:ASTERISK-04434: Zaptel T1 sending double digits
Reporter:Fred Gillette (ajgillette98)Labels:
Date Opened:2005-06-17 14:01:25Date Closed:2008-01-15 15:38:32.000-0600
Versions:Frequency of
Environment:Attachments:( 0) asterisk.txt
Description:RFC2833 specifies that the time-stamp on all packets associated with the transmission of a digit must remain the same. My asterisk is incrementing the timestamp by one milli-second when it adds the end bit on the last three packets.


I have uploaded an ethereal capture see packets 236-241
Comments:By: Fred Gillette (ajgillette98) 2005-06-17 14:06:37

This is my first submission and I messed up the catagory. It should be code not comments. Sorry about that. It should also be major not minor because I can't dial other SIP IVR systems from the asterisk

By: Brian West (bkw918) 2005-06-17 14:52:23

get an RTP debug.  "rtp debug" while making ia call.


By: Fred Gillette (ajgillette98) 2005-06-17 14:59:48

The attached ethereal trace shows the RTP packets. Check out packets 236 to 241 and you will see the time stamp change. The trace was captured on my MKC7000 server which is talking to the Asterisk. Packets 236,237,238 have timestamps of 16160 and packets 239.240,241 have timestamps of 16161.

By: Mark Spencer (markster) 2005-06-18 13:10:46

Okay, fixed in CVS.  The timestamp increment was labeled a sipura fix, but i also believe the proper behavior not to include incrementing the timestamp.

By: Russell Bryant (russell) 2005-06-21 18:57:52

this does not appear to be an issue in 1.0

By: Digium Subversion (svnbot) 2008-01-15 15:38:32.000-0600

Repository: asterisk
Revision: 5935

U   trunk/rtp.c

r5935 | markster | 2008-01-15 15:38:32 -0600 (Tue, 15 Jan 2008) | 2 lines

Revert silly "sipura fix" which breaks RFC compatibility (bug ASTERISK-4434)