Summary:ASTERISK-09919: discrepacy in sendtext
Reporter:Antonio Gallo (agx)Labels:
Date Opened:2007-07-20 11:00:09Date Closed:2011-06-07 14:07:19
Versions:Frequency of
Description:SendText behave in a different way if channell is answered or not and in dependency of the phone used

SendText should be consistent

Example: if channell is answered a GXP2000 display message onto the screen while snom3X0 will not, so add_text in chan_sip.c shoul be changed to address this:

static int add_text(struct sip_request *req, const char *text)
       /* XXX Convert \n's to \r\n's XXX */
       add_header(req, "Content-Type", "text/plain");
       add_header(req, "Content-Disposition", "desktop" );
       add_header_contentLength(req, strlen(text));
       add_line(req, text);
       return 0;

If channell is not answered there should be an option to have SendText answer the channel itself otherwise on GXP2000 it will add the message into the phone's SMS menĂ¹.

I'm not telling SendText that should work how i need, i'm just telling it does not work in the same way on many phones.

IMHO it shoul be splitted in 2 apps: 1 to send the message onto the display (usefull for AOC and other infoes during the call); 1 to send the message into the phone's SMS area (usefull to send reminders and notifications of stuffs happened);


Don't be Lazy and fix this! :-P
Comments:By: Antonio Gallo (agx) 2007-07-20 11:19:53

N.B. on this web based bug system when you go back with any browser button and press OK on there is 99% of genereate a duplicate ticket

By: Joshua C. Colp (jcolp) 2007-07-20 11:22:20

If the channel needs to be answered to work in your environment then you should call Answer before it. As for different behavior and putting into the SMS/on display chan_sip simply sends a MESSAGE packet to the device. It is up to the device how to present it and where to put it.