| Summary: | ASTERISK-24406: Some caller ID strings are parsed differently since 11.13.0 | ||
| Reporter: | Etienne Lessard (hexanol) | Labels: | |
| Date Opened: | 2014-10-09 13:38:16 | Date Closed: | 2014-10-10 07:57:46 |
| Priority: | Critical | Regression? | Yes |
| Status: | Closed/Complete | Components: | Core/CallerID |
| Versions: | 11.13.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Attachments: | ( 0) callerid_fix.diff | |
| Description: | 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. | ||
| Comments: | By: Kinsey Moore (kmoore) 2014-10-09 13:43:16.319-0500 I have attached a patch that should fix this issue and a corresponding unit test to make sure it doesn't break again. By: Etienne Lessard (hexanol) 2014-10-09 13:54:44.181-0500 The patch does fix my use cases. Thank you. | ||