Letractively / webrtcomm

Automatically exported from code.google.com/p/webrtcomm
GNU General Public License v3.0
0 stars 0 forks source link

New feature: use SIP MESSAGE request to send message #11

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Provide API to send message based on SIP MESSAGE request, not only DataChannel. 
 Possibility to send a message outside a call context (eg. no call ongoing).

Original issue reported on code.google.com by laurent.strullu.orange@gmail.com on 5 Sep 2013 at 3:08

GoogleCodeExporter commented 8 years ago

Original comment by laurent.strullu.orange@gmail.com on 25 Sep 2013 at 9:07

GoogleCodeExporter commented 8 years ago
linked to r0d78761ba7cd

Original comment by jean.deruelle on 27 Sep 2013 at 9:06

GoogleCodeExporter commented 8 years ago
Laurent, 

I have a case where the SIP Servlets app between the 2 browsers sends back a 
100 Trying Message Sent once it has forwarded the MESSAGE. but this will 
trigger the call to onWebRTCommMessageSendErrorEvent. 
I think the line 
https://code.google.com/p/webrtcomm/source/browse/src/WebRTComm/PrivateJainSipMe
ssageConnector.js?spec=svn0d78761ba7cd6009f5da236fd6d902b089696964&r=0d78761ba7c
d6009f5da236fd6d902b089696964#124 should be replaced with if (statusCode >= 100 
&& statusCode < 300) {

or have another state for informational response such as message in progress or 
message being delivered

Original comment by jean.deruelle on 27 Sep 2013 at 9:11

GoogleCodeExporter commented 8 years ago
This issue was updated by revision 9bb8ceb960ce.

Fix for handling other 2xx responses and 1xx responses. If 1xx needs a 
differentcallback this will be reopened or done under a different issue

Original comment by jean.der...@telestax.com on 9 Oct 2013 at 1:08

GoogleCodeExporter commented 8 years ago

Original comment by jean.deruelle on 9 Oct 2013 at 1:08