Skip to main content

We have an issue that ring central is sending 200 OK signal right away  even when no one has answered the  call. It’s messing with our call center forwarding. Any idea why RC is sending that signal when the phone hasn't been answered yet. This issue exists  on the call queue and direct line calls.

have answered this in 

 


have answered this in 

 

Thank you, ​@martintsankov!


We have an issue that ring central is sending 200 OK signal right away  even when no one has answered the  call. It’s messing with our call center forwarding. Any idea why RC is sending that signal when the phone hasn't been answered yet. This issue exists  on the call queue and direct line calls.

Let me know how do you detect the “Answered” status (via telephony session event notification?) and what is the purpose to use the “200 OK” signal. I might have a work-around solution for you.


The developer at our callcenter detected the 200 ok signal as the problem when doing testing on the issue. Essentially all calls are registering as answered right away. So they dont pick it up the call. What is a work around?

 

Thanks


The developer at our callcenter detected the 200 ok signal as the problem when doing testing on the issue. Essentially all calls are registering as answered right away. So they dont pick it up the call. What is a work around?

 

Thanks

Well, first of all, you wrote “our call center” is that using RingCX or RingEX service? If it’s RingCX, then I don’t have any solution for it. You mentioned “the developer” so how did he detect the “answered” status. Please give me some technical details around the code where the developer detects a call and check the status of the call.