We've looked through our logs.
When using sip.ringcentral.com, we send sip.rincentral.com:5060 an INVITE request, they reject it with a 407 Proxy Authentication Required.
We send back a new INVITE with Proxy-Authorization credentials and they reject with a 407 Proxy Authentication Required. We repeat the request and the cycle continues until the call times out.
This could be caused by an incorrect username or password.
When using sip.ringcentral.com:5090, we send sip.rincentral.com:5060 an INVITE request, they reject it with a 408 Request Timeout. We return busy signal to the caller.
We're not sure why they are returning the 408. It happens before any authentication information is exchanged, so we can't say it's a username or password problem.
In both cases, ringcentral would have to provide more information about what their logs are saying and why they are returning 407 and 408 codes.
|