Notes from SEMSi [1] users meeting at VON Europe fall 2006
keywords:
 + SEMS and *
 + SERi [2] - SEMS
 + Performance
 + Python/IVRi [3]
 + wishlist



SEMS and *: 
  - why have two F/OSS media servers? 
      -> * is PBXi [4] and feature for everything 
      -> SEMS for high call count and simple functionality
  - have * tell SEMS to send RTPi [5] streams using a midcom-like 
    protocol (similar to mgcp) would enable a */SEMS combination
    to handle a lot more calls

SER - SEMS: 
  - Bogdan Pintea presented the idea behind new SER-external 
    application interface
  - expected: * performance improvement
              * more flexible: new callflows possible
                e.g. sending ACK with SDPi [6] answer from SEMS
              * eases configuration: SEMS tells SER which data 
                it expects
Performance:
  - failures/timeouts on unix socket observed with high throughput 
    (Alexandr)
  - ports not freed? (-> bug tracker, Alexandr)
  - FR: preencoded announcements (also: licensing, Bayan)
  - user vs. kernel space: 

IVR/Python:
  - the name 'IVR' misleading: its actually powerful scripting system
  - future: * 'ivr' module with simple, clear defined API 
              (current 'ivr')
            * 'scripting' ('pysems') module with generated wrappers
              exporting all framework functionality (pysip branchi [7] ivr)
  - python application repositoryi [8] on web-site and SVN needed
  - atle & bayan write python app that executes ivr menu read 
    from db 

wishlist:
  - video (->licensing?)
  - T.38 fax
  - dialout documented
  - SIP stack as module in SEMS (->independent from SER)