Webrtcomm can't handle 100 Trying after sending MESSAGE

RestComm / webrtcomm

WebRTCComm is a simple high level JavaScript WebRTC framework for Web Developers to add Real Time Communications and IM Capabilities to any website.

http://www.restcomm.com/

GNU General Public License v3.0

18 stars 21 forks source link

Webrtcomm can't handle 100 Trying after sending MESSAGE #59

Closed atsakiridis closed 8 years ago

atsakiridis commented 8 years ago

What happens is:

Olympus sends MESSAGE
Olympus receives 100 Trying
Message connector is closed after 100 Trying is handled and the whole flow is ruined (i.e. 407 Proxy Authentication Required is received but can no longer be handled)

Notice that in the 'regular' flow where no 100 Trying is sent, everything works fine, since the connector is closed after 407 is handled.

Before fixing this make sure that 100 Trying is legit at that point

atsakiridis commented 8 years ago

RFC3261, section 8.2.6.1 says that UAS should not issue a provisional response for a not INVITE request, but since Restcomm complies with the RFC there is no point in fixing that until it breaks for some other server