Streaming music on hold from local source?

[Guest]

I have 2 customers asking if we can use their music on hold streaming from a local device managed by a 3rd party. Here are some of the companies:
http://www.pcmusic.com/music-products.html

http://www.amemusic.com/ame2020.asp

Can we use an ATA onsite somehow?

[Karl Stallknecht]

Not sure about having a device on-site, but I do know that they finished building integration so that you can stream a SHOUTcast stream. It should be released pretty soon.

[Guest]

Thanks Karl. Who can provide more info on this? Maybe if I figure out the method used I can port it to other providers...

[Karl Stallknecht]

See ticket KAZOO-4062 in JIRA. Unfortunately that is all I know.

[Guest]

Thanks Karl. 
@Darren - any info on the SHOUTcast integration would be great.

[Jesse Howard]

The page here suggests this might be there already on-demand through a support request. Looks like the pre-requisite is you must have your shoutcast url handy and the location must end in mp3.

"As per another ticket (UI-386), Darren and Karl A have noted that this is already supported for the most part: Darren: On a technical note, we can allow the user to enter any HTTP or HTTPS url that they wish, however it must end in .mp3 to invoke the shoutcast decoder"

[Karl Stallknecht]

The feature is there, but they later discovered that they needed to do a few things to enable it on production. Ticket KAZOO-4062 was to track them doing those things. It won't be available in the GUI the last I heard, and is just something that you can do either with an API or they can do manually from their end. But as of right this second it is not available.

[Guest]

this has resurfaced - anyone tried this yet? I have a prospect who wants to use this Barix Instreamer (https://www.amazon.com/Barix-Instreamer-IP-Audio-Encoder/dp/B0094JJWC0) which says it will push audio to a URL target as a stream. 

How do I see those Jira tickets by the way?

[Tuly]

I believe the streaming music on hold should be released in the UI soon,
It's already in the sandbox

[Guest]

that's great - is it available somewhere in the API?

[FASTDEVICE]

This is something I've discussed with Aaron several years back. Glad to hear it may be available soon.

[FASTDEVICE]

I can confirm that streaming music now works in production. You must configure through the API in order to make it work.

IMHO, it's freakin' awesome. Big thanks 2600hz team for listening and making it possible!

[FASTDEVICE]

Here's an idea... How about providing us a device that can stream a URL much like the SIP URI device.

I can think of endless possibilities for use and monetizing. 

[Darren Schreiber]

58 minutes ago, FASTDEVICE said:

I can confirm that streaming music now works in production. You must configure through the API in order to make it work.

IMHO, it's freakin' awesome. Big thanks 2600hz team for listening and making it possible!

This is correct. You can set 

{ "data" : { "music_on_hold": { "media_id" : "shout://22.22.22.22:80/live" } } }

on your account. We're working on ways to expose this in the GUI but for those who really need it, it's there!

[Darren Schreiber]

29 minutes ago, FASTDEVICE said:

Here's an idea... How about providing us a device that can stream a URL much like the SIP URI device.

I can think of endless possibilities for use and monetizing. 

I'm not sure I understand this request? What do you mean "providing us a device". Like, setup a server that streams media? I don't understand.

[FASTDEVICE]

@Darren As I think through that request more clearly, I'm thinking what would be nice is the ability to connect a shoudcast url to a callflow, much like play media. I confused the request with a device as I'm able to do this using a sip: uri that plays music on hold. 

[Darren Schreiber]

Still not getting this. What's the use case? Like, you dial a number, it's a callflow to play media, but the media is really a shoutcast URL? Are you streaming a radio show with a call-in number or something?

 

[FASTDEVICE]

Yes, the ability to dial-in and listen to a shoutcast stream instead of fixed media. While I can't outline all the wonderful possibilities, there are many that include promotional, seasonal, and ad based that can be accessed via menus. My first thought is old school movie theater times running in a loop; like press 1 to hear our current promotions, upcoming events, and entertainment. The shoutcast server is excellent at changing media and insertions on the fly.       

[Darren Schreiber]

So I'm not 100% sure but I believe the change was made for any media handling. So if you just make a media node but set it to shout:// it should also work, then you make a callflow that plays that media node. The validation might be restricting this, though, so not 100% sure on that.

 

[mc_]

I don't think there's anything restricting the URL from being "shout://...". ecallmgr explicitly checks for shout:// and passes it direct to FreeSWITCH. Give it a shot and let us know!

[FASTDEVICE]

Thanks, I'll give it a shout. lol.

I wonder, if this becomes a formal feature, shouldn't there be some restrictions like; { time limit | forever } | press 0 to escape.  Unlike play media, streams are never ending. 

[FASTDEVICE]

What variable do I assign the "shout:// url?" 

• name: "filename"
• media_source: "upload"
• description: "C:\\fakepath\\_filename.mp3"

 

[mc_]

Where are you putting this media? Most places that take a media_id of some sort will also accept the "shout://" URL as well. FreeSWITCH will need mod_shout enabled as well, by the by.

[FASTDEVICE]

I had to wrap my mind around not creating a media asset, but simply set the media_id to shout://. That's why my previous comment was asking where within the media document to place the shout:// url. Sometimes simple just escapes me, like when Apple came out with a one button mouse I was completely lost.    

Drum roll....I was able to create a media node with shout:// as the media_id and attach it to a callflow. It works!

Thanks again. 

[Darren Schreiber]

Mind pasting the JSON you ended up with for reference?