I wish to know how I can have two kinds of users 1. some users with real time integration with asterisk 2. other users do not
How can I achieve in the same kamailio instance?
On Thursday 18 June 2015 17:52:46 asterisk asterisk wrote:
I wish to know how I can have two kinds of users
- some users with real time integration with asterisk
- other users do not
How can I achieve in the same kamailio instance?
save/lookup and auth methods all have an argument to change the database table used. So if your other users are in a different table it should be pretty straight forward.
Could you show me some tutorials or reference websites?
Thanks
Sent from my iPhone
On 18 Jun, 2015, at 6:31 pm, Daniel Tryba d.tryba@pocos.nl wrote:
On Thursday 18 June 2015 17:52:46 asterisk asterisk wrote: I wish to know how I can have two kinds of users
- some users with real time integration with asterisk
- other users do not
How can I achieve in the same kamailio instance?
save/lookup and auth methods all have an argument to change the database table used. So if your other users are in a different table it should be pretty straight forward.
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
On Thursday 18 June 2015 22:35:11 Asterisk wrote:
Could you show me some tutorials or reference websites?
It depends on your setup, but most likely you can do this source based, something like this:
route[AUTHENTICATE] { if($si=asteriskip) { if (!www_authenticate("$td", "asteriskrttable")) { www_challenge("$td", "1"); } } else { if (!www_authenticate("$td", "othertable")) { www_challenge("$td", "1"); } } }
route[LOCATION] { if (!lookup("asteriskrtlocation") && !lookup("otherlocation")) { ... } }
route[REGISTER] { if($si=asteriskip) { save("asteriskrtlocation"); } else { save("otherlocation"); } }