Scheduled Announcement

[shopcomputer]

Any way to schedule an announcement to a paging group?

 

I have a customer that want every day at 5;45pm an announcement the store will be closing in 15 minutes.

At ^ pm they want an automated announcement the store is now closed, as well as some other scheduled announcements, can anyone think of a way to do this?

[Vodia PBX]

Yes this is something that we have on the to-do list for years... Technically you can have an external application taking care about it using a HTTP URL (e.g. curl). We have already added the "bell" functionality when someone presses the door bell (which gets translated into a HTTP GET request); now we need to extend that so that the PBX does the HTTP get without external help. Should be actually pretty simple.

[chrispopp]

Any news on this. We have several clients that want to be able to create scheduled announcements. For example a school that wants to have the ring bell at 8:45AM, 1:00PM...

Even better, to play a recording such as a wavefile.

[chrispopp]

I see it says this on the vodia.com website (https://vodia.com/en/paging) I don't see any documentation...

 

• Scheduled playback. You may schedule paging announcements, for example for school bells or for playing out the good night story in a hospital.

 

[Support]

Hi,

Unfortunately, we don't offer that as of now, maybe it was left out of our bucket list somehow. Will try to re add to the list.

[chrispopp]

What about the Playback method from a page group. If you select a WAV file and press save, it doesn't save it. And if you call it it gives a Forbidden. The extension is authorized. Also Live and Pre-Recorded methods work, just cannot play a wav file... Seems it's broken too

 

This is the log error: [5] 16:30:14.036    APP:    Paging: no static file associated with the paging group 165@test.reallycool.com

 

2018/8/24 16:30:14 Rx: tls:198.251.111.111:36243 (1361 bytes)
INVITE sip:165@test.reallycool.com;user=phone SIP/2.0
Via: SIP/2.0/TLS 172.16.16.119:36243;branch=z9hG4bK-8k7vhrbqfhh7;rport
From: "Name Test" <sip:299@test.reallycool.com>;tag=a8uqu88njj
To: <sip:165@test.reallycool.com;user=phone>
Call-ID: 313533353134323631323330353732-y5m9wv6rpvup
CSeq: 1 INVITE
Max-Forwards: 70
User-Agent: snom760/8.7.5.35
Contact: <sip:299@172.16.16.119:36243;transport=tls;line=3b4da0oi>;reg-id=1
X-Serialnumber: 00041371ZZZZ
P-Key-Flags: resolution="31x13", keys="4"
Accept: application/sdp
Allow: INVITE, ACK, CANCEL, BYE, REFER, OPTIONS, NOTIFY, SUBSCRIBE, PRACK, MESSAGE, INFO, UPDATE
Allow-Events: talk, hold, refer, call-info
Supported: timer, 100rel, replaces, from-change
Session-Expires: 3600
Min-SE: 90
Proxy-Require: buttons
Content-Type: application/sdp
Content-Length: 504

v=0
o=root 2080425959 2080425959 IN IP4 172.16.16.119
s=call
c=IN IP4 172.16.16.119
t=0 0
m=audio 61676 RTP/AVP 0 8 3 9 99 18 101
a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:n8DPLX5e4V/3XGHIr4FQK0A3vre0JLDtTBrkeVEe
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:3 GSM/8000
a=rtpmap:9 G722/8000
a=rtpmap:99 G726-32/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
a=rtcp-xr:voip-metrics stat-summary=loss,dup,jitt
a=sendrecv
2018/8/24 16:30:14 Tx: tls:198.251.111.111:36243 (352 bytes)
SIP/2.0 100 Trying
Via: SIP/2.0/TLS 172.16.16.119:36243;branch=z9hG4bK-8k7vhrbqfhh7;rport=36243;received=198.251.111.111
From: "Name Test" <sip:299@test.reallycool.com>;tag=a8uqu88njj
To: <sip:165@test.reallycool.com;user=phone>;tag=cbfc9bc1ff
Call-ID: 313533353134323631323330353732-y5m9wv6rpvup
CSeq: 1 INVITE
Content-Length: 0

2018/8/24 16:30:14 Tx: tls:198.251.111.111:36243 (1072 bytes)
SIP/2.0 200 Ok
Via: SIP/2.0/TLS 172.16.16.119:36243;branch=z9hG4bK-8k7vhrbqfhh7;rport=36243;received=198.251.111.111
From: "Name Test" <sip:299@test.reallycool.com>;tag=a8uqu88njj
To: <sip:165@test.reallycool.com;user=phone>;tag=cbfc9bc1ff
Call-ID: 313533353134323631323330353732-y5m9wv6rpvup
CSeq: 1 INVITE
Contact: <sip:299@192.168.1.222:5062;transport=tls>
Supported: 100rel, replaces, norefersub
Allow-Events: refer
Allow: INVITE, ACK, CANCEL, BYE, REFER, PRACK, INFO, UPDATE
Accept: application/sdp
User-Agent: Vodia-PBX/61.0
P-Asserted-Identity: "PAGING TEST" <sip:165@test.reallycool.com>
Content-Type: application/sdp
Content-Length: 394

v=0
o=- 47595 47595 IN IP4 192.168.1.222
s=-
c=IN IP4 192.168.1.222
t=0 0
m=audio 26500 RTP/AVP 0 18 9 101
a=crypto:1 AES_CM_128_HMAC_SHA1_32 inline:oEJMO6NyIETDa98ZNhunSOeewRkJS6QTxNq1YOS/
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:9 G722/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=ptime:20
a=rtcp-xr:rcvr-rtt=all voip-metrics
a=sendrecv
2018/8/24 16:30:14 Tx: tls:198.251.111.111:36243 (528 bytes)
BYE sip:299@172.16.16.119:36243;transport=tls;line=3b4da0oi SIP/2.0
Via: SIP/2.0/TLS 192.168.1.222:5062;branch=z9hG4bK-9cbe27be9ee99c11e467985b5ba0dd91;rport
From: <sip:165@test.reallycool.com;user=phone>;tag=cbfc9bc1ff
To: "Name Test" <sip:299@test.reallycool.com>;tag=a8uqu88njj
Call-ID: 313533353134323631323330353732-y5m9wv6rpvup
CSeq: 9218 BYE
Max-Forwards: 70
Contact: <sip:299@192.168.1.222:5062;transport=tls>
P-Asserted-Identity: "PAGING TEST" <sip:165@test.reallycool.com>
Content-Length: 0

2018/8/24 16:30:14 Rx: tls:198.251.111.111:36243 (505 bytes)
ACK sip:299@192.168.1.222:5062;transport=tls SIP/2.0
Via: SIP/2.0/TLS 172.16.16.119:36243;branch=z9hG4bK-ahgyn0v9e11k;rport
From: "Name Test" <sip:299@test.reallycool.com>;tag=a8uqu88njj
To: <sip:165@test.reallycool.com;user=phone>;tag=cbfc9bc1ff
Call-ID: 313533353134323631323330353732-y5m9wv6rpvup
CSeq: 1 ACK
Max-Forwards: 70
User-Agent: snom760/8.7.5.35
Contact: <sip:299@172.16.16.119:36243;transport=tls;line=3b4da0oi>;reg-id=1
Proxy-Require: buttons
Content-Length: 0

 

[Vodia PBX]

If you see scheduled playback in the service flag web interface, then it is in the software. You need to upload your WAV though the "Upload Audio" menu in the domain (or on system level). After the upload you can actually verify right on the upload page that the WAV file works by pressing the "play" button.

[chrispopp]

Oh Yes, now I see it!

I did upload the wav file and it plays fine under Upload file section when I click on the play button. I even uploaded it to an auto-attendant, and it works. But when I upload it via the web interface under the Paging, it gives me the check mark (OK) when I submit. If I exit the page and come back in (or refresh), it automatically reverts back to no file.

 

 

Then if I refresh:

 

 

If I ring the paging group, it disconnects me without paging. 

 

 

 

[chrispopp]

Also tried it on an older version and the upload file under the page works...

[Vodia PBX]

No the thing is that there are two WAV files needed here: When the services flag gets "active" (whatever that is) and when it gets inactive. That is why the files are provided with the service flag. The paging account is just used for delivering those files.

[chrispopp]

Sorry I don't seem to understand. 

The file cannot be uploaded onto the page in version 61 but in version 56 it works...

I cannot find any documentation that shows how to deploy this automated message. 

Where would I be able to upload 2 files?

Also, how can I upload a file onto a service flag?

[chrispopp]

My apologies... I now realized it! Thank you.