The mount and port obviously have to match what you have the encoder [A/XE] setup to output...
The following shows how we can extend a single listen-socket to work with ShoutCast style source clients. There are two issues ShoutCast source clients have over IceCast source clients, one is the lack of mountpoint and the second is the requirement of two ports. Both of these issues are handled by a simple addition in the listen-socket.
As before, the port specified is allocated but this time the shoutcast-mount implicitly defines a second listening socket whose port number is always one higher than the port defined, this also informs IceCast of which mountpoint the ShoutCast source client on this socket will be using. Using this approach you can allow multiple ShoutCast source clients to connect at the same time. The following is just to show the longer approach to defining ShoutCast compatibility.
<-- You may have multiple <listen-socket> elements -->
Note that multiple listen-socket sections may be configured in order to have icecast2 listen on multiple network interfaces or multiple ports. If a bind-address is not specified for a particular listen-socket, then the socket will be bound to all interfaces (including IPv6 if available).For most people, the bind-address option will not be required and often confuses people.
The TCP port that will be used to accept client connections.
An optional IP address that can be used to bind to a specific network card. If not supplied,then it will bind to all interfaces.
An optional mountpoint setting to be used when ShoutCast DSP compatible clients connect.The default global setting is /stream but can be overridden here to use an alternative name, which may include an extension that some clients require for certain formats. Defining this within a listen-socket group tells icecast that this port and the subsequent port are to be used for ShoutCast compatible source clients. This is an alternative to the shoutcast-compat approach as this implicitly defines the second listening socket and allows for specifying multiple sockets using different mountpoints for ShoutCast source clients. The shoutcast mountoutside of a listen-socket group is the global setting of the mountpoint to use.
This optional flag will indicate that this port will operate in ’shoutcast-compatibility’ mode.Due to major differences in the source client connection protocol, if you wish to use any of the ShoutCast DJ tools, you will need to configure at least one socket as shoutcast compatible.Note that when in this mode, only source clients (and specifically ShoutCast source clients) will be able to attach to this port. All listeners may connect to any of the ports defined without this flag. Also, for proper Shoutcast DSP compatibility, you must define a listen socket with a port one less than the one defined as ’shoutcast-compat’. This means if you define 8001 as shoutcast-compat, then you will need to define a listen port of8000 and it must not also be defined as shoutcast-compat. See the example config file in the distribution for more info.