On-Demand publishers who were on-boarded prior to October 2020 were assigned a dedicated CMOD number. For better performance and response times, Triton Digital recommends you change to the regional or global CMOD endpoints described below.
For fastest response time, On-Demand publishers should call the appropriate regional CMOD endpoint. See the information below to determine which is the best choice for your implementation.
We highly recommend using HTTPS for global endpoints, although HTTP is also available.
Regional Endpoint
North America:
cmod-na.live.streamtheworld.comSouth America (Sao Paulo):
cmod-sa.live.streamtheworld.comEurope:
cmod-eu.live.streamtheworld.comAPAC (Singapore):
cmod-apac.live.streamtheworld.com
Global Endpoint
cmod-world.live.streamtheworld.com
Choosing the Appropriate Endpoint
Choose the endpoint that is closest to the majority of your listeners (for player-based implementations) and closest to the servers (for server-to-server implementations).
Player
The call is issued from the listener's location, so use the endpoint that is closest to the majority of your listeners.
If the vast majority of your listeners are in the same region, you can simply hard-code the endpoint for that region and use it for all connections.
If your listeners are spit across two regions, you should implement player logic that calls the endpoint that is closest to the listener.
If you have an international listenership but you do not want to implement player logic that dynamically connects to the closest endpoint, you can hard-code the global endpoint.
Doing it this way fires a backend service (using the IP resolution of the GSLB logic) that dispatches your On-Demand call to one of the regional endpoints.
Server-to-Server
The same basic logic applies to server-to-server implementations, except you base your choice on the location of the servers instead of the location of the listeners. Consult with your Triton Digital Solutions Specialist for details.