Hi Robert,
I guess you are talking about his
https://opensips.org/html/docs/modules/3.2.x/msilo.html#idp5708384 ?
Which looks like it was not updated since ages.....it is not even 3.2
compatible actually.
The "# if the downstream UA does not support MESSAGE requests" block is
outside the "if(!lookup("location")) ", so it is done when the lookup()
succeeded. And to be honest I do not see that "t_on_if()" anywhere .....
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
OpenSIPS eBootcamp 2021
https://opensips.org/training/OpenSIPS_eBootcamp_2021/
On 11/11/21 10:34 PM, Robert Dyck wrote:
The module documentation for msilo gives us an example of
configuration to deploy the service.
In a block staring with "if(!lookup("location"))" we see the following --
# if the downstream UA does not support MESSAGE requests
# go to failure_route[1]
t_on_if (!db_does_uri_exist("$ru","subscriber"))failure("1");
t_relay();
exit;
We didn't actually establish that the lookup failed because Message is
unsupported. Lookup has only one failure return code -1. This does not
tell us if the lookup failure was due to an non-existant AOR, no UAs
registered or method not supported.
In the statement "t_on_if
(db_does_uri_exist("$ru","subscriber"))failure("1"); " t_on_if is not
documented. Does it mean we should immediately go to the failure route
if the AOR does not exist.
If the AOR does not exist why would we do ---
if (m_store("$ou"))
{
log("MSILO: offline message stored\n");
t_reply("202", "Accepted");
}else{
log("MSILO: offline message NOT stored\n");
t_reply("503", "Service Unavailable");
};
Some clarification would be appreciated.
Rob
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
