I work for an on-hold company that provides streaming URLs to customers that have FreePBX distro. We just did a server migration and the new server will only generate streams in 64-bit format. Is there a version of FreePBX that supports 64-bit URLs, and not only 32-bit/character URLs? Our streaming platform is on Icecast servers in a http format.
I can’t think of a reason why FreePBX wouldn’t support 64-bit URLs. The internationalization code in the system works pretty well for most things; this this is passed intact, not working would fail the Rule of Least Astonishment for me. @xrobau would be a good resource for this (being a guy that pushes buttons and knows the guts of the system). Perhaps he can provide some insight?
If you don’t get any satisfaction here, you can drop an Issues ticket into the mix with the specific URL you are trying to hit so the code monkeys can look into it.
That is a URL to a 64-bit datastream. The URL is not the problem.
This is probably as Asterisk problem (rather than a FreePBX problem). Using a 64-bit data stream for a 16-bit telephone connection seems like a real waste of processing power. Even with a 32-bit stream, Asterisk has to transcode that down to an 16-bit mono on-hold channel.
It is my understanding that the audio files uploaded to the stream are 16-bit, 128k, mp3 mono files. The length of the URL is for security purposes only, we could have a stream with 2 characters. So when I refer to a 64-bit URL it is just the amount of characters for the stream.
Could it be that either FreePBX or Asterisk has a maximum character length size for URLs?
Doubt it, but you never know. The URL is stored in the FreePBX database and is translated into one of the configuration files for Asterisk. If the problem is the length of the URL, it should be a FreePBX problem (based on the fact that all of the FreePBX settings are stored in a MySQL database).
If you have a test environment, you could try dropping your URL into the field on the FreePBX screen, store it, and restart your browser and reopen the screen. If the URL field is truncated, you have your answer.
Not sure if there is any error. This is all implemented by the end user to the FreePBX interface. What I have seen in the past is when a streaming source is used for Asterisk the 64 character URL produces silence while the 32 character URL provides MOH.
Changing our format to UUID’s would be a major infrastructure update to our 20 some streaming servers we already have.