# URL of MPEG-TS re-streaming, must end with ".stream" ? **URL:** \ **Category:** Wowza Streaming Engine\ **Created:** [September 12, 2014, 1:52pm UTC](https://community.wowza.com/t/url-of-mpeg-ts-re-streaming-must-end-with-stream/41720 "2014-09-12T13:52:29Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![David\_Shimamoto](https://avatars.discourse-cdn.com/v4/letter/d/b77776/32.png) [@David\_Shimamoto](https://community.wowza.com/u/David_Shimamoto)\ **Post date:** [September 12, 2014, 1:52pm UTC](https://community.wowza.com/t/url-of-mpeg-ts-re-streaming-must-end-with-stream/41720/1 "2014-09-12T13:52:29Z")
When using Wowza to re-stream incoming MPEG-TS to outgoing RTMP, Is there a way to set an access URL for clients which does not end with “.stream” ? StreamPublisher module which I know is one solution, cannot be used for reasons explained later. \*In detail I have an existing Wowza system feeding live source from FMLE via RTMP. The source encoder is soon to be replaced with one using MPEG-TS (UDP). As this stream is currently fed to a good number of clients with the access URL hard-coded on their side, I would like to keep the access URL unchanged. However, following tutorials on how to re-stream MPEG-TS, I only know of how to set access URLs ending with “.stream”. I know this can be overcome using the StreamPublisher module. However, it is already used to handle scheduling of other streams on the same Wowza application, which when reloading the schedule (.smil) file, causes a break in all managed streams. This is probably easy if the stream not requiring scheduling can be run on a separate Wowza application, but unfortunately that cannot be done. Thank you. ---
**Author:** ![Jason\_Hilton](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/jason_hilton/32/437_2.png) [@Jason\_Hilton](https://community.wowza.com/u/Jason_Hilton)\ **Post date:** [September 12, 2014, 9:28am UTC](https://community.wowza.com/t/url-of-mpeg-ts-re-streaming-must-end-with-stream/41720/2 "2014-09-12T09:28:13Z")
Hi, To change the name of a specific stream, you can use the StreamNameAlias AddOn. Please see [How to get the StreamNameAlias AddOn](https://www.wowza.com/docs/how-to-get-the-streamnamealias-addon) and follow the instructions which are included in the download. Another option would be to use Push Publishing which is now built-in to Wowza Streaming Engine 4. [How to push streams to CDNs and other services (Push Publishing)](https://www.wowza.com/docs/how-to-push-streams-to-cdns-and-other-services-push-publishing%28Push-Publishing%29) Regards, Jason ---
**Author:** ![Jason\_Hilton](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/jason_hilton/32/437_2.png) [@Jason\_Hilton](https://community.wowza.com/u/Jason_Hilton)\ **Post date:** [September 16, 2014, 8:46am UTC](https://community.wowza.com/t/url-of-mpeg-ts-re-streaming-must-end-with-stream/41720/3 "2014-09-16T08:46:30Z")
Hi, Sorry, you can’t alias an alias, which is why you can’t use the StreamNameAlias for .stream files. The easier option would be to use the Push Publishing functionality to publish the stream you’re receiving (MPEGTS.stream) to the same, or another application for your client to view. Push Publishing allows you to choose the name of the stream you’re publishing so this could be called “myStream” if configured in the [Wowza-Install]/conf/PushPublishMap.txt file. In the [Wowza-Install]/conf/PushPublishMap.txt file you would have: ```auto MPEGTS.stream={profile:"rtmp", streamName:"myStream", host:"localhost", application:"live", userName:"myuser", password:"mypassword"} ``` Please see the [Push Publishing guide](https://www.wowza.com/docs/how-to-push-streams-to-cdns-and-other-services-push-publishing%28Push-Publishing%29) for configuration details. Regards, Jason ---
**Author:** ![Jason\_Hilton](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/jason_hilton/32/437_2.png) [@Jason\_Hilton](https://community.wowza.com/u/Jason_Hilton)\ **Post date:** [September 18, 2014, 2:16pm UTC](https://community.wowza.com/t/url-of-mpeg-ts-re-streaming-must-end-with-stream/41720/4 "2014-09-18T14:16:07Z")
Hi, That’s great news, thanks for the update. Regards, Jason ---
**Author:** ![David\_Shimamoto](https://avatars.discourse-cdn.com/v4/letter/d/b77776/32.png) [@David\_Shimamoto](https://community.wowza.com/u/David_Shimamoto)\ **Post date:** [September 16, 2014, 11:28am UTC](https://community.wowza.com/t/url-of-mpeg-ts-re-streaming-must-end-with-stream/41720/5 "2014-09-16T11:28:25Z")
Hi Jason, I am now trying the suggested Stream Name Alias module. I see in the description, “Note: When this alias package is configured for a given application it will replace the built-in alias system that is implemented using .play and .stream files.” This perhaps explains why, with my older .stream files, “Incoming streams” show a “Bytes In” reading of zero after installing the module. Would you please show example of what setting goes in which config file? I am trying to make, an MPEG-TS stream incoming at udp://0.0.0.0:10000, accessible to clients at rtmp://mydomain:1935/live/mystream. Thank you. ---
**Author:** ![David\_Shimamoto](https://avatars.discourse-cdn.com/v4/letter/d/b77776/32.png) [@David\_Shimamoto](https://community.wowza.com/u/David_Shimamoto)\ **Post date:** [September 17, 2014, 3:02pm UTC](https://community.wowza.com/t/url-of-mpeg-ts-re-streaming-must-end-with-stream/41720/6 "2014-09-17T15:02:42Z")
Thank you Jason, Now everything is working as expected. What a beauty