[asterisk-bugs] [JIRA] (ASTERISK-27726) chan_mobile: presents incorrect inbound Caller-ID names

[Brian (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-27726?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=242821#comment-242821 ] 

Brian commented on ASTERISK-27726:
----------------------------------

Initial coding is complete and I expect to test and debug this week and next as time permits.  

If anyone following this issue can direct me to formal syntax specifications for the AT+CLIP message that contains the caller-ID information, that would be helpful.  I've researched ITU-T specifications, but they don't seem to drill down to specific fields and syntax.  CNAM is typically found in field 5, but one document out of Australia seemed to indicate that fields 2 and 3 are sometimes not present (including the field separator), which would move CNAM back to field 3.  I'm coding based on what specifications and samples I can find, but a source of formal documentation might prevent future bugs.

> chan_mobile: presents incorrect inbound Caller-ID names
> -------------------------------------------------------
>
>                 Key: ASTERISK-27726
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27726
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Addons/chan_mobile
>    Affects Versions: 13.19.1, 14.7.6, 15.2.2
>            Reporter: Brian
>            Assignee: Unassigned
>            Severity: Minor
>
> chan_mobile requires that each cell phone be defined in chan_mobile.conf with unique name (e.g. "iphone").  I observed that when presenting inbound caller ID information, chan_mobile always presents the name of phone that received the call instead of the name of the caller.  So a call from "John Smith" at 505-555-5555 is presented as a call from "iphone" at 505-555-5555.
> Looking into the source code, I see that hfp_parse_clip parses out the caller ID number, but does not attempt to parse out the optional caller ID name.  
> Later in the code, the ast_channel routine calls ast_channel_alloc to create the channel.  When it does this it provides the cell phone name (e.g. “iphone”) as the fourth parameter, where the caller ID name should really belong (or a null string if caller ID name is not provided, so the dial plan can use alternate databases to retrieve a name).
> These portions of the code have not changed in versions 14.x or 15.x, so the problem presumably also appears there, though I don't have an environment to test with.
> This is an initial issue report.  I intend to develop a patch that I will submit for review through Gerrit.



--
This message was sent by Atlassian JIRA
(v6.2#6252)