Thanks, actually this was a small error that affected almost every lost function. The error variable was set to 0 before return, and thus there was no error ode returned. The fix (committed to master) now returns 500 in case of error (error code/string of the response is found in pvar/err) and otherwise 200, 201, 202, or 203. 200 neither pidf-lo nor reference, 201 pidf-lo, 202 url, 203 pidf-lo and url found in the response. Please verify using the latest commit. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2724#issuecomment-830827340

Generally LIS code and error message also important for error handling. Error code may be used for `switch` statement and a message for log description for humans. Here examples of LIS error messages *from RFC* ```xml <?xml version="1.0"?> <error xmlns="urn:ietf:params:xml:ns:geopriv:held" code="locationUnknown"> <message xml:lang="en">Unable to determine location </message> </error> ``` my use case ```xml <?xml version="1.0" encoding="UTF-8"?> <urn:error xmlns:urn="urn:ietf:params:xml:ns:geopriv:held" code="generalLisError"> <urn:message>An unspecified error occurred while handling LocationRequest.</urn:message> </urn:error> ``` So I can use a `switch` statement like ``` if ($var(res) == 200 && $var(res) > 203 ) { switch $(varLisErrorCode) { case "locationUnknown": xlog(L_ERR, "Received LIS error response: $(varLisErrorMessage)"); route(TRY_DEFAULT_PSAP); case "generalLisError": xlog(L_ERR, "Received unexpected LIS error response: $(varLisErrorMessage)"); route(TRY_OTHER_LOCATION_METHOD); default: } } ``` For me more preferable to define module param `xavp_responce` ``` modparam("lost", "xavp_responce", "held_responce") ``` If `xavp_responce` defined then set keys. 1) HTTP_ERROR_CODE; 2) HELD_ERROR_CODE; 3) HELD_ERROR_MESSAGE. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2724#issuecomment-831009598

@sergey-safarov: this sounds reasonable and would also fit well for other lost functions - let's leave the issue open and I will think of something. Further inputs are always welcome. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2724#issuecomment-831081013

@henningw this is still relevant ... unfortunately I have not had time to work on it yet -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2724#issuecomment-919846256

Closed #2724 as not planned. -- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/2724#event-11042728499 You are receiving this because you are subscribed to this thread. Message ID: &lt;kamailio/kamailio/issue/2724/issue_event/11042728499(a)github.com&gt;