| Summary: | ASTERISK-02677: asterisk says telephone-event when apps want to hear PCMU. | ||
| Reporter: | dgilbert (dgilbert) | Labels: | |
| Date Opened: | 2004-10-25 18:11:17 | Date Closed: | 2011-06-07 14:10:29 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/Interoperability |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | specifically, I've come up against three different SIP speakers (one of which I can't modify) that expect to know ulaw as a=rtpmap:0 PCMU/8000/1 and asterisk stubbonly reports a=rtpmap:101 telephone-event/8000 in SIP/SDP packets when it intends to be sending PCMU (ulaw) packets. ****** ADDITIONAL INFORMATION ****** shtoom is a good example of an application that does not understand the asterisk 1.0 behaviour. | ||
| Comments: | By: Brian West (bkw918) 2004-10-25 20:47:20 Full sip debug is needed I think you're mixing up an issue here. bkw By: Brian West (bkw918) 2004-10-25 21:18:00 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 1. rtpmap:0 is PCMU 2. rtpmap:101 is telephone-events such as DTMF. how is this a bug? By: Mark Spencer (markster) 2004-10-25 21:47:27 This is a configuration issue and not a bug. | ||