| Summary: | ASTERISK-09521: dring1 values aren't properly read into asterisk | ||
| Reporter: | Brett Thorson (thor101) | Labels: | |
| Date Opened: | 2007-05-25 13:20:04 | Date Closed: | 2007-05-26 23:14:47 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Core/Configuration |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | with usedistinctiveringdetection enabled, the system should read in the ring values for each of the rings. Here is what I have entered into zapata.conf: dring1=1,2,3 dring1context=incoming dring2=4,5,6 dring2context=incoming dring3=7,8,9 dring3context=incoming Here is the CLI output from asterisk when a call comes in: -- Detected ring pattern: 389,337,147 -- Checking 0,0,3 -- Checking 4,5,6 -- Checking 7,8,9 As you can see, the first set of values are not read into the variable. ****** ADDITIONAL INFORMATION ****** The second and third rings are read in properly, and pattern detection works correctly. | ||
| Comments: | By: Jason Parker (jparker) 2007-05-26 23:14:46 Fixed in svn branch 1.4 in revision 66244 (same patch also fixes issue 9809). Should not be an issue in trunk. | ||