[Serdev] Re: [Sr] RE: ser development

[Jan Janak]

Please use serdev at lists.iptel.org for further discussion, this is the
development list now.

 thanks, Jan.

On 29-01 23:13, Jiri Kuthan wrote:
> Chris,
> 
> first of all thank you for your willingness to help.
> 
> Out of themes which are good to address, management and administration
> is to me undoubtably the most important one. For example, integrating
> SER with webmin would be imho a very useful thing. More comments are
> inline, I will be happy to discuss and align our mutual priorities.
> 
> Also, it would be fair to warn you in advance about all frustrating aspects 
> of working with us ;) ... sometimes, checking in our contributor's code 
> takes long because of our reviewing backlog, modifications we wish to apply, 
> alignment with other ongoing changes, etc, etc.
> 
> 
> At 07:34 PM 1/29/2004, Chris Crawford wrote:
> >New modules or entities
> >1- http - An embedded web server module
> 
> There is already skeleton for such, it is called ihttp. Currently, it is
> not on CVS for some reason, I'm following up on it. The primary piece
> of work to be done is integration with fifo server. Today fifo server is 
> currently the piece of work we have been using to access server internals. 
> It would make sense  to share the exported functionality for both servers. 
> 
> 
> >2- xml - Rather than loading the ser.cfg through a flat text file, load
> >it through an xml file.  
> 
> XML benefits are not compellingly obvious to me.
> 
> A more interesting possibility to me would be embedding a more 
> general-purpose language with lot of extra functionality, say PHP or Perl.
> 
> >3- Create an Install Anywhere (or something else) application that
> >prompts users for configurable settings.  The install also encapsulates
> >the other pieces necessary for the features that they wish to support
> >(e.g. mysql).
> 
> That would be very helpful, but not easy. My personal experience is that
> understanding of what a SIP server should do advances week by week and
> a general-purpose configuration utility is a moving target. We rewrite our
> configuration files every while and we may end up rewriting such a tool
> very frequently as well.
> 
> >Modifications to existing modules:
> >1- When debugging the ser.cfg, we would like to print attribute values.
> >This means a change to the grammar in the yacc/lex code.
> 
> I don't understand this one.
> 
> What would be a really good thing is a gdb-like SER debugger.
> 
> >2- Improve the logging mechanism (TBD)
> 
> What's wrong with xlog?
> 
> >3- I have made some modifications to support calling features.  I will
> >post the changes on the forum later today.  
> 
> ok
> 
> >Questions regarding other items that we (Pannaway) need to address:
> >1- Is someone currently enrolled in developing a SNMP MIB for the ser?
> >We would like to discover this element.
> 
> We put it aside -- there was too little interest in it and the SIP MIB
> as proposed in the IETF is imho not entirely practicable. It is on our CVS
> and it has not been maintained for a while. You would have to revitalize it
> and integrate all related SER internals with it.
> 
> >2- Is someone currently working on developing or enhancing the acc
> >module to support AMA format? 
> 
> what is AMA?
> 
> > We have the spec and wish to enhance it
> >for direct support.   Right now, it seems the module dumps the CDRs to a
> >dbms.  We have thoughts on other ways to deal with CDRs, that our
> >customers would like to see.
> 
> what our ways?
> 
> >3- (part of 2) Is anyone working on supporting IPDRs?
> 
> what is IPDR?
> 
> >Probably not an issue for this board, but, we are using Asterisk for
> >voicemail and IVR support.  SEMS (at least the version I have) only
> >emails the voicemail to the user.  Asterisk allows a user to call into
> >the server.  It would be very nice to have this same functionality with
> >SEMS.  How much work would it be to add this type of functionality?
> 
> There is such a piece of work in SEMS. You can write python scripts to
> process voicemail in the IVR way. It is in a quite early stage -- feel
> free to look at how it meets your expectations and how you can contribute.
> 
> >Finally, we are also developing an Open Source Element Management
> >System.  In addition to managing our equipment, and anything that could
> >be discovered and managed, it will also manage the ser and its
> >components.  Managing includes provisioning and monitoring real-time
> >performance.  It will be available soon.  It's a JBoss web app that will
> >have a skin-able front end, so anyone can use it....
> 
> That sounds interesting. All things related to management and administration
> are IMHO very useful.
> 
> -jiri 
>