[asterisk-users] SendImage on SIP channel
Hi, I am using Asterisk 1.6.0.7 and I have a SIP channel configured. I connected a video phone. The sip.conf also has videosupport=yes in the global section. When I use the SendImage application in dialplan, the SENDIMAGERESULT value is set to NOSUPPORT. The phone shows video is enabled and is ready to receive the images. The call is also established with H.263 codec as the video codec. Does asterisk support SendImage on SIP channel? I couldn't find the documentation related to this anywhere. If this is not supported, Is there any other application which can do this? Thanks, Sai Now surf faster and smarter ! Check out the new Firefox 3 - Yahoo! Edition http://downloads.yahoo.com/in/firefox/___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] SendImage on SIP channel
This may be a left-field .02, but it seems that you would need the JPEG codec up on the channel to send an image. -Original Message- From: asterisk-users-boun...@lists.digium.com [mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Tilghman Lesher Sent: Wednesday, April 22, 2009 9:13 AM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: Re: [asterisk-users] SendImage on SIP channel On Wednesday 22 April 2009 03:47:05 Sai P. Varanasi wrote: Hi, I am using Asterisk 1.6.0.7 and I have a SIP channel configured. I connected a video phone. The sip.conf also has videosupport=yes in the global section. When I use the SendImage application in dialplan, the SENDIMAGERESULT value is set to NOSUPPORT. The phone shows video is enabled and is ready to receive the images. The call is also established with H.263 codec as the video codec. Does asterisk support SendImage on SIP channel? I couldn't find the documentation related to this anywhere. If this is not supported, Is there any other application which can do this? SendImage != video. There are features in IAX2 that are not present in any other protocol. One of these is the ability to send a snapshot image across the protocol. Video is something completely different. For video to work on SIP, you must negotiate it on call setup. -- Tilghman ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] SendImage on SIP channel
On Wednesday 22 April 2009 03:47:05 Sai P. Varanasi wrote: Hi, I am using Asterisk 1.6.0.7 and I have a SIP channel configured. I connected a video phone. The sip.conf also has videosupport=yes in the global section. When I use the SendImage application in dialplan, the SENDIMAGERESULT value is set to NOSUPPORT. The phone shows video is enabled and is ready to receive the images. The call is also established with H.263 codec as the video codec. Does asterisk support SendImage on SIP channel? I couldn't find the documentation related to this anywhere. If this is not supported, Is there any other application which can do this? SendImage != video. There are features in IAX2 that are not present in any other protocol. One of these is the ability to send a snapshot image across the protocol. Video is something completely different. For video to work on SIP, you must negotiate it on call setup. -- Tilghman ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] SendImage() to Polycom ip550 or ip670
I tried really quickly the other day to send an image to these phones from the dialplan like this: exten = 2821,n,SendImage(/var/lib/asterisk/images/asterisk-intro) or exten = 2821,n,SendImage(asterisk-intro) It didn't work for me. Should this work? Is anyone else using this with Polycom Phones? Bob ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] SendImage() to Polycom ip550 or ip670
Two things - Polycom phones require specific images sizes (480x180 pixels I thinkg) and the sip.cfg has to allow presentation of images. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bob Pierce Sent: Wednesday, December 10, 2008 1:25 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: [asterisk-users] SendImage() to Polycom ip550 or ip670 I tried really quickly the other day to send an image to these phones from the dialplan like this: exten = 2821,n,SendImage(/var/lib/asterisk/images/asterisk-intro) or exten = 2821,n,SendImage(asterisk-intro) It didn't work for me. Should this work? Is anyone else using this with Polycom Phones? Bob ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] SendImage()
On Sun, Nov 23, 2008 at 10:00 PM, Tilghman Lesher [EMAIL PROTECTED] wrote: On Saturday 22 November 2008 22:18:05 Rob Hillis wrote: Philipp Kempgen wrote: SendImage() in 1.4: ---cut--- SendImage(filename): Sends an image on a channel. If the channel supports image transport but the image send fails, the channel will be hung up. Otherwise, the dialplan continues execution. The option string may contain the following character: 'j' -- jump to priority n+101 if the channel doesn't support image transport This application sets the following channel variable upon completion: SENDIMAGESTATUSThe status is the result of the attempt as a text string, one of OK | NOSUPPORT ---cut--- in 1.6: ---cut--- SendImage(filename): Sends an image on a channel. Result of transmission will be stored in SENDIMAGESTATUS channel variable: SUCCESS Transmission succeeded FAILURE Transmission failed UNSUPPORTED Image transmission not supported by channel ---cut--- Is there any reason to break backwards compatibility? Why is SUCCESS better than OK and UNSUPPORTED better than NOSUPPORT? IMHO there was no need to change anything except for adding the FAILURE return status. This is a case of damned if you do, damned if you don't. That is a perfect complaint, and I understand it completely. On the other side, we are criticized for inconsistent behavior, inconsistent status names, etc. So we've chosen to make Asterisk more consistent going forward, with the one-time problem of a slight change in behavior. Current users see an issue either way, and future users won't see a problem at all. Perhaps somebody from -dev team can be delegated to check naming consistency of new features? So, whenever a feature is added (perhaps at code review), he checks naming to match best of he's opinion. I know that original developers might be stubborn to keep their own names, however that leads to inconsistencies and such changes later. So, if one person is responsible of that, even if change is insignificant, nobody should be offended.. Regards, Atis -- Atis Lezdins, VoIP Project Manager / Developer, IQ Labs Inc, [EMAIL PROTECTED] Skype: atis.lezdins Cell Phone: +371 28806004 Cell Phone: +1 800 7300689 Work phone: +1 800 7502835 ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] SendImage()
On Saturday 22 November 2008 22:18:05 Rob Hillis wrote: Philipp Kempgen wrote: SendImage() in 1.4: ---cut--- SendImage(filename): Sends an image on a channel. If the channel supports image transport but the image send fails, the channel will be hung up. Otherwise, the dialplan continues execution. The option string may contain the following character: 'j' -- jump to priority n+101 if the channel doesn't support image transport This application sets the following channel variable upon completion: SENDIMAGESTATUSThe status is the result of the attempt as a text string, one of OK | NOSUPPORT ---cut--- in 1.6: ---cut--- SendImage(filename): Sends an image on a channel. Result of transmission will be stored in SENDIMAGESTATUS channel variable: SUCCESS Transmission succeeded FAILURE Transmission failed UNSUPPORTED Image transmission not supported by channel ---cut--- Is there any reason to break backwards compatibility? Why is SUCCESS better than OK and UNSUPPORTED better than NOSUPPORT? IMHO there was no need to change anything except for adding the FAILURE return status. This is a case of damned if you do, damned if you don't. That is a perfect complaint, and I understand it completely. On the other side, we are criticized for inconsistent behavior, inconsistent status names, etc. So we've chosen to make Asterisk more consistent going forward, with the one-time problem of a slight change in behavior. Current users see an issue either way, and future users won't see a problem at all. Even the comments made at the time suggesting a parsing tool be provided to point out where changes to dialplan code would be required got a nice idea response, but nothing has been forthcoming. As always, the problem is who is going to write such a tool. The people who are capable of writing such a tool are working on other things (like getting CDRs to an acceptable place or extending bridging code to work better, or lots of other things that will make Asterisk more useful in the future), aren't yet involved in the Asterisk project, or are working on something valuable for their own company. Yes, I think we'd all like to see a parser like that, but who has the time to write it? This habit of breaking functionality for limited or no reason, plus making the results from functions far /less/ useful (note my previous complaints about the REALTIME() function) and more difficult to use is the biggest problem with Asterisk bar none. In 1.6.2, we will introduce REALTIME_FIELD and REALTIME_HASH to solve the problems you've brought up before. These functions are already in trunk, and it shouldn't be too difficult to backport them to 1.4. -- Tilghman ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] SendImage()
SendImage() in 1.4: ---cut--- SendImage(filename): Sends an image on a channel. If the channel supports image transport but the image send fails, the channel will be hung up. Otherwise, the dialplan continues execution. The option string may contain the following character: 'j' -- jump to priority n+101 if the channel doesn't support image transport This application sets the following channel variable upon completion: SENDIMAGESTATUSThe status is the result of the attempt as a text string, one of OK | NOSUPPORT ---cut--- in 1.6: ---cut--- SendImage(filename): Sends an image on a channel. Result of transmission will be stored in SENDIMAGESTATUS channel variable: SUCCESS Transmission succeeded FAILURE Transmission failed UNSUPPORTED Image transmission not supported by channel ---cut--- Is there any reason to break backwards compatibility? Why is SUCCESS better than OK and UNSUPPORTED better than NOSUPPORT? IMHO there was no need to change anything except for adding the FAILURE return status. Might be a -dev question though. Philipp Kempgen -- http://www.das-asterisk-buch.de - http://www.the-asterisk-book.com Amooma GmbH - Bachstr. 126 - 56566 Neuwied - http://www.amooma.de Geschäftsführer: Stefan Wintermeyer, Handelsregister: Neuwied B14998 -- ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] SendImage()
Philipp Kempgen wrote: SendImage() in 1.4: ---cut--- SendImage(filename): Sends an image on a channel. If the channel supports image transport but the image send fails, the channel will be hung up. Otherwise, the dialplan continues execution. The option string may contain the following character: 'j' -- jump to priority n+101 if the channel doesn't support image transport This application sets the following channel variable upon completion: SENDIMAGESTATUSThe status is the result of the attempt as a text string, one of OK | NOSUPPORT ---cut--- in 1.6: ---cut--- SendImage(filename): Sends an image on a channel. Result of transmission will be stored in SENDIMAGESTATUS channel variable: SUCCESS Transmission succeeded FAILURE Transmission failed UNSUPPORTED Image transmission not supported by channel ---cut--- Is there any reason to break backwards compatibility? Why is SUCCESS better than OK and UNSUPPORTED better than NOSUPPORT? IMHO there was no need to change anything except for adding the FAILURE return status. Might be a -dev question though This is typical of the criticism that has been levelled at Digium time and time and time again - making changes that don't really add any functionality, but break compatibility. I had a hell of a time migrating a couple of systems from 1.2 to 1.4 - so much that I have no plans at all in the near future of migrating them from 1.4 to 1.6. Even the comments made at the time suggesting a parsing tool be provided to point out where changes to dialplan code would be required got a nice idea response, but nothing has been forthcoming. This habit of breaking functionality for limited or no reason, plus making the results from functions far /less/ useful (note my previous complaints about the REALTIME() function) and more difficult to use is the biggest problem with Asterisk bar none. ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[Asterisk-Users] SendImage
Hello all, I was wondering if anyone had used SendImage command? And if so with what application, and what phone? It sounds like an interesting command, but few phones support. (If any, as I know of none.) Thanks, James Gardiner ___ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
