[asterisk-bugs] [JIRA] (ASTERISK-24406) Some caller ID strings are parsed differently since 11.13.0
Kinsey Moore (JIRA)
noreply at issues.asterisk.org
Fri Oct 10 07:59:29 CDT 2014
[ https://issues.asterisk.org/jira/browse/ASTERISK-24406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kinsey Moore closed ASTERISK-24406.
-----------------------------------
> Some caller ID strings are parsed differently since 11.13.0
> -----------------------------------------------------------
>
> Key: ASTERISK-24406
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-24406
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Core/CallerID
> Affects Versions: 11.13.0
> Reporter: Etienne Lessard
> Assignee: Kinsey Moore
> Severity: Critical
> Attachments: callerid_fix.diff
>
>
> This is something we have observed when upgrading from asterisk 11.12.1 to asterisk 11.13.0.
> Basically, we are doing some originate for which we specify the caller ID.
> In asterisk 11.12.0, when we pass the caller ID {{"*10"}}, then it is splitted into:
> * name: {{*10}}
> * location: null
> Starting from asterisk 11.13.0, if we pass the same caller ID, then it is splitted into:
> * name: null
> * location: {{*10}}
> To get the same behaviour as in asterisk 11.12.0, we must pass {{"*10" <>}} as the caller ID.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list