Terrific, thanks. that was the final piece of the puzzle. now SER authenticates REGISTERS and INVITES correctly, and clients with bogus usernames/passwds are denied. thank you very much.
scott t DSi
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Friday, March 19, 2004 2:47 pm To: Ticknor, Scott: DGSE Cc: serusers@lists.iptel.org Subject: Re: [Serusers] authentication recommnedations
is_local uses the domain module from ser. This module checks domains against the domain table fo the ser database. Therefore, you have to insert the domains ser is responsible for (e.g. my.sip.domain) into the "domain" table in the mysql database from ser.
Klaus
Ticknor.Scott@ic.gc.ca wrote:
-----Original Message----- From: Klaus Darilion [mailto:klaus.mailinglists@pernau.at] Sent: Thursday, March 18, 2004 12:48 pm To: Ticknor, Scott: DGSE Cc: serusers@lists.iptel.org Subject: Re: [Serusers] authentication recommnedations
Hi!
I use this setup:
if (is_from_local() ) { if (!proxy_authorize("", "subscriber"))
sorry to keep beating this up... i am trying this logic out, but the debug messages show:
is_local(): Realm 'my.sip.domain' is not local is_local(): Realm 'X.X.X.X' is not local
is this an error in the database configuration, or is there
somewhere else
to configure local?? i found this via google:
if (RES_ROW_N(res) == 0) { DBG("is_local(): Realm '%.*s' is not local\n", _host->len, ZSW(_host->s)); db_free_query(db_handle, res); return -1;
thanks,
scott t DSi
-
Ticknor.Scott＠ic.gc.ca