Hello George,
if you have a static mapping from a AoR to an IP address you could also just route this in
the cfg or with another database table (e.g. with a sqlops query). More or less the whole
point of the usrloc/registrar modules is to have people register to your server and then
maintain this mapping.
About the expiration - the easist would be to just enter a value that is in the future.
This is e.g. the default value of the location table: DEFAULT_LOCATION_EXPIRES
"2030-05-28 21:32:15"
Cheers,
Henning
Am 20.09.19 um 15:37 schrieb George Diamantopoulos:
Hello,
Normally I wouldn't be asking this but I was surprised to find no reference to anyone
doing this online. I need to have a few AoRs with static entries in kami's location
table, which will always be reachable at their contacts without ever having to register
with Kamailio.
Am I right in thinking that merely INSERTing respective rows in kamailio's location DB
backend will do the trick? Is there anything I need to worry about, like contacts being
periodically purged? If yes, how do I prevent that from happening? And will kamailio
always query the DB when performing location lookup or do I need to restart upon inserting
new records (to purge caches, for example)?
Lastly, I'm not sure how to treat some fields present in usrloc tables like ruid,
expires (can I set this to NULL?), callid and cseq (which is irrelevant since there's
no REGISTER), flags, cflags and methods.
Thanks,
George
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org<mailto:sr-users@lists.kamailio.org>
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Kamailio Merchandising -
https://skalatan.de/merchandising/
Kamailio services -
https://skalatan.de/services
Henning Westerholt -
https://skalatan.de/blog/