Yes, point taken. Also the modules using SQL should link to theier
dbschema (from README). Still, the status of the destination should be
unified (in terms of values) at script and DB level.
Could you please open github ticket on that I do not forget about it ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
OpenSIPS Summit 2018
http://www.opensips.org/events/Summit-2018Amsterdam
On 01/26/2018 05:39 PM, Pete Kelly wrote:
Hi Bogdan
Thanks for that.
I guess my point is that it would be useful to have that list of
states in the module documentation too, as it differs from the normal
"a"/"i"/"p" values.
Pete
On 26 January 2018 at 14:19, Bogdan-Andrei Iancu <[email protected]
<mailto:[email protected]>> wrote:
Hi Pete,
The meaning of the "status" column is documented in the DB schema
document:
http://www.opensips.org/Documentation/Install-DBSchema-2-3#AEN4379
<http://www.opensips.org/Documentation/Install-DBSchema-2-3#AEN4379>
The "persistent_state" options is related to writing (at shutdown)
back to DB the in-memory state of the destination. It is not
necessary related to pinging, but to preserve the destination
state during OpenSIPS restarts.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com <http://www.opensips-solutions.com>
OpenSIPS Summit 2018
http://www.opensips.org/events/Summit-2018Amsterdam
<http://www.opensips.org/events/Summit-2018Amsterdam>
On 01/26/2018 11:57 AM, Pete Kelly wrote:
Hi Bogdan
The state column appears to be the column which holds the current
state of a GW. I assume this would be i/a/p? But it is not clear
what this value should be set to to correspond to whether a
gateway should be set as Active/Inactive/Probing on startup:
http://www.opensips.org/html/docs/modules/2.3.x/dispatcher#idp5606416
<http://www.opensips.org/html/docs/modules/2.3.x/dispatcher#idp5606416>
The documentation implies that this column can be used on startup too
http://www.opensips.org/html/docs/modules/2.3.x/dispatcher#idp5580768
<http://www.opensips.org/html/docs/modules/2.3.x/dispatcher#idp5580768>
So I guess my questions are:
1) If I want the state column to be referenced on startup, what
are the possible values I can use?
2) If I set the paramater persistent_state=0, will OpenSIPS
assume to ping all gw's on startup?
On 22 January 2018 at 16:25, Bogdan-Andrei Iancu
<[email protected] <mailto:[email protected]>> wrote:
Hi Pete,
The link you posted does not work for me (maybe the docs were
updated in the mean while). But there is no module param or
DB column "probe mode" or so....
So, can you point again to the problematic configuration option ?
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
<http://www.opensips-solutions.com>
OpenSIPS Summit 2018
http://www.opensips.org/events/Summit-2018Amsterdam
<http://www.opensips.org/events/Summit-2018Amsterdam>
On 01/18/2018 12:23 PM, Pete Kelly wrote:
Hi all!!
I frequently have to configure the dispatcher module, and
one of the items that always crops us is which "probe mode"
to set the gateways to within the dispatcher table.
It always proves a bit troublesome because it's not clear
from the documentation which integer corresponds to
"inactive"/"probing"/"probe when disabled" etc.
Is there any chance the documentation here could be updated
in the next iteration so that the state values are enumerated?
http://www.opensips.org/html/docs/modules/2.3.x/dispatcher#idp5608512
<http://www.opensips.org/html/docs/modules/2.3.x/dispatcher#idp5608512>
Pete
_______________________________________________
Users mailing list
[email protected] <mailto:[email protected]>
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
<http://lists.opensips.org/cgi-bin/mailman/listinfo/users>
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
