0

Call Waiting not working (ticket submitted to support)

Larry Neblett

April 26, 2020 12:05

None

Follow

Yeastar made a decision to remove the call waiting function from the PBX, which, by the way, is a gross mistake. Instead they rely upon the phone to respond to the INVITE sent to let the system know if it is capable. 

When testing with a supported Fanvil X7 with multiple lines set to the same extension I am able to call out any/all lines at the same time, the inbound ability to handle multiple simultaneous calls is not functioning. 

I can busy out a line to an account and then call from another extension to the same extension/account that is busy, but the PBX never sends the INVITE according to the pcap trace. The PBX instead responds with a busy as I do not VM enabled while testing.  As a result, it does not seem possible to accommodate more than one inbound call using the X7. I cannot attest to this being the case with other phones....yet. 

 

• Facebook
• Twitter
• LinkedIn

2 comments

• 0
  
  Oscar Colka April 28, 2020 03:34

  Larry, seems like they have a setting name “All busy mode for SIP Forking”, this setting, to my understanding, it is similar to the function of call waiting. But this is a global setting for all the extensions though. Do you need to enable or disable call waiting for some specific extensions?

  

• 1
  
  Larry Neblett June 06, 2020 12:37

  Hi Oscar, 

   

  Support and I have had some discussions about it to include SIP forking. They have confused call waiting with SIP forking. 

  So as the hint for SIP forking indicates, the "other terminals" which I don't think should mean the one I am on and have an active call. So, when I am on a call at a given extension and have other phones elsewhere registered to the same extension, the system sees my extension as in a call and then treats my extension the same as as others. True, the other phones will not ring, but why is the call not being sent to the extension in use?  That is not SIP forking, this is call waiting and does not coincide with their announcement that they are now relying on the phone to handle the call waiting aspect. The system never sends the INVITE. My thought is that before, YS had the call waiting setting in the system, so it seems obvious that the system can see which extension is in a call. Using the SIP forking setting, I was of the impression that the system would see which of the extensions IPs associated to the INVITE were busy in a call and then send the second call to same while not sending to the others (forking). As they changed the call waiting aspect, if my phone sees the INVITE and is set to accept multiple calls, it takes the call whereupon I can elect to answer or reject. If not set for multiple, the 486 is sent back to the system and the rules for busy occur. 

  Additionally, assume that I only have the one extension, and others have more than one. If the SIP forking setting is enabled, does that not also imply, given its current implementation, that the system will not send me the second call although my phone is perfectly capable of multi-call handling? This is what happened in my testing with the X7. 

  It's actually a pretty cool feature. I only question how SIP forking comes into play? SIP forking is when a single call is sent to multiple registered devices. I had a single call (x2) go to a single device with multiple line appearances, not multiple registrations. The system stopped the 2nd call. 

   

  I disabled the forking setting for the time being. I would like to see them refine it.