| Summary: | ASTERISK-06534: [Feature Request]: uniqueid in RDNIS | ||
| Reporter: | Christian Benke (christianbee) | Labels: | |
| Date Opened: | 2006-03-13 04:09:16.000-0600 | Date Closed: | 2011-06-07 14:03:22 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | for billing purpose, i'd like to be able to associate a redirected call to the initiating call-leg. the second call-leg has to be paid by the person the call was targeted at, but who redirected it e.g. to a zap-destination. since the billseconds are written to the first call-leg, i need to find out which record the second call-leg belongs to. currently i do this pretty ugly by writing a key(as variables EPOCH & EXTEN) with the value 'uniqueid' to the ast-db and rereading it on the second call-leg by searching the key with the RDNIS-Variable(was EXTEN on first call-leg) in a epoch-range of 60 seconds(With a loop) - then i can read the uniqueid, write it to the userfield and bill it later. if the uniqueid of the first call-leg was written to the RDNIS-Variable already, this would be a lot easier, cleaner and accurate. Unfortunately i can't code C, maybe someone has the time to add the required code? thanks in advance! regards chris | ||
| Comments: | By: Tilghman Lesher (tilghman) 2006-03-13 07:50:47.000-0600 Feature requests do not belong on the bugtracker. Please submit your suggestion to the Wiki. You may reopen this bug when there is a prospective patch. | ||