I setup kamailio to forward REGISTER packets using dispatcher to two servers main and backup.
The routing logic is quite simple i use the dispatcher probing mechanism to detect if my main dispatcher set id (one server) is active or inactive once it detect a failure all packets are sent to secondary SIP server to achieve High Availability.
I am looking for module or a way to save into kamailio database client information such as IP address, register username (from FROM header), digest username (authorization username), call-id for successful registration.
I tried to use registrar module but once i used function save("location") the client was registered on kamailio and packets was not forwarded to main/secondary SIP server (like dispatcher stopped working, the destination did not override).
REGISTER is sent to SIP URI of kamailio.
Please let me know if you have any idea how to make this data update in database (insert an entry on fresh successfull REGISTER, delete on expired or removed binding).
Best regards, Tomasz
Hello,
Do you want to store them in terms of "active registration"? or simply a list of registers, as in adding to a table?
Adding to a table is simple enough, use https://kamailio.org/docs/modules/4.0.x/modules/sqlops.html
Regards,
David Villasmil email: david.villasmil.work@gmail.com phone: +34669448337
On Thu, Nov 14, 2019 at 8:40 PM Voip support voipexpert0@gmail.com wrote:
I setup kamailio to forward REGISTER packets using dispatcher to two servers main and backup.
The routing logic is quite simple i use the dispatcher probing mechanism to detect if my main dispatcher set id (one server) is active or inactive once it detect a failure all packets are sent to secondary SIP server to achieve High Availability.
I am looking for module or a way to save into kamailio database client information such as IP address, register username (from FROM header), digest username (authorization username), call-id for successful registration.
I tried to use registrar module but once i used function save("location") the client was registered on kamailio and packets was not forwarded to main/secondary SIP server (like dispatcher stopped working, the destination did not override).
REGISTER is sent to SIP URI of kamailio.
Please let me know if you have any idea how to make this data update in database (insert an entry on fresh successfull REGISTER, delete on expired or removed binding).
Best regards, Tomasz
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
you can change that link for whatever version you're using.
Regards,
David Villasmil email: david.villasmil.work@gmail.com phone: +34669448337
On Thu, Nov 14, 2019 at 10:28 PM David Villasmil < david.villasmil.work@gmail.com> wrote:
Hello,
Do you want to store them in terms of "active registration"? or simply a list of registers, as in adding to a table?
Adding to a table is simple enough, use https://kamailio.org/docs/modules/4.0.x/modules/sqlops.html
Regards,
David Villasmil email: david.villasmil.work@gmail.com phone: +34669448337
On Thu, Nov 14, 2019 at 8:40 PM Voip support voipexpert0@gmail.com wrote:
I setup kamailio to forward REGISTER packets using dispatcher to two servers main and backup.
The routing logic is quite simple i use the dispatcher probing mechanism to detect if my main dispatcher set id (one server) is active or inactive once it detect a failure all packets are sent to secondary SIP server to achieve High Availability.
I am looking for module or a way to save into kamailio database client information such as IP address, register username (from FROM header), digest username (authorization username), call-id for successful registration.
I tried to use registrar module but once i used function save("location") the client was registered on kamailio and packets was not forwarded to main/secondary SIP server (like dispatcher stopped working, the destination did not override).
REGISTER is sent to SIP URI of kamailio.
Please let me know if you have any idea how to make this data update in database (insert an entry on fresh successfull REGISTER, delete on expired or removed binding).
Best regards, Tomasz
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Try to use save() when you process the 200 ok reply for REGISTER in the reply route.
Regards, Ovidiu Sas
On Thu, Nov 14, 2019 at 3:40 PM Voip support voipexpert0@gmail.com wrote:
I setup kamailio to forward REGISTER packets using dispatcher to two servers main and backup.
The routing logic is quite simple i use the dispatcher probing mechanism to detect if my main dispatcher set id (one server) is active or inactive once it detect a failure all packets are sent to secondary SIP server to achieve High Availability.
I am looking for module or a way to save into kamailio database client information such as IP address, register username (from FROM header), digest username (authorization username), call-id for successful registration.
I tried to use registrar module but once i used function save("location") the client was registered on kamailio and packets was not forwarded to main/secondary SIP server (like dispatcher stopped working, the destination did not override).
REGISTER is sent to SIP URI of kamailio.
Please let me know if you have any idea how to make this data update in database (insert an entry on fresh successfull REGISTER, delete on expired or removed binding).
Best regards, Tomasz
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Hello,
if you want to just forward a message to a second server, have a look to the “t_replicate” function in the tm module.
Cheers,
Henning
-- Henning Westerholt – https://skalatan.de/blog/ Kamailio services – https://gilawa.comhttps://gilawa.com/ Kamailio Merchandising – https://skalatan.de/merchandising
From: sr-users sr-users-bounces@lists.kamailio.org On Behalf Of Voip support Sent: Thursday, November 14, 2019 9:36 PM To: sr-users@lists.kamailio.org Subject: [SR-Users] Saving REGISTER status in kamailio database while REGSITER packets are forwarded.
I setup kamailio to forward REGISTER packets using dispatcher to two servers main and backup.
The routing logic is quite simple i use the dispatcher probing mechanism to detect if my main dispatcher set id (one server) is active or inactive once it detect a failure all packets are sent to secondary SIP server to achieve High Availability.
I am looking for module or a way to save into kamailio database client information such as IP address, register username (from FROM header), digest username (authorization username), call-id for successful registration.
I tried to use registrar module but once i used function save("location") the client was registered on kamailio and packets was not forwarded to main/secondary SIP server (like dispatcher stopped working, the destination did not override).
REGISTER is sent to SIP URI of kamailio.
Please let me know if you have any idea how to make this data update in database (insert an entry on fresh successfull REGISTER, delete on expired or removed binding).
Best regards, Tomasz
Hello Tomasz,
In the past when I had to implement something similar, I found these to guides very helpful:
https://kb.asipto.com/asterisk:realtime:kamailio-4.0.x-asterisk-11.3.0-astdb https://blog.opensips.org/2016/12/13/how-to-proxy-sip-registrations/
I believe your scenario is very similar as described in the second link, and although it's written for opensips, you can use it perfectly well with Kamailio (in fact, that's what I did).
Hope it helps! Joel.
On Fri, Nov 15, 2019 at 11:30 AM Henning Westerholt hw@skalatan.de wrote:
Hello,
if you want to just forward a message to a second server, have a look to the “t_replicate” function in the tm module.
Cheers,
Henning
--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com
Kamailio Merchandising – https://skalatan.de/merchandising
*From:* sr-users sr-users-bounces@lists.kamailio.org *On Behalf Of *Voip support *Sent:* Thursday, November 14, 2019 9:36 PM *To:* sr-users@lists.kamailio.org *Subject:* [SR-Users] Saving REGISTER status in kamailio database while REGSITER packets are forwarded.
I setup kamailio to forward REGISTER packets using dispatcher to two servers main and backup.
The routing logic is quite simple i use the dispatcher probing mechanism to detect if my main dispatcher set id (one server) is active or inactive once it detect a failure all packets are sent to secondary SIP server to achieve High Availability.
I am looking for module or a way to save into kamailio database client information such as IP address, register username (from FROM header), digest username (authorization username), call-id for successful registration.
I tried to use registrar module but once i used function save("location") the client was registered on kamailio and packets was not forwarded to main/secondary SIP server (like dispatcher stopped working, the destination did not override).
REGISTER is sent to SIP URI of kamailio.
Please let me know if you have any idea how to make this data update in database (insert an entry on fresh successfull REGISTER, delete on expired or removed binding).
Best regards, Tomasz
Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-
David Villasmil -
Henning Westerholt -
Joel Serrano -
Ovidiu Sas -
Voip support