Scroll export button | ||||||||
---|---|---|---|---|---|---|---|---|
|
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:
- no requirement for users
- importable via a dial plan
Find version 2 here: /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.
Paging on the Wildix system is by default real time, meaning that when a person is paging a page group, the paged parties hear what the paging party is saying in real time. There are cases where it would be preferred to record a message and have this recorded message delivered as a page. Specifically:
- If the latency in the environment is enough to be noticeable on an overhead paging system. Example, the paging party can hear the page being delivered slightly after they are saying it. This can be distracting to the paging party.
- If the paging party wants an opportunity to correct their paging message. Example, I am sending a page and I say “the work facility will close at 2pm today due to weather conditions. Sorry, correction … 3pm the facility will close”. In such a case, the paging party would like to start the message over rather than correcting it in real time.
Version 1
Note |
---|
Note: This version of delayed paging is newer and has a couple of significant advantages over the second version. Specifically the following two facts make this solution a lot more administrator friendly.
|
Requirements
No special requirements other than importing the provided dial plan.
Limitation
This configuration currently ONLY works for invite based paging. It does not work for multicast paging. This means that it is useful for Cloud PBX installations that do not utilize any local multicast paging solution such as a local HW PBX with WMS Network configured.
Note |
---|
Note: Work around for this limitation is described in Step Workaround: Using SIP invite for paging more than 15 users |
Configuration
Step 1
Import the Dialplan provided below into your system. This Dialplan provides the origination functionality of the delayed paging.
Step 2
Configure the paging group that is going to be used. On the provided dial plan there is an entry called page:
For that entry, please configure the correct paging group.
Step 3
Configure a pilot number to access the feature. In our example, number 888 was used but any number will do:
In Jump to application: Jump to -> DelayedPaging (imported Dialplan) -> begin
That’s it. Every time someone dials 888, the user will be asked to record a message. The message will then be played using the page group already configured.
Workaround: Using SIP invite for paging more than 15 users
As mentioned above, this solution uses the default paging mechanism, which means that on a Cloud PBX only 15 users can be paged at the same time. In this section a workaround is provided for scenarios where more than 15 users need to be paged. Notice that the change is to simply replace the page application of the page entry in the Dialplan with a custom application.
Replace Step 2:
- Custom application -> Page(Local/<user>@DelayedPaging&Local/<user>@DelayedPaging)
Example: Page(Local/102@DelayedPaging&Local/110@DelayedPaging&Local/111@DelayedPaging&Local/101@DelayedPaging)
Note: In brackets you need to specify all users to be paged using '&' as a delimiter.
Version 2
Limitation
This configuration currently ONLY works for invite based paging. It does not work for multicast paging. This means that it is useful for cloud Cloud PBX installations that do not utilize any local multicast paging solution such as a local HW PBX with WMS Network configured.
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 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.
...
Note |
---|
Note: Originate Channel is set with 555 as being the user part. This user 555 is another “fake user” which forwards the call to a dialplan Dialplan entry that will route to the paging group. Again, it does not need to be an online user, it is simply used for call forwarding to the paging group. |
...
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
...
- Custom application -> Page(Local/<user>@mypaging&Local/<user>@mypaging)
Eg. Example: Page(Local/502@mypaging&Local/503@mypaging)
...
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})
...
A user dials 888. They are prompted to record a message and press pound. If they do not like the message they recorded, they can simply hang up. In In this case, the recording will not be delivered as a page. If they are satisfied with the recorded message they press #. The system then hangs up on this party and originates a new call. This call is originated TO the paging group and is connected to the application that plays back the recorded message.
...