Summary:	ASTERISK-06785: Channel.h (etc) supports sending text, html, and images, but not receiving them
Reporter:	mtaht (mtaht)	Labels:
Date Opened:	2006-04-14 15:08:20	Date Closed:	2011-06-07 14:08:08
Priority:	Minor	Regression?	No
Status:	Closed/Complete	Components:	Core/General
Versions:		Frequency of Occurrence
Related Issues:
Environment:		Attachments:
Description:	Looking over the channel drivers, I see that you can send messages/urls/images via the dialplan, but there is no callback mechanism for receiving them in ast_channel_tech et. al. (get_html,get_text,get_image prototypes don't exist) ****** ADDITIONAL INFORMATION ****** In my case, I have a string of tests executing through multiple paths on random, undefined in advance machines and running on different codecs. It's kind of impossible to know where a call is at any given moment. While I've been rolling a dtmf based protocol for those tests, it would be easier if I could send arbitrary messages back and forth between over iax (inter-asterisk-control-protocol anyone?). You can send messages in asterisk... but no receive them.... Now a theoretically message receiver would have to operate in a couple modes Queued (messages acknowledged to the sending host, stored in a circular (?) buffer) end-to-end-forward (not acked until it reaches furthest destination) spied-but-forwarded and there would need to be a dialplan function and variable or five ${HAVE_MESSAGES} ${HAVE_MESSAGE_COUNT} ${HAVE_MESSAGE(url}} $(HAVE_MESSAGE(text)} ${HAVE_MESSAGE(image)} ,get_text,get_url,get_image) or something along those lines. Has this been discussed anywhere? I saw that the firefly client used some extensions here... A per channel message receiving/intercepting function could also be a callback in the dialplan, and boy, generic callbacks would be useful there... No, aside from looking over the callbacks and writing this up I haven't written any code....
Comments:	By: Russell Bryant (russell) 2006-04-15 17:56:53 If you would like to check out some existing work that moves us in this direction, check out bug 5372. There are significant architecture changes that need to be decided upon before we can fully implement this.  If you would like to discuss options for doing this, I urge you to post your ideas to the asterisk-dev mailing list, and not on the bug tracker.  Thanks!