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?
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@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.
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?
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?
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?
- 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?
- Application Developer support / tools
- Is there anything like a forum or tools to aid a module developer?
- OSS integration
- Is there any?
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
On 07-02 00:09, peter.3.edwards@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.
- 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?
SIP yes, 3GPP ISC no.
- 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?
There is nothing comparable to SIP Servlets, SER is not a servlet container, but a SIP message mangler with the possibility to keep transaction state.
SER modules are written in C and can access SER internals directly. Each module can export function that the administrator can then call in the configuration file.
There is no particular standard for this, it is very similar to the Apache module API.
- 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?
Yes, high availability extensions are available under comercial license from iptel.org.
- 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.
No.
- 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?
No, that is not possible. SER is not an application server, it is a sip proxy.
- Application Developer support / tools
- Is there anything like a forum or tools to aid a module developer?
The C sources and SER developers guide describing the API.
http://iptel.org/ser/devel.html
- OSS integration
- Is there any?
No.
Jan.
-
Dragos Vingarzan -
Jan Janak -
peter.3.edwards＠bt.com