| Summary: | ASTERISK-16805: Remote-Party-ID instead of RFC 4916 (From change)? | ||
| Reporter: | Iñaki Baz Castillo (ibc) | Labels: | |
| Date Opened: | 2010-10-13 06:47:20 | Date Closed: | 2011-06-07 14:00:54 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Channels/chan_sip/NewFeature |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | I've realized that Asterisk 1.8 introduces "hot CLI change" during a dialog by making usage of the old, deprecated, obsoleted and never standarized Remote-Party-Id header. I can understand this as a workaround to make the feature work with today's (and yesterdays) phones. But why is RFC 4916 not implemented at the same time? If the phone announces "Support: from-change" then Asterisk could change the From header rather than using Remote-Party-Id. Is it hard to implement? is it planned? I know about new phones implementing RFC 4916 and not implementing Remote-Party-ID. Do we want out modern Asterisk to give support just for old phones? :) | ||
| Comments: | By: Leif Madsen (lmadsen) 2010-10-13 12:54:33 I consider this a feature request without a patch. While yes, it would probably be ideal that Asterisk supported RFC 4916, the fact is it doesn't and no one has come up with a patch to support such functionality. By: Leif Madsen (lmadsen) 2010-10-13 13:00:01 Spoke with a couple of developers and they agree this is a feature request. It was mentioned we also support P-Asserted-Identity. | ||