DDVTECH / mistserver

The official mistserver source repository - www.mistserver.com
The Unlicense
385 stars 133 forks source link

Stream Name - using only numbers <imei> #182

Open lenee27 opened 1 year ago

lenee27 commented 1 year ago

Hi this is not really a system issue but more so a design restriction. I have a use case where i need to capture streams that are preprogrammed from a vendor. The vendor sends the stream names in the form of an IMEI number. Is there anyway i would be able to get Mistserver to have a stream name with just digits?

nerijus commented 1 year ago

It works if you modify config file by hand and restart mistserver. It does not work via mistserver gui. Maybe this restriction can be removed?

lenee27 commented 1 year ago

Which editor would be the safest? Notepad++.

From: Nerijus Baliūnas @.> Sent: Monday, November 13, 2023 2:57 PM To: DDVTECH/mistserver @.> Cc: Lenee Paulraj @.>; Author @.> Subject: Re: [DDVTECH/mistserver] Stream Name - using only numbers (Issue #182)

It works if you modify config file by hand and restart mistserver. It does not work via mistserver gui. Maybe this restriction can be removed?

— Reply to this email directly, view it on GitHubhttps://github.com/DDVTECH/mistserver/issues/182#issuecomment-1808819448, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BD54ALPA6QRIWFI2RM7D7QDYEJUQNAVCNFSM6AAAAAA7JP6CZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBYHAYTSNBUHA. You are receiving this because you authored the thread.Message ID: @.**@.>>

Rokamun commented 1 year ago

Hey There,

You can indeed add those either by editing the config, or by using the API request add_stream https://docs.mistserver.org/mistserver/integration/api/calls/addstream . We actually don't limit stream names except for certain characters that would break URLs in the backend, however the interface does block certain things due to legacy sorting reasons if I remember correctly. I believe starting with a number is indeed one of the things we block, though we are also working on a newer interface that shouldn't have that limitation in the future.

You can use any editor you'd like, just make sure to keep the JSON format valid. I recommend double-checking whether you did it correctly by pasting whatever you're about to save into https://jsonlintpro.com/ to validate it. I would also recommend making a backup before you start. Saving a configuration that isn't valid can completely break MistServer, however saving a valid configuration afterwards would have it load in the valid configuration as well.

The absolutely safest way would be the API call however, as it's impossible to break MistServers settings through the add_stream call. An easy method of doing a local API call could be through: mistCall https://github.com/DDVTECH/mistserver/blob/master/api/mist_api.sh

With kind regards,

Balder Viëtor Head of Testing

MistServer

On Mon, Nov 13, 2023 at 8:43 PM lenee27 @.***> wrote:

Which editor would be the safest? Notepad++.

From: Nerijus Baliūnas @.> Sent: Monday, November 13, 2023 2:57 PM To: DDVTECH/mistserver @.> Cc: Lenee Paulraj @.>; Author @.> Subject: Re: [DDVTECH/mistserver] Stream Name - using only numbers (Issue #182)

It works if you modify config file by hand and restart mistserver. It does not work via mistserver gui. Maybe this restriction can be removed?

— Reply to this email directly, view it on GitHub< https://github.com/DDVTECH/mistserver/issues/182#issuecomment-1808819448>, or unsubscribe< https://github.com/notifications/unsubscribe-auth/BD54ALPA6QRIWFI2RM7D7QDYEJUQNAVCNFSM6AAAAAA7JP6CZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBYHAYTSNBUHA>.

You are receiving this because you authored the thread.Message ID: @.**@.>>

— Reply to this email directly, view it on GitHub https://github.com/DDVTECH/mistserver/issues/182#issuecomment-1808918584, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAN2RJFMYDXA5CVVUKKQGWDYEJZ5TAVCNFSM6AAAAAA7JP6CZWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMBYHEYTQNJYGQ . You are receiving this because you are subscribed to this thread.Message ID: @.***>