180 Ringing and early media sent to early

[GoogleCodeExporter]

WebRTC2SIP sends and 180 Ringing response to the browser, before it even 
forwarded the INVITE to the network. It also sends a ring tone via early media, 
before it even forwarded the INVITE to the network. This leads to a degraded 
user experience, because when the call is declined immediately (i.e. because 
the B party is not found or offline), the A party may think that a call was 
signaled to the B party and the B party pressed a decline button on their user 
equipment, i.e. the distinction between the case, where the B party declined 
the call actively and the case, where the B party is offline, is blurred.

WebRTC2SIP should send the 180 Ringing/183 Session Progress no sooner than the 
180 Ringing/183 Session Progress from the network arrives. It also should not 
send early media sooner.

Original issue reported on code.google.com by emil.kro...@gmail.com on 8 Apr 2013 at 8:55

[GoogleCodeExporter]

Original comment by boss...@yahoo.fr on 8 Apr 2013 at 2:47

• Changed state: Accepted

[GoogleCodeExporter]

+1, I'm having this issue as well

Original comment by palma.pi...@gmail.com on 18 Jul 2013 at 12:54