Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Scroll export button
scopecurrent
template-id0fa09813-8b86-460a-aa1d-ef450a80e9ce
quick-starttrue
add-onScroll PDF Exporter

Info

This document explains how to set up Delayed Paging – allowing users to record the message and then have it delivered as a page.

Created: January 2019

Permalink: https://wildix.atlassian.net/wiki/x/xwbOAQ

Basic information on Paging feature: Paging - Admin Guide

Table of Contents

Notice

Version 2 of this custom configuration is now available and has the following advantages:

  1. no requirement for users
  2. importable via a dial plan

Find version 2 here:  Delayed Paging Version 2 /wiki/spaces/DOC/pages/30280433.

Use Case

Customers would like a paging solution that allows them to record a message, then have this message delivered as a page. If they do not like the recording that they have recorded, they would like an opportunity to record the message over again before it is sent out.

...

Note

Note: Work around for this limitation is described in Step 5 "Create a separate Dialplan procedure 'mypaging' with two entries".

Configuration

Step 1. Set up an entry in the "users" dialplan to be used for this new “Delayed Paging”

Notice in the screenshot below that there we are using 888 for the number to be dialed by the user to perform the delayed paging. The applications in the dialplan essentially prompt the caller using TTS to “record your page message and then press pound”, then set variables required to originate the page when done and ultimately originate a call to the paging system.

...

  • Set -> ORIGINATE_VARIABLES -> QUEUENAME=Notification,QUEUEPOSITION=1

  • Set -> ORIGINATE_TIMEOUT -> 3600

  • Set -> ORIGINATE_PRIORITY -> 1

  • Set -> ORIGINATE_EXTEN -> 444

  • Set -> ORIGINATE_CONTEXT -> internalcalls

  • Set -> ORIGINATE_CALLERID -> ${CALLERID(num)}

  • Set -> ORIGINATE_CHANNEL -> Local/555@internalcalls/n

  • Set -> ORIGINATE_ASYNC -> true

  • Custom application -> Originate()

Step 2. Add “forwarding users” 444 and 555  

Preferences for user 444:

...

Note

Note: Call forward all is selected and sends all calls destined to this user record to 556.

Step 3. Build your paging group

Build a standard paging group that you want to send the page to. In this example, we built a paging group called “TestPage”. See 556 entry Step 4 below. More information on how to create a Paging group: Paging - Admin Guide.

Step 4. Add "users" dialplan entries for digits 445 and 556


Workaround: Using SIP invite for paging more than 15 users

...

Note

Note: In brackets you need to specify all users to be paged using '&' as a delimiter.

Step 5.  Create a separate dialplan procedure 'mypaging' with two entries


Applications used for X.

  • Jump to if -> "${DEVICE_STATE(SIP/${EXTEN})}"="INUSE" -> Procedure mypaging -> Number hangup
  • Custom application -> SipAddHeader("Call-Info: sip:wildixgw;answer-after=0;force")
  • Custom application -> Page(SIP/${EXTEN})

...