(For the implemenation of such a feature: hwo to you
want to manage all
the
passwords, accounts, etc. at the server.. sounds
horrible to me.)
I really don't think there is much think to be stored for a
single user.
Username: password: proxy: portno:
Which is not really tough though as by the SER DB modules.
A little analogy: would you tell you SMTP server how
it can fetch the mail
from you several mail accounts? I guess not.
Either you use a MAU which can handle several accounts. Or you use
forwardings, to collect all your mails at one central account.
If my remote
SMTP server is not forwarding the email address, then If
I receive a trigger that a email is received on that account, I can POP and
send it again to my local SMTP server. I think there is an acceptable logic
in this.
With respect to the Registration I think only the "REGISTER" sip
message need to be to send to the register module, rest of the call
sequences we can make to handle by SER. right?
Regards,
Kannaiyan
> Asterisk needs a loads of changes to have the
same implementation
compared
to SER.
:-)
Regards
Nils
Kannaiyan
----- Original Message -----
From: "Olle E. Johansson" <oej(a)edvina.net>
To: "Jan Janak" <jan(a)iptel.org>
Cc: <serusers(a)lists.iptel.org>
Sent: Friday, January 09, 2004 7:41 PM
Subject: Re: [Serusers] REGISTER implementation --
Jan Janak wrote:
What does that mean ? Do you want ser to be able
to send a REGISTER
message to another server ? If so then there is nobody implementing
this.
And I can't really understand why a SIP proxy should.
SER is a very good SIP proxy. A proxy sets up calls, doesn't terminate
them. Asterisk is not a SIP proxy, but a good PBX that can originate
and terminate calls, both as a SIP UA Client and a SIP UA Server.
/O
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers