18 Dec
2003
18 Dec
'03
11:48 p.m.
At 05:28 PM 12/18/2003, Hernandez, Cesar wrote:
Sure, but this may not be possible if some sort of authentication is
required. Isn't this better handle on the SIP proxy server?
Both is possible, I just happen to like end-device-driven identity
better. The architectureal principal which applies is the end-to-end
principle, which advices to leave burden away from network. One
could introduce network-driven anonymization, but that would take
a b2bua, i.e., more software to buy and maintain, more scalability
issues (session state must be remembered), etc.
Is caller blocking system wide or configurable per user?
System-wide.
Don't the SIP proxy needs to support the SIP REDIR too?
Redirection is a different feature from call transer. Redirection
divers call to be set up. Call transfer diverts established call.
Redirection is implementd using 3xx reply classes in SIP which we
support. Transfer is implemented using the REFER method, which does
not need to be understood by proxy server. It is just relayed as any
other method is.
Is there software already available or are you just saying that this will
need to be developed as separate software?
It is available under a commercial license.
Again is there some software developed for SER or are you thinking about
clustering software and/or making usage of DNS SRV resource records which
will provide some kind of redundancy?
Likewise. DNS/SRV is only one part of the picture -- state replication
is the other part.
-jiri
* Private number (permanent Caller-ID blocking):
A way I do maintain privacy is I use a stupid user id
(You certainly know how much identity is dislocsed if you
send from mr_goerge_w_bush(a)hotmail.com....) * Caller blocking:
Yes -- we block requests from
source causing annoying traffic. * Call Transfer:
phone feature * Support for call time limit:
call-limitation is
part of separate software * Redundant server configuration:
available as
separate software