[asterisk-bugs] [Asterisk 0018131]: Remote-Party-ID instead of RFC 4916 (From change)?
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Oct 13 13:00:02 CDT 2010
The following issue has been UPDATED.
======================================================================
https://issues.asterisk.org/view.php?id=18131
======================================================================
Reported By: ibc
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 18131
Category: Channels/chan_sip/NewFeature
Reproducibility: always
Severity: feature
Priority: normal
Status: closed
Asterisk Version: 1.8.0-rc3
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Request Review:
Resolution: no change required
Fixed in Version:
======================================================================
Date Submitted: 2010-10-13 06:47 CDT
Last Modified: 2010-10-13 13:00 CDT
======================================================================
Summary: Remote-Party-ID instead of RFC 4916 (From change)?
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? :)
======================================================================
Issue History
Date Modified Username Field Change
======================================================================
2010-10-13 13:00 lmadsen Resolution open => no change
required
======================================================================
More information about the asterisk-bugs
mailing list