Error handling

Top  Previous  Next

Web-server prohibits connection and sends back the 403 FORBIDDEN status

 

connection_403_v2

 

B
R
O
W
S
E
R

<<< IN

OUT >>>

W

C

S

<<< IN

OUT >>>

W

E

B

S

E

R

V
E

R

 

1. connect

 

urlServer

appKey

 

sipRegisterRequired

sipLogin

sipVisibleName

sipAuthenticationName

sipPassword

sipDomain

sipOutboundProxy

sipPort

sipContactParams

mediaProviders

status

 


 

 


2. connect

 

urlServer

sipRegisterRequired

sipLogin

sipVisibleName

sipAuthenticationName

sipPassword

sipDomain

sipOutboundProxy

sipPort

sipContactParams

mediaProviders

status

 

nodeId

sessionId

appKey

 

 

3. 403 FORBIDDEN


 

 


4. ConnectionStatusEvent - FAILED

 

status

info

 

nodeId

sessionId

appKey

 

 

5. 200 OK

 

status

info


6. ConnectionStatusEvent - FAILED

 

status

info

 




 


7. ConnectionStatusEvent - DISCONNECTED

 

status

info

 

nodeId

sessionId

appKey


 

8. 200 OK

 

status

info


9. ConnectionStatusEvent - DISCONNECTED

 

status

info

 



 

An error occurs on the server preventing continuation of connection establishing

 

For example, if a non-existing application appKey is passed, WCS is unable to locate a corresponding application and returns ConnectionStatusEvent with the description of the error and the FAILED status. The same happens in case of other unpredictable errors occur while connecting.

 

connection-error

 

B
R
O
W
S
E
R

<<< IN

OUT >>>

W

C

S

<<< IN

OUT >>>

W

E

B

S

E

R

V
E

R

 

1. connect

 

urlServer

appKey

 

sipRegisterRequired

sipLogin

sipVisibleName

sipAuthenticationName

sipPassword

sipDomain

sipOutboundProxy

sipPort

sipContactParams

mediaProviders

status

 


 

 

EXCEPTION


2. ConnectionStatusEvent - FAILED

 

status

info

 



3. ConnectionStatusEvent - DISCONNECTED

 

status

info