Summary: | ASTERISK-08411: No inbound CallerID when Distinctive Ring Detection is enabled. | ||
Reporter: | Rusty Newton (rnewton) | Labels: | |
Date Opened: | 2006-12-21 11:37:12.000-0600 | Date Closed: | 2011-06-07 14:07:48 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Core/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | Whenever the option usedistinctiveringdetection= is set to "yes" the system will not properly receive CallerID, it will just show "unknown" as the callerID. I have only tested this using Asterisk with Digium Hardware. ****** ADDITIONAL INFORMATION ****** Some customers have the same issue, but on some of their systems, the CallerID will be passed through occasionally, or only on certain distinctive ring patterns. | ||
Comments: | By: Rusty Newton (rnewton) 2006-12-21 11:38:57.000-0600 I was referring to the usedistinctiveringdetection= in zapata.conf obviously but I forgot to specify. By: Dave Bowerman (dbowerman) 2007-01-30 00:57:21.000-0600 fixed in 1.4 with distinctiveringaftercid=yes in zapata.conf By: Serge Vecher (serge-v) 2007-02-02 12:46:17.000-0600 thanks for the note, dbowerman. Rnewton, please move to 1.4 and use the new feature introduced there. Thanks. |