I set up a new hosted system and there seems to be a problem with the queues. When a caller is answered from a ringall queue, that call continues to ring on all the other extensions for 2 seconds.
This occurs on every call, and on every queue. I was able to replicate this at my home office so I thought it wasn’t network related. But I found if the only two phones in the queue are the two phones I have at my home office, everything works fine. If I add just one extension from the customer site, then that delayed ring occurs on my phones. Even if I’m the one who answered the call.
They use Yealink T54w devices.
Has anyone seen this before? I’m pretty sure my troubleshooting has lead me to believe its a network related issue(not my network. Its a town library). I want to be able to point their IT department in the correct direction instead of just pointing to them.
They also reported some(not all) blind transfers show the internal extensions CID on the ringing phone instead of the external phone number. I haven’t been able to troubleshoot this yet though. Just added it incase it could be related.
That will happen if the phone actually implements blind transfer as an automated attended transfer, which some do. (Send a new invite, and automatically send refer replaces when notified that the call is answered.
User answers the call, presses a BLF key for another user, then either hangs up or presses the B Transfer softkey on the yealink phone, then hangs up.
When you say “phone actually implements blind transfer as an automated attended transfer,” is that a setting in the phone/system, or something the user is doing?
That’s almost certainly implemented as an attended transfer, although the REFER probably happens when they press the transfer key. I’d expect an INVITE will be sent when they hit the BLF field, and the INVITE will contain no information about the other call on the phone. Asterisk will set up the call to the new destination based on the INVITE, just as for any outgoing call from the phone.
To actually pass over the original caller ID, the phone needs to send REFER, without replaces, as the first thing it does, and not send INVITE, at all. I suspect you don’t get a choice on that, within any particular phone brand.
The only way out is probably to use a feature code transfer, in which case the feature code is sent before the digits, and the digits have to be sent as DTMF or equivalent.
To confirm it, you would need to do a packet capture, and see what is sent for the BLF key press and the Transfer button press.
Could you be a bit more detailed about this. I don’t understand how ringing doesn’t stop immediately on the phone that answers, unless you somehow have two lines ringing on the same phone.
Apart from that, I don’t think you can avoid some overrun of ringing on the other phones, but the question is whether the network delays are large enough to take up 2 seconds. OK needs to get back and CANCEL needs to go forwards, even if no first transissions are lost.
Could you be a bit more detailed about this. I don’t understand how ringing doesn’t stop immediately on the phone that answers
Sorry, I have two phones set up on my desk. I answer the incoming call on one of the phones, and the other phone continues to ring. The phone who answered the call stops immediately.
I don’t think you can avoid some overrun of ringing on the other phones
I understand this, but its a full 2 Mississippi’s.
question is whether the network delays are large enough to take up 2 seconds
I ran jitter, latency and packet loss tests on their network. results were perfectly fine. If I get a pcap, would you be able to analyze it?