363 results found

1. Allow 911 notification email/SMS recipients to be specified by location

   For organizations that have multiple buildings, locations, etc. they would like to be able to specify what recipients get the 911 notification based on site.  Ex.  This was specifically requested by Special School District of St. Louis who has multiple locations in the St. Louis area. They desire to specifically notify key individuals at the location where 911 was dialed from.

   24 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Planned  ·  12 comments  ·  General Phone  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Create logic to pass calling ext and calling name of user when dialed ext is call forwarded to "1700xyz"

   Need to create "x-header" containing calling name and calling extension when the user dials an internal RC extension that is "call forwarded" to pattern beginning with 1700xyz where xyz is the legacy PBX ext being forwarded over a Custom Engineering SIP trunk. The use case is when we provide a customer with an Ext2Ext (closed user group dialing) SIP trunk from RC (via RCLEC SBCs) to a customer’s SBC and/or PBX, there is a current limitation in providing the calling RC user’s ext number and the user’s calling name (user in SW) when they are dialing virtual ext’s that are forwarded to their Ext2ext SIP using the “+1700xyz” steering digits. Because it’s forwarding over the PSTN (via SIPT) we use the default outbound caller ID settings of the called user instead of the calling user. Therefore not as “RC to RC internal”. Most customers want the transition or permanent solution to be as transparent as possible….sometimes they are ok with the limitation.

   Need to create "x-header" containing calling name and calling extension when the user dials an internal RC extension that is "call forwarded" to pattern beginning with 1700xyz where xyz is the legacy PBX ext being forwarded over a Custom Engineering SIP trunk. The use case is when we provide a customer with an Ext2Ext (closed user group dialing) SIP trunk from RC (via RCLEC SBCs) to a customer’s SBC and/or PBX, there is a current limitation in providing the calling RC user’s ext number and the user’s calling name (user in SW) when they are dialing virtual ext’s that are… more

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Under Review  ·  0 comments  ·  General Phone  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. "Ring additional extensions" for Share Line Group

   Option to ring other devices that just the Shared Line Group phones. In the event the call was picked up on one of the "other phones," the call would no longer be visible on the SLG.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Under Review  ·  0 comments  ·  General Phone  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close