14 May
2007
14 May
'07
4:37 p.m.
Hi,
you can use uri_attrs table/ db_lookup.
into table put:
username 18005551212
did (whatever did is in your domain table)
scheme SIP
name user_alias
value sip:1234567@ourproxy.com
type 2
flags 57
in the config put:
if (load_attrs("$tr","@ruri")) {
#attrs based on request uri loaded
attr2uri("$tr.user_alias");
t_relay();
drop;
}
No RPC call needed for reload, db lookup done per request basis.
Michal
On Po, 2007-05-14 at 08:27 -0400, SIP wrote:
While I'm attempting to redo our SER 0.9.6 config
in SER 2.0, I have a
question concerning migration from an OpenSER 0.9.X module that we user
in our SER config, alias_db.
Currently, all our aliases lookups are done via alias_db. Since we
provision DIDs on the fly via the web, and all our DIDs are E164 format
forwarded to our SER server, it didn't make sense to add in the security
issue of direct server access from the web server to reload the SER
config anytime there was a change to the aliases. Instead, we opted for
having everything in the DB where it should be, and we use the alias_db
module to keep track of our aliases accordingly.
So the question arises... how does one migrate this to the new SER
2.0? I'm still only barely able to grasp the whole concept of Aliases
in the new SER 2.0 stuff, but our current table has information like:
| 18005551212 | ourproxy.com | 1234567 | ourproxy.com |
This gives the alias of 18005551212(a)ourproxy.com a rewrite of
1234567(a)ourproxy.com
Simple enough concept. We add or remove aliases from the DB as
necessary, and never have to touch the running SER server.
So... how does one do this sort of thing now?
N.
_______________________________________________
Serusers mailing list
Serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers