Hi, many users ask via which IP address IoT Creators SCS forwards received uplink messages to the registered application callback URL: IoT Creators SCS forwards the uplink messages to your application callback URL via one of the two IPs 18.195.119.162 18.195.17.174 Hope this helps you to configure the IP whitelists of your application. Regards, Roland

Not so much a question as an observation : After registering the second application, no messages arrive. Unlike the first endpoint, which just automatically gets all data from your project, you will have to ‘subscribe’ to the resources of a specific device before the data of that device is sent to the second endpoint.

@afzal_m Apologies, I may have spoken too soon. After playing with the payload formats on AllThingsTalk I do now see information coming in. Not quite exactly what i expected but I guess that’s down to misconfiguration on my part. So I’d say yes the connection works, parsing of data I need to look into. And yes changing the URL on the application server works which is good news!

If you save the URL the platform sends a request with an empty body to the URL to test it. If the URL doesn‘t exist or returns a code different than 200 you can not save the URL. Regards, Roland

@Roalnd-Baldin Thanks for helping, but not working. AT+CSOSEND=0,22,"48656c6c6f20576f726c64" OK Sim7020 working with hex length, not with the byte, so I tried with hex format, but the message not arrived the iotcreator and Beecaptor. Can you anything idea? Thanks all!

@eric-barten I didn’t register the device in the att assets. I’ve received some messages in the debug tab, but it has a delay of a day?? Now I have registered the device with the IMEI in the assets tab and I sent some test messages but I’m currently not receiving any.

@pilovali Ik krijg de melding invalid url, maar het lijkt aan het sll certificaat te liggen.

Does it also work for @trick2011 now?