[OpenSIPS-Users] Realtime monitoring of registered end-points

Ionut Ionita ionutionita at opensips.org
Thu Feb 18 13:56:38 CET 2016


Sipping_flag must also be set, because matching pings when they return 
can be
done only if using SIP pings. Did you set it?

Ionut Ionita
OpenSIPS Developer

On 02/17/2016 02:56 PM, Dragomir Haralambiev wrote:
> Hello,
>
> I try to setup realtime monitoring.
> Here is part of my script:
>
> loadmodule "nathelper.so"
> modparam("nathelper", "remove_on_timeout_bflag", "RM_ONTO_FLAG")
> modparam("nathelper", "ping_threshold", 5)
> .......
>
> route {
> .........
> setbflag(RM_ONTO_FLAG);
> .........
> }
>
> From location tableI (cflags) I see  "RM_ONTO_FLAG"
> Unplug Internet connection from registered endpoint.
>
> Opensips send sipping. Received "Destination unreachable (Port 
> unreachable)".
>
> Record in location table is not deleted.
>
> Where is problem?
>
> Regards,
> Dragomir
>
>
> 2015-10-01 11:33 GMT+03:00 Ionut Ionita <ionutionita at opensips.org 
> <mailto:ionutionita at opensips.org>>:
>
>     *Hello all,
>
>         I’m glad to announce a new feature that allows OpenSIPS to monitor
>     (via SIP OPTIONS probing) and disable/delete in realtime the
>     registrations
>     which are not responding.
>         The previous approach had two issues when came to so called
>     “zombie”
>     registrations (registrations which are not valid anymore):
>         * resources - such zombie registrations may waste resources in
>     your
>     OpenSIPS server (memory,  processing time, DB space, useless NAT
>     pinging,
>     TCP connect attempts);
>         * user experience - using the zombie registration to reach
>     un-existing
>     users translates into useless calls (calls that will simply timeout),
>     giving delays in the call setup (instead of going straight to VM,
>     you may
>     burn 5-10 seconds in trying to reach the user);
>         The main idea  behind these features is to delete contacts
>     that do not
>     respond to a certain number of SIP pings. The SIP pinging is
>     provided by the
>     nathelper module which was enhanced to keep the state of each
>     pinging requests
>     (basically, the module is waiting and checking the reply of each
>     SIP request
>     sent to the registered users). For registrations detected as
>     “dead” (not responding),
>     the nathelper module interacts directly with the usrloc module in
>     order to
>     remove the zombie contact.
>         For usage perspective, the nathelper module now has two new
>     parameters:
>         * ping_threshold - timeout to consider a ping as unanswered;
>         * max_pings_lost - the number of unresponded pings after which
>     the contact is
>     removed from usrloc;
>         In order to activate this feature, every contact must have the
>     sipping_bflag
>     (to be pinged) and remove_on_timeout_bflag (to be deleted on
>     no-answer) activated.
>     This means these flags must also be configured in the nathelper
>     module. [0]
>         For full documentation of the nathelper module including the
>     newly added
>     feature see [1]. Any feedback is highly appreciated.
>
>     Regards,
>     Ionut Ionita
>
>     [0]http://www.opensips.org/html/docs/modules/2.2.x/nathelper.html#id248011
>     [1]http://www.opensips.org/html/docs/modules/2.2.x/nathelper.html
>     *
>
>     _______________________________________________
>     Users mailing list
>     Users at lists.opensips.org <mailto:Users at lists.opensips.org>
>     http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20160218/743cdc7c/attachment.htm>


More information about the Users mailing list