[Serusers] ser features

[Dragos Vingarzan]

Hi Peter!
  
    I can answer to 1 as I have implemented the ISC. The ISC, as I see 
it, it's very much SIP compliant. And well, to put it simple, it works.
Now about whether ser was "developed with this is mind", ser is out for 
quite some time and I don't really think that anyone thought about 
adapting the core for ISC, nor it is needed as ISC is basically standard 
SIP and any S-CSCF implementation should be able to communicate with any 
AS implementation out there, provided that they both "speak" 
standard-SIP as they should.

P.S. By ISC I understand just the communication betweent he S-CSCF and 
the AS. Controlling it by means of Initial Filter Criteria is another 
thing and gets a little more complicated, but can be resolved by a ser 
module.
   
peter.3.edwards at bt.com wrote:

>Hi,
> 
>Being one of those who tend towards open source, I'm trying to put forward ser for use within my current project as, from my reading, it seems to have most of the features I think we're going to need.  Problem is, before I've had a chance to get it in and play with it, there's a paper sift going on which may see it being shelved before I get a chance to even propose it.  :(
> 
>I realise it's entirely unforgivable, netiquette-wise, but I was hoping if I posted the list of criteria I was looking at whether someone could help confirm or deny what I've cobbled together wrt ser.  Any links to more information on the web would be ideal.
> 
>Any help at all would be gratefully received!
> 
>Many thanks,
> 
>Peter.
> 
>1) Support for SIP - (preferably 3GPP ISC interface)
>    - Obviously SIP is supported but I can't see any explicit mention in the docs wrt to 3GPP ISC .. ?  Has ser been developed with this in mind?
> 
>2) Provide flexible application run time support in terms of standard / well-defined API sets such as SIP servlets
>    - As ser is written in C, it's obviously not exposing SIP servlets internally, but I can't seem to find a specific API specificiation.  I think it sounds like applications are created as C modules which plug into ser.  Is that right (I'm not a C developer, so any clarification appreciated)?  Is it a ser-properietary interface or something that follows a particular standard?
> 
>3) support carrier grade non functional requirements e.g. %age availability, multi-site installation, latency, throughputs etc.
>   - I can't see any specific claims for reliability, or any info on how to deal with redundancy etc.  Has this been looked at before?
> 
>4) Any interfaces that can be exposed to application logic hosted on a remote platform in an untrusted environment - e.g. a Java RMI, Web Services etc.
>   - Does ser expose anything else, other than SIP?  How would a third party application running on, let's say for argument's sake, a J2EE application running on a separate JBoss server?  Would a C module need to be written and plugged into ser to expose, say web services?  Has anything like that been done already?
> 
>5) Application Developer support / tools
>   - Is there anything like a forum or tools to aid a module developer?
> 
>6) OSS integration
>   - Is there any?
>  
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Serusers mailing list
>serusers at lists.iptel.org
>http://lists.iptel.org/mailman/listinfo/serusers
>  
>

-- 
-----------------------------------------
Dragos Vingarzan
FOKUS/MOBIS
Kaiserin-Augusta-Allee 31
10589 Berlin,Germany
Phone +49 (0)30 - 3463 - 7242
Mobile +49 (0)162 - 153 - 0154
eMail vingarzan at fokus.fraunhofer.de
Web www.fokus.fraunhofer.de
Computers are not intelligent. They only think they are.
-------------------------------------------------------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20050207/37dd03d2/attachment.htm>