Summary:	ASTERISK-09647: adding labels to realtime
Reporter:	RogerCasaponsa (casix)	Labels:
Date Opened:	2007-06-11 11:35:50	Date Closed:	2011-06-07 14:02:38
Priority:	Major	Regression?	No
Status:	Closed/Complete	Components:	Core/NewFeature
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	Hi all, I'm migrating a standard asterisk configuration to realtime. The biggest trouble that I have is that in realtime there is no labels, you cannot do: [some_context] ... ... exten => 1111,3,Goto(label) ... ... exten => 1111,10(label),NoOp(jumped to label) It is possible to implement that in realtime?? In the documentation the field priority is numeric and the query that asterisk do is: SELECT * FROM realtime_table WHERE exten = '1111' AND context = 'some_context' AND priority = '2' I don't know if changing the priority field to varchar and the query to: SELECT * FROM realtime_table WHERE exten = '1111' AND context = 'some_context' AND ( priority = '2' OR priority = '2(%)' ) it would be solved or if it needs more internal changes.
Comments:	By: Tilghman Lesher (tilghman) 2007-06-11 13:25:02 It's unlikely to happen.  We already have massive problems with PBX realtime, which necessitates a complete redesign in an upcoming version. By: Tilghman Lesher (tilghman) 2007-06-11 14:10:42 In fact, I'd strongly recommend that you look into making your dialplan dynamic through other means (such as func_odbc in 1.4) and dispose of using pbx_realtime altogether. By: Leif Madsen (lmadsen) 2007-06-12 10:08:33 Agreed with Corydon. Keeping your dialplan in the database is not really necessary, or would really even be advised. Utilizing something like func_odbc where you keep most of the dialplan static, and make the information dynamic from the database that way. By: Leif Madsen (lmadsen) 2007-06-12 10:19:48 Since this is a feature request, and one which is better solved with existing solutions, I'm closing this.