Overview 

OnSIP Groups are used to build simple teams of users. Groups are typically setup with people of a similar function, e.g., sales, support, billing, etc. Typically, a group is called from an Auto Attendant. 

Setup 

Log into https://app.onsip.com/. On the right side of the screen select “Administrators”. Scroll down to “Inbound Call Settings” then choose “Groups”. 

 

 

Next, on the right side click “Add Group”. In the Basic Settings, you will give your group a name, set the ring strategy, the ring duration, add extensions and phone numbers for your group. If you hover over the icon, this will provide information about things like Ring strategy, duration and failover which is very helpful. 

Click Next to go to the Add Users tab. Here you can add users to the group by searching by the name in the search option at the top or clicking on the checkbox by the name below.   

 

To proceed to the final review, click Next. From here you can make any final edits if needed, Cancel go Back or Safe & Finish Setup.  

 

Notable Points 

• A group is limited to 10 members. More than 24 registrations in a simultaneous ring group will cause the call to fail. 
• A group may have, at most, 3 external phone numbers not mixed in a Group of Users.  A group with this setup can only be set as a Hunt Group; Simultaneous Ring will not provide a consistent experience.
• In the case of a Hunt Group: For a User with multiple devices, each registered device will ring independently before moving on to the next User listed in the group. 

  

Technical Details/Timing 

If the group is set for Simultaneous Ring, the "Ring Each" timeout refers to the call in general. We will try all registrations for all users in the group for the duration of the timeout at which point we will fail over to the failover location. The max failover timeout is 120 seconds for groups. ACD Queues can have longer timeouts. 

If the group is set for Hunt (meaning sequential ringing), each registration is a call branch (not each user - if a user has multiple registrations, we will try each registration instance separately) and the timeout set in the "Ring Each" section refers to each branch and it only fails over to the failover after exhausting all branches.