| Summary: | ASTERISK-10399: Add context field to app_meetme.so application for realtime mode | ||
| Reporter: | german aracil boned (tecnoxarxa) | Labels: | |
| Date Opened: | 2007-09-27 18:31:56 | Date Closed: | 2011-06-07 14:02:55 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_meetme |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) meetme_add_realtime_context.patch | |
| Description: | I add context field to meetme table. Only need add context field of type varchar(32) Now, meetme can get same number confroom for distincts contexts. | ||
| Comments: | By: german aracil boned (tecnoxarxa) 2007-09-27 18:33:23 I'm tested this with a good results. By: german aracil boned (tecnoxarxa) 2007-09-27 19:04:27 Revision: 83726 By: Tilghman Lesher (tilghman) 2007-11-06 13:48:43.000-0600 1) You should not be using the channel context for the meetme context. If you want a context, you should be inputting it in the arguments, just like Voicemail does contexts. The context should default to "default" if not otherwise specified. 2) Since realtime is in Meetme in 1.4, you need to ensure that existing tables don't suddenly fail if the context field does not exist. Note that ast_update_realtime() returns -1 if the query fails. Use that to retry the update without the context field. You may choose to issue a warning at this point, too, if you think that not having a context field should be deprecated. 3) This patch no longer applies to trunk. By: Tilghman Lesher (tilghman) 2007-12-07 12:57:31.000-0600 No response from reporter | ||