Woof!

On Wed, 12 Aug 2009 15:20:42 -0400, Damian Krzeminski <[email protected]> 
wrote:

> I am fine with sipXsupervisor handling this. (The drawback would be that  
> if
> someone wanted to manipulate v-mail it would have to do that through
> sipXconfig provided APIs.)
Perhaps, or sipXivr provided ones.

>I suggested sipXivr API route since sipXconfig has to be able to read and
> move (write + delete???) voicemail messages (another thing that is  
> achieved by direct file system manipulation at the moment). Which probably  
> requires more changes in sipXsupervisor than allowing for wildcards  
> sipXsupervisor's resource specifications.

Well, there's two distinct issues here.

1.  sipXconfig generating confing files for sipXivr.
  This should use sipXsupervisor for all those files, even the "per user" ones 
in the mailstore directories.  Thus the requirement to support wildcards in 
sipXsupervisor in order to handle per user config files.

2.  User Portal access to voicemail
  This currently uses direct file manipulation of the mailstore directories.  
To remove direct access there are several possibilities:
  2a: NFS mount (or WebDav, SMB, or other remote file system protocol) each 
voicemail server.  Works great, until it doesn't.  Assume this is a non-starter 
(even though it the easiest).

  2b: Create a REST api 'tween the User Portal and sipXivr to do whatever 
voicemail manipulation is required.  This has good potential to be used as a 
third party API for voicemail access too.  Lots of User Portal changes to 
support this, lots of sipXivr work to support this.

  2c: Move the "user portal" code from the sipXconfig JVM into the sipXivr JVM, 
where it can continue to have direct access.  sipXconfig needs to somehow cross 
site the requests.  I don't have a clue if this makes sense or not.

--Woof!


_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to