Hi,
Is it possible for Kamailio to restrict certain users (like in a group) to only receive calls but never dial out or send SIP Simple messages outbound, while allowing all other "regular" users to make outgoing calls and text messages as well as receive them?
If so, which module do you guys recommend I look into?
Cheers, Peter
On Friday 26 June 2015 13:26:05 Peter Villeneuve wrote:
Is it possible for Kamailio to restrict certain users (like in a group) to only receive calls but never dial out or send SIP Simple messages outbound, while allowing all other "regular" users to make outgoing calls and text messages as well as receive them?
Yes (of course)
If so, which module do you guys recommend I look into?
Put a flag in usr_preferences and check for it using avp_db_query (avpops) or sqlops. If flag exists after authenticating an invite: send_reply your favorite appropriate 4xx message.
Thanks Daniel.
I was looking into this option http://nil.uniza.sk/ip-telephony/voip/kamailio-call-establishment-permission-rulesbut your suggestion seems to be cleaner.
Cheers, Peter
On Fri, Jun 26, 2015 at 1:40 PM, Daniel Tryba d.tryba@pocos.nl wrote:
On Friday 26 June 2015 13:26:05 Peter Villeneuve wrote:
Is it possible for Kamailio to restrict certain users (like in a group)
to
only receive calls but never dial out or send SIP Simple messages
outbound,
while allowing all other "regular" users to make outgoing calls and text messages as well as receive them?
Yes (of course)
If so, which module do you guys recommend I look into?
Put a flag in usr_preferences and check for it using avp_db_query (avpops) or sqlops. If flag exists after authenticating an invite: send_reply your favorite appropriate 4xx message.
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 Friday 26 June 2015 14:28:14 Peter Villeneuve wrote:
I was looking into this option http://nil.uniza.sk/ip-telephony/voip/kamailio-call-establishment-permissio n-rulesbut your suggestion seems to be cleaner.
A nice way to accomplish the mission without direct database queries, but if dynamic queries to a db might be a bottleneck for your callflow you might want to store these flags for authenticated users in sht at startup.
But as ever: TIMTOWDI
I use usr_preferences to store barred prefixes for source and destination, the couple of milliseconds it takes to do the lookup are fine by me.