Dynamic allocated socket [^SIS] error | Thales IoT Developer Community

Thanks by reply Jędrzej i have not AT log, because the app is running between a mcu host and the module itself and i can't get direct at communications log. however i always print to a debug screen (seria stdout) the response from the cinterion module, the logic is as below. 2 profile servives are running 0 and 1, the service '0' is a tcp listener, so when some wants to connect to the module, there is a URC coming out from the module telling me the profile (if i accept that request) to open. so opening it using 'at^siso=n', where 'n' is the number taken from the urc string, when i do that, the reponse is ERROR 767 hope this helps.