Karun,
unfortunately your logic cannot work at all. First of all, it is not clear if changing user identity for user location database makes sense at all. This does not sound like a reasonably secure idea.
Secondly, rewriteuser is used for something else: for rewriting request-URIs and not AOR as stored in To header field. Rewriting To header field is not advisable -- it is used in RFC2543 and RFC3261 for many other purposes.
If you are interested like you say in forwarding user A to user B then provison aliases or user location entries and do not try to change the registration process.
Andy
At 11:47 PM 5/17/2004, Karun Chemudugunta wrote:
REGISTER sip:172.16.12.231 SIP/2.0 From: sip:olduser@bevocal.com To: sip:olduser@bevocal.com Contact: sip:olduser@encamed006:5060;transport=udp;q=1;action=proxy;expires=3600 Call-ID: 12729303125234000@encamed006.bevocal.com CSeq: 12317 REGISTER Content-Length: 0
Hi List,
I was trying to replace user name "olduser" using
rewriteuser("newuser") before saving in user db with save("location") with "newuser", but it it ignoring my rewriteuser("newuser") function in ser.cfg.
I am trying to forward newuser invite to olduser user agent.
Please find attached ser.cfg.
Plz help me to find how to configure ser.cfg to achieve this.
Thanks in advance. Karun
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Andy Blen iptel.org Services