| Summary: | ASTERISK-26454: CallerID for BLF Not Displaying Number or Name | ||||
| Reporter: | Andi Topp (comfine) | Labels: | |||
| Date Opened: | 2016-10-10 06:41:01 | Date Closed: | 2016-10-10 07:21:46 | ||
| Priority: | Major | Regression? | |||
| Status: | Closed/Complete | Components: | Core/CallerID | ||
| Versions: | 13.11.2 | Frequency of Occurrence | Constant | ||
| Related Issues: |
| ||||
| Environment: | FreePBX, Asterisk is patched to 13.11.2 | Attachments: | |||
| Description: | The Notification Messages doesn't contain the Name or CallerID of the Caller, but contains instead the Number of the Requesting Extension.
In Asterisk 12 an inbound call sends the following: <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="101" state="full" entity="sip:300@10.8.0.1"> <dialog id="300" call-id="pickup-1291033974@10.8.0.6" local-tag="1346047910" remote-tag="as29d68671" direction="recipient"> <remote> <identity display="300">sip:300@10.8.0.1</identity> <target uri="sip:300@10.8.0.1"/> </remote> <local> <identity display="300">sip:300@10.8.0.1</identity> <target uri="sip:300@10.8.0.1"/> </local> <state>early</state> </dialog> </dialog-info> Running Asterisk 11 it shows: <?xml version="1.0"?> <dialog-info xmlns="urn:ietf:params:xml:ns:dialog-info" version="61" state="full" entity="sip:300@10.8.0.1"> <dialog id="300" call-id="pickup-940919781@10.8.0.6" local-tag="1210254278" remote-tag="as67bec903" direction="recipient"> <remote> <identity display="J SMITH">sip:4159962869@10.8.0.1</identity> <target uri="sip:4159962869@10.8.0.1"/> </remote> <local> <identity display="Naomi">sip:300@10.8.0.1</identity> <target uri="sip:300@10.8.0.1"/> </local> <state>early</state> </dialog> </dialog-info> The Bug was already filed under FreePBX: http://issues.freepbx.org/browse/FREEPBX-8209 | ||||
| Comments: | By: Asterisk Team (asteriskteam) 2016-10-10 06:41:02.073-0500 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. By: Andi Topp (comfine) 2016-10-10 06:56:17.670-0500 also this forum-post handles the same topic: http://forums.asterisk.org/viewtopic.php?f=1&t=94062 it contains the necessary codechanges! it would be great if you can fix this soon, as this is a mayor problem for our customers. | ||||