| Summary: | ASTERISK-19391: Unable to edit From Caller Name with RPID | ||||
| Reporter: | Krzysztof Chmielewski (kristoff) | Labels: | |||
| Date Opened: | 2012-02-20 09:40:17.000-0600 | Date Closed: | 2012-02-21 07:26:22.000-0600 | ||
| Priority: | Major | Regression? | Yes | ||
| Status: | Closed/Complete | Components: | |||
| Versions: | 1.8.9.2 | Frequency of Occurrence | |||
| Related Issues: |
| ||||
| Environment: | Attachments: | ||||
| Description: | When using RPID header with CallerID set to prohibit we cannot edit the From Caller Name filed. Furthermore Asterisk 1.8 sets the value of this filed to asterisk. According to http://tools.ietf.org/html/draft-ietf-sip-privacy-00 in this case, Caller Name Filed should be left blank. So it would be helpful if we could change this value from DialPlan/AGI. Dial Plan: exten => 111,1,Set(CALLERID(name-pres)=prohib) exten => 111,n,Set(CALLERID(num-pres)=prohib) exten => 111,n,Set(CALLERID(name)=Hello) exten => 111,n,Dial(SIP/+48xxxxxxxxx@ffff) Peers configuration is from Real Time. Peer ffff has rpid=rpid flag. INVITE Debug: INVITE sip:+48xxxxxxxxx@sip.freeconet.pl:5060 SIP/2.0 Via: SIP/2.0/UDP 10.0.4.52:5060;branch=z9hG4bK55074a83;rport Max-Forwards: 70 From: "asterisk" <sip:login1@sip.freeconet.pl>;tag=as63cff618 To: <sip:+48xxxxxxxxx@sip.freeconet.pl:5060> Contact: <sip:xxxx@10.0.4.52:5060> Call-ID: 3bd0220e5442f6226379f7613ceb1c0b@sip.freeconet.pl CSeq: 102 INVITE User-Agent: IP PBX Date: Mon, 20 Feb 2012 15:34:53 GMT Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH Supported: replaces, timer Remote-Party-ID: "Hello" <sip:test001@sip.freeconet.pl>;party=calling;privacy=full;screen=yes Content-Type: application/sdp Content-Length: 271 | ||||
| Comments: | By: Matt Jordan (mjordan) 2012-02-21 07:26:15.531-0600 This is not a bug. In the context of the draft RFC you referenced, Asterisk follows closest to "uri" or "full" privacy, wherein: * From: The UAC SHOULD supply a cryptographically random identifier for the userinfo, and a non-identifying hostname, e.g. "localhost", in the host name. In our case, we use "asterisk". You'll note that your "name" field that you specified is included in the Remote-Party-ID field. By: Maciej Krajewski (jamicque) 2012-02-21 08:17:29.258-0600 In my opinion nevertheless ability not to change "asterisk" in from field is a bug. Please notice that it is a regression na asterisk 1.6 did not put anything in user name from field. Which in my opinion none username in this situation is better than hardcoded asterisk. | ||||